7 Roles of a Developer
A solo developer wears 7 hats. The skill is knowing which one you're wearing — and when to switch.
Here is something they don't tell you when you start learning to build software: building an app is not one job. It is seven jobs, all done by the same person.
When a large technology company builds a product, these seven roles are filled by different teams — sometimes hundreds of people. A product manager decides what to build. A UX team figures out how it should feel. A database team designs the data structure. Frontend engineers build what you see. Backend engineers build the logic underneath. A DevOps team keeps everything running. A QA team tries to break it before real users do.
When you are a solo developer — which is what you are becoming — you do all of it.
That sounds overwhelming. Here is the good news: you do not do all of it at the same time. You wear one hat at a time, and you switch deliberately.
The 7 Hats
| # | Role | What they decide | Excel analogy |
|---|---|---|---|
| 1 | Product Owner | WHAT to build, what is in scope, what counts as done | The CA partner who decides what the model should show |
| 2 | UI/UX Designer | How it looks, how users move through it | Who decides the pivot layout, formatting, color coding |
| 3 | Data Architect | Database structure — tables, columns, relationships | Designing the raw data sheet structure before any formula |
| 4 | Frontend Developer | What users see and interact with | Building the formatted client-facing sheet |
| 5 | Backend Developer | Logic, business rules, integrations | The formulas, VBA macros, data connections |
| 6 | DevOps / Infrastructure | Deployment, environments, availability | Making sure the file is always accessible and backed up |
| 7 | QA / Tester | Breaking things before users do | Stress-testing the model with wrong inputs |
Why This Matters More Than You Think
This is the section most developers skip — and the section most responsible for rebuilding from scratch.
The most expensive mistake in software is not a bug. It is building the wrong thing well.
And the second most expensive mistake is building the right thing in the wrong order.
Both of these mistakes happen because someone was wearing the wrong hat at the wrong time. A developer who jumps straight to building screens (Frontend hat) without first deciding what the database looks like (Data Architect hat) will eventually have to tear the screens apart and start over. A developer who keeps building features (Frontend hat) when the client is actually asking a product question (Product Owner hat) will ship something technically correct that solves the wrong problem.
The failure mode is not incompetence. It is not knowing which hat you are wearing.
The Most Critical Hat
The Product Owner role is the most important and the most neglected.
With Claude Code, the other six roles are heavily AI-assisted. Claude can write React components. Claude can design database schemas. Claude can write deployment scripts. Claude can write tests.
But Claude cannot decide what your client actually needs. It cannot tell you which feature to build next. It cannot negotiate scope. It cannot read the room in a client meeting and understand what is really being asked.
The Product Owner role is 100% human judgment. It cannot be outsourced to AI.
This is why we spend time on it first.
What You Will Learn in This Module
Each section in this module covers one role in depth:
- What decisions belong to this role
- The Excel analogy that makes it concrete
- The signals that tell you it is time to put on this hat
- What goes wrong when you skip this role
- How Claude Code helps you in this role
- A mindset shift prompt to consciously enter the role
The final section — The Hat Switch Protocol — gives you a practical decision tree for real projects: which hat to wear, in what order, and the most common traps that cause developers to rebuild from scratch.
A Note on AI and These Roles
Claude Code is an extraordinary assistant. But you need to understand what it can and cannot do in each role.
When you are the Product Owner, Claude can help you think through tradeoffs — but it cannot make the business decision. When you are the Data Architect, Claude can suggest a schema — but you need to understand it well enough to reject a bad suggestion. When you are the QA Tester, Claude can write tests — but it tends to test the happy path. You need to think adversarially.
The goal of this module is not to make you a professional in all seven roles. It is to give you enough literacy in each role that you can:
- Know which hat you are wearing
- Give Claude Code the right instructions for that role
- Evaluate Claude's output with the right questions
- Switch hats deliberately instead of accidentally
That combination — human judgment on the right question, AI execution on the implementation — is the workflow this entire training program is built around.
Let us begin with the most important role.
Check Your Understanding
- I can name all 7 roles and give one example task that belongs to each
- I understand the correct order: Product Owner → Data Architect → Backend → Frontend → DevOps → QA
- I understand why mixing hats — designing the UI before defining the data structure — causes rebuilds
- I know that Claude Code assists all roles but cannot replace the Product Owner role