Independent (Founder, Indie Hacker, Consultant, Fractional CTO, Advisor, Educator)
You own the demand side as well as the work: nobody hands you the problem or the budget.
The independent path covers founding a company, building small products alone, consulting, fractional CTO and advisory work, and teaching. What unites them is that you carry the whole loop yourself: finding the problem, deciding it is worth solving, getting someone to pay for it, delivering, and getting paid. Engineering becomes one part of a job that is at least as much selling, positioning and judgement about where to spend limited time.
What this path actually involves
Day to day you split your time between the work someone is paying for and the work that creates the next payment. That means conversations with prospective clients, writing that establishes what you are known for, scoping and pricing, invoicing and chasing money, alongside the actual delivery. Technical decisions become commercial decisions: the cheapest thing that solves the client's problem usually beats the best-engineered one, and you feel the cost of every hour directly. Nobody reviews your plan, and nobody notices if you spend a month on something that turns out not to matter.
What it does not mean
Independence is not primarily an escape from bad management. If the pull is "no more politics, no more meetings, no more manager", the reality is worse on all three: you now manage clients whose incentives differ from yours, you sell in meetings you cannot delegate, and the manager becomes you - with less feedback and nobody to escalate to. It is also not more freedom by default; early on you have less, because income depends on the next conversation. And it is not a path to technical purity: the market pays for problems solved, not for elegant systems.
Typical responsibilities
- Finding and qualifying demand: knowing who has the problem, and whether they will pay to fix it.
- Positioning yourself narrowly enough that people know when to call you.
- Scoping, pricing and contracting work, including saying no to badly shaped engagements.
- Delivering enough value that clients renew or refer you, which is the real growth engine.
- Running the business side: cash flow, taxes, invoicing, pipeline, insurance, and time off you have to fund yourself.
- Managing your own attention and standards with no external structure holding them up.
Skills that matter
What changes from a strong senior engineer role
As a senior engineer, someone else validated that the work mattered and guaranteed your salary while you did it. Independently, both of those become your job, and both come before the engineering. Feedback stops arriving as reviews and performance conversations and arrives as revenue, silence or churn - much slower and much blunter. The scarce resource shifts from technical difficulty to attention and trust.
Signs you may enjoy it
- You already do the unpaid parts - writing, speaking, helping people, building small things - without being asked.
- Being told what to build frustrates you more than not knowing what to build.
- You find the commercial question genuinely interesting, not a distraction from the real work.
- You are comfortable being visibly wrong in public and adjusting.
- Uneven, unstructured weeks suit you better than a predictable rhythm.
Signs you may dislike it
- Selling feels like something to be endured rather than part of the craft.
- Irregular income affects your sleep, your relationships or your appetite for risk more than you expected.
- You miss colleagues, code review, and having people who care about the same system you do.
- Without external deadlines and accountability, your standards drift.
- You want to build deep, long-lived systems, and client work keeps you in the first six months of everything.
Common misconceptions
- That it is mainly a way out of a bad manager or a bad company, when it is a change of job description entirely.
- That the best engineer gets the clients; distribution and trust do, and both are built years before you need them.
- That you need a finished product or a large audience to start - most independent income begins as a single paid engagement.
- That it is irreversible; plenty of people move between employment and independence more than once.
Where it typically leads
Independent work tends to fork. Some people grow it into a product or a company with employees, others keep it deliberately small and high-margin, and many use a few years of it as leverage back into a senior in-house role - Head of Engineering, CTO - with a far better understanding of commercial reality. Consulting and advisory work also compounds: a narrow reputation becomes more valuable the longer you hold it.
How AI is changing this role
For independents, AI-assisted engineering has changed the economics of delivery most sharply. One person can now credibly build and maintain more than a small team could a few years ago, which makes small products and solo consulting more viable - and clients know it, so hours-based pricing for work an agent can largely do is under pressure. What sells is judgement: choosing the right problem, designing something that survives contact with real users, and verifying what was generated. Being fast at producing code matters less than being trusted to say what should exist and what should not, and clear architectural thinking is now what keeps an AI-heavy codebase maintainable by one person.
Experiments to run before deciding
Sell one small thing before you leave anything
8-12 weeks
- Check your employment contract and your employer's side-work policy before you take money, so the engagement sits cleanly outside your job rather than being something you have to hide.
- Write down, in one sentence and without naming any technology, one specific problem you could solve for a specific kind of company.
- Have ten conversations with people who have that problem, asking about their situation rather than pitching.
- Make one paid offer, however small - a review, an audit, a workshop, a fixed-scope build - and put a real price on it.
- Deliver it in your own time, to your own standard, and record every hour it actually took.
- Ask the buyer what they would have paid, what nearly stopped them, and who else has this problem.
Then ask yourself
Did you find the selling and scoping interesting in itself, or were you only really alive once the technical work started?
Build in public for one quarter
10-12 weeks
- Choose one narrow subject you want to be known for, and publish on it every week for twelve weeks.
- Ship one small tool, template or open source utility related to it that someone can use today.
- Track only two numbers each week: how many people started a conversation with you unprompted, and how many of them came back with a second question or referred someone else.
- Take at most two calls a week from those conversations, and note after each one whether you actually wanted to be on it or took it out of obligation.
Then ask yourself
Twelve weeks in, was the visibility work energising and repeatable, or did it feel like a tax you were paying to avoid a job?
Run an internal engagement as if you were external
8-10 weeks
- Take on a piece of work for another team in your company and treat them as a client.
- Write a one-page proposal first: their problem, the outcome, what is out of scope, how long, and how you will both know it worked.
- Refuse scope creep explicitly at least once, in writing, with an alternative attached.
- Close it with a short written handover and ask them whether they would hire you again for this.
Then ask yourself
Was defining and defending the scope of your own work satisfying, or did you miss having someone else carry that responsibility for you?
Worth reading
The Mom Test - Rob Fitzpatrick
The most useful book on talking to potential customers without fooling yourself.
Company of One - Paul Jarvis
A sober case for staying small on purpose rather than growing by default.
Million Dollar Consulting - Alan Weiss
On pricing by value rather than by the hour; immodest in tone, practical in substance.
Shape Up - Basecamp
Useful for shipping against a fixed appetite when nobody else is setting your deadlines.
Not sure whether this path is closest to you?
Take the Career CompassHelp improve this page
If you have worked in this role and something here is inaccurate, incomplete or out of date, tell me. Suggestions are reviewed before anything changes.