Senior Backend Engineer – Accounts and Subscriptions

The Accounts & Subscription teams own billing and authorization - two services that everything else at Text depends on. That means text-billing (subscriptions, usage-based pricing, payment provider integrations) and SSO with account management, including the OAuth implementation that sits at the base of how clients authenticate across Text products. Current projects include things like integrating with Google Payments, building a flexible role and permissions system (ACAM), and migrating customers from the legacy platform to TextApp. About The Role We're looking for a Senior Backend Engineer to join as the technical owner of SSO and account services. The work here isn't just backend coding - it's taking a business requirement, designing the technical solution, aligning dependent teams across the company, and getting it shipped. You'll sit at the center of some of the most cross-functional projects at Text, working closely with product managers on the business side and engineers across the org on the technical side. If you want full ownership over services that actually matter - and the autonomy to shape how they evolve - you got this. What you'll do Own the SSO service and OAuth implementation — lead technical decisions, propose improvements, communicate trade-offs to stakeholdersWork on text-billing: subscriptions, usage-based pricing, payment provider integrationsDrive projects end-to-end: take business requirements, design the solution, coordinate dependent teams, set milestones, ship itProactively maintain your services — flag issues before they become incidents, propose fixes before they become blockersContribute to ongoing cross-company work: client migration to TextApp, ACAM role management improvements Who you are: Owner, not ticket-taker. You notice problems before they're assigned to you, propose fixes, and push them forward. If a dependency is stuck, you move itFluent in auth at the protocol level. You understand OAuth — not as someone who adds a login button, but as someone who knows the flows, the token types, and what goes wrong when they're implemented incorrectlyCross-team communicator. You're comfortable presenting technical solutions to non-technical stakeholders and making sure external teams deliver what you need to close a projectPragmatic. You balance doing it right with shipping it. You've maintained production systems and can defend your tradeoffsAI-native. AI coding tools — Cursor, Claude Code, or similar — are part of how you work, not something you occasionally try You are a great fit if you have: Deep understanding of OAuth 2.0 at the protocol level — flows, token types, authorization models. Experience implementing OAuth (not just consuming it) is a strong advantageStrong Go experience in production. If you have solid backend fundamentals and deep OAuth knowledge from another language, the switch to Go is workable — but it will need to happenSolid MySQL experienceGCP and Kubernetes familiarityA track record of owning backend projects end-to-end: design, cross-team coordination, and delivery — not just the implementationExperience with billing, subscriptions, or payment systems - nice to haveClickHouse or similar columnar databases - nice to have. We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us.