Software Engineer 3 · Backend systems

Node.js · TypeScript · Distributed systems

I build software that survives real traffic.

I own backend services from architecture to production: event-driven systems, caching, query performance, CI/CD, deployments, and the product workflows sitting on top of them.

6microservices owned end to end
~300kmonthly active users on Vision
5+ yrsbuilding across product and platform layers

01 / Selected work

Systems with real responsibilities.

Products where performance, reliability, search, events, and delivery all matter because users notice when any one of them fails.

Hackathon platform

Vision

Own six microservices across feature development, Kafka event streaming, Redis caching, query optimization, testing, CI/CD, deployments, and production operations.

Node.jsKafkaRedisPostgreSQL

Commerce search

Sparq

Worked on catalog search and synchronization for large Shopify catalogs, including indexing, infrastructure migrations, and faster data freshness.

TypeScriptKoaLuceneAzure

BigCommerce operations

Trackorder

Built a merchant delivery-tracking product from scratch and led a cross-functional team through implementation, review, testing, and launch.

Node.jsVue / NuxtPostgreSQLGitHub Actions

02 / Engineering approach

Make complexity easier to own.

I care less about collecting infrastructure and more about making the system understandable when traffic spikes, dependencies fail, or requirements change.

01

Start with boundaries.

Give each service a clear responsibility and make data ownership explicit before adding queues, caches, or another fashionable box to the diagram.

02

Measure before optimizing.

Use query plans, latency percentiles, event-loop delay, cache hit rates, and downstream pressure to decide what deserves engineering time.

03

Carry it into production.

Testing, rollout strategy, observability, and rollback are part of the feature. A merge is not the finish line.

03 / My story

One layer led to the next.

Frontend taught me to see the user. Backend work taught me to see the system. Production ownership forced both views to agree.

Interface

Started with what people see.

Responsive web interfaces and frontend fundamentals gave me an instinct for the product experience behind every API.

Product

Built across the stack.

Trackorder brought Node.js, PostgreSQL, Vue/Nuxt, team leadership, and launch responsibility into one product.

Scale

Moved beneath the surface.

Sparq pushed deeper into catalog search, synchronization, indexing, infrastructure, and performance.

Ownership

Now I carry systems to production.

Vision combines product features with events, caching, query tuning, deployments, and operations across six services.

Engineering notes

Blogs

Short, practical notes about backend systems, performance, reliability, and the decisions that matter after the happy-path demo ends.

View all engineering notes →

04 / Contact

Let’s talk about what you’re building.

Backend-heavy product engineering, distributed systems, performance, and taking services from design to production.