Pragmatic Fullstack Engineer · TypeScript · Node.js · NestJS · Next.js · React · Python · AWS

I'm a pragmatic fullstack engineer with ~5 years of commercial experience, built mostly inside a software-house environment where switching between projects, stacks, and business domains is the norm.

My strongest confidence today is around TypeScript, Node.js, NestJS, Next.js, and React on the frontend/backend, with solid backend work in Python/FastAPI and PHP/Laravel, plus real AWS + Terraform experience connecting application decisions to infrastructure reality.

I care about maintainability, tests, performance, and developer experience - not as dogma, but because good structure and good tooling make everything after day one cheaper and safer.

Languages & core TypeScript · JavaScript · Python · PHP · SQL · Node.js · Bun

Backend NestJS · FastAPI · Laravel · Django · Express · REST APIs · WebSockets · Event-Driven Architecture · webhooks · queues / async jobs (Redis, Horizon, Celery)

Frontend React · Next.js · Redux · Zustand · React Query · RxJS · React Hook Form · Styled Components · shadcn/ui · Tailwind · Ant Design · semantic HTML & WCAG-aware UI

Data PostgreSQL · MySQL · Redis · DuckDB · InfluxDB · vector databases · large-table query optimization & data-heavy frontends

Cloud & infra AWS (ECS, Lambda, EC2, RDS, ElastiCache, CloudFront, WAF, Kinesis, EventBridge) · Terraform · Docker / Docker Compose · nginx

AI-enabled product engineering OpenAI tool-calling · RAG · in-product agents · Claude Code / OpenCode workflows · structured agent context (AGENTS.md, CLAUDE.md)

Testing & DX / CI-CD Jest · Cypress · Playwright · ESLint · Biome · Prettier · Ruff · GitHub Actions · GitLab CI · CircleCI · pre-commit · conventional commits · npm workspaces / monorepos

• Pragmatic over dogmatic. I value clean architecture and design patterns, but I understand tradeoffs and inherited, imperfect systems. I optimize the next section I touch.
• Tests aren't optional. Without them, a team can't honestly say a change is still safe - especially now that AI accelerates how fast code is written.
• Strong on foundations. Tooling, CI/CD, linting, conventions, and project rules. One day spent on good automation can save weeks over a year.
• AI as an executor, not an authority. I use AI heavily but with structure - clarify the problem first, keep the human as architect and reviewer. When I genuinely want to learn something, I turn the agents off.
• Initiative over complaints. Anyone can point out what's weak; I try to bring two or three realistic solutions with it.