A job ad is a filter. Most of them filter nobody.
TL;DR
- Publish the band. n8n listed €176k–€212k base plus €58k–€70k commission for Western Europe, split by region. That single block saves both sides three calls.
- The strongest line in the ad was an assignment: try the product, build something, send a screenshot with your application. It filters for effort and creativity before anyone books a slot.
- Watch the scope creep. "Head of Solution Engineering" that also covers partner motions and post-sales deployments is a go-to-market mandate, not an SE job. Take it apart in the interview.
- Must-haves have to be answerable with yes or no. "AI curiosity" is not a criterion. It's a mood.
- What was missing: any definition of what success looks like after twelve months. Ask for it — most hiring managers have never been asked.
€176,000 to €212,000 base. €58,000 to €70,000 commission on top. Western Europe. Printed at the top of the ad, above a single requirement, next to separate bands for the UK, Ireland and the US.
The posting was Head of Solution Engineering at n8n — the Berlin workflow-automation and AI-orchestration company that started as an open-source project in 2019 and now sits at a $5.2 billion valuation after a strategic investment from SAP. Tim found it, shared it in our PreSales Leader Community, and we both read it three times. It's offline now. The lessons in it aren't.
This is not a review of one company's hiring. It's a checklist: what a PreSales leadership ad should do for the person reading it, what this one did better than almost anything we've seen, and the two places where it still leaked.
What does a job ad tell you before you reach the requirements?
More than the requirements do. The header block on this one listed full-time, location type remote, and — our favourite detail — department: Sales. If anyone still wants to argue whether solution engineering belongs under sales or under product, a company valued at over five billion dollars just answered it in a dropdown field.
There was an application deadline too, which tells you the process has a clock on it. And remote meant remote: Berlin, Portugal, Texas, California — the band changes, the welcome doesn't.
Then came the company context, and it was written for a very specific reader. 650,000 active developers and builders. 190,000+ GitHub stars, described as one of the world's top 40 most popular projects on GitHub. Backers including SAP and Sequoia. Two years ago a GitHub star count meant little outside engineering circles; in an AI-native company it now works as a credential. If those numbers mean nothing to you, that's useful information about whether this is your employer.
Should the salary band be in the ad?
Yes, and the law is coming for the companies that disagree. The EU Pay Transparency Directive should have been transposed into German law by 7 June 2026; Germany missed the deadline and national legislation isn't expected before 2027. So publishing the band today is voluntary. Do it anyway.
The practical argument is cheaper than the ethical one. A band filters in both directions. If you want €400k, you're in the wrong tab. If you're at €120k today, a jump to €220k+ happens, but rarely — and now you know that before you invest four interview rounds. The regional split (Southern Europe lower, California in the low $300k range before conversion) shows someone actually thought about cost of living instead of copying one number across a global posting.
What we look for is the scissors: a wishlist of requirements at the top and €60k at the bottom. There were no scissors here. The demands were heavy and the package matched them. That congruence is the real signal a senior candidate reads.
Every block in an ad either helps both sides decide — or wastes both sides' time.
Why "send us a screenshot" is the best line in the ad
Because it moves the first filter before the first call. The ad invited applicants to try the product, build something, and share a screenshot of it with the application. One sentence, and you learn whether someone will spend an hour on you, how creative they get, and whether they can translate a business requirement into a working flow.
Two criticisms. First, it was buried in running text. A filter that good deserves a box, a heading, a call to action — as written, you have to read carefully to even notice the assignment. You could argue that's the point (the careless applicants screen themselves out), but then you're filtering for reading stamina, not for building.
Second, it says "whether you are technical or not" — and the rest of the ad is unambiguously technical. Multiple must-haves circle back to hands-on depth. That opening line looks like boilerplate the company uses everywhere, and in a Head of SE posting it sends the wrong signal.
Is this one job or three?
Read the responsibilities and decide for yourself. Four buckets: defining the future, building scalable customer and partner motions, developing a high-performing global team, shaping company and product strategy. Inside bucket two: differentiated playbooks for scaled mid-market engagements, complex enterprise sales cycles, strategic accounts, partner-led opportunities and post-sales deployments.
That's the moment the phrase that gave our discussion its name showed up — eierlegende Wollmilchsau, the German idiom for a creature that lays eggs, gives milk and grows wool. The do-it-all hire.
The generous reading is the right one: this is a role defined for the next three to five years, not the next twelve months, and the ad itself names balancing short-term operational needs against long-term vision as a success criterion. The company clearly sees the pre/post split dissolving and wants someone who has already run end-to-end. Elsewhere it lists partnering closely with Sales, Customer Success, Partnerships, Product, Product Marketing and Engineering — so those functions exist and you're not building them alone.
Still: if you interview for a role scoped like this, take it apart line by line in the call. Who owns post-sales today? What resources come with the partner motion? Which of these five playbooks matters in year one? Nobody builds six playbooks in a quarter, and a leader who pretends otherwise gets eighteen months.
Two details we'd steal outright. The role explicitly owns the two existing first-line team leads in a 15-person org — a clean, honest statement that this is second-line leadership, which most ads leave you guessing about. And under team development it asks the leader to define what good performance in solution engineering actually looks like, then equip the team with training, tools and feedback to get there. An ad that makes performance definition a named responsibility is an ad written by someone who has led SEs.
What was missing, and what you should ask
A definition of success. Nowhere does the posting say: this is what good looks like twelve months in. We've honestly never seen an ad that does — which is exactly why the question is so effective in an interview. Ask the hiring manager what success looks like after twelve months, and you'll learn more in their thirty-second pause than from the whole requirements list.
Our suggestion to anyone writing the next one: name the outcome. Something like increase SE-attached revenue in the enterprise segment, or a target on enterprise logos, or adoption. If you can't write the number down, you probably haven't decided what you're hiring for.
The must-haves had the same problem in miniature. AI curiosity was listed as a must-have. What is that? Are you AI-curious because you opened ChatGPT once last month, or because you've been wiring your own agents, APIs and MCP servers into working flows? A must-have that everyone can answer "yes, sure" to filters nobody. Set a threshold — what have you shipped, automated or committed in the last four weeks — and the list starts doing its job. While you're at it, cluster the requirements into technical, personal and strategic. A flat bullet list reads as a priority order whether you meant it to or not, which is how value-led leadership: you lead with humility, integrity and without ego ended up dead last. That one belongs near the top.
Do the benefits match the band?
Mostly, with one gap. 30 days of holiday in Europe, 20 in the US plus eight sick days — a cultural difference worth noticing rather than judging. Equity for everyone, framed as ownership. Visa sponsorship for Germany, right-to-work required elsewhere, English as company language. $100 a month to donate to open-source projects you care about — $1,200 a year per person, and if everyone uses it that adds up to something real.
Then: a €1,000 annual education budget in a role paying up to roughly €282k on target. A thousand euros buys books and a video course. It doesn't buy the kind of development that turns two first-line leads into leaders who can run segments. It's better than the many companies offering nothing, and it's almost certainly a company-wide number rather than an SE decision — but for the person expected to define what great performance looks like, it's the thinnest line in an otherwise well-built ad.
And remote-first is listed as a benefit. In a year where plenty of companies are quietly pushing people back into offices two or three days a week without explaining why, saying it out loud counts.
Frequently asked questions
What should a Head of Solution Engineering job ad include? Compensation band by region (base, commission, equity), the reporting layer — first-line or second-line, and how many people and team leads are already there — the responsibilities split into team, customer and strategy, must-haves you can answer with yes or no, and a definition of what success looks like after the first twelve months. Anything else is decoration.
Do German employers have to publish salary ranges? Not yet. The EU Pay Transparency Directive should have been transposed into German law by 7 June 2026, Germany missed that deadline, and implementing legislation isn't expected before 2027. Companies publishing bands today are doing it voluntarily — and getting better-matched applicants for it.
What should I ask in an interview for a PreSales leadership role? "What does success in this role look like twelve months from now, and how will you measure it?" Then, for any role that spans partners or post-sales: who owns those functions today, what budget and headcount come with the mandate, and which priority wins when two of them collide.
Is "AI curiosity" a legitimate hiring requirement for SE leaders? The intent is legitimate — in an AI-native company you cannot lead solution engineers who don't build. The wording isn't. Replace it with evidence: what have you built or automated recently, in which tools, and what happened when it broke.
If you're the one writing that ad — or preparing for the interview on the other side of it — bring the question to our PreSales Leader Community, where 250+ SE leaders across Europe compare notes on exactly this. Want to talk about how you define and measure SE performance before you hire for it? Book a discovery call.
Tim Brömme (LinkedIn) & Jan-Erik Jank (LinkedIn) are the co-founders of SE Rockstars, with 30+ years of enterprise PreSales experience and 350+ SEs coached.
Listen to the full episode
The full teardown, line by line and in German, is here: PreSales Unleashed: Auseinandernehmen erlaubt: Traumjob oder Wollmilchsau bei n8n? (279)