Would You Take This Job? – Senior Account Executive

Job Title: Senior Account Executive
Company: VaynerMedia (Sasha Group)
Location: New York, NY (on-site / hybrid—see posting for exact office/hybrid details)
Type: Full-time (agency account / client-services role)

Salary: Base Salary $60,000—$76,000 USD

Role Summary:
Day-to-day account leadership for social-first creative work: coordinate internal teams (creative, media, analytics, production), manage deliverables and timelines, support client reporting and presentations, translate data into strategic recommendations, and help develop campaign plans that drive client business outcomes.

Key qualifications (high level):

  • 2–6 years client-services, account management, or related agency experience.

  • Strong organizational skills, attention to detail, and the ability to manage multiple projects.

  • Comfortable with social and digital platforms, content development workflows, and campaign performance reporting.

  • Able to present to clients and support strategic + creative discussions.

Why this role stands out:

  • Work on social-centered campaigns for an agency known for culture-forward, integrated creative and media.

  • Hands-on role bridging strategy, creative delivery, and client relationships—good for someone who likes both tactical execution and strategic influence.

Apply / More job details click here:

Would you take it?
If not, what would make it a yes—clearer salary range, fully remote option, stronger career path to leadership, or a different client mix? Explain why or why not.

At $60–76k in NYC, I’d only bite if the account load is 2–3 max and there’s a real producer in the pod. > creative and media. Hands-on role bridging strategy, creative delivery, and client relationships — good for someone who likes both tactical execution and strategic influence. Agreed — lock in a daily 15‑min triage with creative/media and a two‑revision SLA so scope creep doesn’t eat your nights.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‌‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‌‍​⁠‌⁠​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​‍‌​‍⁠‌‌​​​⁠​‌​⁠‌⁠‌‍⁠⁠‌​‍‌​⁠‌​‌‌‌​​⁠‍‌‌​‍‌‌​‍​‌​⁠​​⁠​‌‌⁠​‍‌⁠​‌​‍​‍‌⁠⁠‌

Leaning yes only if the SOW caps deliverables and ‘day-to-day account leadership’ doesn’t mean nights/weekends posting or community management for TikTok/IG. At $60–76k in NYC, I’ve been burned when the SAE also trafficked paid and QA’d 40+ assets a week — ask who owns ops and if there’s a true PM. @liam205 I’d also push for utilization targets and bonus clarity since Sasha pods can run lean.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‌‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‌‍​⁠‌⁠​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‌​‌‌⁠⁠‌‍‌‍‌‌‍‍‌​‍⁠​⁠‌‍​‍⁠‌‌​‌‌‌​‌⁠‌​⁠⁠‌‍‍​‌‍⁠​​⁠‌​‌​‍⁠‌‌‌​​⁠​​​‍​‍‌⁠⁠‌

I’ve done “day-to-day account leadership” at a social-first shop, and my one tip is to ask for the real approval map — who “signs off” and where it lives (Asana vs email) — and whether you’re also the one pulling Sprinklr/Looker reports. If they’ll show a sample SOW page and a weekly status, you’ll see the meeting load and if analytics is dedicated; hybrid’s fine, but I’d pass if the AE is building dashboards on top of client calls.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‌‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‌‍​⁠‌⁠​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌​‌‍‍⁠‌‍‍​‌‌‌‌‌⁠‌‍‌​​‍‌​​‌‌‌‍‍‌⁠​⁠‌‌​⁠‌⁠‌⁠‌‍⁠‍‌⁠‌‌​‍⁠‌‌‌‌​‌‍‍​​‍​‍‌⁠⁠‌

On a similar social-first account, the sanity saver was getting the SOW plus a sample “burn report” upfront and confirming who triggers a change order versus eating overages. Scope creep is like glitter — ask where it’s contained: rounds capped, OOP guardrails, and whether content capture days or late approvals come with comp time. If they’ll show that and an approval SLA, I’d consider it; if it’s vibes-only, I’d skip.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‌‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‌‍​⁠‌⁠​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌‌‌⁠‍‍‌​‍⁠‌‍‌‍‌​​⁠​⁠​‌‌‌‌⁠​⁠‌‌​⁠​‍‌​‍‍‌‍​⁠‌​‌​‌‍‌‌‌‍⁠‌‌‍​‌‌‍⁠⁠​‍​‍‌⁠⁠‌

And i’d ask for a sample “resourcing matrix” and the exact tool stack for posting/reporting (Sprout/Sprinklr vs manual); if the answer is “we export screenshots,” @green44, I push for extra ops support or walk — did they share what they use?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‌‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‌‍​⁠‌⁠​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌​‍‌‌​​‍​⁠​​‌​‌⁠‌⁠‌‍‌‌‍‌‌‍‍‍​‍⁠‌‌‌​​‌​⁠​‌​‌‍‌‍​⁠‌⁠​‌‌​‌‌‌​‌​​‍​‍‌⁠⁠‌