32% of developers are fully remote and dress for nobody. Here's the honest answer to what coders actually wear, with data, culture, and four shirts worth owning.
Someone out there is writing a think piece about developer fashion. It includes phrases like "smart casual" and "professional polish." It has a section on "elevating your look with a blazer."
That person has never been on call.
The actual answer to what developers wear is simpler and more honest. It's mostly t-shirts. Sometimes jeans. Occasionally a hoodie that predates the current job. The data backs this up, the culture backs this up, and if you've spent any time around a software team, your eyes back this up.
Here's the breakdown.
The Dress Code That Isn't One
Tech killed the formal dress code, and the numbers make it look deliberate. According to Brightmine/Employer Advisor (2024), organizations enforcing dress codes via contract fell from 30% to just 4.3% between 2018 and 2024. That's not a gradual shift. That's a collapse.
Gallup confirmed the result in September 2023: 31% of all U.S. workers now wear casual street clothes to work daily, while only 3% still wear a suit. That number was 7% in 2019. Four years, more than half the suit-wearers gone. (Gallup, Sept 2023)
The Monster Poll from January 2025 put an even finer point on it: 43% of workers said they haven't worked somewhere with an official dress code in the past year.
Tech didn't just follow this trend. Tech led it. The hoodie-and-t-shirt culture in software engineering has been the norm since before casual Fridays became a thing in other industries. The formal dress code in tech was already a relic. The data just made it official.
According to Brightmine/Employer Advisor (2024), organizations enforcing dress codes via contract dropped from 30% to 4.3% between 2018 and 2024. Gallup (Sept 2023) found only 3% of U.S. workers wear a suit daily, down from 7% in 2019. Formal dress is no longer the default in any sector, and tech abandoned it well before the data caught up.
The WFH Wardrobe: What Actually Happens
Most developers aren't in an office. According to the Stack Overflow Developer Survey 2025, which surveyed over 65,000 developers, 32.4% are fully remote and another 37.1% work in some form of hybrid arrangement. Only 17.9% are fully in-person. (Stack Overflow Developer Survey 2025) U.S. developers skew even higher: 45% are fully remote.
| Work arrangement | Share of developers |
|---|---|
| Fully remote | 32.4% |
| Hybrid (in-person) | 19.9% |
| Fully in-person | 17.9% |
| Hybrid (flexible) | 17.2% |
| Flexible / your choice | 12.6% |
Source: Stack Overflow, Developer Survey 2025.
When the office disappears from the equation, so do the social pressures that kept the wardrobe in check. SHRM and NORC surveyed teleworking Americans in 2020 and found that 60% wear sweatpants or casual clothes daily while working from home. Seventeen percent reported pajamas as their usual work outfit.
That number goes further. A YouGov/Otter.ai survey from 2021 found that 30% of remote workers had worn pajamas during work video calls in the past twelve months. One in ten admitted to no trousers at all during calls.
Nobody is publishing those numbers in a LinkedIn post. But they are real.
| Attire | Share of remote workers |
|---|---|
| Sweatpants / casual clothes | 60% |
| Pajamas | 17% |
| Business-casual top only | 17% |
| Business attire | 6% |
Source: SHRM / NORC, 2020. Survey of 336 U.S. teleworking employees.
The camera frame is roughly shoulders to forehead. The argument for business attire in a remote job is almost entirely theoretical. What most developers have concluded in practice is that comfort is fine, being presentable on camera is fine, and anything below the waist is strictly personal business.
The wardrobe reality for remote developers is: t-shirt or sweatshirt on top, whatever on the bottom, and a strong preference for clothing that does not require effort.
The T-Shirt as Tribal Uniform
There's a reason the developer dress code, such as it is, converged on t-shirts specifically. Not polo shirts, not button-downs, not casual sweaters. T-shirts.
Marketplace/APM captured it plainly in 2014 in a quote that has aged without a wrinkle: "Engineers wear t-shirts, jeans and hoodies. In the fast-moving world of tech, the idea is to show that you're not wasting precious time on something as vain as fashion."
That framing gets at something real. The t-shirt in software culture isn't a fashion choice. It's a statement about priorities. It says: I am here to write code, not to manage impressions. There is a certain amount of professional identity wrapped up in that.
But then something happened. The t-shirt went from blank canvas to signal.
Once you're wearing a t-shirt anyway, what's on it starts to matter. A shirt that references a specific error, a known tool quirk, a shared frustration, a universal developer experience: that's a different object than a plain white tee. It does something. It identifies you to other people in the same room or the same Zoom tile who immediately get it.
The best coding swag works this way. The design requires prior knowledge to appreciate. Non-developers don't get it. Other developers do, instantly, and the recognition creates a connection that takes zero words. That's a lot of work for a cotton t-shirt.
The developer t-shirt functions more like a credential than clothing. It communicates specialization, role, and in some cases specific opinions about methodology, tools, or management. A shirt that says "Agile Sucks" is not a fashion item. It's a position statement. Worn in a room full of developers, it starts conversations. Worn outside that room, it is invisible.
The Conference or Interview Exception
There are contexts where developers actually have to think about what they wear. Not many, but they exist.
Tech conferences are not one of those contexts. A clean t-shirt, jeans, and clean shoes is appropriate for every tech event from a local meetup to a large developer conference. Nobody at those events is dressed up. The person giving the keynote is probably wearing the same thing. A hoodie is still fine. What matters is that the shirt is clean and that you can talk about what's on it if someone asks.
Job interviews are the genuine exception, and even then, it depends entirely on the company. Startup interview, pre-seed to Series B: t-shirt and clean jeans are fine and possibly correct. Interviewing at a bank, a consulting firm, or any company that has a "dress for the job you want" line in the onboarding packet: err toward business casual. The safest move is to look at the company's photos and match the least-dressed person in the room, not the most-dressed.
The universal rule for interviews: clean, ironed, deliberate. Not "dressed up" but "clearly thought about it." There is a difference.
Only 17.9% of developers work fully in-person, according to the Stack Overflow Developer Survey 2025 (65,000+ respondents). For the 82% who are remote or hybrid, the practical wardrobe question is not "what is appropriate for the office" but "what do I want to wear today." That shift changes what developer clothing means and who it's for.
Four T-Shirts Worth Owning
These are not generic recommendations. Each of these earns its place in regular rotation.
Works On My Machine
The Works On My Machine shirt is black and earns its spot because it captures a specific institutional failure mode in four words. Every developer has said this. Every QA engineer has received this response. The shirt does not apologize for it. It wears it as the badge it became.
It also works as a conference shirt: legible from across a room, no explanation required for anyone who has been on a software team longer than three weeks.
Breaking Prod
Breaking Prod is for the developer who has had the "this is fine" moment. The deploy went out. Production went down. The incident channel got very active very fast. You kept your composure publicly and dealt with it.
That experience earns something. This black shirt treats it like the badge it is rather than the apology some post-mortem template thinks it should be.
I Test In Prod
There is a version of this that is a confession. There is also a version where it is a flex. The I Test In Prod navy shirt accommodates both interpretations without resolving the ambiguity, which is correct, because in practice the line between "confession" and "flex" here is mostly a matter of team size and how good your rollback script is.
For developers who have accepted that no staging environment fully replicates production, this shirt is honest in a way that most SLAs are not.
No As A Service (NaaS)
Sprint planning generates an impressive quantity of new requirements. It rarely removes old ones. The No As A Service navy shirt takes the SaaS/PaaS/IaaS naming pattern, which is already a parody of itself at this point, and turns it into the one service most teams are chronically under-provisioned for.
If you have sat through enough planning sessions where the board fills up but never empties, this shirt requires zero explanation.
Featured product
Works On My Machine
The canonical developer badge in t-shirt form. Earns its place in regular rotation because every developer has said it, every QA engineer has received it, and neither party is wrong.
Shop the shirt →All four and more in the coding t-shirts collection.
Four shirts worth owning
Each references something real. Non-developers won't get it. Other developers will, immediately.
FAQ
What do software developers typically wear to work?
T-shirts, jeans, and hoodies are the standard across the industry. According to the Stack Overflow Developer Survey 2025 (65,000+ respondents), only 17.9% of developers work fully in-person. The majority are remote or hybrid. In those settings, casual clothes are the default, with sweatpants and t-shirts making up the most common WFH wardrobe (SHRM/NORC, 2020).
Is there a dress code at tech companies?
Mostly no, and the trend is toward fewer of them. Brightmine/Employer Advisor (2024) found that organizations enforcing dress codes via contract fell from 30% to 4.3% between 2018 and 2024. Most tech companies have no formal dress code, and those that do rarely enforce it. The working assumption across the industry is smart-casual at most, usually just casual.
What should a developer wear to a job interview?
It depends on the company type. For startups and product-focused tech companies, clean jeans and a plain or printed t-shirt is genuinely fine. For finance, consulting, or enterprise environments, business casual is the safer call. The practical test: look at the company's team or culture photos and match the least-dressed person you can find in the room, not the most.
What makes a good developer t-shirt?
A good developer t-shirt requires insider knowledge to appreciate. If a non-developer can wear it without feeling out of place, it probably isn't specific enough. The best designs reference something real: a named error, a shared workflow failure, a specific flavor of planning meeting frustration. That specificity is what makes the shirt worth owning versus what makes it end up in the company swag drawer.
