Are You a Builder or a Consumer With Technical Skills?

There’s a question worth asking yourself early in your career — and worth revisiting every few years after that:

Are you actually into tech? Or are you a consumer who happens to have technical skills?

Neither is wrong. But confusing one for the other leads to a lot of unnecessary suffering, misdirected effort, and careers that feel vaguely hollow even when the money is good.

What the Difference Actually Looks Like #

A builder is someone who, when they encounter a problem, instinctively thinks about how to make something that solves it. They get genuine satisfaction from the process of construction — not just the result. They tinker. They stay up too late on side projects not because they should but because they want to. The craft itself holds their interest.

A technically-skilled consumer is someone who is good at using technology — often very good — but whose real interests lie elsewhere. They’re smart, capable, and can do the job, but the technology is a means to an end. They’re not staying up late thinking about database indexes. They’re using technical skills to serve some other goal: financial stability, a specific product they believe in, solving a business problem, working in an industry they care about.

Here’s the thing: both of these people can have excellent software engineering careers. The mistake is when a consumer tries to perform being a builder, or when a builder doesn’t notice that they’re in a job that requires a consumer.

Why This Question Matters for Your Career #

It changes what kind of work energizes you #

Builders tend to thrive in roles with significant technical latitude — research, open-ended platform work, early-stage startups, or roles where the problem itself is genuinely hard and unsolved. They get frustrated in environments where the technical work is rote and the interesting problems are upstream in product or business.

Consumers often do their best work when the technology is in service of something they care about — a specific product, a specific industry, a business problem they find genuinely interesting. They can be extraordinary at tech-adjacent roles: product engineering, technical product management, solutions engineering, developer relations.

If you’re a consumer in a builder’s job, or vice versa, you’ll feel it. The work will be fine but not satisfying. You’ll watch other people get animated about things that leave you cold.

It changes how you should grow #

Builders should invest in technical depth. Going genuinely deep on something — distributed systems, compilers, mobile performance, whatever the domain — pays dividends. The craft rewards serious practitioners.

Consumers should invest in breadth plus domain knowledge. Understanding enough of the stack to be dangerous, combined with deep expertise in the business domain or product space, is a legitimately powerful combination. Many of the most effective engineers at product companies are technically skilled consumers who understand the business better than anyone on the product team.

It changes how you should market yourself #

A builder’s resume looks like a trail of things they made. Side projects, open source contributions, technical writing, conference talks, deep technical expertise in specific areas. The portfolio is the proof.

A consumer’s most compelling career story is about outcomes — the product that shipped, the business problem that got solved, the cross-functional influence they had. Technical skills are the enabler, not the headline.

The Trap: Pretending to Be Something You’re Not #

The tech industry has a cultural bias toward builders. Open-source contribution, side projects, talking about technology as a hobby — these are the signals that get you hired at certain companies and respected in certain circles.

This creates pressure on technically-skilled consumers to perform builder behavior. To claim enthusiasm they don’t have. To spend weekends on side projects that bore them. To feel like they’re failing at being a developer because they don’t want to spend their evenings reading release notes.

This is exhausting and unnecessary. The industry is full of people who got into tech for practical reasons — good pay, transferable skills, intellectual engagement without needing to be obsessive about it. There’s nothing wrong with that. You don’t have to love Hacker News to be a good engineer.

Conversely, builders who end up in jobs that don’t let them build anything — pure maintenance work, heavy process bureaucracy, layers of approval before a line of code gets written — will be quietly miserable even if the salary is great. Recognizing this early saves years.

How to Figure Out Which One You Are #

Some honest questions:

• When you have free time, do you find yourself building things? Or do you find yourself doing something completely unrelated to technology?
• What do you get actually excited about at work — the technical problem or the thing the technical solution enables?
• If you won the lottery tomorrow, would you keep coding? Would you keep building the same kinds of things you build now?
• When a new technology comes out, is your first instinct curiosity about how it works — or curiosity about what you could do with it?

There are no right answers. But the honest ones are useful.

The Hybrid #

Worth noting: most experienced developers are some blend. Pure builders who have no interest in outcomes are usually frustrated eventually — code in service of nothing gets old. Pure consumers who have no technical interest at all struggle to keep up with the craft.

The most effective senior developers tend to be builders who developed genuine interest in the product or domain over time, or consumers who went deep enough on the technical side that they can hold their own in any engineering conversation.

But knowing which end of the spectrum you lean toward — and being honest about it — is the starting point. From there, you can point yourself toward work that fits, market yourself honestly, and stop measuring yourself against a version of a developer career that was never going to make you happy.

The industry needs both. Know which one you are, and stop apologizing for it.