Brian Schimpf Outfit Guide: Inside the Hardware and Robotics Founders Uniform

Decoding the Brian Schimpf uniform: what it is, why it stuck, and how to translate it for engineers who write the actual code.

By Emcy, founder of Cold Culture · May 2026

Brian Schimpf dresses like a person who has lost sleep on a clean-room floor, which is to say, with deliberate practicality.

What Brian Schimpf wears

Utilitarian founder casual: dark T-shirt or collared shirt, practical jacket, jeans, and the no-frills look of someone close to engineering reviews.

The thing to notice is the repetition, not any single garment. Worn once, this is just another outfit; worn every day for a decade, it becomes a uniform with all the semiotic weight that implies: a shorthand the audience can read instantly, a refusal to spend attention on something the wearer has decided not to care about, and an asset every press photo amortises against the brand.

The hardware-founder uniform, briefly

The hardware founder dress code has roughly three components: a daily silhouette that the wearer never has to think about, a subtle quality signal (fabric, fit, or one quiet detail), and a deliberate refusal to chase fashion cycles. None of these are individually unusual; the combination is what reads as a uniform.

It is appropriately plain. In defense autonomy, the product should look engineered and the founder should look serious enough to own the tradeoffs.

In practice the dress code is enforced by repetition, not by rulebook. Spend a few months around the cohort and you'll see the same three or four base silhouettes appear over and over with small personal-quirk variations. Brian Schimpf's variation is one of the cleaner ones.

Why function beats branding in this vertical

The argument for a daily uniform is decision-fatigue plus brand consistency. Pick a silhouette once, ship it forever. Every morning that a wardrobe choice does not have to be made is a morning where attention can flow somewhere downstream. Co-founded Anduril and leads its work on autonomous defense systems, sensors, UAS, counter-UAS, and command-and-control software.

For hardware founders specifically, the look doubles as a low-key signal: serious about the work, indifferent to anything that distracts from it. The signal works precisely because so few of them sustain the discipline, the cohort talks a good game about minimalism, but you can count the people who actually wear the same five pieces for a decade on two hands.

The pushback against the daily-uniform idea is that it is a vanity move disguised as efficiency. When the "minimalist" choice is a $300+ luxury tee, the discipline reading and the brand-building reading can both be true at once.

Adjacent founders with similar wardrobes

Other hardware founders running parallel uniforms: Palmer Luckey, Adam Bry, Marc Raibert, plus Trae Stephens (more in the Hardware and Robotics Founders index).

If you want to channel the energy without copying the costume, see autonomous-systems tee for serious field software at Cold Culture.

The engineer-friendly takeaway

The literal costume is rarely the right move. The principle is simpler: a quiet, repeatable silhouette that you do not have to think about at 7am, and one piece on you with enough personality to be conversation-worthy at standup.

For developers, that usually translates to a single trusted t-shirt fit, dark jeans, sneakers you have already broken in. The piece with personality is the t-shirt graphic, because it sits at exactly the height that catches the eye on a video call, in the office cafe, or on a conference badge photo. Autonomous-systems tee for serious field software is the dev-friendly version of the same idea, same silhouette discipline, different aesthetic context.

Skip the literal recreation. The principle is portable, same silhouette discipline, same deliberate repetition, same "this is a non-decision now" energy. The specific items and price tags that made the original famous are not the point.

Frequently asked questions