Skip to content

mbfinotti/advertising-skills / skills/advertising-hiring

advertising-hiring

Verified

Build the complete hiring packet for a paid-advertising role - the rung decision (media buyer vs performance marketer vs growth marketer; creative strategist is its own role), an outcome scorecard, a 2-3 round interview loop with a judgment-first question bank, a time-boxed in-interview work sample, and a 30-60-90 ramp with staged spend authority. For the marketing leader or founder recruiting. Use for "hire a media buyer", "interview questions for a performance marketer", "paid media work sample", "scorecard for our first ad hire", or "30-60-90 for a new paid media hire". Does not source candidates, post jobs, run applicant tracking, or write offers, and does not cover the candidate side - that is the sibling mbfinotti/advertising-skills@advertising-career.

references/ramp-and-spend-authority.md

View on GitHub
# Ramp and Spend-Authority Staging

Build the ramp with all access on day one, an explicit spend-approval threshold in week one, and a staged authority ladder. The two anchor rules below come from a named source; the spend-authority ladder and the milestone skeleton are a synthesis drawn from general 30-60-90 frameworks and paid-media onboarding guidance, not a named source. Label the ladder and milestones as synthesis in every deliverable produced.

## The two rules with a named source

eCommerce Placement is the most concrete published source on paid-media onboarding:

- **Access on day one, not on request.** "Give access to every tool on day one, not on request. Delayed access is one of the most common, and most avoidable, causes of a slow start."
- **Spend-approval threshold in week one.** "Set a clear ad spend approval threshold in week one so the new hire isn't guessing what they can act on independently."

And the constraint governing the whole first month: "Don't ask a new growth leader to commit to a CAC or LTV target before they've validated your attribution setup... Budget real time in the first 30 days for a measurement audit before promising performance improvements you can't yet verify."

## Week-one access checklist

Grant every one of these on day one, tracked as a table (tool / access level / granted):

- Every ad platform account the company runs.
- The web-analytics property.
- The tag manager.
- The commerce or CRM backend.
- The BI/reporting layer.
- For app advertisers, the mobile measurement partner.

## The spend-authority ladder

- **Weeks 1-2 - shadow.** Observe, ask, audit; no changes. The general 30-60-90 framing: "shadowing, asking questions... not trying to fix things yet."
- **Weeks 3-6 - co-sign.** Changes go live with a second signature, or independently under a small explicit cap.
- **By day 60 - independent within a cap.** The cap is a number written in the packet, not a vibe.
- **By day 90 - full authority**, contingent on a validated measurement audit. No audit, no full authority.

The realistic first win is a tracking fix or a contained optimization, never a scaling bet - attribution validation must precede any performance commitment.

## Milestones per rung

| Rung                 | Day 30                                                                        | Day 60                                                         | Day 90                                                                 |
| -------------------- | ----------------------------------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Media buyer          | Account audit delivered, first co-signed optimizations live                   | Owns pacing and optimization within cap                        | Full channel ownership with a weekly reporting cadence the team trusts |
| Performance marketer | Measurement audit complete, platform-versus-backend reconciliation documented | Creative-testing cadence running, first contained wins shipped | Owns blended targets against validated numbers                         |
| Creative strategist  | Creative performance audit and first brief batch                              | Testing pipeline live with win/loss documentation              | Owns creative win-rate reporting and the brief backlog                 |

End every ramp with watch areas - the early signals this specific hire is struggling - as a distinct section from the goals.

## Two domain constraints that bound any milestone

- Channel verdicts take time: run "at least 3-6 months before concluding whether or not [a channel] is for you" (AJ Wilcox). An organization unwilling to wait that long will also fire the hire before the ramp completes - surface this at scoping time.
- Platform learning phases and statistical power mean a new hire's first tests often cannot resolve inside 30 days regardless of skill. Do not write a day-30 milestone that requires a resolved experiment.

## Churn: the numbers and the attribution rule

Quote turnover as a range with named sources, never as a single industry rate.

Primary figures:

- Media-only agency client-relationship tenure averages 3.7 years, versus 7.3 years for integrated full-service agencies (ANA/4As AOR tenure study, released April 30, 2025).
- UK member-agency staff turnover: 26.8% (IPA, 2021).
- Sampled-agency average: 18-20% (Campaign US Agency Performance Review, 2025).
- Industry average around 30% (ANA, via Adweek).

Secondary aggregations, labelled as secondary:

- "22% of new agency hires leave within the first 45 days," and junior agency turnover "nearly 45% in their first two years" (The Trust Agency).
- Replacement cost "up to four times the position's salary" (SHRM figure via NetSuite).

The honest statement: turnover runs 18-45% depending on source, cohort, and year.

The attribution rule: when early-tenure churn appears in the first 45-90 days, the evidence points at scoping and onboarding - access delays and unclear spend thresholds - not at the candidate. Fix the ramp before blaming the hire.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall