Full Stack Developer (Backend Focused)

Job Description: Hands-on development on a live production SaaS platform. The role covers end-to-end feature delivery, API design, database schema, business logic, and the frontend built on top of it. The focus is backend, with full ownership of features from specification through to production. Responsibilities: • Design, build and maintain REST APIs and backend services in production • Design and evolve database schema — tables, constraints, indexes, migrations • Develop frontend interfaces for delivered features (React / Next.js) • Integrate third-party APIs and external services • Write and review database migrations before they reach production • Debug and resolve production issues • Deploy, monitor and maintain delivered work Short release cycles, direct ownership of shipped features, and involvement across the full stack of the product.

• 2+ years building production backend systems — REST APIs, authentication, integrations, background jobs • Strong in at least one modern backend stack: Python, Node.js, Go, Java or similar • Solid relational database skills — schema design, constraints, indexes, migrations. Comfortable writing SQL, not only ORM calls • Frontend ability — React or a modern JavaScript framework, sufficient to build and ship user-facing features • Proven ownership of features from specification through to production • Clear written English • Bachelor's degree in Computer Science, Engineering, or equivalent practical experience Preferred: • Python / FastAPI — the primary backend stack for this role • Next.js / React • PostgreSQL, and Supabase or another Postgres-based BaaS • Row-Level Security • Migration discipline (Alembic or equivalent) • Async programming • Third-party API integration under real constraints • Cloud deployment, monitoring and CI/CD Candidates who have moved into DevOps or platform engineering and no longer write application code daily, or who prefer backend-only roles with no frontend involvement, are unlikely to be a good match. Applicants should state in the first line of their application: the backend service they are most proud of — the stack used, what it did, and a repository link if public. Applications that do not include this will not be reviewed.