Python SDE

Systems Problems · APIs · Workflows · Operational Reliability

Bengaluru 5+ years Full-time Reports to Engineering Lead 6 openings

About the Role

This is a backend engineering role for engineers who enjoy solving real-world systems problems across APIs, workflows, integrations, data correctness, background jobs, platform logic, and operational reliability. We value engineers who can think in systems, reason through trade-offs, and build backend foundations that remain reliable as complexity grows.

What We Are Looking For

• 5+ years of backend engineering experience with strong Python proficiency
• Enjoy solving real-world systems problems: APIs, workflows, integrations, data correctness, and background jobs
• Ability to think in systems and reason through trade-offs in architecture and design
• Experience building backend foundations that remain reliable as complexity grows
• Comfort with platform logic, event-driven systems, and operational reliability patterns
• Experience with data pipelines, geospatial systems, or financial rails is a plus
• Comfortable working closely with frontend engineers, product managers, and operations teams

What Success Looks Like

In the first 6 months, the strongest engineers here ship meaningful work to production consistently, become dependable in at least one core area of the platform, and understand the operational and business context behind the systems they build. They raise the quality bar through better judgment, sharper execution, and stronger follow-through.

The Environment

Product decisions are tied to operational reality. Engineers are expected to understand workflows, not just APIs. Documentation, reviews, instrumentation, and iteration matter. Delivery is visible and predictable. Speed matters, but not at the cost of judgment.

Non-Negotiables

• Understand the problem before coding.
• Care about data correctness, edge cases, and production robustness.
• Collaborate well with frontend and product teams.
• Maintain code hygiene across naming, structure, testing, and documentation.
• Accept critique without ego.
• Ship iteratively and measure impact.