You're starting a tech job on Monday. You don't want to be the person who showed up overdressed, but you also don't want to be the person who showed up in a hoodie and clearly didn't take the day seriously. Most "what to wear on first day at a tech job" advice splits the difference badly. Either it tells you to wear a suit (please don't) or it tells you to wear "smart casual" (which doesn't mean anything in tech).
What follows is what to actually wear, written by someone who has had several first days at tech companies of varying sizes and gotten the calibration wrong enough times to have opinions.
Key Takeaways
- Tech company dress codes are real, but they look nothing like what your parents think they look like
- Big tech (FAANG-style), startups, enterprise tech, and remote-first companies have noticeably different defaults
- The safe first-day outfit at 80% of tech companies is dark t-shirt or henley plus dark jeans plus clean sneakers
- According to a 2023 Hired developer survey, 71% of software engineers say their company has a casual or no dress code
- Read the room before day one: Glassdoor photos, the engineering team's LinkedIn, what people wore at your onsite
- Save the graphic t-shirts and personality fits for week two, you don't have the social capital yet
- Avoid: suits, brand-new outfits you haven't worn before, anything that requires explaining
The Tech Job Dress Code Spectrum (Read the Room First)
Tech companies are not a single dress code. They are a spectrum, and the wrong end of the spectrum reads as if you don't understand the company. Here is what each tier actually looks like.
Big tech (FAANG-style)
Google, Meta, Amazon, Microsoft, Apple. Engineers wear t-shirts and jeans. Hoodies are common, especially for engineers who came in early or stayed late. Free company swag dominates the visual landscape, you'll be issued a stack of t-shirts in your first week. Day one: a plain t-shirt, dark jeans, clean sneakers reads as appropriate and aware. A button-up reads as someone who hasn't worked in big tech before.
Series A to C startups
The variance is highest here. Some Series A startups are aggressively casual (t-shirts and joggers), some are overcorrected toward "we're serious" (button-ups and chinos). The signal is the founders. If the founders wear hoodies on the company website, the engineers wear hoodies. If the founders wear button-ups, you'll see more of those. Default: a dark henley or polo, dark jeans, sneakers. You can rotate up or down from there.
Late-stage startups and scale-ups
Stripe, Airbnb, Notion, Figma stage. Smart-casual but skewed casual. Engineers in t-shirts and chinos, or t-shirts and jeans. Designers in slightly more curated outfits. Operations and sales in business-casual. Day one as an engineer: dark t-shirt or henley, chinos or dark jeans, clean sneakers. Avoid the suit voice.
Enterprise tech (IBM, Oracle, Salesforce types)
This is the only segment where the dress code visibly skews business-casual. Even here, in pure engineering roles, t-shirts and jeans are common. Customer-facing roles (sales engineers, solution architects) lean more formal. Day one as a software engineer at one of these: button-down (no tie), dark trousers or chinos, leather sneakers or low-key dress shoes. Slightly more formal than the rest of tech, but still nowhere near a suit.
Remote-first companies (yes, this matters)
You'd think remote means it doesn't matter. It does, because your first day usually involves a video call where the camera is on. The visible-from-the-shoulders-up dress code is "looks intentional but casual." A solid color t-shirt or light pullover with no busy graphics. Avoid: pajama-looking henleys, white t-shirts that wash out on camera, and anything you'd be embarrassed to be screenshotted in.
How to Read the Dress Code Before Day One
Don't ask HR what to wear. They'll tell you something safe and unhelpful like "smart casual." Here are the actual signals.
Check the Glassdoor photos
Most tech companies have employee-uploaded Glassdoor photos showing the office, sometimes with people in them. This is the truest representation of what people actually wear. Five minutes on Glassdoor will tell you more than any HR email.
Look at the engineering team on LinkedIn
Find your future teammates and your future manager on LinkedIn. Look at their profile photos and any conference photos they've been tagged in. People wear what they normally wear in those photos. If everyone is in dark t-shirts, that's the uniform.
The onsite interview tells you everything
If you interviewed onsite (or did even a virtual loop), pay attention to what your interviewers wore. Engineers usually interview in what they wear to work, not a special outfit. According to a 2023 Hired developer survey, 71% of software engineers say their company has a casual or no dress code. The interviewers were probably calibrated to whatever that company's normal is.
If you got an offer and you're still unsure, the lowest-cringe option is to email your hiring manager something like: "Quick question, what's the typical dress code for engineers? Trying not to overdress on day one." Most managers find this charming. Some will say "wear whatever you want." Both answers are useful.
The Default First-Day Outfit (Works at 80% of Tech Companies)
If you've done zero research and you're reading this an hour before bed on Sunday night, this is the safe default.
Top: a plain dark t-shirt or henley
Solid color (black, navy, charcoal, dark heather grey). No graphic, no logo, no clever joke. Save the personality shirts for week two. You haven't earned the right to wear the Testing In Prod Street Neon Shirt yet, but you will. A henley is a good middle ground: slightly more intentional than a t-shirt, still casual enough to not feel overdressed.
Bottom: dark jeans or chinos
Dark, clean, not distressed. No rips, no fading at the knees, no logos. Chinos are slightly safer if you want to skew toward "I took this seriously" without going formal. Dark jeans are slightly safer if your company's whole vibe is laid-back. Either works.
Layer: a zip-up or unstructured blazer
Optional but recommended for two reasons: offices are aggressively air-conditioned, and a thin layer makes any outfit read as "intentional" instead of "thrown together." A dark zip-up hoodie works at most startups. An unstructured blazer in dark grey or navy works at scale-ups and enterprise. Avoid: bright colors, bold patterns, anything that announces itself.
Shoes: clean sneakers or minimal leather
White or off-white sneakers that have been worn before but aren't beaten up. Or low-key leather sneakers in black or brown. No dress shoes (you'll look out of place). No brand-new sneakers you haven't broken in (foot pain on day one is brutal). No sandals (some offices forbid them, all offices judge them).
What NOT to Wear on Your First Day
The most common first-day mistakes are overcorrections from people who have only been to job interviews and dressed-up events before.
The overdressed mistake
Wearing a suit to your first day at a tech job, even a "tech-y" suit, makes you look like you have no idea what tech work looks like. Your future teammates will silently judge you, and you will spend the rest of week one trying to make up for it. According to a 2024 Stack Overflow Developer Survey, the global majority of professional developers describe their work environment as "casual" or "very casual." Showing up dressed for a different industry signals misalignment.
The brand-new outfit mistake
The worst first-day outfit is one you bought specifically for the first day and have never worn before. The clothes don't sit right, the shoes give you blisters, and you spend the day adjusting your collar instead of focusing on onboarding. Wear something you already own and feel comfortable in. If you must buy something new, wear it for at least a few hours over the weekend so you know how it sits.
The statement piece mistake
Your first day is not the day to wear the Breaking Prod On A Friday Shirt or the loud sneakers or the patterned button-up. You haven't earned the social capital yet. Statement pieces work after people know who you are. On day one, you're a stranger, and a strong outfit signal lands as "trying too hard." Wait two weeks. The shirts will be more fun once people are in on the joke.
When to Show Personality (and When to Wait)
Week one is about reading the room and not making waves. Week two onwards is about establishing your personal style within the room you've now read.
The graphic-tee strategy works extremely well at most tech companies, but the timing matters. Show up to your first standup with a developer-humor shirt and nobody knows yet whether you're someone they want to vibe with or whether you're trying. Show up to your fourth standup with the same shirt and it's an in-joke between you and the team.
The same applies to bolder fits, statement sneakers, and anything that requires a beat to explain. None of it is forbidden in tech. All of it is just better deployed once people have context for who you are.
If you want to signal personality on day one without overcommitting, the t-shirt graphic is the lowest-risk option. Pick something so subtle that it doesn't read as a graphic from across the room. Let people get close enough to see it before they have an opinion.
Frequently Asked Questions
What should I wear on my first day at a tech job?
The safe default at most tech companies is a plain dark t-shirt or henley, dark jeans or chinos, and clean sneakers. Add a zip-up hoodie or unstructured blazer for layering. Avoid suits, brand-new outfits, and anything with a bold graphic. Save personality pieces for week two. Solid colors and broken-in shoes are the goal. The vibe is intentional-casual, not nervous-formal.
Is there a dress code at tech companies?
Most tech companies have no formal dress code, but they do have unwritten norms. Big tech and startups skew aggressively casual: t-shirts, jeans, hoodies. Enterprise tech (IBM, Oracle, Salesforce) skews slightly more business-casual but still nowhere near a suit. Remote-first companies care about what's visible on camera (shoulders up). The only way to know your specific company's norm is to look at engineering team photos on LinkedIn or Glassdoor.
Should I wear a suit on my first day at a tech startup?
No. Wearing a suit to a tech startup signals that you don't understand the culture, which is exactly the opposite of the impression you want to make on day one. Even at the most polished startups (Stripe, Airbnb, late-stage scale-ups) engineers wear t-shirts and chinos. Save the suit for client meetings where suits are expected, or the post-IPO photo if you're lucky. For day one as an engineer, a suit is overdressed.
What do software engineers wear to work?
The honest answer is t-shirts, jeans or joggers, and sneakers. According to the 2024 Stack Overflow Developer Survey, the vast majority of professional developers work in casual environments. Hoodies are common, especially among engineers who arrive early or stay late. Free company swag dominates many engineers' wardrobes. Senior engineers tend to dress slightly more intentionally than juniors, but the dress code differential between levels is small.
Is it okay to wear a graphic t-shirt on day one?
Technically yes, but strategically no. On day one you have no social capital yet, and a graphic tee with a clever developer joke can read as trying too hard before anyone knows who you are. Save it for week two. By then your team will have context for who you are, and the same shirt becomes part of your identity instead of a first-impression risk. If you must wear something with character, pick something so subtle it requires people to lean in.
What shoes should I wear on my first day at a tech company?
Clean sneakers, broken-in. White or off-white canvas sneakers, low-key leather sneakers, or comfortable trainers all work. Avoid: brand-new sneakers (blisters), dress shoes (out of place at most tech companies), sandals (often forbidden, always judged), and worn-out shoes that look like you didn't make any effort. The shoes should not be the most noticeable thing about your outfit, but they shouldn't undercut it either.
By Emcy
Once you've read the room and you're ready to bring some personality into the office, browse the Code Culture tech-nerds collection for week-two and beyond. Insider developer references, dark forgiving colors, and the kind of pre-shrunk ringspun cotton that holds up through long sprints, all-hands, and the occasional accidental coffee spill.