Flowglad

Compensation

Full Description

About Flowglad We’re building the payments layer for the next chapter of the internet. It’s programmable in natural language, requires zero glue code, and is tax compliant out of the box. We just raised a substantial seed round led by a top 5 VC (not yet announced!), with participation from Y Combinator, Essence VC, and some incredible angels including Alex Rattray (CEO of Stainless), Geoff Charles (CPO of Ramp), Colin McDonell (creator of Zod, 35m monthly downloads), Kareem Amin (CEO of Clay). We are 100% in person in NYC. Since proessing our first transactions in early April, we’ve grown πayment volume 10% weekly - and we haven’t even launched yet. The core product brings the reactive data model found in React to payments + billing state. Instead of imperatively managing low level resources and reconciling state between your payment processor and your app via webhooks, you just read the latest customer billing state from our SDK. We tell you in real time what features and usage credits your customers have based on their billing state. Here’s how: Our core app: a postgres DB → ORM layer → declarative query interface → TRPC router → web app or REST endpoint that we transpose to TRPC requests with an OpenAPI spec that we auto-generate via trpc-openapi On the client-side: we access the REST API via Node SDK, that we wrap in a “semantic SDK” that avails easy to understand methods on our customers’ backends via a flowglad-managed API route that our customers mount on their servers. In our customers’ webapps, our React SDK hits their flowglad API route, allowing them to get door-to-door delivery of payments + billing data. Our SDK determines which user’s billing state to load by coupling tightly with each app’s backend auth logic. And the frontend just reads billing data as needed, and sends mutations back to the Flowglad API by authenticating through the server All of this is 100% open source: https://github.com/flowglad/flowglad/ About the Role We need an experienced platform engineer who has built production-grade systems. Ideally from scratch, and at scale. You will own productionizing our services so that they are GA-ready. Here are some of the problems we need help with urgently: Developing a versioning system for our REST API and client SDKs Enhancing observability in every layer of our services using logging and monitoring tools Developing CI/CD workflows to rigorously test all supported SDKs’ versions on every commit Cleaning up the type-system of our REST SDK, with direct access to the Stainless team Reviewing the architecture of our API so that it meets regulatory requirements for different flow of funds models, with minimum drift between the different API interfaces Designing, implementing, and evaluating RAG pipelines Here are some more challenging medium term problems where you will work with Agree, cofounder + CEO, to define and architect solutions: Developing service architectures to enable us to interact between closed source and open source services Composing key services (merchant onboarding, platform risk) in a way that makes them consumable in a platformized way (e.g. by others hoping to offer Merchant of Record services in their products) Designing the caching layer of our low-latency, realtime billing data read layer Scaling our API key solution to support 1,000-10,000x the current request volume Developing observability tools for our billing engine, including visibility of billing state at a per-customer level We know that visible progress on this work does not usually happen in hours. Sometimes it may take days. But it should not take months. This does not mean rushing the work, but breaking complex projects down into achievable sequential tasks. For each project, these tasks usually build on their predecessors as the project reaches higher and higher levels of fidelity. We expect that AI will not only be a core part of your workflow, but that you will help make our codebase more friendly to AI. Much of the secret to our engineering productivity to date has been engineering for correctness in a way that makes it easier, not harder, to generate the correct code once. About You We are looking for someone who can balance deep instincts for correctness engineering and rigor with the natural pace of startups. You don’t believe in “move fast and break things” (certainly not when it comes to payments infrastructure!). But you pride yourself on landing complex infrastructure quickly, mainly because you’ve done it before. You’ve ideally brought several services from initial commit to scalable production volumes. You’ve seen multiple codebases evolve over multiple years each and you know where rust, mold, and calcification accrue. When confronted with a problem you either: Know how to build a durable, generalized solution based on your direct experience Can reach out to someone world-class in your close network does The Anti-Pitch If this all sounds exciting, great! We want to give you fair warning about some of the things we hold dear. They are core to us, but are not for everyone. We are aiming to be the best in the world at what we do. So we seek excellence in ourselves and those around us. We believe in that this is a once-in-a-lifetime magic opportunity. Truly consequential companies in payments hatch when technology shifts bring new kinds of commerce online. We move very quickly, even for an early stage startup. We have thousands of engineering-years of work to re-litigate so that we can get to the frontier of a rapidly evolving field. We are an all-Typescript engineering team Languages like Rust, Elixir and Go may be better for certain systems and service engineering tasks. But polyglot engineering teams tend to devolve into fiefdoms and low cohesion engineering cultures. We want to encourage correctness engineering and rigor across the engineering team.