Forward Deployed Engineer
Posted Aug 26, 2026
The role in short
Embed with wealth management customers to design integrations, deploy AI agents, and own the technical success of enterprise implementations.
About Nevis
Nevis is building the world’s first AI wealth management platform. We are building the system financial advisors will run on for the next decade. Our AI completes work, automates workflows end to end, and frees advisors to spend more time with clients. In the future, every wealth management firm will run on Nevis.
Nevis was founded by an exceptional team of ex-Revolut executives and has raised $110 million in just two years, including a $70 million Series B led by EQT Ventures & Growth, backed by world-leading investors including Sequoia Capital, ICONIQ, and Ribbit.
The Role
We are looking for a Forward Deployed Engineer to be the technical counterpart for our customers and make sure every implementation succeeds.
When one of the largest wealth management firms in the country decides to run on Nevis, you are the engineer in the room with them. You learn how their business actually works, translate that into what we build and configure, and own the technical side of the deployment from first workshop to a platform their advisors use every day. You work with their engineers, their operations team and their vendors, and you stay their technical point of contact long after go-live.
The work spans whatever the deployment needs: integrations with the systems they already run, getting their data into our platform, configuring and deploying AI agents and workflows against their real processes, prototyping fast to show what is possible, and being the person who diagnoses it when something does not behave the way anyone expected.
You will be trusted by the customer and relied on internally, so two things have to be true at once. You have to be precise, because these firms make decisions on the numbers we show them. And you have to move fast with whatever tools get you there, because the problems are novel and nobody is handing you a specification
What You’ll Do
- Own the technical side of enterprise deployments end to end, from initial scoping through go-live and expansion
- Be the customer's main technical point of contact, working alongside their engineers, operations teams and leadership
- Understand how each firm operates deeply enough to translate their workflows into what Nevis builds, configures and automates for them
- Design and deliver the integrations and data flows a deployment depends on, working with our engineering teams to make the pipes right
- Configure and deploy AI agents and automated workflows against real customer processes, and tune them until they hold up in production
- Build prototypes and demos fast, so customers can see what is possible before anyone commits to building it
- Diagnose and resolve technical issues in live deployments, and be honest with customers about what the platform can and cannot do
- Partner with Deployment Strategists on the commercial relationship, giving them the technical grounding that wins and grows accounts
- Feed what you learn in the field back into the product, shaping the roadmap so every future customer inherits it
Who You Are
- You have 3+ years in a forward deployed, solutions engineering, technical implementation or similar customer-facing engineering role at a high-growth technology company
- You are a strong engineer. Python and SQL are second nature, and you are comfortable working across systems, APIs and messy real-world data
- You have put LLMs and agentic tooling into production, and you have judgment about where they are reliable and where they are not
- You build fast. You would rather ship something working and iterate than design something perfect on paper
- You are precise about numbers. You know the difference between an honest "the data cannot answer that" and a confident wrong answer, and you know which one costs more
- You communicate exceptionally well with people who are not engineers. You can walk a COO through what you built and where it is weak without losing them
- You have low ego and high ownership. You do what needs to be done and the outcome matters more than the credit
- You are comfortable with ambiguity, and you bring clarity to unstructured problems rather than frustration
- You are happy to travel and work onsite with customers
- STEM degree from a top university, or equivalent demonstrated experience
Nice to Have
- Prior experience in wealth management, financial services or fintech
- Familiarity with the US RIA landscape, including how large advisory firms are structured, regulated and operated
- Experience with data integration, pipelines or systems migration at enterprise scale
- You are at the frontier of using LLM-powered workflows in your day-to-day work, with hands-on fluency across tools like Claude, ChatGPT, Cursor or similar
Why Join Nevis?
- Work alongside a high-calibre founding team backed by some of the best investors in the world
- A fast-paced, high-growth environment with the opportunity to shape how the business operates
- Be part of a mission-driven company transforming the wealth management industry with huge potential for global impact
- 15 days’ annual leave & Bank Holidays
- Private medical insurance
- Competitive salary and benefits package, including company equity
Prep for this interview
5 questions likely to come up at Nevis, each matched to a line in this posting.
- 1LLMs, RAG and agents
They wrote: “You have put LLMs and agentic tooling into production, and you have judgment about where they are reliable and where they are not”
The model gives a confident wrong answer to an important customer. What now?
How to answer
Why they ask: Tests how you handle trust, on top of the technical fix.
- Tell the customer the same day what you know and when they'll hear more
- Reproduce it and find the cause (bad retrieval, missing data, prompt, model)
- Add the case to the test set so it can't come back unnoticed
- Add a guard where it matters: citations, confidence checks, human review
Tip: Own it with the customer first, then show the change that stops it happening again.
- 2Integrations and APIs
They wrote: “Design and deliver the integrations and data flows a deployment depends on, working with our engineering teams to make the pipes right”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 3Data and SQL
They wrote: “You are a strong engineer. Python and SQL are second nature, and you are comfortable working across systems, APIs and messy real-world data”
Write a query that finds each customer's first and most recent order.
How to answer
Why they ask: A quick check that you're comfortable with grouping, joins and window functions.
- Clarify the tables and what counts as an order (cancelled ones?)
- Use MIN/MAX with GROUP BY, or ROW_NUMBER() if you need the whole row
- Handle ties on the same timestamp, and customers with no orders
- Explain how you'd test it on a few known customers
Tip: Say what you'd check in the data before writing the query: duplicates, time zones, nulls.
- 4Coding
They wrote: “Own the technical side of enterprise deployments end to end, from initial scoping through go-live and expansion”
Build a small in-memory cache. Then add expiry. Then a size limit.
How to answer
Why they ask: Staged exercises show how your code holds up when requirements change mid-interview, like at a customer.
- Start with get and set on a dictionary, plus tests
- Store an expiry time with each value and check it on read
- Track use order and evict the least recently used entry when full
- Say what you'd change for many threads or many machines
Tip: Keep the first version simple and well tested so the next stage is a small change.
- 5Ownership and working with customers
They wrote: “You have low ego and high ownership. You do what needs to be done and the outcome matters more than the credit”
Tell me about something you shipped that broke in production.
How to answer
Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.
- What broke and who it affected
- How you found out and what you did in the first hour
- The root cause, said plainly
- What you changed so it can't happen the same way again
Tip: Pick a real one with a cost. Spend most of the answer on what you changed.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.