Join Polygon Labs as a Forward Deployed Engineer to drive payment integrations and enhance the Open Money Stack.
Posted by employer 2 days ago
First seen on Joblaze 1 day ago
Last verified on the company career page 1 day ago
What you'll build
Must have
Nice to have
Role intensity
70% hands-on coding
AI in the day-to-day
AI-native in how you work: AI coding tools for demos and middleware, AI for docs, and building agents as needs come up.
Requirements
Not disclosed in this posting: compensation, visa sponsorship.
Benefits
Joblaze summary
In the role of Forward Deployed Engineer at Polygon Technology, the individual will focus on hands-on integration of payment systems, collaborating closely with customer teams to ensure smooth transitions from contract to production. Key skills include deep knowledge of US payment rails, proficiency in programming languages like TypeScript or Python, and experience in shipping production software. This position is suited for seasoned engineers with a background in payments who thrive in dynamic environments and are comfortable navigating incomplete documentation. The role emphasizes automation and the creation of reusable assets to streamline future integrations.
Joblaze insights
Quick facts
From the original posting
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.
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.
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.
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.
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.
Bring Product and Engineering feedback grounded in demand across several customers, not one-off asks.
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
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.
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.
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).
Remote first global workforce
Company matching 401k with 3% match*
$200 Annual AI Allowance
$75 Monthly internet or phone reimbursement
Flexible Time Off
Company issued laptop
*401k is for United States employees only
Standard company text repeated across Polygon Technology's postings is omitted here.