Available for new projects & full-time roles

Let's Talk

Senior Full Stack Developer & Technical Leader

I own outcomes, not tickets: architecture decisions, product tradeoffs, and delivery risk, then the accountability for what happens after

Solution Architect

Owns system design decisions end to end, from RFC to rollout, and defends the tradeoffs made along the way

Product-Minded Engineer

Sits close enough to the roadmap to challenge it, and turns business intent into technical scope

Decision Owner

Default answer to ambiguous problems is a decision, not an escalation, with the accountability to match

Highlights

As A Solution Architect

I want to own system design decisions from RFC to rollout

So that engineering teams inherit fewer regrets and less rework

5+ years experience30+ systems shipped to productionFinal say on architecture across multiple teams

As A Technical Leader Moving Toward Staff Scope

I want to set technical direction across teams, not just within one

So that the organization ships coherent systems instead of eleven local optima

25+ developers mentored5+ teams ledCross-team standards authored and enforced

As A Product-Aware Engineer

I want to sit in on roadmap and prioritization conversations, not just sprint planning

So that technical decisions get made with business context, not in a vacuum

Direct client ownershipScope and tradeoff calls made pre-build95% delivery success rate

Epic Journey

The Foundation Years

Built strong fundamentals through self-directed learning and practical projects, with an early bias toward shipping over studying

  • Mastered the MERN stack through hands-on production work, not tutorials
  • Built and shipped a production-ready LMS serving 5k+ users solo
  • Learned to take a system from zero to live without a safety net

The Ownership Shift

Moved from assigned work to owned outcomes, and started making architecture calls other people had to live with

  • Led an enterprise migration from VB.NET to a modern web stack, owning the technical roadmap end to end
  • Made the call on system boundaries, data models, and rollout sequencing, not just implementation
  • Mentored 25+ developers while staying hands-on, the classic staff-track split

The Authority Phase

Now operating with architectural and product authority across projects, not just technical authority within one

  • Set technical direction and standards enforced across multiple teams
  • Architected microservices handling 10K+ concurrent users, and owned the capacity and failure-mode decisions behind that number
  • Delivered for international clients where scope, tradeoffs, and outcome were mine to own, not just the code

How I Make Decisions

The operating pattern behind moving from senior to staff, and staff to VP-track: less time writing code, more time deciding what code should exist and why.

RFC before code

Contentious or expensive decisions get written down, with tradeoffs stated explicitly, before implementation starts

Reversibility first

Decisions get sorted by how expensive they are to undo. Cheap-to-reverse calls get made fast and alone. Expensive ones get a written case

Own the blast radius

If a decision is mine to make, the outcome is mine to answer for. No distributing credit for wins and diffusing blame for failures

Business context before technical elegance

A technically correct answer that ignores product timing or client reality is the wrong answer

Technical Expertise

🎨

Frontend Technologies

  • React, Next.js, Remix, Redux/RTK
  • Vue, Nuxt, Vuex, Pinia
  • Svelte, SvelteKit, Qwik
  • React Native, Flutter, Ionic
  • TypeScript, JavaScript, WebAssembly

Backend & APIs

  • Node.js, Express, NestJS, Fastify
  • Django, DRF, FastAPI, Flask
  • GraphQL, REST, gRPC, WebSockets
  • OAuth2, JWT, API Gateway
  • Message Queues (RabbitMQ, Kafka)
💾

Data & Storage

  • PostgreSQL, MySQL, MSSQL
  • MongoDB, Cassandra, Redis
  • Elasticsearch, Clickhouse
  • Data Modeling & Normalization
  • Query Optimization & Indexing
🏗️

System Architecture

  • Microservices, Event-Driven
  • Monolithic, Layered, Hexagonal
  • CQRS, Event Sourcing
  • Serverless, FaaS, BaaS
  • Domain-Driven Design (DDD)
🧮

Core CS Concepts

  • DSA, Time/Space Complexity
  • Design Patterns, SOLID, Clean Code
  • Concurrency, Threading, Async
  • Distributed Systems, CAP Theorem
  • System Design & Scalability
🔧

DevOps & Infrastructure

  • Docker, Kubernetes
  • CI/CD, GitOps, Infrastructure as Code
  • AWS S3, Ec2, Cloudefront, RDS, Amplify,EFS
  • Monitoring, Logging, Tracing
  • Security Best Practices, OWASP

Beyond Code

IoT & Custom Rigs

Building smart home automation systems and custom PC setups for optimal performance

Generative AI

Exploring and developing AI models for creative problem-solving and automation

Music Lover

Finding inspiration in melodies while coding and creating playlists for different programming moods