Personal branding for software engineers
Almost all of your work is invisible. It sits in private repositories under a company's name, and it cannot be shown to the people deciding whether to hire or fund you.
Your best work is legally unshowable
This is close to unique among skilled professions. A designer has a portfolio, a writer has clippings, an architect has buildings. An engineer has years of work inside private repositories they cannot publish, under NDAs, credited to a team. So the personal brand is not a supplement to the evidence, it IS the evidence, and it has to be constructed from things adjacent to the work: how you reason, what you have opinions about, the small things you can release. That reframes it from self-promotion to the only available proof.
What the generator produced for a software engineers brief.
Captured output, not a mock. It came back from the same engine behind the free persona generator, run against the brief below, and the engine is deterministic so you can reproduce it. Dev Okonjo is an illustrative name, not a customer.
- Offer
- senior backend engineering
- Tone
- precise, unhyped, generous
- Audience
- engineers evaluating where to work next
- Precise
- Unhyped
- Generous
- Expert
- Authority
Archetype: The Sage
Tagline: Precise. Made real.
- Name engineers evaluating where to work next directly, in the words they would use about themselves.
- Lead with the outcome of senior backend engineering, then explain how it works.
- Earns trust by explaining, not asserting.
A note for engineers evaluating where to work next. Engineers evaluating where to work next use Dev Okonjo to get results that actually move their brand forward, with senior backend engineering that stays consistent. If that is the problem you are sitting with, this is what we do about it.
Generate one for your own brief → No signup for the first output.
The mistake most people in this job make
Most engineers treat visibility as marketing and therefore beneath the work. The consequence is that the strongest engineer in a hiring pool is often the least legible one, and legibility is what gets read.
What to actually post about
- A decision you made and the trade-off it cost
- A bug whose cause was more interesting than the fix
- The tool you stopped using and why
Who should skip this entirely.
An engineer happy in a role they intend to keep. This is leverage on optionality, and optionality has to be worth something to you.