You're an Artisan
You could operate as a Builder. You have the experience and judgement to direct agents at a high level and move quickly. But in your domain, speed isn't the priority. Precision is.
The gap between what AI produces by default and what the work actually demands is still wide enough that staying close to the code remains the most effective way to work.
What this means
Your expertise has moved beyond what AI can reliably handle in your domain. Whether it's database performance, rendering, a specific framework, or another niche where the average output still falls short, you've developed the depth to spot subtle issues before anyone else does.
That expertise didn't come from avoiding AI. It came from working with it closely enough to understand where it breaks. Seeing those failures firsthand is exactly what makes you good at directing it.
What you actually do
- Work within your IDE, watching AI write code and course-correcting at a granular level rather than reviewing output after the fact.
- Lead AI toward the right decisions rather than accepting default patterns, because in your domain the defaults compound into real problems.
- Act as the canary in the coalmine: you feel codebase friction before it becomes visible to others, and you surface it to Multipliers rather than absorbing it quietly.
- When you see code causing pain, you improve it, and when you find an approach that works, you turn it into a reusable pattern the team can build on.
- Defend your worldview when it's challenged. Staying close to the code is a deliberate decision, and you can articulate why the tradeoff is worth it in your area of work.
What you don't do
- Accept AI output without scrutiny. The whole value of this archetype is the judgement you apply to what the AI produces, and switching that off defeats the purpose.
- Hold up velocity in the name of perfection. You know the difference between a refactor that matters and one that can wait, and you ship accordingly.
- Act with ego when you catch issues. The point is a better codebase, and pragmatism gets you there faster than being right.
How you use AI
You work inside your IDE with AI writing alongside you, and you review what it produces at a level of detail most engineers have moved away from. You're watching for whether the code is correct in the ways that matter in your domain, which is a more demanding standard than just making it run. When it drifts, you catch it early and correct it in real time rather than letting small problems accumulate into structural ones.
Where you shine
- Feature development that requires precision, where a Builder's approach would introduce risk that compounds over time.
- Maintaining code quality in your area of specialisation, and catching drift before it becomes someone else's emergency.
- Levelling up the team's understanding of your domain by turning what you know into patterns others can use.
Your blind spots
- The precision that makes you effective can tip into over-engineering if you're not careful. Not every part of the codebase needs Artisan-level attention, and knowing when Builder-level output is genuinely good enough is part of working well with the rest of the team.
- Because you feel friction early, there's a temptation to absorb it rather than surface it. Flagging problems to Multipliers is part of the job, not an admission that something went wrong.
- Worldview defence has a shadow side here too. When a Builder ships something that wouldn't meet your standards in your domain, the question worth asking is whether your standards are the right ones to apply, or whether the tradeoff they made was reasonable given the context.
Where you might be heading
Artisans who develop an interest in how their patterns and approaches could benefit the broader team are building toward Multiplier territory. The depth that makes you effective in your domain is exactly what makes your guardrails and tooling valuable to everyone else.
Artisans who broaden their scope, moving from deep expertise in one area toward fluency across more of the stack, are building toward Builder. The precision stays, but the abstraction level rises.
Neither shift is necessary. Some of the most valuable engineers a team has are the ones who go deeper and deeper in a specific area for years, and the work they produce reflects it.
Explore the other archetypes
Not sure this one fits? Read about the others and see what lands.
- The Multiplier: Makes everyone around them faster. Uses AI to think bigger: prototyping patterns, setting guardrails, and extending team capability instead of just personal output.
- The Builder: Treats AI as an execution engine. Operates one level up from code, steering agents rather than writing syntax.
- The Explorer: Reads systems from the outside in. Uses AI to answer their own questions about the codebase instead of pulling other people off product work.
- The Apprentice: Co-creates with AI through dialogue. Builds judgement one prompt at a time, and ships only what they can defend.
Or go back to the AI Engineering Archetypes overview to see the full picture.