Lead Software Engineer
Location: Remote
As Chegg Skills engineers, our software empowers students to move from 'learning' to 'earning.' We build the applications and systems that help students make life-changing career transitions into high-growth job opportunities. We take pride in making education accessible to motivated career switchers, and we build the technology that helps them achieve mastery and success.
In this role, you will play a leading role in a fully remote team of diverse, motivated engineers who are rethinking what education can look like. Join us and help scale the engineering foundation for our next phase of growth.
We're hiring a Lead Software Engineer, Backend to own the delivery execution of a team building backend services, APIs, and distributed systems for learner-facing and operational experiences. This is a backend-first role with full-stack reach — and the team you lead has that same full-stack reach, not backend-only depth. You need enough fluency across the stack to review a frontend PR, unblock a stuck UI engineer, or make a cross-stack architecture call, not just depth in backend.
This role sits above individual technical ownership: you are accountable for the team's delivery rhythm, you proactively coach engineers before they get stuck, and you act as the technical filter between Product and the team — refining ambiguous asks before they ever reach an engineer's backlog.
Own the team's delivery rhythm and milestone execution — break major epics into milestones with clear dependencies, spot team-wide delivery risk early, and escalate with options already framed, not after deadlines slip.
Act as the technical filter between Product/PM and the team — refine ambiguous product asks into structured technical tasks before they hit the backlog, shielding the team from scope creep and chaotic requirements.
Set and enforce the team's technical and AI-usage norms — review standards, AI code-ownership expectations, and guardrails the whole team follows, so responsible AI usage is the default rather than something you re-check on every PR.
Review,
unblock, and make architecture calls on frontend work (React/Next.js or equivalent), even where you are not hands-on daily — your team's engineers have full-stack reach, and you need to be able to lead across the stack, not just deep in backend.
Design and build backend services and distributed systems with a focus on scalability, reliability, and maintainability, and set the technical roadmap others on the team execute.
Build and extend GraphQL-powered APIs and workflow-driven systems that support learner-facing and operational experiences.
Review PRs with a systemic lens — prevent tight coupling, catch AI-generated code that duplicates existing modules, and enforce long-term maintainability over short-term velocity.
Partner closely with Product, Design, Data Engineering, Platform/SRE, and Content Operations to deliver and harden high-impact workflows.
Most qualified candidates will likely bring 7+ years of professional software development experience building production backend systems.
Solid backend system design experience — distributed systems, scalability, reliability patterns, and service architecture.
Strong experience with Java/Kotlin and/or Python-based backend systems (Spring, FastAPI, Django, or similar frameworks), plus API design and GraphQL integration.
Experience with workflow orchestration systems (Temporal, AWS Step Functions, Airflow, or similar).
Experience debugging production issues end to end, from symptom to root cause, fix, and prevention.
Experience working on async or integration-heavy systems, including retries, timeouts, idempotency, and workflow/state handling.
Strong testing and release-validation discipline in environments where engineers own quality directly.
Experience with observability and operational ownership, including dashboards, alerts, runbooks, and participation in on-call support.
Comfort using AI-assisted development tools responsibly, with the ability to explain, validate, and safely ship the code you produce.
Enough exposure to React/Next.js or frontend web applications to review, unblock, or make architecture calls on frontend work — not necessarily hands-on daily, but enough to lead engineers who have full-stack reach.
Has owned a team's delivery rhythm — breaking epics into milestones, spotting cross-team delivery risk weeks before it becomes a miss — not just their own workstream.
Has coached or mentored engineers with a concrete, named outcome (a promotion, a specific skill gap closed), not generic 'mentored juniors' language.
Has reviewed, unblocked, or made architecture decisions on frontend/web work, or has managed engineers who were themselves frontend or full-stack.
Has set or enforced team-wide technical or AI-usage norms — review standards, AI code-ownership expectations — not just personal practice.
Backend: Python (FastAPI / Django), GraphQL, Kotlin / Java, Spring-based services, Temporal
Frontend: React / Next.js, Node.js, Auth0-integrated web flows
Cloud / Delivery: AWS, Docker, GitLab CI
Observability / Operations: New Relic, Rootly, Playwright
AI / ML: OpenAI, AWS Bedrockk
Our recent research study called State of the Student shows that nearly 3 out of 4 students are working to support themselves through college and 1 in 3 students feel pressure to spend more than they can afford. Since then, we've expanded our offerings to supplement many facets of higher educational learning through Chegg Study, Chegg Math, Chegg Writing, Chegg Internships, Chegg Skills, and more to support students beyond their college experience. These offerings lower financial concerns for students by modernizing their learning experience. Video Shorts
📌 REMOTE Software Developer Lead (Delhi)
🏢 Chegg
📍 Delhi