Lead Software Engineer

LeadSquared · Bangalore

Source and collection record

Last observed by our collector: 8 October 2026 at 11:40 pm IST. This is not a manual review or a confirmation from the employer.

Job type and experience labels are automated discovery categories. The employer determines eligibility. Original experience wording was not retained separately; check the current employer page.

How sourcing and classification work · Report a discrepancy

Your application evidence checklist

Mark the statements you can support after reading the employer source. This checklist stays on this page; it does not score your eligibility or submit an application.

Attendance and availability: I checked the employer page for work location, office attendance, start date and duration.Current requisition: I checked the current employer requisition and its application requirements.

0 of 2 checks marked. Keep unresolved requirements as questions for the employer.

Collected role description

<h1>Lead Software Engineer (Backend-heavy Full Stack)</h1><h2>Role Overview</h2>Role: Lead Software Engineer Experience: 6+ Years Team: Converse Engineering Primary Skillset: Backend-heavy full stack; distributed, event-driven systems; technical leadership Location: Bangalore, Karnataka, IndiaYou will own systems end to end: from design and implementation to production operation and debugging. The weight is on the backend, but you are expected to build and own the interfaces that sit on top of it.This is a hands-on role with technical leadership responsibilities. Alongside your own delivery, you will lead the design of larger workstreams and help grow the engineers around you.<h2>About the Team</h2>Converse is LeadSquared's conversation platform. It comprises the agent-facing chat applications and the underlying channel layer that delivers messages across an expanding portfolio of communication channels.Converse is shared infrastructure. Several LeadSquared products depend on it for message delivery, including products unrelated to chat. As a result, interface contracts, backward compatibility, and availability are first-order concerns.<h2>Core Responsibilities</h2><ul><li>Design, build, and operate high-throughput, event-driven, multi-tenant backend services and the interfaces on top of them.</li><li>Own the platform's integration surface: external messaging providers, the pipelines behind them, and the cost of onboarding each new provider.</li><li>Own correctness, observability, and running costs across your area, including multi-tenancy, encryption, and regulatory requirements that vary by market.</li><li>Lead the technical design of larger workstreams and break them into work that other engineers can execute independently.</li><li>Mentor senior and mid-level engineers through design reviews, code reviews, and pairing.</li><li>Set and uphold engineering standards for the team across design, testing, and operational readiness.</li><li>Own architecture and technical direction for your area and represent the team in cross-team discussions.</li></ul><h2>Expected Candidate Profile</h2><ul><li>6+ years of experience building and operating production backend services, with depth in distributed, event-driven architecture.</li><li>Strong proficiency in at least one server-side language — Node.js/TypeScript, Java, Go, or C# — and the ability to work effectively across unfamiliar technology stacks.</li><li>Strong React and TypeScript skills, with production experience owning user-facing interfaces, including real-time or event-driven applications.</li><li>Strong experience designing APIs and data models that other teams build on.</li><li>A track record of leading the design and delivery of workstreams spanning several engineers.</li><li>Experience mentoring engineers and raising the technical bar of a team.</li><li>Ability to make architectural decisions, defend them, and change position when the argument warrants it.</li><li>Accountability for code you did not write by hand, including code produced with AI assistance.</li></ul><h2>Preferred Experience</h2><ul><li>Experience with messaging, CPaaS, or communication platforms: WhatsApp Business API, SMS aggregators, push services, or telephony.</li><li>Experience with third-party provider integration or middleware at scale.</li><li>Depth in more than one backend ecosystem, such as the JVM alongside Node.js.</li><li>Deep AWS expertise and experience with streaming platforms such as Kafka, Pulsar, Kinesis, or Redis Streams.</li><li>Experience with multi-tenant SaaS and regulated or compliance-sensitive systems.</li><li>Experience in reliability engineering, observability, and cloud cost optimisation at scale.</li><li>Experience taking a system from its first implementation to a platform that other teams depend on.</li><li>Experience growing engineers into independent owners of significant systems.</li><li>Experience leading technical evaluations of external providers and contributing to technical hiring.</li></ul><h2>Technology Environment</h2>Backend: Node.js, TypeScript, NestJS, Express, Serverless Framework, Java, Spring Boot, Spring Cloud Gateway, Micronaut, OpenFeign, Resilience4J, jOOQData: MySQL, DynamoDB, Elasticsearch, RedisMessaging and Streaming: Kafka, Pulsar, Redis Streams, Kinesis, SQS/SNSInfrastructure: AWS Lambda, EKS, Batch, API Gateway, KMS, S3, CloudFront, Docker, Helm, Bitbucket PipelinesFrontend: React 18, Preact, TypeScript, Signals, micro-frontends, WebSockets, Web Workers<h2>About the Opportunity</h2>This is a platform engineering role. The systems are used by several LeadSquared products and are subject to external constraints from platform providers, telecom regulators, and carriers. The problems center on scale, correctness, and reliability.The leadership here is exercised first through design, review, and mentoring. How the role develops from there depends on the person in it.

Collected experience requirement

5 - 7 Years