Job title: Technical Lead – Cloud Platform &
Connected Systems
Location: Chennai, Tamil Nadu
Work model: Primarily Office Based
Reporting to: Engineering Manager
Team size: Initially 4–7 software engineers, with close collaboration
across QA, DevOps/platform engineering, and firmware/hardware-adjacent teams
Compensation: TBD
Role summary
We are hiring a hands-on Technical Lead to own the design and delivery of cloud
and application-platform capabilities for connected software systems. This role
is best suited to a senior engineer who is strongest in backend and
cloud-native platform engineering, can lead a small team, and has practical
exposure to telemetry, IoT, edge-connected, or hardware-integrated software
products.
You will
lead the software architecture and execution of APIs, services, data flows,
deployment patterns, and operator-facing applications that connect cloud
systems with devices or field systems. This is not a firmware lead role
and it is not a pure people-management role. The centre of gravity is
modern cloud/platform engineering with real-world connected-systems
integration.
· Lead
the technical design and delivery of cloud-native services, APIs, and platforms
components for connected software products.
· Provide
day-to-day technical leadership for a small engineering team, including task
breakdown, code review, mentoring, and technical decision-making.
· Design
resilient backend systems for telemetry, device or edge integration, data
ingestion, event processing, and operational workflows.
· Work
with frontend engineers, or contribute directly where needed, to support
internal tools, dashboards, and operator-facing web applications.
· Define
and improve engineering standards for system design, testing, release quality,
observability, and operational reliability.
· Collaborate
closely with product, QA, DevOps/platform, and firmware or hardware-adjacent
teams to deliver end-to-end outcomes.
· Support
production operations through incident review, root-cause analysis, and
iterative improvements to reliability and visibility.
· Contribute
to architecture roadmaps, technical hiring, and capability-building within the
software team.
· 8+
years in software
engineering, with at least 2 years in a technical lead, staff engineer,
or architecture-ownership role.
· Strong
hands-on experience in one primary backend language: Python or Java or JVM. Working familiarity with the other is useful but not mandatory.
· Proven
experience building and operating cloud-native or distributed systems using at least one major cloud platform and modern container tooling such as Docker and Kubernetes.
· Strong
design and implementation experience with APIs, microservices, event-driven
systems, SQL/PostgreSQL, and production-grade backend services.
· Practical
experience with connected systems such as telemetry platforms, IoT
products, industrial software, remote monitoring, edge-connected services,
device integration, or hardware-adjacent applications.
· Experience
leading engineers through architecture reviews, delivery planning, code
quality, and technical problem-solving.
· Experience
with React, Angular, or TypeScript for internal tools, operational
dashboards, or web applications.
· Experience
with observability and monitoring tools such as Prometheus, Grafana,
OpenTelemetry, Datadog, or Splunk.
· Familiarity
with CI/CD, infrastructure automation, and Git-based release workflows.
· Exposure
to message brokers or streaming systems such as Kafka, MQTT, RabbitMQ,
or cloud-native event services.
· Familiarity
with security-by-design, identity/access patterns, and secure
API/platform engineering.
· Domain
exposure in industrial automation, mobility, robotics, drones, smart
devices, or connected equipment.
· Exposure
to AI-enabled features or ML-backed services is welcome, but not required.
Requirements
· Bachelor’s degree in Computer
Science, Electronics, Information Technology, or a related engineering
discipline. Equivalent practical experience is also acceptable.
· Typical fit: 8–12 years of
software engineering experience in product, platform, GCC, or high-quality
engineering-services environments.
· Within 3 months, build a strong
understanding of the current architecture, deployment model, engineering
workflow, and product roadmap.
· Within 6 months, own one or
more critical platform or service areas end to end, and drive measurable
improvements in code quality, delivery predictability, and system reliability.
· Within 9 months, establish
clearer engineering standards across APIs, observability, testing, and release
readiness.
· Within 12 months, have
materially improved the platform’s ability to support connected-system
workflows, scaled team delivery, and reduced recurring production or
integration issues.
