Build the systems behind a better phone call
Taalk gives people one public profile for their contact details and a direct way to call them or plan a time to talk. The app brings context before a call and keeps the transcript, summary, and next steps afterwards.
We’re looking for a back end developer in Stockholm to help make that experience dependable. You’ll work on the services that connect our native apps and web product, with a direct say in how features are designed and built.
What you’ll work on
- Develop GraphQL APIs for profiles, contacts, availability, and scheduled calls.
- Build reliable call signalling, subscriptions, and notifications. Handle reconnects, retries, and events arriving out of order.
- Improve data models, database queries, and migrations as the product grows.
- Connect calendar and communications services, with clear boundaries around authentication, permissions, and personal data.
- Add useful tests, tracing, and monitoring so we can understand failures and resolve them quickly.
- Work with frontend, mobile, and design to take features from an idea through to release.
Our stack
TypeScript and Node.js, Express, Apollo Server and Pothos for GraphQL, PostgreSQL with Prisma, Redis, and WebSocket subscriptions. We use OpenTelemetry for observability and integrate with calendar, notification, and calling services.
What you’ll bring
- Experience shipping and maintaining backend services in TypeScript or a comparable language.
- A solid understanding of API design, relational databases, authentication, and authorisation.
- Care with concurrency, data consistency, and failure handling.
- The ability to explain trade-offs, review code thoughtfully, and work through an unfamiliar problem.
Experience with real-time systems, calling infrastructure, calendar integrations, or GraphQL is useful. You don’t need to have used every part of our stack.
Apply
This role is based in Stockholm. Email jobs@taalk.app with your CV or LinkedIn profile and a short description of a backend system you helped build. Tell us what you owned, a difficult decision you made, and what you learned. Code or project links are welcome if you can share them.