> Markdown version of [/jobs/ext/153077-senior-backend-engineer](https://www.wearedevelopers.com/jobs/ext/153077-senior-backend-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Backend Engineer - **Company:** ROUND TWO LLC - **Location:** Stuart, FL, United States (Remote available) - **Experience:** Expert - **Salary:** $110,000.0 - $140,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Audit Trail, Software as a Service, Encodings, Databases, Data Validation, Data Integrity, Database Design, Database Queries, Github, Internet Security, Key Management, PostgreSQL, Query Optimization, Application Data, Next.js, Shopify, TypeScript, Data Logging, Large Language Models, Software Security, Backend, Stripe, Webhooks - **Published:** May 19, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=9e7b37513a519444 ## About the Role Do you have experience in TypeScript?, * Strong PostgreSQL depth - not just read-level comfort, but real experience optimizing schemas, writing complex queries, managing indexes, and understanding how the database behaves under load. * TypeScript fluency and experience on the Node.js / Next.js backend stack. * Hands-on experience with Supabase or a comparable managed Postgres platform, including Row Level Security, edge functions, and the operational realities of running on a hosted stack. * Hyperscaler experience - AWS or GCP. You've built and operated production workloads on at least one, and you understand the tradeoffs involved in migrating to and operating on them versus a managed platform like Supabase/Vercel. * Security as a practice, not a checklist - API security, auth/authz design, secrets management, and the specific risks that come with AI-dependent and API-dependent architectures (prompt injection, data isolation, credential exposure). * Experience building or operating multi-tenant SaaS systems where tenant isolation and data integrity are non-negotiable. * Ownership mindset - you identify problems before they become critical, come with a point of view on how to fix them, and raise them early with context. * Hands-on experience with a local-first or sync engine - Replicache, ElectricSQL, PowerSync, or comparable. You understand the tradeoffs involved in offline-first design, conflict resolution strategies, and what it takes to make realtime sync reliable at scale. Nice to have * Accounting or ERP domain knowledge. * Experience with AI context pipelines - retrieval, embedding storage, and grounding LLM calls in structured application data. * Familiarity with Drizzle ORM or similar TypeScript-native ORMs. * Experience with GitHub Actions and CI/CD pipeline design. * Background in compliance-adjacent environments (SOC 2, financial data handling, audit logging). * Familiarity with LLM output validation and guardrails - understanding how to verify AI-generated content before it touches financial records, and how to build logging and fallback logic into AI-dependent workflows. ## Description We're looking for a Senior Backend Engineer to own that foundation. You'll set the technical standards for the backend, make the architectural calls, and work closely with two full-stack developers and a UX designer. This is an individual contributor role with real ownership - the decisions you make will shape how the system scales and how well it holds up under real business load., * Database design and administration - schema design, query optimization, index strategy, and maintaining PostgreSQL performance as data and tenant volume grow. You understand what slow queries cost and how to fix them before they become a problem. * Multi-tenant data isolation - ensuring clean boundaries between tenant data at every layer, including AI context assembly. In a financial product, a data leak between tenants is not a minor bug. * Secrets and key management - owning how API keys, LLM provider credentials, webhook secrets, and other sensitive credentials are stored, rotated, and scoped. Security here is not UI-driven; it lives in the infrastructure and the code. * API and integration security - authentication, authorization, rate limiting, input validation, and the controls that protect an application that is heavily API- and AI-dependent. You think about attack surface as a first-class concern. * Infrastructure readiness and migration planning - we currently run on Vercel and Supabase (both AWS-hosted). As the platform grows, we'll need to evaluate when and how to migrate to a more robust hyperscaler stack (AWS or GCP). You'll help us recognize that inflection point, plan the migration, and execute it. * Backend standards - setting patterns for how the backend is structured, tested, and maintained. The full-stack developers write backend code too; your job is to make sure the standards are clear and the bar is consistent. * Performance and scalability - identifying bottlenecks before they surface in production, and building with growth in mind from the start. * Local-first storage and sync architecture - designing and maintaining a sync engine that supports offline-first operation, realtime updates, and conflict resolution across a multi-tenant environment. You've evaluated or worked with approaches like Replicache, ElectricSQL, or PowerSync and can make a reasoned call about the right fit for our stack. * Integration standards - establishing the patterns the whole team follows for connecting external services (Stripe, Shopify, webhooks, and a growing list beyond): auth flows, rate limiting, retry logic, error handling, and managing schema drift. Implementation is shared across the team; the standards are yours. ## Related Videos - [Build and Deploy a Fullstack App with Open Source Tooling](https://www.wearedevelopers.com/videos/775-build-and-deploy-a-fullstack-app-with-open-source-tooling) - [Navigating Growth, Scaling Challenges, and Office Expansions with David Singleton, CTO at Stripe](https://www.wearedevelopers.com/videos/100362-navigating-growth-scaling-challenges-and-office-expansions-with-david-singleton-cto-at-stripe) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Innovating Developer Tools with AI: Insights from GitHub Next](https://www.wearedevelopers.com/videos/1268-innovating-developer-tools-with-ai-insights-from-github-next) - [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape) - [Build Your Own Subscription-based Course Platform](https://www.wearedevelopers.com/videos/321-build-your-own-subscription-based-course-platform) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss) - [Dev Digest 138 - Are you secure about this?](https://www.wearedevelopers.com/magazine/486-dev-digest-138-are-you-secure-about-this) - [Dev Digest 119 - ❤️ === ❤️](https://www.wearedevelopers.com/magazine/454-dev-digest-119)