It is a Tuesday, you are three coffees into a stubborn bug, and your manager appears at your shoulder walking a client toward your desk for an unplanned hello. There is no time to change. Whatever you put on this morning is now what the client thinks a developer at your company looks like.
This is the unannounced meeting that every developer in Koramangala, HITEC City and Hinjewadi eventually has. The code you ship is invisible in that moment. The collar is not.
What the client decides in ten seconds
First impressions form fast, faster than feels fair. Research summarised by the Association for Psychological Science found that a tenth of a second is enough to form an impression of a stranger from their face. Clothing is not the face, but it is in the same glance, part of the snap read before you have said a word.
And that read sticks to your work. A study led by a VCU professor found that work colleagues judge you partly by how you dress, which in turn shapes their evaluation of your performance and even their willingness to help you. A client meeting you for the first time is running the same quiet calculation.
One notch up, and what the research supports
The convention everyone repeats is to dress one notch above the room. It is sound advice, and it is more defensible than the famous studies behind it.
Take enclothed cognition, the idea that clothes change how you think, not only how you look.
What holds up better is subtler. Researchers found that students in more formal clothing leaned toward abstract processing, the big picture rather than the detail, and, tellingly, that formality was judged relative to peers. You are not formal in the abstract. You are formal compared with the room. On a developer floor where the baseline is a tee, a collar is already one notch up.
The hoodie problem
The hoodie is not the enemy. Carelessness is. The research on dressing against the grain draws a sharp line: when the deviation looks deliberate, it can raise status; when it looks accidental, it reads badly.
"When the deviant behavior appears to be deliberate, it can lead to higher rather than lower status and competence inferences."
Association for Psychological Science, on the red sneakers effect
A clean, plain layer worn with obvious intent can pass. A washed out hoodie with a frayed cuff cannot, because it reads as an accident rather than a choice. The safe rule for a client day: if you want to dress down, make everything else on you look considered, so the casual piece reads as deliberate.
A default with three tiers
You do not need a different wardrobe. You need three settings and the sense to know which one the day calls for.
| Setting | Top | Bottom | Shoes |
|---|---|---|---|
| At your desk | Plain tee or polo | Chinos or dark denim | Clean trainers |
| Internal demo | Polo or shirt | Chinos | Leather trainers or loafers |
| Client on site | Shirt, add a shacket | Trousers | Leather shoes |
The polo does the heavy lifting in the middle. It keeps the comfort and the short sleeve of a tee while reading a notch more put together, which covers most internal client moments without a change of clothes. For the step up, a shirt, or a shirt with a shacket over it, handles almost any client meeting without tipping into costume.
A kit for the dev who meets clients
Keep it small and keep it at your desk if you have to. Two polos in neutral colours. One shirt that fits across the shoulders. A shacket for the layer and the step up. One pair of leather shoes that are not the ones you crossed a flooded road in. That is enough to turn an ambush meeting into a non event.
The goal is not to look like a banker. It is to look like someone who knew the meeting mattered, even when you did not know it was coming.