Software engineer headshots: the photo that has to feed GitHub, LinkedIn, and a FAANG team page

01Specific poses for software engineers

• Direct gaze, slight head tilt, soft smile: The LinkedIn-and-team-page default. Reads as engaged without performative. The dominant pose on most senior IC and staff-engineer team-page bios.
• Three-quarter turn, neutral expression: The conference-speaker default. Travels well to YouTube thumbnails and event-program print where the higher-energy LinkedIn smile reads as overproduced.
• Square crop, head-and-upper-shoulders, centered: The GitHub avatar pose. The platform crops to a circle at 280-pixel render; anything below the collarbone is cropped out anyway. Frame tight.
• Casual, leaning, environmental in an office or coworking space: The seed-stage and startup-founding-engineer pose. Reads as 'works in real spaces' over 'sat in a studio for an hour'.
• Standing, hands relaxed, no folded arms: Folded arms in a tech headshot reads defensive even when intended as confident. Senior IC and staff-level engineers consistently photograph better with hands at sides or in pockets.
• Profile or three-quarter with laptop or whiteboard prop: Almost never works. The prop signals 'I am pretending to be at work' and dates the photo within a year. Skip.

02Software engineer wardrobe guide

The 'level up one notch from your daily norm' rule. If you wear t-shirts to work, shoot in a fitted button-down or a crew-neck sweater. If you wear button-downs, add a blazer over a t-shirt. Solid colours work best at avatar size: navy, charcoal, olive, white, soft blue, muted burgundy. No graphic tees, no logos, no ties (reads costume-y in tech), and hoodies only for creative-engineer or designer-engineer roles where they signal voice rather than indifference.

03What you should expect to pay

A professional studio session typically ranges from to . The AI route provides a comparable result for $15.

01The platform specs to design around

The four targets each publish or imply a hard spec:

• GitHub avatar: PNG, JPG, or GIF; under 1 MB; max 3000 by 3000; recommended 500 by 500 per the official GitHub profile reference. Render is a 280-pixel circle; tight head-and-shoulders crop required.
• LinkedIn profile photo: 400 by 400 minimum; recommended 800 by 800 for retina displays. Square aspect ratio.
• FAANG/company team page: typically 600 by 800 or 1200 by 1600. The visual grammar across most large tech employers converges on neutral grey or soft-tone backdrops, three-quarter turn, soft smile, and no environmental backdrops on the official engineering team grid. Specific company style guides vary; if your employer publishes one, follow it.
• Conference speaker bio: typically 600 by 600 square or 800 by 1200 portrait. Sized for both the event program print and the speaker-card YouTube thumbnail.
• e shoot has to deliver an image that crops cleanly to a 1:1 square (GitHub, LinkedIn, conference avatar) and a 4:3 or 3:4 portrait (team page, speaker bio) from the same capture. That requires composing for the tightest crop (head-and-upper-shoulders, no props, no environmental detail that reads as "office of a particular era") and accepting that the wider crop will use the same frame with slightly more shoulder.

02The wardrobe rule that tech actually follows

Tech industry conventions on headshot wardrobe converged in the 2020s on a single rule: dress one level above your daily norm. The full mapping:

• Daily t-shirt → shoot in a fitted button-down or a crew-neck sweater. Solid colour, no logos.
• Daily button-down → shoot with a blazer over a t-shirt. The unstructured blazer is the tech-coded version of the suit.
• Daily blazer or jacket → shoot the same. Don't downgrade for the photo; it reads inauthentic on internal team pages.
• Daily hoodie → shoot in a fitted crew-neck sweater. The hoodie itself reads as "I don't care" on a LinkedIn primary photo, even when the engineer's role makes a hoodie appropriate. Reserve hoodies for the GitHub avatar where the peer audience reads them as authentic.
• ip the tie. A tie in a tech headshot reads as overdressed across most engineering audiences; tech recruiters and hiring managers consistently mention it as a "fit" mismatch when screening profiles. Skip graphic tees, brand logos beyond a small chest mark, and statement jewellery that catches harsh studio light.
• e colour palette that photographs cleanest at small avatar sizes: navy, charcoal, olive, soft blue, white, muted burgundy. Anything saturated (true red, neon green, electric blue) crops badly into the LinkedIn ring border and the GitHub circle.

03GitHub avatar versus LinkedIn primary photo

The same photo often plays differently on the two platforms because the audiences screen for different things:

• GitHub is read by other engineers and engineering hiring managers. The screening question is "is this person a real human who is actually building." A relaxed, slightly less polished version of the photo wins. The default avatar of a cartoon Octocat is the baseline; anything that reads as "real engineer in their natural environment" beats the formal LinkedIn shot.
• LinkedIn is read by recruiters who skim hundreds of profiles per day. The screening question is "is this person at the seniority level the role requires." The polished, soft-smile, neutral-backdrop shot wins. Slightly more posed and lit than the GitHub version.
• e practical workflow: shoot one session, deliver two crops. The square 1:1 with slightly tighter framing for GitHub (and a marginally less retouched version for the peer audience), and the 4:3 or 1:1 with marginally more retouching and slight smile-upgrade for LinkedIn.

04The five mistakes that show up across engineering team pages

1. Hoodie on the LinkedIn primary photo. Even when the engineer's actual role and culture justify a hoodie, the LinkedIn convention reads it as either "doesn't care" or "trying too hard to signal startup." It survives on GitHub; it loses on LinkedIn.
2. Stale photo on a high-velocity profile. Engineers who have changed companies twice in three years often have a LinkedIn photo from the first company. The visual mismatch with the current bio is a credibility hit at the recruiter screen.
3. Folded arms. Reads defensive at avatar size even when intended as confident. Hands at sides, in pockets, or holding nothing photograph cleaner.
4. Webcam selfie used at LinkedIn primary scale. Webcam at 720p crops badly when LinkedIn rescales to 400 by 400 for the recruiter view. The compression artefacts read as "didn't care enough to commit a real photo."
5. Same photo unchanged across all four platforms for five-plus years. GitHub allows it; LinkedIn punishes it; the FAANG team page locks the engineer into a visual identity that no longer matches. Refresh on a three-year cadence at minimum.

05What it actually costs in 2026

Engineer headshots track the broader tech-headshot market with one quirk: many studios offer a "tech package" that includes both a primary photo and a square-cropped GitHub variant.

• Budget tier ($150–$250): 15 to 30 minutes, plain backdrop, 1 to 3 retouched. Adequate for the GitHub avatar; marginal for a senior LinkedIn shot.
• Mid-range ($300–$500): 45 to 60 minutes, two outfits, soft natural-light setup, 4 to 6 retouched in both square and portrait crops. The standard for an IC-to-staff transition or a job-search shoot.
• Premium ($550–$700): 60 to 90 minutes, three outfits, multiple backdrop options, environmental and studio variants, 6 to 8 retouched. The correct spend for a conference-speaker shoot or an executive-track engineer.
• market: SF and South Bay $295 to $450 (most tech professionals shoot here); Seattle $250 to $400; NYC $350 to $924 depending on studio; Austin $200 to $350; remote-first engineers in mid-tier markets often shoot in the $150 to $300 range.
• e often-skipped add-on: a separate hair-and-makeup pass for a conference shoot ($50 to $200). For YouTube thumbnails and event programs, the same flat-lit no-makeup look that works on LinkedIn often loses against staged-event photos.

06The AI route, with the platform-specific framing in mind

For software engineers, the AI portrait route works well across all four target platforms because the visual grammar each platform expects is consistent and the input source (a few selfies on a phone) is exactly what most engineers have on hand. The output crops cleanly to both square and portrait without further capture. Note: MyPhotoAI generates high-quality single-person portraits only; multi-person or group AI generation is not supported at this time.

The workflow:

1. Upload 5 to 15 recent selfies. Recent matters because the LinkedIn photo will be screened against the current company in the bio.
2. Pick the engineer headshot style. Tech-casual neutral, soft-light environmental, FAANG-team-page studio, or conference-speaker variants.
3. Wait about three minutes. Output is sized at 1024 by 1536 and crops cleanly to GitHub 500 by 500, LinkedIn 800 by 800, team-page 600 by 800, and speaker bio 800 by 1200 without further capture.

What it does well: the four crops from one input. The most expensive part of the studio shoot is the time it takes to produce a square avatar and a portrait bio in the same session; the AI route compresses that to one upload.

What it doesn't: the conference-speaker shot for a flagship tech-industry event where the visual stakes are higher (KubeCon keynote, Apple WWDC, Google I/O). For those, the studio session and a known event-photographer credit are still the right tool.

Starter plan is $15 for five portraits. That's lower than the lowest local studio session in any major tech market and produces enough variation to pick a strong primary plus a square avatar plus a backup.

07One-line version

GitHub: square 500 by 500, casual, peer-readable. LinkedIn: 800 by 800, soft smile, level-up-one-notch wardrobe. Team page: lock to the company's visual grammar. Speaker bio: studio shoot, separate hair-and-makeup pass.

Try a software engineer headshot. 12 professional headshot styles including tech-casual, FAANG-team-page studio, and conference-speaker variants. HD from $15.