Tech Lead at Saleshandy

Experience: 5–7 years

About Saleshandy

Saleshandy is how thousands of sales teams around the world find their next customer and reach them. A lead database of 850+ million contacts. Email sequences and mailbox warmup running continuously across tens of thousands of inboxes. Analytics that has to be correct the moment someone looks at it.

Every one of those is a systems problem before it's a product problem, and that's where the interesting work is. Searching hundreds of millions of records in under a second. Processing event streams that can't lose or double-count a message. Building interfaces that stay fast when the dataset behind them only ever grows.

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

What's the Role About

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

You'll 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 it's going. You make the call between queue and stream, between a new service and a boundary in an existing one, and you can defend it on trade-offs rather than preference.
• Force multiplication. Your result isn't what you shipped, it's 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 you're 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 doesn't 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 it's 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 isn't moving it
• Use AI coding agents as a core part of the workflow, and own the quality bar that keeps their output honest

What We're Looking For

• Distributed systems experience that's real. Services that stay correct when they fail halfway and get retried. Event pipelines that don't 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 that's 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 surface's state architecture as seriously as you review a service boundary. You don't 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 you've thought about what breaks when an entire team does and put something in place for it.
• A track record with people. Engineers you've 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. You'll pick these up here if you haven't used them.
https://stackshare.io/saleshandy/saleshandy

Why Join Us

1. Purpose: You'll own a core part of a product used every working day by thousands of sales teams, at a scale, 850 million records, continuous delivery infrastructure, real-time analytics, you can't get at most companies.
2. Growth: This is the seat that leads to Staff Engineer or Engineering Manager here, depending on which half of it you find you love. You'll find out which one you are.
3. Leverage: We're serious about AI-first engineering. You'll set how an entire team works with coding agents, not just how you do.
4. Ownership: Architectural direction, a customer metric, and the team. Not a ticket-routing role with a senior title.

Culture Fit, Are You One of Us

1. You still write code :)
2. You use AI as a multiplier.
3. You don't wait for permission on the calls you can reverse, you make them, write down why, and keep moving.
4. You get genuine satisfaction out of someone else levelling up.
5. You'll tell someone their design is wrong, or that they aren't growing, in a way they can actually hear.
6. You raise a "yellow" early, and you thank the people who do the same.
7. You debug with traces, logs, and metrics, never with guesswork.
8. You'd rather define the right pattern once than personally fix the same bug five times.