From Pull Request to Production
The PR-driven workflow behind this platform: GitHub Actions as the quality gate, Nx affected checks, Vercel previews, and production deploys that stay out of CI.
Read articleHello! I'm a
Full-Stack Engineer
Building scalable software, exploring architecture, and documenting the journey from Senior Engineer to Staff Engineer and beyond.
Biography
About me
Senior Software Engineer with 10+ years of experience building large-scale enterprise web applications using Angular, TypeScript, JavaScript, and Node.js. I lead frontend architecture, deliver end-to-end features, design reusable UI components, and collaborate across teams — with a strong background in performance, accessibility, REST APIs, scalable application design, CI/CD, and modern AI-assisted development including Spec-Driven Development and agentic workflows. This site is my public engineering home for architecture thinking, technical experiments, and the journey toward Staff Engineer and architectural leadership.
Experience
Where I have worked
A selection of roles across product engineering, from UI development to senior full-stack delivery.
- Contributing to a next-generation email security platform spanning multiple products, built with Angular micro frontends in an Nx monorepo.
- Adopted Spec-Driven Development and agentic coding workflows to turn requirements into structured specifications, implementation plans, and production-ready code.
- Owned features from UI components and state management through API consumption, error handling, and contract alignment with backend teams.
- Delivered end-to-end features across frontend and backend, including user flows, forms, and data tables.
- Improved shared UI libraries and build tooling, contributing to platform quality, consistency, and cross-team delivery.
- Led the migration of existing enterprise applications to a new internal framework, ensuring a seamless transition, minimal disruption, and improved system performance.
- Integrated Changelog tracking with Kafka and Elasticsearch, enhancing client module functionality and enabling real-time data processing.
- Participated in architectural discussions and complexity analysis, contributing software design practices for scalable services.
- Designed and built a leave application suite using Angular, Node.js, Express.js, and MongoDB.
- Managed the end-to-end leave application cycle, from request submission and workflow tracking to final approval.
- Contributed to system design discussions that improved architecture, usability, security, and overall user experience.
- Developed frontend components and business logic using Angular, Node.js, Express.js, and MongoDB.
- Implemented Angular routing, client-side state management, and backend data flow.
- Conducted code reviews to maintain quality, maintainability, and engineering standards.
- Collaborated with senior developers to design, structure, and modify HTML, CSS, and JavaScript for web pages.
- Implemented interactive UI features with JavaScript, including client-side form validation and dynamic content.
Skills
What I work with
Skills drawn from day-to-day engineering work across frontend, backend, architecture, data, and delivery.
Frontend
- Angular
- TypeScript
- JavaScript
- HTML5
- CSS3
- SCSS
- Material UI
- Responsive Design
- Accessibility
- Performance
Backend
- Node.js
- Express.js
- Python
- Web Services
Architecture
- Microservices
- Micro Frontend Architecture
- Distributed Systems
- Software Design
Data & Messaging
- MongoDB
- PostgreSQL
- Kafka
- Data Modeling
Cloud & DevOps
- Docker
- CI/CD
- Jenkins
- GitLab
- GCP
- Azure
- Cloud Security
- Linux
- Shell Scripting
Practices
- Test Driven Development
- Spec-Driven Development
- AI-Assisted Development
- Agentic Coding
- Root Cause Analysis
- Debugging
- Code Review
- UI Engineering Best Practices
Engineering notes
How I think
I write about frontend architecture, Angular, Nx, and the practices that keep production systems understandable as they grow.
Frontend Architecture for a Personal Platform
How this Angular platform stays thin: app boundaries, a Blog-local content contract, and Portfolio linking to Blog through public URLs only.
Read articleBuilding an Angular Monorepo
Why this site became an Nx workspace when Blog appeared — and how two Angular apps stay independently deployable under one domain.
Read article
Contact
Get in touch
If you want to talk about architecture, engineering, or a role that might be a fit, email is the most direct way.