Nobody hires a backend engineer for their jawline
True, and the photo still does work you did not ask it to do — in a recruiter's first screening pass, in a four-thousand-person internal directory, in the conference bio due Friday. Upload one photo, pick a style, and stop thinking about it for two years.
Powered by the world's best AI models
100+ models · commercial use included
The objection is correct. Here is the narrow case anyway.
Most engineers do not want a headshot, and the reasoning is usually sound. The work is legible. The artefacts are public. A hiring process that weighs your face more heavily than your commit history is a process worth failing early. Nobody has ever been hired to run a distributed systems team because their jaw photographed well, and a page claiming otherwise would be selling something. So this one will not argue that a portrait makes you a better engineer, or that it changes how your pull requests are received.
What is true is narrower and duller. Technical hiring runs through profiles, and a recruiter working a list of two hundred people makes a first pass in which the photo is one of four things visible — a blank silhouette is an unanswered question in a process whose entire design is eliminating quickly. An internal directory at a company of four thousand is how a colleague in Sydney puts a face to whoever left eleven comments on their design doc at 2am. Conference programmes, open-source project pages, meetup listings and podcast show notes all ask for a picture, always with a deadline attached. And the move toward staff, principal or engineering management is exactly the point where people begin being assessed on presence rather than output alone.
None of that requires a good photo. It requires a photo that is not actively strange: one that looks like the person who turns up to standup, taken this decade, without a rented suit or a stock-photography smile. That is the target here — technical credibility without corporate costume. Upload one clear photo, choose a style, and get up to four variations in about thirty seconds. There is no folder of selfies to assemble and no training step; one source photo and one style per run.
The four photos engineers actually have
One of these is probably yours. None of them are a crisis. All of them take about a minute to stop being true.
The grey silhouette
No photo at all, on the entirely defensible theory that it is nobody's business. It has one measurable cost: a recruiter skimming a list reads an empty avatar as an abandoned profile and moves on before reading the headline underneath it. If you never want to be contacted this works perfectly. If you would take the right message about the right team, it is filtering out precisely the people who research before they write.
The photo from a company that no longer exists
Cropped out of a group shot at an offsite, eight years and two acquisitions ago, with somebody else's shoulder still in the frame and a lanyard from an employer that got absorbed. It survived because no moment ever forced a replacement. The cost is not vanity — it is that the person joining the video call is visibly not the person in the picture, which spends a beat of everyone's attention at the start of every first conversation.
The suit somebody talked you into
A navy three-piece on an infrastructure engineer does not read as professional. It reads as a photo taken for somebody else's benefit — a recruiting agency's template, a consultancy brochure, a compliance box. Other engineers spot the costume instantly, because they know what their peers actually wear on the days they are doing the work, and the mismatch makes the whole profile feel staged.
The bio request with a deadline on it
A conference accepts your talk and wants a photo and a hundred words by Friday. A podcast needs a square image. A foundation is building a maintainers page. Every one of these arrives on somebody else's schedule, and the fallback is whatever is nearest in the camera roll, which is how a cropped holiday photo ends up on a speaker grid beside eleven studio portraits.
What the photo is actually being used for
It is worth being precise, because the honest answer is unglamorous. An engineer's photo is doing identification, not persuasion. It connects a name in a Slack thread to a person in a video call, a design-doc comment to a colleague in another timezone, a conference badge to the talk somebody wants to ask a follow-up about in the hallway. That is a real job, and it is the job these photos fail at when they are eight years old or missing entirely.
The second use is narrower and only begins to matter at a certain point. As you move toward staff, principal or management, part of the work becomes representing technical positions to people who cannot evaluate them directly — a board, a customer, a partner org, a hiring loop you are now running rather than sitting in. At that point presentation stops being irrelevant. The useful move is still not to become polished. It is to stop looking accidentally unconsidered.
- Is this the person I have been arguing with in the design doc?
- Is this profile live, or was it abandoned three jobs ago?
- Does this look like an engineer, or like an image an agency supplied?
- If this person presents to a room of non-engineers, will they be taken seriously?
A minute of your time, once
No shoot to book, no scheduling, no standing in front of a lens while somebody adjusts a light.
Upload one photo
Upload one clear, front-facing photo of yourself. Even light, eyes visible, no sunglasses, and recent enough that it matches how you look on a call.
Choose a style
Pick Tech Startup, or any of the 38 styles, and set lighting, background, attire and expression if you want to steer the output.
Download your pick
Get up to four variations in about 30 seconds. Use one everywhere — profile, internal directory, conference bio — and leave it alone.
What technical credibility actually looks like
The register is narrower than a general headshot guide suggests, and the common failure is over-formality, not under.
- Skip the suit. Genuinely.
- Business Casual, Turtleneck, Polo and Smart Casual Blazer are the four attire options that fit here. A plain, well-fitting shirt or knit is the entire brief. Navy Suit and Charcoal Suit exist in the studio and are correct for finance and law; on an engineer they signal that the photo was produced to satisfy somebody else's idea of professional, which is exactly the impression worth avoiding.
- Directional daylight beats studio polish
- Natural Window is the closest thing to the light engineers are actually photographed in, and it produces a portrait that looks taken rather than manufactured. Soft Studio is the neutral fallback when the image has to sit in a corporate directory grid. Ring Light flattens everything toward webcam; Dramatic and Cinematic are excellent portraits that will look like an album cover on a maintainers page.
- A background with no whiteboard in it
- Neutral Grey, Soft Gradient and Clean White carry no information, which is the point. Home Office and Modern Office give a blurred suggestion of a workspace with nothing readable in it — worth remembering that in a real photo, whiteboards, monitors and sticky notes can contain things your employer would rather were not indexed by a search engine.
- Composed, not enthusiastic
- Thoughtful and Confident are the two expressions that fit this field. A restrained, closed-mouth expression is the norm across engineering profiles and reads as neither cold nor performed. Energetic and a broad Friendly Smile push a portrait toward the sales register, which is the specific thing most engineers are trying not to look like.
- Make it survive a square crop
- The places this photo lands are mostly square or circular: Slack, a Git host, the internal directory, a speaker grid. Generate at the 3:4 default so you also have something for a bio page, then crop square. Close Headshot framing survives that trim; anything wider loses most of your face when the corners are discarded.
- Keep it recognisable, not improved
- The one rule that matters. If the result is smoother, younger or slimmer than you are, discard it — you will be on a video call with the same recruiter next week, and the only thing a photo can genuinely cost you is that moment of recalibration. A run returns up to four variations precisely so you can throw away the three that flatter too hard.
Styles that read as technical
Four of the 38 studio styles, chosen for the narrow register engineering profiles live in.
Do it once and forget it
The correct amount of time to spend on this is small. One source photo, one style, one run, pick the least objectionable result, upload it in four places, and go back to what you were actually working on. The goal is not to have a good photo. It is to stop having an absent or obviously stale one, so that the next recruiter, conference organiser or colleague two timezones away gets a straightforward answer to a question they were only ever going to ask once.
The single moment worth revisiting it is a change of altitude. Moving off the pure IC track into staff, principal or management shifts the audience: more of the job becomes explaining technical decisions to people who cannot check them, and the photo starts turning up in contexts where it is the only thing they have seen of you. Regenerate then, in a slightly more neutral style, and give it another two years.
Frequently asked questions
Keep looking around
Create your engineer headshot
One photo in, up to four variations out, in about 30 seconds.