SDE-2 – Performance & Scalability

Hey There

At Saleshandy, we're building the Cold Email Outreach platform of the future. We're building a product toward eliminating manual processes and helping companies generate more replies / book more meetings / generate leads (faster). Since our founding in 2016, we've grown to become a profitable, 100% geographically dispersed team of 65+ high-performing happy people who are dedicated to building a product that our customers love.

What’s the Role About?

Ever wondered how Saleshandy schedules millions of emails and still feels lightning-fast? Behind that magic is performance engineering.

We’re hiring a Performance Engineer who thrives on making systems faster, leaner, and more reliable across backend, frontend, and infrastructure. Your mission : eliminate latency, fix CPU / memory bottlenecks, optimize queries, tame queues, and guide teams to build with performance in mind.

This isn’t just about fire-fighting, it’s about owning speed as a product feature. You’ll work across the stack and use deep diagnostics, smart tooling, and system intuition to make things fly.

Why Join Us?

1. Purpose :   Your work will directly impact page speeds, email throughput, scale. At Saleshandy, performance isn’t a luxury, it’s part of our premium promise.

2. Growth :   You’ll operate across multiple teams and tech layers, Node.js, MySQL, Redis, React, Kafka, ClickHouse, AWS, with the freedom to shape how we build fast systems.

3. Motivation : If you’ve ever celebrated shaving 500ms off a page load, or chased a memory leak across 3 services just for fun, this is your home. We celebrate engineers who care about P99s, flamegraphs, and cache hits.

Your Main Goals

1. Identify and Eliminate Backend Bottlenecks (within 90 days)

Run deep diagnostics using Clinic.js, heap snapshots, GC logs, and flamegraphs. Tackle high CPU / memory usage, event loop stalls, and async call inefficiencies in Node.js.

Goal : Cut backend P95 response times by 30–40% for key APIs.

2. Optimize MySQL Query Performance & Configuration (within 60 days)

Use slow query logs, EXPLAIN, Percona Toolkit, and indexing strategies to tune queries and schema. Tune server-level configs like innodb_buffer_pool_size.

Target : Eliminate top 10 slow queries and reduce DB CPU usage by 25%.

3. Improve Frontend Performance & Load Time (within 90 days)

Audit key frontend flows using Lighthouse, Core Web Vitals, asset audits. Drive improvements via lazy loading, tree-shaking, and code splitting.

Goal : Get homepage and dashboard load times under 1.5s for 95% users.

4. Make Infra & Monitoring Observability-First (within 120 days)

Set up meaningful alerts and dashboards using Grafana, Loki, Tempo, Prometheus. Lead infra-level debugging — thread stalls, IO throttling, network latency.

Goal : Reduce time-to-detect and time-to-resolve for perf issues by 50%.

Important Tasks

1. First 30 Days – System Performance Audit

Do a full audit of backend, DB, infra, and frontend performance. Identify critical pain points and quick wins.

2. Debug a Live Performance Incident

Catch and resolve a real-world performance regression. Could be Node.js memory leak, a slow MySQL join, or Redis job congestion. Share a full RCA and fix.

3. Create and Share Performance Playbooks (by Day 45)

Build SOPs for slow query debugging, frontend perf checks, Redis TTL fixes, or Node.js memory leaks. Turn performance tuning into team sport.

4. Guide Teams on Performance-Aware Development (within 90 days)

Create internal micro-trainings or async reviews to help devs write faster APIs, reduce DB load, and spot regressions earlier.

5. Use AI or Smart Tooling in Diagnostics

Try out tools like Copilot for test coverage, or use AI-powered observability tools (e.g. Datadog AI, Loki queries, etc.) to accelerate diagnostics.

6. Build Flamegraph / Profiling Baselines

Set up and maintain performance profiling baselines (using Clinic.js, 0x, etc.) so regressions can be caught before they ship.

7. Review Queues and Caching Layer

Identify performance issues in Redis queues — retries, TTL delays, locking — and tune caching strategies across app and DB.

8. Contribute to Performance Culture

Encourage tracking of real metrics : TTI, DB query time, API P95s. Collaborate with product and engineering to define what “fast enough” means.

Experience Level : 3–5 years

Tech Stack : Node.js, MySQL, Redis, Grafana, Prometheus, Clinic.js, Percona Toolkit

Culture Fit – Are You One of Us?

We're a fast-moving, globally distributed SaaS team where speed matters  not just in product, but in how we work. We believe in ownership, system thinking, and real accountability.

If you like solving hard problems, value simplicity, and hate regressions, you’ll thrive here.