Building systems that scale and interfaces that feel alive.

Engineering Process

that scale

01
ARCHITECTURE

Start with real constraints

I begin with real failure points — load, bottlenecks, and edge cases — before thinking about polish or UI.

02
RESILIENCE

Design for failure, not success

Retries, queues, fallbacks, and observability are designed early so systems remain stable under pressure.

03
DELIVERY

Ship the smallest reliable system

I prioritize simplicity and iteration — building systems that are easy to extend, debug, and scale over time.

Experience

MINTSKILL HR SOLUTIONS · 2025-26

Full-Stack Engineer

Architected system design and delivery of a multi-tenant recruitment SaaS processing 10k+ jobs/day.

Multi-tenant

ARCHITECTURE

Shared infrastructure isolation across tenants without data leakage.

Async

WORKFLOWS

Reliable async sync with BullMQ-backed queue processing.

Production

SYSTEMS

Production SaaS delivery with real constraints and real users.

Currently Building

ClipRelay.

A decentralized alternative to Apple's Universal Clipboard. Seamlessly syncs clipboard state and files across macOS, Windows, Linux, and Android over local mDNS without cloud dependencies.

Continuity Infrastructure2026In Progress

Local-first mesh routing. Rust core. E2E Encrypted.

100% Local Mesh
p2p-encryption
Key Engineering Decisions
mDNS over CloudZero latency and absolute privacy on local network.
Rust Core vs ElectronTiny memory footprint and native OS integrations.
X25519 HandshakeTrust-on-first-use authentication without central accounts.
RustTokioReactChaCha20
Selected Work

Core Systems.

Production-grade architectures engineered with real constraints — not just toy demos.

Multi-tenant recruitment platform processing 10k+ jobs daily through event-driven architecture with BullMQ queues, PostgreSQL persistence, and Zoho CRM sync.

10k+ jobs/day
event-driven
GitHub
Next.jsNestJSBullMQPostgreSQLZoho
Key Decisions
Queue vs Real-timeIsolate unpredictable external API latency.
Tenant context at guard levelAvoid per-service duplication.
Modular monolithPrevent multi-tenant code drift.
Landing
Landing1/6
Landing
Landing
Login
Login
Dashboard
Dashboard
Candidates
Candidates
Interviews
Interviews
Reports
Reports
How I build

The goal is not just shipping features. It is making the product feel simple on the surface while the system underneath stays resilient.

What this usually leads to

Clean interfaces

Reliable under pressure

Readable, maintainable systems

INPUTCONSTRAINTSFALLBACKSYSTEM

STEP 01

Map real flows

I start with the actual handoff points, bottlenecks, and messy edge cases before I touch UI polish.

Focus

Users, events, queue boundaries

STEP 02

Design for failure

Retries, isolation, and fallback behavior get designed early so systems stay calm under pressure.

Focus

Backoff, tenant safety, observability

STEP 03

Ship smallest version

I cut extra ceremony, keep the architecture readable, and optimize where it meaningfully changes outcomes.

Focus

Fast iteration, fewer moving parts

Capabilities

What I use to build scalable systems.

Designing APIs, handling concurrency, structuring services for real-world load.

Node.jsNestJSExpress
Open to opportunities

What's next

systems

Designed for scale. Built with intent. Ready to ship.

Navi Mumbai, India
System Status: Nominal
Uptime0m 0s
Requests128,000
Latency42ms
RegionMumbai, IN
Chinmay Kudalkar