Bilingual Forward Deployed Engineer (English/Spanish)
Posted Sep 10, 2026
The role in short
Embed with strategic customers to build custom integrations, deploy production code, and solve compliance workflow challenges in real-time.
About AiPrise
AiPrise is a YC-backed (S22) global compliance orchestration platform helping fintechs, marketplaces, and payment companies verify and onboard customers worldwide. We integrate with 80+ identity and compliance vendors to deliver a holistic view of risk. We're building AI-powered compliance agents to transform KYB, AML, sanctions screening, and risk scoring, enabling customers to onboard faster, reduce manual reviews, and prevent financial crime.
We operate across 200+ countries.
The Role
This is not a typical engineering role. As a Forward Deployed Engineer, you'll sit at the intersection of engineering, product, and customer success. You'll work directly with AiPrise's largest and most strategic customers to understand their compliance challenges, build custom integrations, and ship solutions that make the platform indispensable.
You won't be waiting for a ticket to land in your queue. You'll be in the room with the customer, scoping the problem, writing the code, and deploying the fix, sometimes in the same day.
This role is ideal for engineers who get energy from solving real problems for real people, and who want their work to have visible, immediate impact.
What You'll Do
Customer-facing engineering. Embed with key customers to understand their onboarding, KYB, and compliance workflows. Translate their pain points into technical solutions, whether that's a custom integration, a new API endpoint, or a workflow tweak.
Build and ship fast. Design and deploy customer-specific configurations, integrations with third-party compliance and identity vendors, and custom data pipelines. Own the full lifecycle from scoping through production.
Bridge product and engineering. Bring customer insights back to the core product team. Identify patterns across customer needs that should become platform features. Help shape the roadmap based on what you're seeing in the field.
Technical problem-solving under pressure. Debug production issues in real time. Troubleshoot complex vendor integrations across 80+ providers. Be the person customers trust to get things working.
Scale what works. Turn one-off solutions into reusable patterns. Write internal tooling, documentation, and runbooks that make the next deployment faster for everyone.
What We're Looking For
- 3+ years of software engineering experience building and shipping production systems. You've written code that real users depend on.
- Written and spoken proficiency in Spanish, as you will be working with our customers in the LATAM region.
- Strong backend fundamentals. Proficiency in at least one modern language (Python, Go, Java, Node.js). Experience with REST APIs, microservices, and relational databases (PostgreSQL, MySQL).
- Customer-facing comfort. You can hold your own in a call with a VP of Compliance at a fintech. You listen well, communicate clearly, and know how to translate business language into technical requirements (and vice versa).
- Spanish fluency required. You can read and write in Spanish to support our Spanish-speaking customer base directly.
- Bias toward action. You don't wait for perfect specs. You scope, build, and iterate. You're comfortable with ambiguity and thrive when given ownership.
- Cloud experience. Hands-on with AWS (preferred), GCP, or Azure. Familiar with CI/CD, Docker, and modern deployment practices.
Nice to Have
- Experience in fintech, regtech, payments, or fraud/risk detection
- Familiarity with compliance workflows (KYC/KYB, AML, sanctions screening)
- Experience integrating with third-party APIs at scale
- Frontend skills (React, TypeScript) for building internal tools or customer-facing dashboards
- Background working with ML/AI systems or data-intensive applications
Why This Role
- Your work has direct, measurable impact on customers and revenue. No abstraction layers between you and the outcome.
- You'll learn the compliance and fintech space deeply, working across diverse customer environments.
- You're joining a 70-person, fast-moving team where your code hits production in days, not months.
- Competitive compensation with meaningful equity in a YC-backed company with strong momentum.
- In-person team in San Jose, working alongside the founders and core engineering team.
Prep for this interview
5 questions likely to come up at AiPrise, each matched to a line in this posting.
- 1Cloud, deployment and security
They wrote: “Cloud experience. Hands-on with AWS (preferred), GCP, or Azure. Familiar with CI/CD, Docker, and modern deployment practices.”
How would you debug a deployment that works in staging but fails at the customer's site?
How to answer
Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.
- Compare versions, config and environment variables
- Check network rules, proxies and certificates (common in enterprise)
- Look at resource limits and permissions
- Add the missing check to your install steps afterwards
Tip: List the usual suspects and how you'd check each without full access.
- 2Coding
They wrote: “Strong backend fundamentals. Proficiency in at least one modern language (Python, Go, Java, Node.js). Experience with REST APIs, microservices, and relational databases (PostgreSQL, MySQL).”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 3Ownership and working with customers
They wrote: “Bias toward action. You don't wait for perfect specs. You scope, build, and iterate. You're comfortable with ambiguity and thrive when given ownership.”
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.
- 4Discovery and scoping
They wrote: “You won't be waiting for a ticket to land in your queue. You'll be in the room with the customer, scoping the problem, writing the code, and deploying the fix, sometimes in the same day.”
How do you decide what to build first when a customer wants ten things?
How to answer
Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.
- Score each request by business value and by effort, with the customer in the room
- Pick one item that proves value fast and unblocks later work
- Write down what's out of scope so it doesn't creep back in
- Revisit the list after the first release, with real usage data
Tip: Show a simple way to rank the list and name what you'd leave out on purpose.
- 5Integrations and APIs
They wrote: “Build and ship fast. Design and deploy customer-specific configurations, integrations with third-party compliance and identity vendors, and custom data pipelines. Own the full lifecycle from scoping through production.”
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.
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.
