The engineering job market is changing, but are companies changing the way they hire?
Spend any time looking at engineering vacancies across the AI startup ecosystem and you’ll notice something interesting.
Alongside the familiar Software Engineer, Backend Engineer and Full Stack Engineer titles, we’re seeing companies hiring for Product Engineers, AI Engineers and Forward Deployed Engineers (FDEs).
On paper, these sound like three very different jobs.
In practice, the lines between them can be surprisingly blurred.
A strong Full Stack Engineer might already be building AI-powered features, speaking directly with customers and making product decisions. Yet that same engineer could be overlooked for an AI Engineer or Product Engineer position simply because their CV doesn’t contain the right title.
This raises an important question for engineering leaders: are we hiring for genuinely different skill sets, or are we creating new labels for capabilities that increasingly overlap?
The Rise of the Product Engineer
Product Engineering isn’t a completely new concept, but the title is becoming increasingly relevant in modern, product-led engineering teams.
Traditionally, software engineering roles were often structured around fairly clear responsibilities.
Product Managers defined requirements, designers created the experience, and engineers built the functionality.
That model still exists, and works well in many organisations.
But smaller, faster-moving startups increasingly want engineers who can take greater ownership of the entire process.
A Product Engineer isn’t simply someone who writes code.
They’re expected to understand the problem being solved, contribute to product decisions, work closely with design and ultimately take responsibility for delivering something customers actually want.
A useful example comes from Linear’s engineering careers page.
Its Product Engineer role emphasises full-stack development, product judgement, working closely with founders and designers, and taking features from initial ideas through to production.
What’s interesting is how familiar those requirements might sound to an experienced Full Stack Engineer working at an early-stage startup.
The technical foundations haven’t necessarily changed.
What’s changing is the level of ownership and commercial awareness expected from the engineer.
AI Engineer: A New Discipline or an Evolution of Software Engineering?
AI Engineer is arguably one of the most interesting titles in today’s technology recruitment market.
According to LinkedIn’s 2026 Jobs on the Rise report, Artificial Intelligence Engineer ranked as the UK’s fastest-growing job title, based on growth over the preceding three years.
And the demand isn’t limited to engineers developing foundation models.
A growing area of applied AI engineering involves taking existing models and integrating them into useful, reliable products.
That might mean building LLM-powered applications, developing retrieval-augmented generation (RAG) systems, creating AI agents, integrating APIs or designing evaluation frameworks.
Much of this work relies on skills that experienced software engineers already possess.
Backend architecture, API development, databases, distributed systems, testing and production reliability all remain essential.
The difference is that engineers must also understand the behaviour and limitations of AI systems.
For example, a traditional backend engineer might be responsible for building a reliable service that processes customer requests.
An AI Engineer working on the same product might build a service that uses an LLM to interpret those requests, retrieve relevant information and generate a response.
Both require strong software engineering fundamentals.
However, the AI Engineer must also consider model accuracy, hallucinations, evaluation, latency and inference costs.
The overlap is significant, but the additional expertise matters.
This is reflected in OpenAI’s Applied AI Engineer role, which combines production engineering, model evaluation, agent behaviour and reliability.
The takeaway? AI Engineering is not simply traditional software engineering with a new title, but neither is it an entirely separate world.
For many engineers, it represents a natural extension of their existing capabilities.
Forward Deployed Engineers: Where Engineering Meets the Customer
Perhaps the most interesting evolution is the growing attention around Forward Deployed Engineers.
The FDE model has existed for years, notably at Palantir, but it’s particularly relevant to the current AI landscape.
AI companies increasingly need engineers who can work directly with customers to turn technical capabilities into functioning products and workflows.
That’s where FDEs come in.
Rather than focusing exclusively on a central product roadmap, Forward Deployed Engineers often work closely with customers to understand their problems, design solutions and get systems into production.
They need strong technical skills, but also communication, commercial awareness and the ability to operate in ambiguous environments.
OpenAI’s Forward Deployed Engineer role provides a good illustration.
The responsibilities span customer discovery, system design, full-stack development, production deployment and feeding real-world insights back into product and research teams.
Now consider an experienced engineer at an early-stage B2B SaaS company.
They might already spend time speaking with customers, building integrations, adapting the product to customer requirements and managing deployments.
They may never have held the title Forward Deployed Engineer.
But how different is their experience from what an AI startup might need?
In some cases, not very.
There are important distinctions, particularly around customer-facing responsibilities and domain expertise, but the transferable skills are substantial.
Three Different Titles, One Increasingly Connected Skill Set
What’s particularly interesting is how these roles connect.
Imagine an engineer working at a 30-person AI startup.
They build a customer-facing feature using React and Python.
They integrate an LLM, develop evaluation tests and improve the reliability of its responses.
They speak with customers to understand why the feature isn’t working as expected.
They then redesign part of the workflow and deploy the improved version.
Depending on the company, that person could reasonably be described as a Product Engineer, AI Engineer, Forward Deployed Engineer or Full Stack Engineer.
The title changes depending on which responsibilities the business wants to emphasise.
The underlying engineering capability remains largely the same.
Of course, this doesn’t mean every engineer can move seamlessly between these roles.
A deeply specialised ML Engineer developing training infrastructure may have very different strengths from a customer-facing FDE.
Equally, an exceptional Product Engineer may have limited experience evaluating production AI systems.
But there’s a meaningful group of engineers whose experience crosses these boundaries.
And those are precisely the candidates companies risk missing when they recruit too rigidly around job titles.
What This Means for Companies Hiring Engineers
For founders and engineering leaders, this creates an interesting hiring challenge.
The instinct when creating a new role is often to look for someone who has already held that exact title.
Hiring an AI Engineer? Search for existing AI Engineers.
Hiring an FDE? Prioritise candidates currently working as FDEs.
It’s understandable, particularly when teams need people who can contribute quickly.
But in an evolving market, this approach can unnecessarily restrict the available talent pool.
A better starting point is to define the actual problems the engineer needs to solve.
When assessing candidates across these overlapping roles, we’d encourage hiring teams to consider five areas:
- Engineering fundamentals: Can they design, build, test and maintain reliable production software?
- Product ownership: Have they taken responsibility for solving problems rather than simply delivering predefined tickets?
- AI experience: Have they built, integrated or evaluated AI-powered systems, and how deeply do they understand their limitations?
- Customer communication: Can they understand user requirements, explain technical decisions and work effectively with non-technical stakeholders?
- Adaptability: Have they demonstrated the ability to learn unfamiliar technologies and take ownership beyond their formal job description?
Not every role requires equal strength across all five.
An FDE may need exceptional customer-facing skills, while an AI infrastructure position may demand much deeper systems expertise.
The important thing is to distinguish genuine requirements from preferences that can be developed.
An engineer who has never held an AI Engineer title but has successfully shipped several LLM-powered products could be a stronger candidate than someone whose title matches but whose experience is largely experimental.
Likewise, a commercially minded Full Stack Engineer with strong customer-facing experience could be an excellent FDE candidate.
The evidence of what someone has delivered should carry more weight than the label attached to their previous position.
What Does This Mean for Engineers?
There’s an equally important message here for candidates.
If you’re a Software Engineer looking to move into AI, Product Engineering or Forward Deployed Engineering, don’t assume you need to start your career again.
You may already have much of the relevant experience.
The challenge is demonstrating it.
Rather than focusing exclusively on technologies, think about the outcomes you’ve delivered.
Have you taken a feature from an initial customer problem through to production?
Have you integrated AI functionality into an existing application?
Have you worked directly with customers to solve complex technical problems?
Have you made decisions involving performance, reliability, cost or user experience?
These experiences can be relevant across several emerging engineering roles.
That doesn’t mean every transition will be straightforward.
Moving into applied AI may require developing skills around model evaluation, retrieval systems and AI-specific reliability.
Moving into an FDE position might require stronger stakeholder management and a willingness to work directly with customers.
But the transition could be much closer than the job titles suggest.
The Future of Engineering Recruitment Is About Capabilities, Not Labels
One of the most interesting developments in the AI startup ecosystem isn’t necessarily the creation of entirely new engineering disciplines.
It’s the way existing disciplines are beginning to overlap.
Software Engineers are becoming more involved in product decisions.
Product Engineers are increasingly building AI-powered functionality.
AI Engineers need strong software engineering foundations.
And Forward Deployed Engineers are combining technical delivery with customer understanding.
The boundaries haven’t disappeared, and specialist expertise remains incredibly valuable.
But the traditional approach of matching candidates to vacancies based primarily on previous job titles is becoming less effective.
For companies, that means thinking more carefully about the capabilities they actually need.
For engineers, it means recognising that their experience may be relevant to a wider range of opportunities than their current title suggests.
Ultimately, the best engineering hire isn’t always the person who’s already doing the exact same job.
Sometimes it’s the person who has the fundamentals, judgement and adaptability to solve the problems your business will face next.
And in a market evolving as quickly as AI, that distinction matters.
Looking Beyond the Job Title?
Whether you’re building an AI engineering team or considering your next move, understanding how these roles overlap can open up opportunities that aren’t immediately obvious.
We work with engineering teams and candidates across the AI and software ecosystem, helping businesses identify the technical capabilities they need and engineers find opportunities where their experience can make a genuine impact.
If you’re navigating this changing market, we’d be happy to have a conversation.