Meurer's Periodization of FDE Work
The title on an FDE posting does not reveal the vintage of the work, so identical titles can hide different jobs.
Two Postings, One Title
Imagine two job postings that both advertise a Forward Deployed Engineer position and list the same responsibilities in the title. On paper they look interchangeable. Once you read the day-to-day descriptions, they may turn out to be very different jobs. This article shows how to look past the title and work out which stage of FDE work a team is actually in.
What do you think happens?
One team describes keeping an existing platform stable. The other describes deploying agents. Both postings use the same title. Are these likely to be the same job?
Reveal answer
No, the shared title does not tell you what the daily work is
The source is direct that the title on a posting does not reveal the vintage of the work. Identical titles can hide different jobs, because the daily tasks, the kinds of problems solved, and the skills that matter can differ sharply between teams.
Why a Title Hides the Work
The most common error is assuming that teams sharing a title are doing the same work. The assumption feels reasonable. A title is the simplest signal available, and people tend to treat it as a summary of responsibilities. The source says this shortcut fails: the title on a posting does not tell you the vintage of the work.
Teams that look identical from the outside can sit at very different points in the role's development. The difference is not hidden in the title. It shows up in the daily tasks, the kind of problems being solved, and the skills that matter. The useful habit is to examine what a team does, rather than accepting the label on the posting.
Vintage, in this context, means the stage of FDE work a particular team is in. Asking which vintage a team operates in gives you a concrete basis for comparing roles.
Meurer's Five Stages
The source frames the vintage question using Meurer's periodization, introduced in Chapter 3, which sorts FDE work into stages. The five stages are platform stability, data integration, custom solutions, enablement, and agent deployment. Each names a different kind of work.
Notice that this list is not a ranking. The source does not present any one stage as the correct destination for a career or a team. The point of naming them is to give you vocabulary for describing what a team does, so that two teams can be compared on substance rather than on their titles.
Placing a Team on the Map
To place a team, you examine what its work actually involves and match that work to the stage it belongs to. The source describes the result as a team that may sit squarely in one stage or may have work that blends across several. The step-by-step move is to read the duties, identify the stage each one fits, and then see whether one stage dominates or several are present.
What the Interview Question Signals
The vintage question also works in the other direction during an interview. When a candidate asks which vintage the team works in, the interviewer's answer is informative. The source notes that an interviewer who understands this question is communicating something: they know where their function sits in the role's history.
Applying the Vintage Question to Two Postings
Comparing two postings with the same title
Two postings both advertise a Forward Deployed Engineer position with the same title. Posting A describes keeping an existing platform stable. Posting B describes deploying agents into live business processes. Use the vintage question to decide whether the two are the same job.
- 1Ignore the shared title
Both postings carry the same title, so the title cannot distinguish them. The source says the title does not reveal the vintage of the work.
- 2Read each posting's duties
Posting A centers on keeping an existing platform running smoothly. Posting B centers on putting autonomous agents into live processes.
- 3Map each set of duties to a stage
Posting A's duties fall under platform stability. Posting B's duties fall under agent deployment. These are two different stages from the five in Meurer's periodization.
- 4Check for blending
If either posting also contained work from other stages, it would be a blended vintage. Here each description points mainly to one stage, so each team sits squarely in its stage.
- 5Compare on substance
Because the stages involve different tasks, problems, and skills, the two postings describe different jobs even though the titles match.
The two postings are most likely not the same job. The shared title hides a difference in vintage: one is platform stability work and the other is agent deployment work.
Common Mistakes When Comparing Roles
Common mistake Assuming teams with the same title do the same work
What it looks likeTwo postings both say Forward Deployed Engineer, so the learner assumes both involve identical duties.
Why it failsThe source says the title does not reveal the vintage of the work, and identical titles can hide different jobs.
Do this insteadRead the duties and map them to a stage before comparing the two roles.
Common mistake Treating the five stages as a ranking
What it looks likeReading the list of stages and concluding that agent deployment is the advanced or preferred destination.
Why it failsThe source states the list is not a ranking and does not present any one stage as the correct destination.
Do this insteadUse the stages as vocabulary for describing what a team does, and compare teams on substance.
Common mistake Forcing a blended team into a single stage
What it looks likeA posting that mixes platform upkeep with data pipeline work is labeled as purely platform stability.
Why it failsA team may blend several stages, so forcing one label discards real information about the role.
Do this insteadIdentify which parts of the role come from which stage and how much of the role each part takes up.
Common mistake Treating an interviewer's answer as proof
What it looks likeAn interviewer who understands the vintage question is assumed to run a deliberate function with certainty.
Why it failsThe source offers this as a reasonable inference using the word usually, not as a guarantee.
Do this insteadTreat the interviewer's awareness as one signal among several.
Practice Placing Two Teams
Two postings share the title Forward Deployed Engineer. Posting X says the team spends most of its time keeping an existing platform running smoothly, with a smaller share of time spent setting up pipelines that bring data into that platform. Posting Y says the team spends most of its time putting autonomous agents into live business processes. Which stage or stages does each posting fall into, is either posting a blended vintage, and are the two jobs likely to be the same?
Hints
- Start by setting the title aside and reading only the duties in each posting.
- Posting X's main work matches platform stability, and its secondary work matches data integration. Ask whether that secondary work is large enough to count as a blend.
- Compare the stages each posting maps to. The source says the title does not reveal the vintage, so identical titles do not settle the question.
Key Takeaways
- A shared job title, such as Forward Deployed Engineer, does not reveal the vintage of the work, so identical titles can hide different jobs.
- Meurer's periodization, introduced in Chapter 3, names five stages of FDE work: platform stability, data integration, custom solutions, enablement, and agent deployment.
- A team may sit squarely in one stage or may blend several stages into one role, and the useful question is which parts of the role come from which stage.
- The stages are not a ranking. They give you vocabulary to compare teams on what they actually do.
- An interviewer's understanding of the vintage question usually signals a deliberate function, but this is an inference, not a guarantee.