Repository navigation
From /setup to a signed contract in 81 days – numbers, what worked, and three suggestions #810
Replies: 1 comment 3 replies
|
Congratulations, and thank you for writing it up with numbers. This is the first write-up I have seen from someone at Head of Engineering level, in German, on the German market, and the funnel is the part I would point other people at: 2,156 scanned, 117 scored, 8 sent, 1 contract. My own run was 69 applications for one contract, so scoring hard before writing anything is the lesson this confirms. And thank you for the coffees. On the three suggestions, honestly:
Two asks back. Your StepStone, Arbeitsagentur and Indeed skills are exactly what other German-market users look for; if your fork is placeholder-clean, an entry in #78 would help them find it. And may I link this post from the README? It says what the project is for better than I can. Viel Erfolg am 1. Januar. |
Uh oh!
There was an error while loading. Please reload this page.
Thanks to Mads and everyone who contributed. I used the framework as a Head of Engineering / CTO-level candidate in Berlin (25+ years Java/JVM, German market, CV in German) from 31 July to 20 October 2026. Result: signed contract with a large German company, start 1 January 2027.
The numbers
What helped most
What did not help
Three suggestions from a German-market setup (happy to share wording if useful)
no_responseconvention. No reaction within 10 working days after submitting: set the tracker tono_responseand stop reserving attention. It is a housekeeping rule, not a prediction about any employer. It keeps the follow-up branch of /outcome and the calibration data clean.Mads' post says the best part is the community. This is one more data point from the German market. Thanks again. If this framework helped you land a job too, a coffee for Mads is a nice way to say thanks. I've already bought two.
All reactions