Forward Deployed Engineer, Cardless

• 6+ years building production backend systems, including work shipped with a partner or customer in the loop rather than behind a product manager
• You go genuinely deep on systems. You can hold an end-to-end flow in your head and debug someone else's integration against it faster than they can
• Strong with partners: you can run a technical conversation with their engineers and explain the same tradeoff to their business team without changing the substance
• Product sense you'll actually use. You can reason about where a card application, offer, or servicing surface belongs in a partner's journey, and make the case for a different placement when the one they asked for will hurt their customers
• Sound judgment on bespoke versus platform, being able to say no and explain why certain requests doesn’t make sense

Desirable

• As a Forward Deployed Engineer at Cardless, you own getting a new partner from signed contract to live card program, and you do it with your hands in the code on both sides
• Every launch starts similarly: a partner has a product in mind, an existing app, their own engineering team, and a set of constraints
• You scope it with them, design the integration, write the guides they build against, and help them get to production
• This involves coordinating the risk, compliance, processor, and bank work that has to land to launch a partner’s card end to end
• To do this effectively, you’ll need to carry a view on where our product belongs inside theirs
• Our card lives in the partner's app, in their onboarding funnel, next to their existing product
• An application or offer surface placed in the wrong spot converts worse, confuses their customers, and results in a less successful card offering
• Every partner asks for something slightly different, and you decide which of those requests deserve a bespoke path and which are telling you our platform is missing something
• Then you go build the missing thing
• The goal is that the fifth integration takes a fraction of the time the first one did, because you spent the first four making it so
• Own the technical relationship for new partner launches end to end, from the first scoping workshop through the first approved application in production
• Develop real product sense for each partner's app: where our application, offer, and card management surfaces belong in their flow
• Write the integration guides, API specs, and sandbox tooling partners build against, so they can self-serve
• Decide what we build bespoke for a partner versus what becomes a supported platform feature, and invest in the integration platform so each launch is faster than the last