
Forward Deployed Engineer, AI
Posted Oct 14, 2026
The role in short
Embed with business teams to map workflows, build and deploy production AI agents and automations, and ensure adoption through evaluation and controls.
About Us:
At ClarityPay, we’re redefining the point-of-sale credit market to bring more value to merchants. Based in NYC and Atlanta, our fast-growing fintech empowers large merchants with configurable “Pay-Over-Time” tools— including monthly installments, BNPL, and revolving products. We solve complex credit challenges with speed, precision, and intelligence.
Our values guide everything we do: we put merchants first, stay data-driven, always know the why, learn relentlessly, and win together as a team.
Role Overview:
ClarityPay is seeking Forward Deployed Engineers to embed with the teams that run the company and turn how they work into dependable, AI-native systems. You will sit with process owners in finance, credit and portfolio risk, servicing and collections, and operations; scope the problem with them before building; ship agents, controls and automations into production; and stay through adoption as the named secondary owner of the process. You will join the Data & AI organization, working alongside engineers in New York and India on a shared platform, and alongside Product and Engineering you will build external-facing AI solutions for merchants and partners on the ClarityPay platform. You will use AI tooling to make the build the easy part, and you will be measured on what is adopted and relied upon, not on what is demoed.
Key Responsibilities:
- Embed with process owners to map how the work actually runs, scope the problem with them before building, and agree success criteria and a baseline up front.
- Own delivery end to end — discovery, technical scoping, system design, build and production rollout — and stay through adoption as the named secondary owner of the process.
- Choose the simplest dependable solution: simplify or remove a step before automating it, then pick a scheduled job, a triggered job, or a bounded agent with a defined mandate, action set, escalation owner and pause conditions.
- Write evaluations for everything you ship: prove the output is correct before a team depends on it, and re-check it as models, data and processes change.
- Instrument what you build, and the processes around it, with detective (“day-zero”) controls — thresholds, exception inventories and alerting, each with an action path and a named owner — so a breach surfaces the same day, not at month-end.
- Build external-facing AI solutions for merchants and partners with Product and Engineering; anything external ships through Engineering’s review and deployment standards.
- Codify reusable patterns, evals and harness standards so the second deployment is faster than the first; prefer reusable capabilities over one agent per task, and bring field signal back to the platform roadmap.
- Work inside ClarityPay’s controls for AI — evaluate before exposure, bound the exposure, keep a person at the gate — and propose where a human must review, where automation may act unattended, and what gets logged.
- Own the value case: set impact hypotheses and baselines, measure before and after, and report to executives on business impact, total effort saved (including review and maintenance), control quality and reuse.
- Continually promote and apply ClarityPay values; be a role model of trust and integrity.
What Success Looks Like in Your First 6–12 Months:
- Desktop and spreadsheet-based reporting processes are inventoried, baselined and moved onto AI agentic systems running on governed data, with a person at the gate where judgment is needed.
- Recurring performance reporting — portfolio, collections, servicing and finance — is produced by agents from governed metrics rather than manual pulls, on time and traceable to source.
- Day-zero controls are live in your first processes, each with a threshold, an action path and a named owner, so breaches surface the same day.
- The effort returned is measured against the baseline, net of review, exceptions and maintenance, and reported to executives.
- At least one external-facing solution for merchants or partners is in production and adopted.
- The patterns, evals and agent-harness standards you built are reused by the next deployment.
Qualifications:
- Curious, energetic, positive, solution-oriented, collaborative, trusted.
- 2–5 years of software engineering or technical deployment experience that includes working directly with business users — in operations, business systems, solutions engineering, or technical consulting.
- Production experience with LLMs: prompt engineering, agent or skill development, and evaluation. Things other people depend on, not demos.
- Strong Python and SQL: you write and review production code and use AI-assisted development to move faster. Low-code and automation platforms (e.g., Retool, Zapier, n8n) are useful, not a substitute.
- Data fluency in a lakehouse environment (e.g., Databricks, ClickHouse): pull answers out of governed data, build reliable pipelines, and catch when the output is wrong.
- High agency and comfort with ambiguity — you will choose what to automate as often as you are told.
- Strong discovery and communication skills: able to sit with a collections specialist or a finance analyst, understand their workflow, and explain trade-offs to a non-technical audience; comfortable working across time zones with engineering colleagues in India.
- Judgment about what should not be automated — where the cost of being wrong outweighs the time saved.
Nice to Have:
- Fintech, lending, payments, banking, or another regulated environment.
- Experience building MCP servers, sub-agents, or agent skills.
- MLOps or experimentation experience: evaluation frameworks, staged A/B tests, model monitoring.
- Prior forward-deployed, professional services, or founding-engineer experience.
How You’ll Know This Role Is Right for You:
- You see manual, repetitive work and cannot leave it alone.
- You would rather ship a working automation this week than design the perfect one this quarter.
- You have receipts — things you actually built that other people now depend on.
- You want range: collections one month, month-end close the next, portfolio risk monitoring after that.
- You would rather stay through adoption than hand off at launch.
What We Offer:
- Base salary range: $145,000–$195,000, plus variable compensation and equity.
- Comprehensive benefits (medical, dental, vision).
- 401k program.
Ready to redefine point-of-sale financing with us? Apply today and join a passionate team committed to making financial clarity a reality.
ClarityPay is an equal opportunity employer. We do not discriminate based on race, ethnicity, color, ancestry, national origin, religion, sex, sexual orientation, age, disability, veteran status, marital status, or any other legally protected status.
Prep for this interview
5 questions likely to come up at ClarityPay, each matched to a line in this posting.
- 1Discovery and scoping
They wrote: “Own delivery end to end — discovery, technical scoping, system design, build and production rollout — and stay through adoption as the named secondary owner of the process.”
A customer says “we want AI in our claims process.” What do you ask in the first meeting?
How to answer
Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- Ask what data you can access, and who signs off on security
Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.
- 2LLMs, RAG and agents
They wrote: “Production experience with LLMs: prompt engineering, agent or skill development, and evaluation. Things other people depend on, not demos.”
How do you know an LLM feature is good enough to ship?
How to answer
Why they ask: Evals are what separate a demo from production. Many roles list them by name.
- Write 50–200 real examples with expected outcomes, with customer experts
- Agree on a pass bar and the errors that are never acceptable
- Score automatically where possible; review a sample by hand
- Re-run on every prompt or model change, and watch live traffic after launch
Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.
- 3Data and SQL
They wrote: “Strong Python and SQL: you write and review production code and use AI-assisted development to move faster. Low-code and automation platforms (e.g., Retool, Zapier, n8n) are useful, not a substitute.”
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: “2–5 years of software engineering or technical deployment experience that includes working directly with business users — in operations, business systems, solutions engineering, or technical consulting.”
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: “High agency and comfort with ambiguity — you will choose what to automate as often as you are told.”
Tell me about a project where the requirements kept changing. What did you do?
How to answer
Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.
- The project and why requirements kept moving
- What you did to pin them down (short demos, written decisions)
- The trade-offs you made to keep shipping
- The result, with a number if you have one
Tip: Show how you reduced the change, beyond how you coped with it.
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.