Chegg logo

Chegg

Lead Software Engineer

🇮🇳 Remote - IN 🕑 Full-Time 💰 TBD 💻 Software Engineering 🗓️ November 17th, 2026
Python AWS React

Edtech.com's Summary

Chegg is hiring a Lead Software Engineer. The role leads a fully remote, backend-focused engineering team at Chegg Skills, the division serving post-collegiate learners who are moving from learning to earning. The lead owns the team's delivery rhythm, coaches its engineers, and acts as the technical link between Product and the team.

Highlights
  • Own the team's delivery rhythm by breaking epics into milestones with clear dependencies, spotting delivery risks early, and escalating with options already framed.
  • Refine ambiguous product requests into structured technical tasks before they reach the backlog, coach engineers by pairing on complex bugs and designs, and contribute to hiring and team health.
  • Design and build backend services and distributed systems, including GraphQL-powered APIs and workflow-driven systems behind learner-facing and operational experiences, and set the technical roadmap the team executes.
  • Improve the reliability of integration-heavy and asynchronous workflows through retries, idempotency, error handling, and recovery paths.
  • Review pull requests with a systemic lens, make architecture calls on React and Next.js frontend work, and set the team's review standards and AI-usage norms.
  • Partner with Product, Design, Data Engineering, Platform/SRE, and Content Operations, and drive cross-squad initiatives that produce shared tooling and workflow templates other teams adopt.
  • Around seven or more years of professional software development experience building production backend systems, with strong distributed systems design and Java/Kotlin and/or Python experience in frameworks such as Spring, FastAPI, or Django.
  • Experience with workflow orchestration tools such as Temporal, AWS Step Functions, or Airflow, plus end-to-end production debugging, observability, and on-call support.
  • Prior ownership of a team's delivery rhythm and coaching of engineers toward concrete outcomes, along with enough React and Next.js exposure to lead engineers with full-stack reach.
  • Fully remote role listed under Chegg's New Delhi, India location, working with a stack that includes Python, Kotlin and Java, Temporal, AWS, Docker, GitLab CI, and New Relic.

Lead Software Engineer Full Description


Job Description
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. We serve thousands of students and educators every year, and your work will directly shape how those students learn and succeed.

Chegg Skills is a growing division of Chegg focused on post-collegiate learners. We are continuing to grow our engineering team to support business expansion as more students take the next step in their careers with Chegg. Join us and help scale the engineering foundation for our next phase of growth.
 
About the Role
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.

What You'll Do

  • 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.
  • Proactively coach engineers on the team — pair on complex bugs and designs, and spot technical struggles before they become delivery blockers, not just when asked.
  • 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.
  • Improve reliability for integration-heavy and asynchronous workflows, including retries, idempotency, error handling, and recovery paths.
  • 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.
  • Drive cross-squad initiatives to completion, producing artifacts (shared tooling, workflow templates, register items) that other teams adopt without reinventing them.
  • Partner closely with Product, Design, Data Engineering, Platform/SRE, and Content Operations to deliver and harden high-impact workflows.
  • Treat hiring, calibration input, and team-health contributions as first-class work, not something you respond to only when chased.

Required Qualifications Technical

  • Most qualified candidates will likely bring 7+ years of professional software development experience building production backend systems.
  • Strong 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.
Leadership & Scope
  • 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 acted as the technical filter between Product/PM and an engineering team — refining ambiguous requirements before they reached engineers.
  • Has driven cross-squad initiatives to completion, producing artifacts (shared tooling, workflow templates, register items) that other teams adopted without reinventing them.
  • Has set or enforced team-wide technical or AI-usage norms — review standards, AI code-ownership expectations — not just personal practice.
Tech Stack
  • 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

Why do we exist?
Students are working harder than ever before to stabilize their future. 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. We founded our business on provided affordable textbook rental options to address these issues. 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. We exist so students everywhere have a smarter, faster, more affordable way to student.
Video Shorts
Chegg Corporate Career Page: https://jobs.chegg.com/
 
Chegg out our culture and benefits!
Chegg is an equal opportunity employer