Your Job Ad Is a Sieve With No Holes [78]
Job ads function as filters to self-select candidates, not marketing brochures. The episode analyzes what a real job posting does well (specific compensation bands and active skill tasks) and poorly (vague adjectives like "AI curiosity" and missing success metrics), providing concrete rewrites to improve candidate quality.
Summary
In this episode of Leading Pre-Sales, hosts Nate and Ava conduct a teardown of a job advertisement for a Solution Engineer role. They frame job postings as filtering mechanisms rather than promotional tools, arguing that every element should either qualify or disqualify candidates efficiently.
On the positive side, the ad explicitly states compensation by region (e.g., €176-212K base plus €58-70K commission in Western Europe, $300K+ in California), which immediately filters candidates by salary expectations. This specificity prevents both overqualified candidates from wasting time and underqualified ones from applying. The ad also includes an active task asking candidates to build something in the product and submit a screenshot, creating a proof-based filter rather than relying on claims.
However, the ad fails in two critical ways. First, it includes vague adjectives like "AI curiosity" as a must-have requirement, which is unmeasurable and allows nearly all candidates to self-qualify, defeating the filter. The hosts recommend replacing such adjectives with concrete, binary thresholds: "You've built at least one automation you personally use every week. Show us." Second, the ad never articulates what success looks like. The hosts argue that including a success metric—such as "Twelve months in, SE-attached revenue in the enterprise segment is materially up"—actually filters better by surfacing candidates uncomfortable with that standard early.
The discussion also reveals that Nate's organization of 200 SEs publishes full transparency on compensation and career progression, with no history of employees leaving over pay. Ava admits she hesitates to publish success metrics due to risk, but the hosts counter that filtering out uncomfortable candidates early is preferable to discovering misalignment during onboarding. A final caveat emphasizes keeping active tasks to under 30 minutes to avoid scaring away strong candidates with free consulting requests.
About this episode
Nate tears apart a publicly posted Head of Solution Engineering ad from a fast-growing automation vendor — two things it does brilliantly, two it gets badly wrong. Ava pushes back on publishing comp bands and on asking candidates to sign up for a number before they know the territory.
Key Insights
- Specific compensation bands published by region filter candidates in both directions—those seeking higher pay self-disqualify while those at lower salary thresholds recognize rare opportunity, whereas generic 'competitive compensation' language creates no filter at all.
- Vague adjectives like 'AI curiosity' in must-have lists create ineffective sieves because candidates can self-qualify without clear thresholds, resulting in screening 40 people to find 2 desired candidates instead of narrowing the pool upfront.
- Including a one-sentence success metric (e.g., 'Twelve months in, SE-attached revenue in the enterprise segment is materially up') filters out candidates uncomfortable with that standard before hire, surfacing misalignment in week one rather than month four.
Topics
Transcript
Hey there and welcome to Leading Pre-Sales, the show for solution engineering leaders who want to build teams that drive revenue and not just demos. My name is Tim and I'm the co-founder of SE Rockstars and together with Jan, we've coached over 350 solution engineers and their leaders across several dozens of companies. Every conversation you hear on this show is based on real coaching situations, real challenges, real problems that as leaders like you are dealing with right now, none of this is made up. We use AI to bring these stories to life through our two hosts, Nate and Ava, but the insights come straight from the trenches. Each episode gives you one actionable takeaway you can…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Leading PreSales | The Solution Engineering Leadership Show
Core vs. Context: When Your SEs Should Let a Build Deal Go [92]
The episode teaches solution engineering leaders to distinguish between core and context business functions when customers consider building custom solutions versus buying software. SEs should let lightweight, context-focused builds go while fighting harder for core capabilities, and leaders must publicly validate this approach to change team culture.
The Iceberg Under Every Build Deal [91]
Solution engineering leaders need a standardized five-year cost model to evaluate Build vs. Buy decisions in the AI era, grounded in hidden maintenance costs and opportunity expenses rather than vendor pitches. The key is creating an 'iceberg checklist' of often-overlooked costs and having customers co-create the financial analysis rather than presenting a pre-built case.
Leaderboards, Not Cameras [89]
The episode examines why AI adoption dashboards and leaderboards often fail to drive behavior change, and proposes an alternative approach: publicly sharing AI workflows that actually shipped on real deals, ranked by peer reuse rather than usage metrics.
Your SEs Just Inherited the Customer's Bill [88]
Solution engineers must own usage estimation and sizing in consumption-based pricing models, even though they don't set prices. When SEs fail to accurately estimate how often workflows trigger, customers face billing surprises that damage relationships and renewals.
Rebrand or Real Role? The FDE Test [86]
The episode examines whether Forward Deployed Engineers (FDEs) represent a genuinely different role from Solution Engineers or merely a rebranding strategy. Through analysis of real job postings and market trends, the hosts present a three-question test to distinguish authentic FDE positions from SE roles with inflated titles.