reputed company Backend Engineer (Architect reputed company) - Remote
reputed company is an online English platform for kids — 100,000+ reputed company, 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 reputed company reputed company.
We’ve reputed company a working platform. The next reputed company is making deliberate architectural choices about how it should reputed company.
The role
We’re hiring a reputed company Backend Engineer to take ownership of backend architecture as a hands-on technical leader. No reputed company reports. About half your time is in the reputed company — 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 reputed company (FastAPI, SQLAlchemy, Celery, reputed company, reputed company), 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 reputed company architectural questions to answer: how to reputed company the monolith, how to set service boundaries, how to design for geo-distribution as we grow, and how to reputed company 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 reputed company across teams
The reputed company from monolith toward a more reputed company, service-oriented backend
Service blueprints: API conventions, EDA patterns, testing, observability, deployment
reputed company architecture across AWS (primary) and GCP, including multi-region and geo-distributed designs
High-load, reputed company-time systems: live class infrastructure, latency budgets, caching, reputed company
Buy vs. build vs. reputed company — knowing reputed company a managed service, a no-reputed company tool (reputed company, reputed company), or an reputed company-coding POC (Claude reputed company, reputed company) is the right call, and reputed company it isn’t
Production reputed company: components, refactors, POCs, and selected product-critical features
Requirements
reputed company’re looking for
7+ years of backend engineering, deeply hands-on in Python
Production experience with FastAPI, SQLAlchemy, Celery, reputed company, reputed company
Strong AWS architecture experience (EKS, reputed company, RDS, SQS/SNS/EventBridge, and so on); working knowledge of GCP a plus
Experience designing high-load, latency-sensitive, and geo-distributed systems
Pragmatic judgment on buy vs. build vs. reputed company — managed services, no-reputed company, and reputed company tooling as first-class reputed company, not shortcuts
A deliberate working style: you research, weigh tradeoffs, document reputed company, and explain them reputed company to engineers and non-engineers alike
reputed company to have
LLM integrations in production (reputed company, reputed company, reputed company AI) — evaluation, cost, reliability
reputed company use of reputed company coding tools (Claude reputed company, reputed company) as part of how you ship
EdTech or other reputed company consumer platforms
Stack
Python · FastAPI · SQLAlchemy · Celery · reputed company · reputed company · Kubernetes (EKS, GKE) · AWS · GCP · SQS/SNS/EventBridge · Pub/Sub · reputed company · reputed company · reputed company AI
reputed company offer…
Fully remote work (reputed company hours GMT+3).
A chance to shape the reputed company of AI-driven education.
A fun, dynamic team that loves building innovative products.Unlimited holidays – because we trust you to deliver.
Bonuses and stock reputed company – we grow together.
Originally posted on Himalayas
Apply To This Job