As a senior engineer on our founding Austin team, you'll own substantial parts of Spoks' backend, from technical design through to production. You'll build alongside our established engineering team in Europe, making the platform faster, more reliable and more efficient as we grow from millions of emails to billions.
The platform and stack
The same communication platform powers Spoks for Shopify merchants and Knips for real estate businesses. It brings together email, SMS, automation, CRM, analytics, forms and AI-powered workflows across web and mobile.
We use NestJS with TypeScript, PostgreSQL and Google Cloud Platform on the backend, React and Next.js with TypeScript for web, and Flutter for mobile. You'll take responsibility for core backend components and help shape architecture and technical direction with the team.
What you will do
- Build backend functionality for email, SMS, automation, CRM, analytics and AI-powered workflows.
- Improve APIs, data flows and database performance as stores and sending volumes grow.
- Make sound decisions about architecture, security and cloud costs, and implement the changes.
- Keep the services you own reliable, with useful monitoring, safe releases and effective debugging.
What you will bring
- You have hands-on experience building and operating large-scale production systems on GCP, AWS or Azure. You can explain the traffic or data volumes involved and how you handled bottlenecks, reliability and cloud costs. Strong experience with any one of these clouds is relevant; you'll work in GCP at Spoks.
- You're strong in TypeScript backend development and relational databases. Experience with NestJS and PostgreSQL is particularly relevant.
- You understand queues, retries and how to keep background processing reliable as workloads grow.
- You can turn an unclear problem into a practical implementation and explain the tradeoffs.
Coding agents
We expect you to use coding agents such as Claude Code and Codex as part of your development workflow. Show us how you give an agent context, break down a task, review its changes and verify the result. You should be able to catch mistakes, redirect the work and explain the code you ship.
What to tell us
Tell us about a backend problem you solved as a product grew. What was happening, what did you change, and did it work? Give us a sense of the scale and your part in it. A short written explanation is enough.



