Flowglad

| 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’re backed by Y Combinator, Essence VC, a top 5 VC fund (not yet announced!) and some incredible angels including Kareem Amin (CEO of Clay), Alex Rattray (CEO of Stainless), Geoff Charles (CPO of Ramp), and Colin McDonell (creator of Zod, 180m+ monthly downloads). Our product is live, but we have not yet launched. That’s because, as you can imagine, there is a veritable British coastline of product surface area that we need to polish and cohese together. We have: A production-grade billing engine for subscription and usage based billing, Our own checkout screens that handle single payments, subscriptions, and even payments for invoices A dashboard with graphs, catalog management, etc. Backend services to capture webhooks, run processing and cron jobs in the background A full stack SDK that delivers data door-to-door from our servers to our customers’ backends and frontends A thriving community of builders that has grown 5x in the last month, with many seeking to integrate Flowglad Our stack is fun: everything is on Next.js (even our REST API), tailwind, TRPC, Drizzle ORM, postgres backend, and zod everywhere! We have 150,000 lines of Typescript of which about 100,000 lines are tests. While we have a lot of room for improvement, we strive to make the customer-facing experience simple. The full product, including the back office that interfaces with the regulated and financial aspects of the business, is inevitably very complex. All of this is 100% open source: https://github.com/flowglad/flowglad/ About the Role We need an energetic founding product engineer to help us polish, systematize, and stabilize the many facets of this product. They will work very closely with Agree, cofounder and CEO (and only engineer on the project to date), our founding platform engineer, and our founding designer (one of the best in the field), and the world class payments industry experts in our network. In the next 2 months, you will own productionizing our services so that they are GA-ready. Here are just a few of the problems on our plate: Helping us deploy a multi-faceted onboarding flow to allow customers to pick between using us as their merchant of record or being the settlement merchant themselves Crafting the first-ever conversational onboarding flow for a payments product Building agentic antifraud and KYC workflows Building a shadcn component registry Building integration pathways for builders using Cursor, Windsurf, Lovable, Replit, Bolt, Kiro and every other vibe coding platform Parameterizing the UI and backend in our app to account for the regulatory requirements of merchant of record vs self settlement flows Developing plugins for major builder ecosystems: Better Auth, Framer, Convex Making our documentation more robust to cover all of the use cases we support. And then, making it ingestible into our RAG pipelines Engaging the members of our community who want to integrate to help unblock them or guide them through the process Over the next 4 months, you’ll also work closely with Agree and the eng team to help us scale our engineering output with AI. This will go beyond just using coding agents, and will involve thinking through how to design our codebase to make it easier for AI to extend or maintain. About You We are looking for a highly energetic engineer who is most motivated by the impact of their work, and wants to become an expert on-the-job about payment processing. You are excited to own the quality of the final product, which means making sure it is robust, consistent, resilient, and fits like a glove for our target users. You should have wide curiosity, and a joy for putting points on the board. You are excited at the thought of talking with customers to help unblock them, because you know that it will give you the feedback needed to further polish the product. You’ll dive into the work immediately. Slope of growth is much more important for this position than calendar years of experience. You are hungry, and want an environment where you feel unfettered to run quickly to improve the product. You are excited at the thought of posting 3 pull requests per day on average, because you know that’s only possible when: the work has been well defined you have a deep understanding of the job to be done 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 very best in the world at what we do. So we seek excellence in ourselves and those around us. We believe this is a once-in-a-lifetime magic opportunity. Consequential payments companies hatch during technology shifts. So this will not be a chill job 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.

| 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.