The €1,000 Contradiction: Don't Promise Enablement You Haven't Funded [80]
The episode critiques a job posting that promises an ambitious enablement mandate with insufficient budget (€1,000/year for training), arguing that posting mandates without adequate funding creates a contradiction that damages employer credibility. The hosts discuss how to align budget visibility with job posting promises and advocate for transparent, regional-specific benefit listings.
Summary
Tim introduces Leading Pre-Sales, a show for solution engineering leaders, and frames the episode as part of a job ad teardown series examining real posting contradictions. Hosts Nate and Ava analyze a specific job posting offering €1,000 annual education budget while simultaneously mandating the building of demo infrastructure, automation, sandbox environments, and new product enablement—projects that far exceed what a training budget can cover. Ava notes that €1,000 is better than some situations but insufficient for meaningful development, citing a specific example where one conference ticket and hotel would exhaust the entire budget. Nate counters that the real constraint on his team isn't money but calendar time, with team members overbooked across three concurrent cycles and training budgets regularly going unspent. However, Ava emphasizes that job postings can only communicate tangible numbers (money), not intangibles like calendar availability, making the posted figure the only verifiable commitment candidates can evaluate. Nate reveals a strategy for securing adequate funding by making invisible spending visible: he asked directors to price what teams were already quietly purchasing (sandbox licenses, demo tools, courses on corporate cards), nearly doubling the official budget. Finance, he argues, won't challenge ambition but will act on documented receipts. The conversation shifts to emerging transparency requirements from the EU Pay Transparency Directive (effective June, with Germany's national transposition expected the following year), which will make benefits directly comparable across employers. The hosts praise the job posting's regional specificity for benefits (different vacation days, sick leave, visa sponsorship by region) while criticizing global postings that confuse candidates about applicability. They note the posting positioned 'remote first' as a benefit, contrasting it with postings demanding office days without justification. Nate explains that when he reduced his team from two anchor office days to one, explaining the reasoning for 20 minutes reduced resistance even though nobody loved the policy. The core actionable recommendation is to audit all live job postings by writing Euro figures next to every 'you'll own, you'll build, you'll equip' statement, adding a second column for actual calendar time allocated. If numbers embarrass leadership or don't exist, the posting should be revised or the sentence removed. The hosts emphasize this internal audit matters because existing team members read postings too, and discovering new hires were promised more creates credibility damage.
About this episode
Nate reads a Head of SE posting that makes the new leader responsible for training, tools and feedback — then funds it with €1,000 a year, less than the same company gives people for donating to open-source projects. He and Ava dig into why that gap is read as a culture signal, and what to do before pay transparency makes every line comparable.
Key Insights
- Nate demonstrates that finance departments resist new budget requests for ambitions but will fund documented receipts: he discovered his team was already spending nearly double the official training budget on invisible purchases (sandbox licenses, demo tools, courses on corporate cards), and made this existing spending visible rather than arguing for additional allocation.
- Ava argues that job postings communicate only verifiable numbers to candidates, not intangible constraints like calendar availability; therefore, when a posting lists €1,000 training budget, candidates cannot evaluate whether the actual time exists to use it, making the posted number the sole checkable commitment.
- The hosts claim the EU Pay Transparency Directive will shift competitive comparison from salary differentiation to benefits line-by-line comparison across employers within one browser tab, making contradictions between promised mandates and allocated resources immediately visible to candidates and existing employees alike.
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
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.
No Quota, Still Commercial [85]
Forward Deployed Engineers (FDEs) should be measured on time-to-first-value and usage ramp rather than traditional sales quotas, with compensation tied to commercial outcomes that directly correlate to revenue under consumption pricing models. Success requires a disciplined 10x cost-recovery model, a defined pilot-to-contract path, and mandatory product feedback loops to prevent FDE teams from becoming expensive consulting operations.
Engineering Is the Entry Ticket [84]
Forward-deployed engineering engagements often fail due to poor discovery, scoping, and stakeholder management rather than technical deficiencies. Engineering skills are necessary to enter the room, but success depends on identifying success criteria, mapping stakeholders (especially those who lose if the project succeeds), and having leadership cover to push back on misguided requests.