Approach
How I engineer
Practical architecture, business-domain understanding, and ownership across the full product lifecycle.
- Principles
- 14
- Pipeline stages
- 13
- Release practices
- 11
- Testing disciplines
- 8
Software Engineer with 2+ years of professional experience as a Full Stack Developer, DevOps Engineer, and technical product builder from the Philippines. Focused on production-ready web applications, SaaS platforms, ERP and business systems, recruitment platforms, AI-powered products, APIs, and cloud infrastructure.
I work across the entire software development lifecycle—from understanding business requirements and designing system architecture, to building frontend applications, developing backend APIs, managing databases, integrating third-party services, establishing CI/CD pipelines, deploying systems, securing infrastructure, troubleshooting production issues, and continuously improving the product.
My strength is not being limited to one layer of the stack. I’m comfortable taking ownership of a complete system and making decisions across frontend architecture, backend architecture, databases, infrastructure, deployment, integrations, security, performance, user experience, analytics, and operational reliability.
I particularly enjoy solving problems where software engineering and business requirements intersect: taking a complex business workflow, turning it into a practical system architecture, and then actually building and operating that system in production.
I also have a strong interest in AI-assisted software development and agentic systems, particularly when AI can be integrated into real business workflows instead of being treated simply as a chatbot.
How I approach engineering
I’m not just interested in writing code. I enjoy understanding how the entire system works and why it needs to work that way.
I prefer solutions that are practical and maintainable over solutions that are unnecessarily complex—while remaining comfortable with justified complexity when business requirements demand it.
Choosing a framework, database, deployment strategy, architecture, or third-party service isn’t just a coding decision—it affects cost, performance, maintainability, reliability, developer productivity, security, and ultimately the business.
Principles
- 01Clean and maintainable code
- 02Practical architecture
- 03Strong API design
- 04Reliable infrastructure
- 05Good user experience
- 06Security
- 07Scalability
- 08Automation
- 09Observability and operational reliability
- 10Business-domain understanding
- 11Appropriate use of AI
- 12Cost awareness
- 13Developer experience
- 14Continuous improvement
Ownership pipeline
Best suited to environments where an engineer is expected to take broad ownership rather than work on an isolated technical layer.
Ownership pipeline
- 01Business Requirements
- 02Domain Modeling
- 03System Architecture
- 04Frontend Development
- 05Backend & API Development
- 06Database Engineering
- 07AI & Automation
- 08Third-Party Integrations
- 09Cloud Infrastructure
- 10Security & Compliance
- 11CI/CD & Deployment
- 12Monitoring & Production Operations
- 13Continuous Improvement
Go deeper
My goal is to build systems that are not only technically functional, but also reliable, secure, maintainable, scalable, cost-conscious, and genuinely useful to the business.