Let’s Roast.
What if your job was to turn someone’s worst day with a product into a moment of clarity… and maybe even joy? The "Happiness Engineer" role isn’t about forced fun or office parties; it’s a high-stakes, customer-facing gig disguised as a Silicon Valley punchline. For job seekers, it’s a chance to do meaningful work with real autonomy. For hiring managers, it’s a blueprint for how to actually value your support teams. But does the reality live up to the hype? Let’s find out.
Follow along with the full job ad here:
The Bigger Picture
How do you design a role that keeps customer empathy at the heart of a scaling organization, without letting it become a cost centre or a revolving door? This isn’t just a job posting; it’s a test case for whether companies can truly treat support as a strategic function, not an afterthought.
At a Glance: The Job Profile
Job Title: Happiness Engineer - Customer Support & Success
Report-to Title: Unknown
Company Size: 1,001 - 5,000 Employees
Industry: Software Development
What do they do?: They create software that helps people build websites, sell products online, and manage their digital content.
Head Office Location: San Francisco
Job Location: Remote
Geographical Operating Area: Global
Job Type: Full-Time, Remote
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:
Self-scheduled hours sound great… but how do you ensure coverage during peak times, and what happens if my ‘ideal’ hours don’t align with customer demand?
You mention ‘high autonomy’… can you give me a real example of a time a Happiness Engineer made a decision that impacted the product or company direction without needing approval?
The role blends customer support with advocacy. How do you measure success in this role… is it ticket resolution speed, customer satisfaction scores, or something else?
You say support is a long-term career here. Can you share specific examples of Happiness Engineers who’ve grown into leadership or other departments, and what that path looked like?
Global salary ranges sound equitable, but how do you account for cost-of-living differences? For example, how does this salary compare to local market rates for similar roles?
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:
Issues Created:
Ambiguity in Scheduling: Self-scheduled hours could lead to gaps in coverage during peak times, risking customer satisfaction and operational efficiency.
Outcome: Inconsistent support availability, frustrated customers, and potential burnout for employees covering gaps.
Fix: Implement a hybrid model… self-scheduled within core hours, with clear expectations for coverage during high-volume periods.
Overpromising Autonomy: Claiming “high autonomy” without defining boundaries may result in employees overstepping or feeling unsupported.
Outcome: Confusion about decision-making authority, potential conflicts with other teams, and disillusionment if autonomy is limited in practice.
Fix: Define what autonomy looks like (e.g., process improvements, customer solutions) and where it ends (e.g., product changes require collaboration).
Vague AI Requirements: “AI fluency” is trendy but undefined, risking mismatched expectations between candidates and the role.
Outcome: Hiring people who either over- or under-deliver on AI capabilities, leading to inefficiencies or missed opportunities.
Fix: Specify how AI is used in the role (e.g., automating workflows, analyzing customer data) and provide examples of successful applications.
Global Salary Ranges: Paying the same USD amount globally may create inequities in purchasing power and local market competitiveness.
Outcome: Difficulty attracting top talent in high-cost regions or overpaying in lower-cost areas, leading to retention issues or budget strain.
Fix: Adjust salary ranges by region or clearly communicate how purchasing power parity is considered.
Lack of Structural Clarity: No reporting structure or team hierarchy is mentioned, which could lead to confusion about career paths and accountability.
Outcome: Employees may feel adrift in a remote environment, unsure of how to grow or who to turn to for support.
Fix: Include a brief org chart or describe the team structure (e.g., “Reports to a Customer Experience Lead, with opportunities to collaborate across product and engineering teams”).
The Verdict
Paul Austin-Menear:
9 / 10 (Job Ad)
8 / 10 (Role Design)
One of the best job ads that we’ve ever roasted. The job ad itself was detailed, struck a nice balance between employer branding and what matters for the candidate, and outlined purpose for the organization well. The role design hinted at respect and sustainability, with policies for wellness and fulfillment throughout.
Jennifer Houle:
9 / 10 (Job Ad)
8 / 10 (Role Design)
Absolutely one of the best we’ve ever roasted. If the whole thing wasn’t just window-dressing, many companies could learn from how this ad was structured and the role designed (from what we could tell). A few things were missing, but it was pretty good overall.
Support the Show
Roast the Post is a passion project of Jennifer Houle and Paul Austin-Menear. The show helps job-seekers and employers get dud job ads out of their lives. There are several ways that you can help us on our mission to unf*ck the hiring process…
1 —> Share this episode with someone who’d like it.
2 —> Pick up a copy of our new e-Book, the Job Description Decoder and leave a review. Proceeds will be donated equally to Ronald McDonald House BC & Yukon and the Toronto Humane Society.
3 —> Send us a one-time or recurring tip on Buy Me a Coffee. This helps pay for our production costs.
