Logo for Novakid

Principal Backend Engineer (Architect Track) - Remote

Roles & Responsibilities

  • Hands-on backend architecture leadership with strong coding experience in Python (FastAPI, SQLAlchemy, Celery, Postgres, Redis)
  • Experience evolving monoliths toward modular, service-oriented architectures and defining geo-distributed service boundaries
  • Proficiency with cloud architecture on AWS (primary) and GCP for data/AI, including multi-region deployments and observability
  • Ability to trade off buy/build/assemble decisions, document tradeoffs, and communicate architecture choices clearly

Requirements:

  • Own backend architecture standards and major technical decisions across teams, including API conventions, event-driven patterns, testing, observability, and deployment
  • Drive the path from monolith to modular backend with well-defined service blueprints and geo-distribution considerations
  • Design and optimize cloud infrastructure across AWS and GCP for high-load, real-time systems (live classes) with latency budgets and caching
  • Evaluate and select when to buy, build, or use no-code/low-code tools and POCs, delivering production-ready components and refactors

Job description

Novakid is an online English platform for kids — 100,000+ students, 2,500+ teachers, 15+ countries. Live classes run around the clock across time zones, which sets the technical bar: low latency, high availability, and a backend that holds up at real scale.

We’ve built a working platform. The next chapter is making deliberate architectural choices about how it should evolve.

The role

We’re hiring a Principal Backend Engineer to take ownership of backend architecture as a hands-on technical leader. No direct reports. About half your time is in the code — reference implementations, critical components, refactors. The other half is the harder work: deciding what to build, what to buy, what to defer, and why.

Our backend today is a Python core (FastAPI, SQLAlchemy, Celery, Postgres, Redis), surrounded by services and event-driven flows, with a growing AI layer. It runs primarily on AWS, with GCP for data and AI workloads. There are real architectural questions to answer: how to evolve the monolith, how to set service boundaries, how to design for geo-distribution as we grow, and how to integrate AI without accumulating debt. We’re looking for someone who treats those questions seriously — researches before deciding, thinks in tradeoffs, writes things down.

What you’ll work on

  • Backend architecture standards and major technical decisions across teams

  • The path from monolith toward a more modular, service-oriented backend

  • Service blueprints: API conventions, EDA patterns, testing, observability, deployment

  • Cloud architecture across AWS (primary) and GCP, including multi-region and geo-distributed designs

  • High-load, real-time systems: live class infrastructure, latency budgets, caching, capacity

  • Buy vs. build vs. assemble — knowing when a managed service, a no-code tool (Retool, n8n), or an agentic-coding POC (Claude Code, Cursor) is the right call, and when it isn’t

  • Production code: components, refactors, POCs, and selected product-critical features

Back-End Engineer Related jobs

Other jobs at Novakid

We help you get seen. Not ignored.

We help you get seen faster — by the right people.

🚀

Auto-Apply

We apply for you — automatically and instantly.

Save time, skip forms, and stay on top of every opportunity. Because you can't get seen if you're not in the race.

AI Match Feedback

Know your real match before you apply.

Get a detailed AI assessment of your profile against each job posting. Because getting seen starts with passing the filters.

Upgrade to Premium. Apply smarter and get noticed.

Upgrade to Premium

Join thousands of professionals who got noticed and hired faster.