Forward Deployed Engineer, Payments
Posted 2 days ago
The role in short
Embed with customer engineering teams to design and implement production payment integrations, write code, and build automation/agents to streamline future onboarding.
About Polygon Labs
Polygon Labs is a global blockchain payments company building and operating infrastructure to move money instantly, reliably, and at internet scale, with the mission to move all money onchain. It is building the Polygon Open Money Stack, an open and integrated stack of services and technologies to instantly and reliably move money anywhere, and put it to work. Its infrastructure has facilitated trillions of dollars in onchain value transfer and supported millions of transactions daily for some of the globe's largest banks, fintechs, enterprises, and consumer applications.
Your Role
Polygon is building the Open Money Stack: one API for moving money anywhere and putting it to work. It's live, and the work spans US and international money movement.
A typical integration takes four to eight weeks. The path from contract to production is split across Sales, Compliance, Customer Success, and Engineering. Core product managers and engineers get pulled into enablement and troubleshooting. No one owns the hands-on integration work end to end. This role does.
You'll embed with a customer's product managers and engineers, write code next to them, and drive the integration live. You own the technical execution, from the pre-sales conversations to the first production transaction.
Then you work yourself out of the loop, so the next customer, or their AI, can integrate without asking anyone on our side.
Your Responsibilities
Embedded integration and delivery (the core of the job)
- Own the path from contract to production: discovery, solution design, environment setup, API and webhook enablement, testing through UAT and failure modes, go-live sign-off, and first-transaction hypercare.
- Embed with the customer's engineers, on-site if it moves the work faster, and hold them to milestones so weeks become days.
- Integrate customers across the OMS APIs.
- Handle the hard parts: key rotation, webhook signing, retries, idempotency, error handling, and reconciliation.
Pre-sales and solution design
- Answer the technical questions on prospect calls with BD and in the follow-ups, going deeper than Sales or Product can. Then write the answer down in KB articles so nobody asks it again.
- Lead discovery on legacy payments systems, fund flows, and compliance constraints, and write the integration plan we share early in the sale.
Keep core Engineering building
- Triage partner issues yourself, with access to code, logs, and transaction data, so most never reach core Engineering.
- When one is a real bug, bring Engineering a scoped ticket: reproduction, impact, logs, recommended fix.
Automate the integration path (out of the work, not instead of it)
- Turn each bespoke integration into reusable assets: SDKs, runbooks, partner docs, and automation for the steps that repeat, like KYB intake, staging keys, and go-live gates.
- Raise the API and integration docs and machine-readable specs to where a developer, or the customer's own AI coding agent, can integrate us without talking to anyone on our side.
- Build the agents that answer partners' integration questions, so the same question is never answered twice.
Product and roadmap feedback
- Bring Product and Engineering feedback grounded in demand across several customers, not one-off asks.
The reality of this role
We want this clear up front, because fit matters.
- This is hands-on. You will write code every day. It is not a pre-sales-only or architecture-only seat, and not a coordinator seat: you solve the problem; you don't track it.
- The stack is proprietary and parts of it are still being documented. You will often build the docs and tooling that don't exist yet.
- Most partners are large, slow-moving organizations, many outside the US.
- The stack changes weekly and nobody will hand you a plan. You should want that.
What You'll Need
Responsibilities
- Deep US payments rails experience: ACH pull and push, settlement windows, reconciliation, fund flows, money movement. This is the top thing we're hiring for. You don't need to have lived in the US.
- 5+ years shipping production software, ideally payments. Forward deployed or implementation experience is ideal. A solutions engineer who codes is absolute the floor, not the target.
- Hard integrations you shipped to production and can walk through, in at least one mainstream language (TypeScript, Python, Go, or similar). Not prototypes and slideware.
- Comfortable embedding with a customer's team, working from incomplete docs (and helping complete them), and explaining the system to a developer and a CFO.
- A reflex to automate. Once you've done a step twice, you build the tool, doc, or agent that removes it.
Technical profile and AI fluency
- Hands-on with APIs, SDKs, webhooks, and authentication. You've built systems that scale and can read and contribute to a customer's codebase.
- AI-native in how you work: AI coding tools for demos and middleware, AI for docs, and building agents as needs come up. Be ready to show it.
Preferred Qualifications
- Wallets, stablecoins, onchain payments, or crypto rails. We'll teach the crypto side to the right payments engineer.
- Non-US rails and regulation (SPEI, PIX, SEPA, PSD2, SCA, Open Banking).
- Compliance-driven design in regulated environments (KYB, KYC, transaction monitoring).
Polygon Labs Perks
The goal of the Polygon Labs total rewards program is to support the health and well-being of you and your family. Our comprehensive compensation plan includes the following benefits for our full time employees:
- Remote first global workforce
- Industry leading Medical, Dental and Vision health insurance*
- Company matching 401k with 3% match*
- $1,500 Home Office Set Up Allowance (life-time max)
- $200 Annual AI Allowance
- $75 Monthly internet or phone reimbursement
- Flexible Time Off
- Company issued laptop
- Egg freezing, mental health, and employee wellness benefits
*In certain countries medical, dental and vision is fully covered for employees & their dependents. This is country and plan specific.
*401k is for United States employees only
Polygon Labs is committed to a diverse and inclusive workplace and is an equal opportunity employer. We do not discriminate on the basis of race, national origin, gender, gender identity, sexual orientation, protected veteran status, disability, age, or other legally protected status. Polygon Labs is committed to treating all people in a way that allows them to maintain their dignity and independence. We believe in integration and equal opportunity. Accommodations are available throughout the recruitment process and applicants with a disability may request to be accommodated throughout the recruitment process. We will work with all applicants to accommodate their individual accessibility needs.
If you think you have what it takes, but don't necessarily meet every single point on the job description, please still get in touch. We'd love to have a chat and see if you could be a great fit.
Learn More about Polygon Labs
Website |Twitter|Telegram |Reddit |Discord |Instagram |Facebook |LinkedIn
Prep for this interview
4 questions likely to come up at Polygon Labs, each matched to a line in this posting.
- 1Coding
They wrote: “Hard integrations you shipped to production and can walk through, in at least one mainstream language (TypeScript, Python, Go, or similar). Not prototypes and slideware.”
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.
- 2Integrations and APIs
They wrote: “Raise the API and integration docs and machine-readable specs to where a developer, or the customer's own AI coding agent, can integrate us without talking to anyone on our side.”
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.
- 3Discovery and scoping
They wrote: “Own the path from contract to production: discovery, solution design, environment setup, API and webhook enablement, testing through UAT and failure modes, go-live sign-off, and first-transaction hypercare.”
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.
- 4Cloud, deployment and security
They wrote: “Lead discovery on legacy payments systems, fund flows, and compliance constraints, and write the integration plan we share early in the sale.”
The customer's security team sends a 200-question review. How do you handle it?
How to answer
Why they ask: Security reviews often block deals. FDEs help get through them.
- Start from your company's standard answers (SOC 2 report, past reviews)
- Answer clearly; don't oversell
- Bring in your security team for anything you're unsure of
- Keep the new answers for the next customer
Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.
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.
