> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/ai-engineering-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/ai-engineering-handbook/roles-and-teams/expert-generalist.md).

# Expert Generalist

[Martin Fowler on Expert Generalists](https://martinfowler.com/articles/expert-generalist.html)

> Inside the organisation, narrow verticals can freeze growth: UI developers, QAs, data engineers, or cloud experts seldom step outside their lanes. The growth paths map one-to-one with vertical silos: UI Engineer → Senior UI Engineer → UI Architect, or Data Engineer → Senior Data Engineer → Principal Databricks Guru. The unintended message is, “wander outside your lane and your progress stalls.
>
> We have found that encouraging people to experiment—letting them make mistakes and learn in adjacent disciplines—yields remarkable benefits. A business analyst writing code out of curiosity, a front-end engineer dabbling in DevOps, a data engineer trying product analysis: each cross-pollination broadens both the individual and the team.

## What is an Expert Generalist?

Specialists go deep in one area, whereas Generalists go broad, linking multiple domains. <mark style="color:purple;">Expert generalists</mark> combine depth and breadth. They:

* Show curiosity—always learning, exploring new domains
* Value collaboration—work with specialists, ask questions, and share knowledge
* Focus on customer outcomes—prioritise what helps users
* Favour fundamental knowledge—master patterns and principles, not just tools
* Blend specialist and generalist skills—have deep expertise in a few areas, broad awareness elsewhere

## LLMs and Expert Generalists

* LLMs lower barriers to new domains—generalists use them to learn faster
* Expert generalists ask better questions, assess AI suggestions critically
* LLMs amplify the value of broad, principle-based knowledge

## Why Expert Generalists

Modern software systems involve many components, needing collaboration <mark style="color:purple;">between specialties</mark> to deliver features to production. Expert generalists can unplug the pipes, bridge gaps, and drive features to completion. Their broad view leads to better leadership and knowledge transfer across teams.

* Broader talent pool—less reliance on rare specialists
* Faster delivery—generalists unblock dependencies and get things done
* Better problem-solving—see the whole system, not just silos
* Grow future leaders—generalists develop communication and strategic skills
* Expert generalists ensure complex tasks get done
* <mark style="color:purple;">Teams should blend expert generalists with a few key specialists</mark>

## Growing Expert Generalists

* Look for learning agility, systems thinking, and people skills
* Ask about tackling new domains, collaboration, and problem-solving
* Value stories of cross-disciplinary growth
* Encourage career paths that cross silos
* Promote experimentation and learning outside comfort zones
* Focus on fundamentals—patterns, principles, and core concepts
* Avoid overemphasis on tool-specific certifications

## See Also

* [AI Roles](/ai-engineering-handbook/roles-and-teams/ai-roles.md)
* [AI Team](/ai-engineering-handbook/roles-and-teams/ai-team.md)
* [AI Engineer](/ai-engineering-handbook/roles-and-teams/ai-engineer.md)
* [AI Researcher](/ai-engineering-handbook/roles-and-teams/ai-researcher.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jamiewen00.gitbook.io/ai-engineering-handbook/roles-and-teams/expert-generalist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.