You're going to be in the same outfit for 36 hours. You're going to sleep in it, sweat in it, spill ramen on it, and demo in it at noon. The hackathon dress code isn't a dress code, it's a survival decision.
Most "what to wear to a hackathon" advice misses this. They write it like it's a fashion problem. It isn't. It's a logistics problem with a fashion side effect.
This is the guide written by someone who has done it the wrong way enough times to have opinions.
Key Takeaways
- Comfort beats style at every hackathon, including ones with cash prizes and recruiters present
- You will sleep, sweat, and spill in the same outfit for 36 hours, plan accordingly
- According to Major League Hacking's 2023 community survey, 85% of student hackathon participants stay on-site for the full event, sleep included
- Layers matter more than fits, the AC will be set to "meat locker" in every venue
- Recruiters at hackathons judge code, not clothes, but they do remember the t-shirt
- Joggers, not jeans, the moment you sit cross-legged on the floor at 3am you will understand
- Skip the new sneakers, blisters at hour 12 are not recoverable
The Hackathon Reality Check (Why Comfort Wins)
A hackathon is not a job interview. It is not a tech conference. It is not even a long workday. It is closer to camping with laptops, and the people who treat it like camping outperform the people who treat it like networking.
You're sleeping in this
The thing nobody tells you about hackathons is that you don't usually go home. According to Major League Hacking's 2023 community survey, 85% of student hackathon participants stay on-site for the full event. That means you sleep there. Sometimes on a beanbag. Sometimes under a table. Sometimes upright in a chair while your teammate does the next sprint. Whatever you wore in is what you wear out, including through whatever sleep you manage to get.
So the first question to ask about your outfit is not "does this look good," it is "would I be okay sleeping in this." If the answer is no, change before you arrive.
The bathroom situation
You are not getting a real shower for the duration. Most venues have one bathroom per floor and 200 hackers competing for it. The smart move is wearing materials that handle being worn for two days without becoming a biohazard. Cotton and polyester blends are forgiving. Pure cotton holds smell. Athletic fabrics are best, but most developers don't own them, so cotton blends are the realistic answer.
Bring a clean t-shirt for demo day if you're presenting. Change at hour 30 if you can. Otherwise, accept what you're working with and apply deodorant aggressively.
The AC will hate you
Every hackathon venue runs the air conditioning at temperatures that suggest the organizers have a personal grudge against humans. By 2am the room will feel like a server farm. Bring layers. Always bring layers. The single most common mistake at a first hackathon is showing up in a t-shirt and freezing for 36 hours straight.
The 36-Hour Outfit Formula
The formula is base layer plus mid layer plus correct bottom plus thoughtful feet. Each piece earns its place by surviving the full timeline.
Base layer: a shirt you can actually sweat in
Your base layer is whatever t-shirt you'd be willing to wear for two days. The best hackathon t-shirts have three properties: dark color (hides spills), insider reference (starts conversations during the food line), and a fabric that doesn't pill or stretch out by hour 24.
A graphic tee with a developer joke does double duty. It signals competence without saying anything, and it gives someone a reason to walk up to your table. The I Test In Prod Shirt is a personal favorite because the joke lands instantly with anyone who has ever shipped code, and the dark color forgives a lot of midnight pizza.
Avoid: white shirts, anything you'd be sad to ruin, anything that requires a specific fit to look right. The hackathon will not be kind to a tailored fit.
Mid layer: the hoodie that saves you at 3am
This is non-negotiable. A zip-up hoodie or full-zip fleece is the most important piece of clothing you bring to a hackathon. Zip-up specifically, because at hour 6 you'll be hot and at hour 18 you'll be cold and you don't want to be pulling a pullover over your head every two hours.
Solid color, dark, no graphics on the front. You want something that layers cleanly over whatever t-shirt you're wearing for demo day photos. Pockets are a real consideration. You will accumulate dongles, badges, snack wrappers, and a phone you forgot to charge. Hoodie pockets are the only reason any of this gets back to your bag.
Bottom: joggers, not jeans (trust me)
Jeans at a hackathon are a punishment you've decided to inflict on yourself for 36 hours. They don't breathe, they bunch up when you sit cross-legged on the floor (you will sit cross-legged on the floor), and the rivets dig into you when you slouch in a chair for the eighth hour straight.
Joggers, sweatpants, or athletic-cut chinos. Drawstrings are good because you will eat irregularly and your waistline will fluctuate. Side pockets matter. Cargo pockets are unironically useful for hackathon-specific reasons (charger cables, USB sticks, sponsor merch you don't want to carry).
Feet: socks matter more than you think
Hackathon foot count is real. Even though you're sitting most of the time, you will walk to the food table, the bathroom, the sponsor booths, the coffee station, the other team's table to ask if their build is broken too. Cumulative steps over 36 hours easily clear 10,000.
Comfortable sneakers you've already broken in. Not new ones. Bring a second pair of socks if your event has a sleep area, your feet will thank you. Sandals or slides are acceptable at very informal hackathons but not at any event with sponsors present.
What NOT to Wear to a Hackathon
The hackathon mistakes are usually overcorrections from people who have only been to job interviews and tech conferences before.
The suit mistake
Wearing a suit to a hackathon makes you look like you don't know what a hackathon is. Every recruiter present already assumes you're a developer. They're not impressed by formal wear, they're slightly worried that you might have shown up to the wrong event. Save the suit for the post-hackathon recruiter follow-up if you get one.
The brand-new-sneakers mistake
Brand new shoes plus 36 hours plus walking around equals blisters that will distract you for the entire second half of the hackathon. If you bought new sneakers specifically for this event, leave them at home and wear something you've already worn for at least 20 hours of walking. Hackathon foot pain is real and unrecoverable mid-event.
The statement outfit mistake
Wearing something specifically designed to get noticed (loud patterns, brand-heavy streetwear, anything that requires explanation) reads as trying too hard at a hackathon. The vibe is genuine and self-deprecating. Save your boldest fits for the demo day after-party. The Breaking Prod On A Friday Shirt is the right kind of statement, the kind that says something true about you without trying.
Hackathon Packing Checklist (Beyond Clothes)
Clothes are 30% of the packing problem. The other 70%:
- Laptop and charger (the charger is the part most people forget)
- Phone charger, ideally with a long cable because outlets are far
- Headphones, over-ear if you can, because your team will be loud
- A reusable water bottle, free water beats free soda for sustained focus
- Deodorant, because you will need it
- A change of socks, see above
- Toothbrush, toothpaste, face wash (basic hygiene matters at hour 24)
- A small backpack you can lock or keep with you
- Energy bars or snacks you actually like (sponsor food fatigue sets in fast)
- Cash for the times the food trucks don't take cards
- A printed copy of your idea or a sketch on paper, because sometimes wifi dies
What Recruiters Actually Notice (and Don't)
If you're at a recruiter-heavy hackathon, this section matters. According to a 2024 Stack Overflow Developer Survey, 41% of developers say they got a job lead through a hackathon or community event. So the question of what recruiters see is reasonable.
What recruiters notice: your code, your demo, how you talk about the project, and whether you can explain your technical choices without faking confidence. They notice if you're working as a team or carrying it alone. They notice if you stayed for the full event.
What recruiters do not notice: the brand of your hoodie, whether your jeans match your shirt, whether you've showered (everyone is in the same situation). The most they'll notice about your clothes is the t-shirt graphic, and only because it's at eye level when you're sitting at a laptop.
The t-shirt is the one wardrobe choice with any networking value at a hackathon. A specific developer reference (one only people who have shipped code in production would understand) functions as ambient signaling. It gives a recruiter or another hacker a free conversation opener: "where did you get that shirt." That conversation has, more than once, led to the kind of job offer that bypasses the standard application funnel.
So the optimization is: wear something comfortable that you wouldn't be embarrassed to be photographed in, and put your one piece of "personality" into the t-shirt graphic. Everything else should fade into the background.
Frequently Asked Questions
What should you wear to a hackathon?
The short version: a graphic t-shirt with developer humor, a zip-up hoodie, joggers or athletic pants, and broken-in sneakers. Bring layers because the air conditioning will be aggressive. Choose dark colors that hide food stains. Avoid jeans, new shoes, and anything formal. The goal is comfort for 36 straight hours including sleep, not impressing anyone with fashion.
What do you wear to your first hackathon?
For your first hackathon, lean conservative on the outfit and just copy what experienced hackers wear: a t-shirt you don't mind sleeping in, a hoodie, joggers, and sneakers. Bring a backup t-shirt for demo day. Don't try to make a statement with your clothes. The goal is to disappear into the crowd visually and stand out with your project. Save fashion experiments for events where you're not also competing.
Is there a dress code at hackathons?
There is no formal dress code at any hackathon. The unofficial dress code is "casual enough to sleep in." Sponsor t-shirts, free conference merch, and unbranded hoodies dominate the visual landscape. The only soft expectation is that you've showered before arriving and aren't wearing something that explicitly violates the venue's rules (no offensive graphics, closed-toe shoes if the venue requires them, etc).
Should I dress up for the demo at a hackathon?
A clean fresh t-shirt and a brushed-out hoodie is the upper bound for hackathon demo dress code. You're presenting in a giant room where everyone has been awake for 36 hours and looks tired. Showing up in business casual makes you look out of place, not professional. The signal you want to send is "I just built something and I'm proud of it," not "I dressed up for this."
What shoes should I wear to a hackathon?
Comfortable sneakers you've already broken in are the only correct answer. New shoes will give you blisters by hour 12. Dress shoes are uncomfortable for 36 hours of sitting. Sandals are fine for very casual student hackathons but not for events where sponsors and recruiters are walking around. Bring a backup pair of socks, and if you can swing it, change them at hour 18 or 24. Foot fatigue is one of the most underrated hackathon problems.
Do recruiters at hackathons judge what you wear?
Recruiters at hackathons judge your code, your demo, and how you talk about your project. They do not judge your hoodie or your sneakers. They do, however, register your t-shirt graphic if you're wearing one with a clever developer reference, because that's at eye level when you're sitting at a laptop. A great insider t-shirt has, more than once, started the conversation that led to a job offer. Everything else about your outfit is invisible to them.
By Emcy
When you find the t-shirt that survives a hackathon, you don't have to think about it again. Browse the Code Culture tech-nerds collection for shirts with insider references, dark forgiving colors, and the kind of pre-shrunk ringspun cotton that handles 36 hours of pizza, code, and ramen.