Turn an Engineer's Work Into Sourcing Content
When to use it
Get a specific, credible story out of what the team actually built, for outreach and social posts.
The prompt
Help me turn a real piece of engineering work into content I can use in sourcing. WHAT THE TEAM BUILT: {{the project, in whatever detail you have}} WHY IT WAS HARD: {{the actual constraint — scale, latency, a migration with no downtime, a deadline, a legacy system}} WHO WORKED ON IT: {{names and roles, if they've agreed to be mentioned}} WHAT I CAN'T DISCLOSE: {{anything confidential}} Give me: 1. A two-sentence version I can drop into an outreach message to someone with a relevant background. 2. A short social post, written so an engineer would find it credible rather than marketing-flavoured. 3. Three questions I could ask the engineers to get the detail that makes this specific rather than generic. 4. A note on which parts, as written, an engineer would read as exaggeration.
Tip
Ask the team what was hard, not what was impressive. The hard part is what a good engineer recognises and wants to work on; the impressive part is usually the bit that sounds like a press release.
How to use it
Paste the prompt into ChatGPT, Claude or whichever assistant you use, then replace every {{bracketed}} part with your own detail. The more specific and messier your input, the better the output — a model given raw notes has more to work with than one given a tidy summary you wrote first.
More Employer Brand prompts
Open the full tool for all 87 prompts, the glossary, and the JD decoder.