Tech Headshots in NYC: Hoodie, Quarter-Zip, or Blazer? (2026 Guide)

# Tech Headshots in NYC: Hoodie, Quarter-Zip, or Blazer? (2026 Guide)

Every tech professional who books a headshot eventually hits the same wall: what do I wear? In most industries the answer is obvious. A litigator wears a suit. A banker wears a suit. Tech is the one field where the dress code is genuinely a question, because the people you are trying to reach — recruiters, investors, design partners, conference organizers, your own future hires — read clothing very differently depending on the room.

A founder pitching a Series B does not want to look like they are trying too hard. An enterprise account executive selling six-figure contracts to a bank cannot look like they wandered in from a hackathon. A staff engineer applying to a top lab wants to read as senior without reading as corporate. The garment on your shoulders is doing real signaling work, and getting it wrong is the most common reason a technically strong professional ends up with a headshot that quietly undersells them.

This guide settles the question the way I settle it in the studio: not with a rule, but with a decision. I shoot headshots out of a studio in Riverdale, in the northwest Bronx, and a large share of my calendar is tech — founders, engineers, product managers, designers, DevRel, and the operators around them. Below is the exact framework I walk clients through, organized as three wardrobe registers and a short set of questions that tells you which one is yours.

*Ready to book? [Book Your Session](/book) — same-week appointments are usually available.*

Why tech headshots are their own category

Before the wardrobe, it helps to understand why tech is different. In law, finance, and consulting, the headshot's job is to signal that you belong to an established institution. The wardrobe is a uniform, and the photograph confirms you wear it correctly. There is very little room to express anything personal, and clients in those fields usually do not want room.

Tech inverts that. The audience is not looking for proof that you conform — they are looking for proof that you are competent, current, and easy to work with. A photo that is too formal can read as out of touch, like a candidate who does not understand the culture they are applying to. A photo that is too casual can read as junior or unserious, like someone who has not yet had to be accountable to a board, a customer, or a payroll.

The result is a narrower target than people expect. Tech headshots live in a band between "approachable" and "credible," and the wardrobe is the single biggest lever for landing inside it. That is why this is a decision worth making deliberately rather than defaulting to whatever is clean in your closet the morning of the shoot. If you want the broader strategy for the field, my [tech headshot service page](/headshots-for-tech) covers session types and turnaround; this article is specifically about the wardrobe call.

The three registers, and when each one wins

Almost every good tech headshot falls into one of three wardrobe registers. None is universally right. Each wins in specific situations and loses in others.

Register one: the considered casual (crew-neck, henley, soft hoodie)

This is the most "tech-native" look, and it is more demanding than it appears. A plain, well-fitted crew-neck tee, a henley, or a clean structured hoodie in a solid muted color reads as confident and unbothered — the person is senior enough that they do not need a costume. That is the signal you are buying.

It wins when your audience is inside the culture: an early-stage founder photographed for a startup's about page, an engineer building a personal brand on technical Twitter or a developer blog, a designer whose portfolio is the real résumé. In those rooms a blazer can actively work against you by reading as someone performing seriousness rather than possessing it.

It loses the moment your audience sits outside tech. A casual look photographed badly — wrinkled cotton, a hoodie with a loud logo, a tee that has lost its shape — collapses into "I did not prepare." The considered-casual register only works when the garment is genuinely well-made and well-fitted and the lighting is doing the heavy lifting. This is the register where photographer and styling matter most, because there is nothing structured to hide behind.

Register two: the smart-casual default (quarter-zip, fine-gauge knit, overshirt)

If you are unsure, this is almost always the answer. A fine merino quarter-zip, a crew-neck sweater over a collar, a knit polo, or a structured overshirt sits exactly in the middle of the credible-to-approachable band. It is the register that reads correctly to the widest range of audiences without alienating any of them.

It wins for the broadest set of tech roles: product managers, mid-to-senior engineers, founders who sell to other businesses, customer-facing and revenue roles, and anyone whose headshot has to work on LinkedIn, a company team page, and a conference site all at once. The quarter-zip in particular has quietly become the default uniform of the tech operator class for exactly this reason — it signals "I take this seriously, and I am still approachable."

It rarely loses outright. Its only failure mode is blandness: if everyone on your team shoots in the same gray quarter-zip with the same lighting, the photos blur together. The fix is not a different garment but better direction — expression, posture, and light that make the person, not the sweater, the subject.

Register three: the polished layer (blazer, structured jacket over a tee or collar)

The blazer is back in tech, but its job has changed. It is no longer about formality — it is about authority. A well-cut unstructured blazer over a plain tee or a fine knit reads as "I operate at the level where decisions get made," without the full institutional weight of a suit and tie.

It wins when you are reaching outside the building: a founder raising from later-stage investors, a CEO or CRO whose face appears in press and on earnings-adjacent materials, an enterprise seller calling on regulated industries, a leader being announced into a board or an executive role. In those contexts the blazer is reassurance. If your headshot is doing the work of an executive portrait, this is your register — and my [executive portrait page](/executive-portraits) covers that end of the spectrum in more depth.

It loses when the audience is purely internal-tech and the role is hands-on. A blazer on a heads-down engineer applying to a research lab can read as a mismatch, like dressing for a job you are not actually interviewing for. Authority you do not need is just friction.

The tech headshot wardrobe decision in five questions

If you only have a minute, answer these in order. The first one that gives a clear answer is your register.

1. **Who is the primary audience for this photo?** If it is mostly other engineers, designers, or early-stage operators, lean considered-casual. If it is mixed or business-facing, default to smart-casual. If it is investors, press, boards, or regulated buyers, go polished. 2. **What is the most senior room this photo has to work in?** Photograph for the most demanding audience, not the average one. A photo can always be slightly overdressed for a casual context; it cannot recover from being underdressed for a serious one. 3. **Is this a personal headshot or part of a team set?** Solo headshots can lean into personality. Team sets need a shared register so the page reads as one company — more on that below. 4. **What does your current title imply, and where are you headed?** Dress for the role you are stepping into. A senior engineer moving toward staff or management is well served by smart-casual over pure casual. 5. **Will this photo be used for two or more years?** The longer the shelf life, the safer the register. Trend-driven casual dates fastest; a fine knit or unstructured blazer ages slowest.

If you went through all five and still landed in the middle, that is the system working — choose the smart-casual register and stop deliberating. It is the highest-floor, lowest-risk option in tech, and a good photographer can make it look like a deliberate choice rather than a hedge.

Reading it by role

The register framework maps cleanly onto the roles I photograph most.

**Founders.** Early and seed-stage, building an audience: considered-casual or smart-casual, depending on who you sell to. Raising later rounds or appearing in press: add the blazer. Many founders book two looks in one session for exactly this reason — one approachable, one authoritative — and use them in different contexts.

**Engineers and technical ICs.** Smart-casual is the safe center. Considered-casual works beautifully if your brand is technical depth and your audience is peers. Skip the blazer unless you are moving into management or speaking on stage.

**Product managers and designers.** Smart-casual is the natural home. PMs sit between engineering and the business and benefit from a register that reads to both. Designers can push slightly more personal — a considered-casual look with intentional styling signals taste, which is part of the job.

**Revenue, partnerships, and customer-facing roles.** Default to the polished end. If you sell into enterprise or regulated industries, a blazer is rarely wrong. Your buyers are often not in tech, and they read clothing the way their industry does.

**Executives and operators.** Polished, full stop, with rare exceptions. If your face appears in board materials, press, or recruiting at the leadership level, you are shooting an executive portrait whether you call it that or not.

For company-wide work where many of these roles appear on one page, the goal shifts from individual choice to consistency — which is its own discipline. My [team headshot service](/team-headshots) handles exactly that: keeping a single visual standard across a mix of casual ICs and polished leaders.

Keeping a team looking like one company

The most common mistake I see on engineering and startup team pages is not bad wardrobe — it is inconsistent wardrobe. One person shot in a black blazer against gray, another in a bright hoodie against white, a third cropped tighter than everyone else. Individually fine. Together they read as a company that does not pay attention to detail, which is a strange signal for a tech company to send.

The fix is to set a register and a background as a team standard before anyone shoots, then let individuals vary within it. A team can absolutely mix casual ICs and blazered leaders in one set — what has to stay constant is the background, the lighting, the crop, and the overall tonal range. When those four hold, a mixed-wardrobe team page looks intentional. When they drift, even a uniform-wardrobe page looks sloppy.

This is also why staggered hiring is worth planning for. If you shot your team six months ago and have added four people since, those four need to be photographed to the same standard, not just "a headshot." Booking the same photographer, same lighting, and same background closes that gap — and it is most of why companies come back rather than rotating photographers.

How a tech headshot session works at Fuentes Studio

A session in Riverdale runs about 30 to 45 minutes for an individual. We talk through your audience and your register before the camera comes out, because the five questions above are easier to answer out loud than alone in front of a closet. If you are between registers, bring options — a fine knit and a blazer take ten seconds to swap, and seeing both on camera usually makes the decision for you.

I shoot tethered so you see frames as we go, which means you leave knowing the shot is there rather than hoping. Edited, retouched images are delivered within 48 hours. The studio holds a 5.0 Google rating, and the work has gone out to professionals across more than 800 sessions, including people at Fortune 500 companies. Sessions are priced for individuals and teams alike, and you can see current options and reserve a time on the [booking page](/book).

If you are weighing the broader strategy — how many looks, which usage, studio versus on-location — a quick read of the [tech headshot service page](/headshots-for-tech) will answer most of it before you book.

Frequently asked questions

**Is a hoodie ever actually appropriate for a professional tech headshot?** Yes, with conditions. A clean, structured, solid-color hoodie with no loud logo can read as confident and culture-native — but only when the audience is inside tech and the garment is genuinely well-made. For business-facing or external audiences, step up to a quarter-zip or knit. When in doubt, the smart-casual register is the safer bet.

**What color should I wear for a tech headshot?** Solid, muted, mid-tone colors photograph best: navy, charcoal, forest, slate, deep burgundy, or a soft neutral. Avoid pure white (it blows out), pure black (it loses shape), tight patterns, and stripes (they can shimmer on camera). The garment should support your face, not compete with it.

**Should everyone on my team wear the same thing?** No — they should shoot to the same standard. Background, lighting, crop, and tonal range need to match across the team. Wardrobe can vary by role as long as those four constants hold. That is what makes a team page read as one company rather than a collage.

**Can I bring more than one outfit?** Bring two or three. Most tech clients shoot one approachable look and one more polished look so they have the right image for different contexts — a casual one for the team page and developer community, a sharper one for investors, press, or external sales.

**How fast can I get my photos?** Edited, retouched images are delivered within 48 hours of the session. If you have a launch, a funding announcement, or a conference deadline, mention it when you book and we will make sure the timing works.

---

The wardrobe question only feels hard because tech gives you real choices. Answer the five questions, pick the register that fits the most demanding room your photo has to work in, and let the photographer handle the rest. If you happened upon this page already knowing you need it done well, that is the easy part.

*Looking to update your professional image? [NYC corporate headshot photographer](/) — same-week sessions in Riverdale, NYC. Happy with your last session? You can [leave a review here](/leave-a-review).*