No, it is a different job, not a lower one. You code less and talk to customers more, and part of a sales engineer's pay may depend on deals. For engineers who like people and real problems, it can grow faster than product engineering. The real risks are letting your engineering skills fade and choosing it only to escape coding.
What people tell me
I have been working as a software engineer for a few years and a recruiter approached me about a solutions engineer role. Another company has a sales engineer opening that pays well on paper. Some friends say moving into anything with sales in it means leaving real engineering and I will never be able to come back. I enjoy explaining things and I like meeting users, but I do not want to damage my career or end up as a salesperson who used to code.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- It is a different mix of work, not a lower rung: less coding, more discovery, design, demos and writing.
- Check whether the pay includes variable pay tied to sales, and how often people actually hit target.
- Keep coding every week so a move back to product engineering stays open.
- The field experience is valuable later in product engineering, product management and founding.
- Choose it because you enjoy the daily work, not because you want to escape coding.
My honest answer
It is not a step down. It is a step sideways into a different mix of work. You will write less code and spend more time on discovery, solution design, demos, writing and handling objections. Whether that is good for you depends on what you enjoy and how you manage the move.
What actually changes
| Product software engineer | Solutions or sales engineer | |
|---|---|---|
| Most of the week | Building and reviewing code | Customer calls, designs, demos, proofs of concept |
| Who you serve | Your team and product roadmap | Specific customers and deals |
| Feedback loop | Releases and metrics | Conversations, often daily |
| Pay shape | Usually base plus equity | Often base plus variable pay tied to sales, especially for sales engineers |
| Pressure | Deadlines and incidents | Deals, customers and quarter ends |
Sales engineers in particular often have part of their pay tied to sales targets. Together, the base and the variable part are called on-target earnings (OTE). Two offers with the same headline number can be very different in how certain the money is, so ask how variable pay is calculated and what share of the team usually hits target.
Why it can be a step up
- You learn how software makes money. Few product engineers see why customers buy, what they fear and what makes a rollout succeed.
- Your skills compound. Discovery, writing for executives and presenting under pressure help in every later role, including engineering leadership.
- Demand is real in some areas. Customer-facing engineering has grown with AI deployments. A June 2026 announcement on Amazon's own news site described AWS investing 1 billion dollars in a forward deployed engineering organisation, and a June 2026 analysis of about 1,000 job posts by Perspective AI reported forward deployed engineer hiring up more than 1,000 percent year over year. Those numbers are about the forward deployed end of this family and about AI companies in particular, so check postings in your own market.
- It opens doors. People move from these roles into product management, back into product engineering with better judgement, into leading field teams and into founding companies.
When it really is a step down for you
- You love deep, uninterrupted engineering work. These roles are full of context switching, travel and meetings.
- You are choosing it to escape coding. Customers trust engineers who can open a laptop and fix the problem. If you stop being technical, you lose the thing that makes you valuable.
- The posting is really a sales role with an engineering title. Read the responsibilities: if it is mostly pipeline and quota with little technical depth, it is not the job you think.
How to keep the door back open
- Code every week, even when your calendar is full. Build demo tools, integrations and prototypes yourself.
- Keep evidence of engineering work: systems you built, integrations you owned, problems you debugged at customers.
- Stay close to the product team by sending evidenced feedback from the field. It keeps you technical and visible.
- Consider a forward deployed role if you want the customer side without giving up daily coding.
How to decide
Try the work before you decide. Run two discovery conversations with real users, build something small for one of them and demo it to people who do not code. If that energises you, the move is likely a good one. If you rushed through the conversations to get back to the code, stay in product engineering or look at forward deployed roles.
Where to go next on Sefism
- The forward deployed and solutions engineering roadmap has a path for solutions engineers and sales engineers, including discovery, demos, integrations, pay structure and how people get in.
- The cheat sheet compares the roles and gives you a discovery question bank and a demo structure to practise with.
- Mastering Technical Sales is the long-running handbook on the sales engineer's job.
- PreSales Collective is a free community where you can ask working sales and solutions engineers about their week.
- If you are weighing a bigger career move, read how to switch from a service-based to a product-based company too.
If you want to talk through an offer or your own situation, create a free Sefism account and book a session with me.
Was this answer helpful?
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.