mbfinotti/advertising-skills / skills/advertising-career
advertising-career
VerifiedPlan and advance a paid-advertising career from the candidate side - media buyer, performance marketer, PPC specialist, creative strategist, growth marketer - covering the junior to lead ladder, the five real interview formats (live account audit, mental-maths case, metric diagnosis, take-home, behavioural), an NDA-safe results portfolio, platform certifications, in-house vs agency vs freelance, and promotion and pay conversations. Use whenever the user asks how to get into paid media or PPC, preps a media-buyer or growth interview, wants an ad portfolio, or weighs an agency vs in-house move - even if they never say 'career'. Do NOT use for the employer side of hiring - use mbfinotti/advertising-skills@advertising-hiring instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 35.9 KB |
| evals/evals.json | config | 41.1 KB |
| references/anonymised-case-study-example.md | markdown | 3.7 KB |
| references/interview-question-bank.md | markdown | 21.0 KB |
| references/promotion-case-one-pager.md | markdown | 3.0 KB |
references/promotion-case-one-pager.md
View on GitHub# Promotion-case one-pager
The ladder pays for accountability, not time served: cases citing owned revenue or P&L impact succeed; cases citing tenure, hours, campaign counts, or effort fail. Scope creep is the modal experience - Marketing Week's 2026 Career & Salary Survey (2,350 respondents) found 51.2% of marketers saw their remit grow without matching pay - which makes it a legitimate lever, but only once converted into an owned-number argument.
Every figure in the one-pager is the candidate's own evidence; market anchors carry source, date, and grade (survey vs aggregate). An undated or last-year anchor in a declining market damages credibility.
## Template
```
# Case for [target title], [name], [date]
## What I own now that I didn't at [start of period]
- [Scope item 1: e.g. budget/forecast responsibility for X accounts / £Y band]
- [Scope item 2: e.g. measurement ownership - tracking, attribution, first
incrementality test]
- [Scope item 3: e.g. QA or mentoring of N juniors]
## What the owned number did
[1-3 lines: the revenue, pipeline, contribution, or efficiency number you are
accountable for, and its movement over the period - your own evidence,
indexed if the absolute figure is confidential internally.]
## Evidence against the next rung's screen
[Map each item above to what the next level is screened for: forecasts and
budgets, C-level narrative, cross-channel allocation, incrementality - cite
the internal ladder or a real JD for the target title.]
## Market anchor
[Target-title range, with currency, source, date, and grade. State the grade
out loud: "survey-grade" or "aggregate estimate, treat as a range".]
## The ask
[Title, band, and timing. One sentence.]
```
## Positive example (shape)
"Since January I have owned the paid-media budget and quarterly forecast for our three largest accounts - responsibility that sat with my director a year ago - and ran our first geo-holdout test, which changed how we allocate between search and social. The number I'm accountable for is [owned metric and its movement]. That maps to the senior screen - forecast ownership, measurement depth, portfolio economics. The 3Search 2025 survey (1,300+ responses) puts UK PPC Managers at £50,000-£70,000; I'm asking for [band] effective [date]."
Why it works:
- Every claim is an owned scope item or an owned number.
- The evidence is mapped to the next rung's documented screen.
- The anchor is dated and graded.
## Negative example
"I've been here four years, I've never missed a deadline, I ran over 200 campaigns this year and regularly stay late during launches. Everyone else at my level has been promoted. I'd like the senior title."
Why it fails:
- Four years is tenure, not evidence.
- 200 campaigns and late nights are activity, not evidence.
- Peer comparison is not evidence.
- Nothing maps to what senior is screened for: no owned budget, no forecast, no number.
This case reads as a request for recognition, not a demonstration of accountability, and it fails even when the underlying work was genuinely strong.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |