If you like writing code and you also like being in the room with the people who will use it, look seriously at the Forward Deployed Engineer (FDE) role. A Solutions Engineer spends more of the week helping a customer decide to buy. A Software Engineer spends it building the core product for every customer. The FDE writes real software inside one customer's environment and keeps going until it works for them.
These three titles come up in the same job searches, use a lot of the same words and attract the same applicants, so it is easy to take the wrong one and spend a year in a job that drains you. Below is how they differ day to day, and a way to test which one suits you before you apply.
How the three jobs differ
A Software Engineer builds and maintains a product that many customers use. You work mostly with your team, your product manager and the people reviewing your code, and you are judged on what ships, how reliably it runs and how easy it is to change later. Some software engineers go months without talking to a customer.
A Solutions Engineer (also called a sales engineer or pre-sales engineer) works alongside the sales team. You run demos, answer technical questions, build proofs of concept and show a buyer how the product would fit their systems. Your results are usually tied to deals: whether the customer signed, and whether they understood what they bought.
Wikipedia describes a Forward Deployed Engineer as a customer-facing software engineer who develops and deploys software within a client company, often working beside the client's own staff for a set period. The same page says Palantir popularized the title and that AWS, OpenAI and Anthropic have also hired under it. It also lists the roles it overlaps with: solutions architects, sales engineers, customer engineers and professional services engineers. That overlap is why people confuse them.
I find it easiest to ask where the code lives and who it is for:
- Software Engineer: code in the company's product, for all customers.
- Solutions Engineer: demo and prototype code, to help one customer decide.
- Forward Deployed Engineer: production code in one customer's environment, to make the product work for them after they have bought it.
What an FDE posting looks like in Canada
Titles vary, so read a real posting. In November 2026 EY listed a Forward Deployed Engineer, AI role in Toronto. The work it describes includes:
- Finding generative AI and automation opportunities with clients.
- Designing and deploying AI applications using large language models, retrieval augmented generation (RAG) and agent workflows.
- Building a prototype first, then a production version.
- Running client workshops and presentations.
- Deploying open-weight models in client environments, including on-premises hardware.
It asks for 1 to 5 years in AI engineering, software engineering, app development, technology consulting or a related delivery role. You need hands-on programming in a language such as Python, TypeScript, Java or C#, and comfort with GitHub, APIs, CI/CD and Docker. The posting also mentions Model Context Protocol and hosted models such as Claude or OpenAI's. The Toronto pay range is $90,500 to $115,000 CAD.
One posting is not a market benchmark, but this one has the usual shape: part software engineer, part consultant, with most of the effort going into getting AI to work in a messy real environment.
What each role costs you
Every one of these jobs asks you to give something up, and it helps to know what before you sign.
Software engineering keeps you at a distance from the people you serve. Some engineers love the long stretches of focused work and never miss customer calls. Others start to feel cut off from why the work matters.
As a Solutions Engineer you rarely see the finished result. You help close the deal, then another team takes the customer from there, which wears on people who need to see a project through. Pay often includes a variable portion tied to sales. Some people like that and some find it stressful.
Wikipedia notes that some engineers see the FDE role as undesirable because of the travel requirements and the pressure to solve customer problems in short timeframes. You also work inside someone else's systems, with their security rules, their legacy code and their politics. If that sounds like fun to you, take it as a strong signal.
A quick self-check
Answer these honestly and count which role gets the most yes answers.
- Would you rather fix one customer's problem completely than improve a feature a little for thousands of users? (FDE)
- Do you enjoy presenting and explaining technical ideas to non-technical people? (Solutions or FDE)
- Do you want long stretches of uninterrupted coding? (Software)
- Are you comfortable not knowing what the environment looks like until you arrive? (FDE)
- Does the idea of part of your pay depending on deals closed appeal to you? (Solutions)
- Do you want to own a system for years and watch it improve? (Software)
- Have you been the person on a project who got the integration working when everyone else was stuck? (FDE)
If you landed on FDE, check how much of the job your current experience already covers.
Where career changers have a head start
The FDE role rewards experience that pure software paths mostly ignore. Business analysts, project managers, consultants, implementation specialists and support leads already know how to turn a fuzzy problem into something buildable, run a workshop until the room agrees, manage expectations when the timeline slips, and work inside a client's processes without breaking them.
What most people from those backgrounds still need is the hands-on technical side: working Python, calling model APIs, how RAG and agents are put together, and how to deploy something small and keep it running. You can learn that in a few focused months without going back for a degree.
A 30 day plan to test the fit
You can find out whether this suits you without quitting anything.
In week 1, read five FDE postings and five Solutions Engineer postings from Canadian employers. Highlight the skills that repeat, and note which postings excite you and which feel like a chore.
In week 2, build one small thing end to end, for example a question-answering tool over a set of public documents using a model API. Keep it simple. You are finding out whether you enjoy the build.
In week 3, treat a friend's small business as your customer. Spend an hour learning their real process, then adapt your tool to it, and pay attention to how it feels to work within someone else's constraints.
In week 4, write a one page summary of what you built, the problem it solved and what you would do next. It doubles as a portfolio piece and an interview story.
If week 3 was your favourite, you are probably an FDE at heart. If it was week 2, look harder at software engineering roles. If you enjoyed explaining it in week 4 most, solutions engineering may suit you.
For a structured path, our Forward Deployed Engineer course covers scoping, building and shipping an AI solution in a customer setting, with live feedback. If you are still deciding which of the three roles to aim for, a coaching session can help you match your background to the right one.
To see what employers want right now, browse the open roles on our job board: Forward Deployed Engineer jobs, Solutions Engineer jobs and Software engineering jobs. Reading a handful side by side is the quickest way to do week 1 of the plan.
Checklist before you apply
- I can explain the difference between FDE, Solutions and Software Engineer in one sentence each.
- I have read at least five real Canadian postings for my target role.
- I have built one small, working AI tool and can describe it plainly.
- I have one story about solving a messy problem inside someone else's environment.
- I know which trade-offs I am willing to accept: travel, sales targets or distance from customers.