Browse current jobs

Senior Software Engineer

LeadSquared · Bangalore

Apply on employer website

Source and collection record

Read the employer source

Last observed by our collector: . 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.

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

Collected role description

<h2>Senior Software Engineer (Backend-heavy Full Stack)</h2> <p><strong>Experience:</strong> 4+ Years<br /> <strong>Team:</strong> Converse Engineering<br /> <strong>Location:</strong> Bangalore, Karnataka<br /> <strong>Primary Skillset:</strong> Backend-heavy full stack, distributed and event-driven systems</p> <h3>Role Overview</h3> <p>You will own systems end to end: design, implementation, 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.</p> <h3>About the Team</h3> <p>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.</p> <p>Converse is shared infrastructure. Several LeadSquared products depend on it for message delivery, including products unrelated to chat, so interface contracts, backward compatibility and availability are first-order concerns.</p> <h3>Core Responsibilities</h3> <ul> <li> Design, build and operate high-throughput, event-driven, multi-tenant backend services. </li> <li> Build and extend integrations with external messaging providers and reduce the cost of onboarding each new provider. </li> <li> Build data pipelines over high-volume message delivery and engagement events. </li> <li> Contribute to platform-level data modelling across chat and channel domains. </li> <li> Ensure correctness under multi-tenancy, including encryption, key management, consent and regulatory rules that vary by market. </li> <li> Instrument what you build for production diagnosis through metrics, logs, traces and alerting. </li> <li> Own the running cost of your services and treat infrastructure spend as a design constraint. </li> <li> Operate services in production and debug across service boundaries with Product, QA, DevOps and provider teams. </li> <li> Contribute to architecture reviews and technical direction for the platform. </li> </ul> <h3>Expected Candidate Profile</h3> <ul> <li> 4+ years of experience building and operating production backend services. </li> <li> Strong proficiency in at least one server-side language: Node.js/TypeScript, Java, Go or C#. </li> <li> Strong understanding of event-driven and distributed systems, including queues, streams, consumer design, idempotency, ordering and failure handling. </li> <li> Ability to debug across distributed systems. </li> <li> Experience with relational and non-relational data stores and sound judgement in choosing between them. </li> <li> Experience designing APIs other teams build on, with attention to contracts and backward compatibility. </li> <li> Strong React and TypeScript skills with production experience owning user-facing interfaces, including real-time or event-driven applications. </li> <li> Strong problem-solving and data structures fundamentals. </li> <li> Accountable for code you did not write by hand, including anything produced with AI assistance. </li> </ul> <h3>Preferred Experience</h3> <ul> <li> Messaging, CPaaS or communication platforms such as WhatsApp Business API, SMS aggregators, push services or telephony. </li> <li> Third-party provider integration or middleware at scale. </li> <li> Experience across multiple backend ecosystems, such as JVM alongside Node.js. </li> <li> Strong AWS experience and streaming platforms such as Kafka, Pulsar, Kinesis or Redis Streams. </li> <li> Micro-frontend architecture, fine-grained reactivity models or performance work with Web Workers. </li> <li> Multi-tenant SaaS and regulated or compliance-sensitive systems. </li> <li> Reliability engineering, observability and cloud cost optimisation at scale. </li> <li> Taking a system from first implementation to a platform other teams depend on. </li> </ul> <h3>Technology Environment</h3> <p><strong>Backend:</strong> Node.js, TypeScript, NestJS, Express, Serverless Framework, Java, Spring Boot, Spring Cloud Gateway, Micronaut, OpenFeign, Resilience4J, jOOQ</p> <p><strong>Data:</strong> MySQL, DynamoDB, Elasticsearch, Redis</p> <p><strong>Messaging & Streaming:</strong> Kafka, Pulsar, Redis Streams, Kinesis, SQS/SNS</p> <p><strong>Infrastructure:</strong> AWS Lambda, EKS, Batch, API Gateway, KMS, S3, CloudFront, Docker, Helm, Bitbucket Pipelines</p> <p><strong>Frontend:</strong> React 18, Preact, TypeScript, Signals, Micro-frontends, WebSockets, Web Workers</p> <h3>About the Opportunity</h3> <p>This is a platform engineering role. The systems are consumed by several LeadSquared products and constrained externally by platform providers, telecom regulators and carriers. The problems are centred around scale, correctness and reliability, with strong individual ownership.</p>

Collected experience requirement

4 - 6 Years