Job Summary

Experience: 5-7 years

Were hiring a Tech Lead to own a significant part of that surface, and the engineers who build it.

Role Overview

Youll lead a team of engineers working across the stack, and youll still be one of the strongest engineers on it. You take the hardest problem of the quarter yourself, youre in the design reviews catching what everyone else missed, and you own the architectural direction for everything your team touches.

Youll also own something less visible and worth more: that there is one right way to do the things that have to be correct. One approach to retries and failure recovery. One source of truth for the numbers customers see. Defined once and inherited, instead of five engineers each arriving at a slightly different, slightly wrong version of it.

Three things matter more than the title you held before:

- Technical direction. You can hold the whole system in your head and say where its going. You make the call between queue and stream, between a recent service and a boundary in an existing one, and you can defend it on trade-offs rather than preference.
- Force multiplication. Your result isnt what you shipped, its what the team shipped and how much better they got doing it. You know where every engineer stands, you deal with a performance problem when you see it rather than when the calendar says to, and youre the reason the strong ones stay and people grows.
- High agency. You act when the spec is unclear instead of waiting for someone to decide for you. Work doesnt stall on your side waiting on another team, you go and unblock it. You stay on the hook for what you ship until it actually works in production, not until its merged.

What You'll Do

- Own the architectural direction across your surfaces, and the trade-offs behind every call
- Design and ship the hardest work yourself, you stay a builder
- Run design reviews that catch races, partial failures, and everything that only breaks at volume
- Define the shared patterns your team inherits, and consolidate the ones that got built twice




- Own operability: what you ship is observable, alerted, and runnable by more than one person
- Grow the engineers on your team, and give leadership an honest, evidence-backed read on each of them
- Run interview loops and make the call on who joins
- Own a customer-facing metric, and cut the work that isnt moving it
- Use AI coding agents as a core part of the workflow, and own the quality bar that keeps their output honest

What Were Looking For

- Distributed systems experience thats real. Services that stay correct when they fail halfway and get retried. Event pipelines that dont lose or duplicate work. You can defend your choice of queue, stream, or store instead of reaching for whichever is fashionable.
- Data at volume. MySQL that holds up under genuine load, schema, indexing, and finding the query thats quietly costing you. Search and analytics at scale with OpenSearch or ClickHouse. Caching as a deliberate decision, not a reflex.
- Credibility across the stack. You review a data-heavy React surfaces state architecture as seriously as you review a service boundary. You dont need to out-build your specialists; you do need to recognise the design that will hurt in six months.
- You can run what you ship. Containerised deploys, CI/CD, and production observability. When something is intermittently timing out, you find it in traces and metrics rather than guessing.
- AI fluency with judgment. You use coding agents daily, and youve thought about what breaks when an entire team does and put something in place for it.
- A track record with people. Engineers youve led who got measurably better, and who you can talk about specifically.

Our stack: Node.js, TypeScript, MySQL, Redis, Kafka, OpenSearch, React, Docker, AWS, Grafana/Tempo/Loki.

Nice to have, not required: ClickHouse, MongoDB, Terraform. Youll pick these up here if you havent used them.

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 Tech Lead at Saleshandy (Ahmedabad)
🏢 SalesHandy
📍 Ahmedabad