Let’s Roast.

A job posting that tries to hire an entire operations department in one human is always “exciting”… right up until you’re the one triaging edge cases at 9:47 p.m. Jen and Paul roast a Chief of Staff / Client Ops role that’s stuffed with scope, vibe, and moral pressure—then translate what it really means for candidates and founders.

Follow along with the full job ad here :

VIEW DOCUMENT

The Bigger Picture

How do you design an operations role that actually scales a portfolio of startups, without turning “flexibility” into permanent cognitive overload? The real problem here isn’t tone or length; it’s role definition, boundaries, and the operating model the post quietly admits the company is using.

Note : we talk about reference checks in this episode—a great background piece is Jen’s essay on them over at Uncompliant :

Uncompliant

Reference Checks Are Useless

Last week, I posted the following on LinkedIn…

a year ago · 14 likes · 15 comments · Jennifer Houle

At a Glance: The Job Profile

Job Title: Chief of Staff (Client Operations)
Report-to Title: Unknown
Company Size: 11-50
Industry: Operations Consulting
What do they do?: Startup operations platform and service that handles back-office functions like HR, finance, compliance, payroll, and equity so founders can outsource administrative work and focus on growing their business.
Head Office Location: Beaverton, Oregon, United States
Job Location: Fully Remote - Canada
Geographical Operating Area: U.S.
Job Type: Full-Time / Permanent

For the Job Seekers

Did you come across a job ad like this? These questions might help you shed some light on what working there is really like:

When a post says “context switching,” what’s the underlying system: structured priorities, or constant interruption?
What does “owning delivery” mean here… outcomes you control, or accountability for everything that breaks?
How many clients at once, and what’s the expected weekly cadence (calls, async updates, reporting)?
What’s the escalation path when a founder is wrong, unrealistic, or changing priorities daily?
What are the actual performance metrics tied to “pay and promote based on performance”?
“No negotiation” aside: what’s the pay band by level, and what triggers movement within it?
What’s the split between tactical work (taxes, NDAs, offboarding) and strategic advising (comp benchmarks)?
Do you have authority to say no, or just the requirement to “say no without it feeling like no”?

For the Job-Seeker Seekers

Are you writing a job ad for a similar role? Consider these hidden issues that might impact the success of your recruitment campaign:

Problem: The role is framed as hero-work (“unsung hero,” “dumping ground,” “we revel in it”). Outcome: You’ll attract saviours and burn them out, or repel strong operators who want sane boundaries. Fix: Define scope by category (finance, compliance, PM), define what’s explicitly out of scope, and publish escalation rules.
Problem: Title/level ambiguity (“Chief of Staff,” “Client Ops Manager,” “fractional COO”). Outcome: Misaligned candidates, comp disputes, and messy expectations with clients. Fix: Pick one primary identity, then list the adjacent hats as occasional responsibilities (not core).
Problem: Heavy reliance on “context switching” as a core competency. Outcome: Quality drops, errors rise, client trust erodes… especially in compliance/finance work. Fix: Build an intake + triage system, cap concurrent work-in-progress, and define response SLAs by priority.
Problem: “We don’t negotiate” paired with “pay based on performance” without publishing the metrics. Outcome: Candidates assume opacity; high performers self-select out; perceived bias risk increases. Fix: Publish clear levelling, measurable success criteria, and sample promotion timelines.
Problem: Five interviews + four manager references is a lot for an $80k base role. Outcome: Drop-off from top candidates; hiring pipeline slows; signals distrust. Fix: Reduce steps or make them lighter; use work-sample + one structured panel; references only at finalist stage.

The Verdict

Closure + brand consistency (reinforce the “game show” undertone of the format).

Paul Austin-Menear: 3.5 / 10

It was unclear what the person will actually be doing. There was structural, systemic risk in the way that the role was designed. We don’t know if we’re going to be interviewed by one of the clients or by another person in the organization. There’s five interviews. There’s a bunch of benefits that are wrapped in very showy, flowery language to try and make them more than what they actually are in terms of real value to the employee. The potential value of equity grants is very uncertain—if it’s equity in the agency, that’ll be practically worthless. Agencies don’t accumulate capital value like companies that produce monetizable assets do. They live or die by their cashflow, every month.

Jennifer Houle: 5 / 10

Sometimes you start to read a job posting and then as you get into the nitty-gritty, you’re like, “dang… this isn’t as great as I thought it was going to be.” Which is kind of how I feel about this one. I like what they’re trying to do, I like their enthusiasm, but there’s a lot about the role design that needs to be reworked even if they were transparent about the utter chaos that person who gets this job will be faced with.

SUPPORT THE SHOW

Roast the Post is a passion project of Jen Houle and Paul Austin-Menear. The show helps job-seekers and employers get dud job ads out of their lives. We use tips to help pay for our production costs, and donate anything raised beyond our costs to charity.

Roast the Post Podcast

Chief of Staff: Context Switching as a Love…