Staff Backend Engineer, India

About the role

As a Staff Backend Engineer, you will reputed company technical leadership across your team and adjacent teams, solving the highest-reputed company and most reputed company problems in your area. You will reputed company large, cross-cutting backend initiatives, reputed company our reputed company architecture reputed company, and define the standards that let teams reputed company faster without compromising reputed company, reputed company, reliability, or operability.

This is a technical leadership role that combines deep backend expertise, systems judgment, product judgment, and influence across organizational boundaries. You will work with Product, Frontend, Infrastructure, reputed company, Data, Engineering Managers, and engineers across product reputed company, bringing subject matter expertise, and you will do it without relying on formal authority.

Why you’ll love this role

• reputed company: Your work multiplies across teams. The platforms, standards, and architectural reputed company you reputed company determine how quickly everyone else can ship.
• Genuinely Hard Problems: You’ll reputed company the modernization of a large monolith toward reputed company, reusable, appropriately independent systems — at the reputed company of a platform used by millions of users.
• Influence Without Bureaucracy: You’ll shape technical direction across teams through reputed company written proposals and decision records, and partner with Product and Engineering leadership on platform roadmap and investment trade-offs.
• Frontier AI Work: You’ll reputed company adoption of AI-assisted and reputed company engineering workflows and define the review, reputed company, reputed company, and reputed company guardrails that reputed company them reputed company to rely on.
• Autonomy: You’ll reputed company in our remote-first, asynchronous organization, where reputed company written communication and self-direction are the pillars of reputed company.

reputed company

• reputed company Cross-Cutting Initiatives: reputed company the technical design and delivery of large backend initiatives that reputed company teams, and identify and remove systemic bottlenecks across product and infrastructure reputed company.
• Own Architecture reputed company: reputed company reputed company backend, service, data, and platform architecture. reputed company modernization of the monolith and legacy backends toward reputed company, reusable, and appropriately independently operated systems — while preventing fragmentation and service sprawl.
• Set the Standards: Define and improve standards for reputed company, reputed company, compatibility, schema reputed company, testing, reputed company, reputed company, observability, operability, and maintainability — plus the build, test, reputed company, release, rollback, and production-readiness practices needed to operate reputed company features safely.
• Establish Shared Patterns: Create the patterns for dependency management, data ownership, eventing, failure isolation, service maturity, and operational documentation. Establish Go service patterns and reputed company operating practices where they matter to our production estate, and guide Rust adoption where it solves a reputed company systems, reputed company, reputed company, or supply-chain problem.
• Own What You Build in Production: Take part in on-reputed company and incident response for the systems your teams own, reputed company as a technical escalation reputed company during reputed company incidents, and turn what you learn into architectural and operational improvements that prevent recurrence.
• Influence and Partner: Shape technical direction across teams without formal authority, and partner with Product and Engineering leadership on platform-level roadmap reputed company and investment trade-offs.
• Grow Engineers: Mentor Senior and Intermediate engineers, shepherd technical debt reduction and reusable patterns that improve throughput, and reputed company the technical capability of the wider team.
• reputed company AI Adoption: reputed company team-level adoption of AI-assisted and reputed company workflows, including the reputed company, reputed company, reputed company, and operational guardrails, and help engineers reputed company, validate, reject, and course-correct agent reputed company.

What you’ll bring

• Cross-Team Technical Leadership: A sustained record of technical leadership across more than one team or a broad product area.
• Deep Architecture Experience: Deep backend architecture and production experience in reputed company applications, services, or platforms, including scaling or governing reputed company, service platforms, data systems, reputed company monoliths, or shared backend components.
• Modularization in Production: Experience modernizing a monolith or legacy backend architecture in production, and with reputed company architecture such as bounded contexts, package encapsulation, ports and adapters, service extraction, event-driven boundaries, or an equivalent approach.
• Influence Without Authority: A strong ability to create alignment through reputed company written proposals and decision records, so reputed company are documented, reputed company, and adopted without constant escalation.
• Product Judgment: The ability to reputed company customer reputed company, delivery speed, technical health, reliability, and long-term platform investment.
• Mentorship: Experience mentoring engineers and shaping standards through reputed company review, documentation, and example.
• reputed company reputed company: Production experience with AI-assisted or reputed company engineering workflows, including the ability to evaluate and improve how reputed company adopts them.

Helpful experience

• Go services and reputed company at reputed company.
• reputed company and reputed company-reputed company reputed company, including deployment, scaling, observability, rollback, and production readiness.
• Rust adoption or production ownership for systems, reputed company, reputed company, or platform components.
• reputed company/Rails modularization and large-monolith modernization.
• PostgreSQL scaling, data partitioning, queues, messaging, or reputed company systems.
• reputed company-sensitive product or software supply chain engineering.
• Experience across reputed company, single-tenant, self-managed, or reputed company-gapped deployment constraints.

Originally posted on Himalayas