How I lead - A framework for engineering excellence
Every great engineering outcome starts with a clear framework. Mine has three pillars: People, Product, and Process.
People
The best products are built by people who feel safe, valued, and challenged. Before strategy, before roadmaps, I focus on the humans on the team.
This means regular 1-on-1s, individual growth plans, and creating an environment where engineers can bring their whole selves to work. I foster psychological safety so that disagreement is healthy and learning from failure is expected.
I also care deeply about work-life balance. Sustainable pace isn't just a nice-to-have. It's how you retain great people and build long-term team health.
What this looks like
- Regular 1-on-1s
- Individual growth plans
- Psychological safety
- Mentorship culture
- Healthy work-life balance
- Recognition & feedback
Product
Engineering exists to serve the product and the user. I work closely with product managers and designers to ensure engineering decisions align with business goals.
I push for high code quality and technical excellence, not as an end in itself, but because quality products come from quality engineering practices. Regular code reviews, clear standards, and staying current with the technology landscape are non-negotiable.
At the same time, I know when to ship. Perfectionism is the enemy of progress. I help teams find the right balance between velocity and quality.
What this looks like
- Code reviews & standards
- Technical roadmapping
- Cross-functional alignment
- Quality without perfectionism
- Continuous improvement
- Shared engineering goals
Process
Good process is invisible. It reduces cognitive load, keeps teams aligned, and creates predictability without bureaucracy.
I build lightweight rituals and systems that scale, from squad planning and async communication to cross-functional coordination across Product, DevOps, and Marketing.
The goal of process is always to free up engineers to focus on what matters most: solving real problems for real users.
What this looks like
- Planning & rituals. Sprint planning, retrospectives, and async check-ins that keep the team aligned without eating up their calendar.
- Cross-functional coordination. Working bridges between engineering, product, design, DevOps, and marketing to remove blockers before they happen.
- Technical alignment. Ensuring engineering initiatives are tied to business objectives and communicated clearly up and down the org.
My values - Principles I lead by
These aren't just words. They're the lens through which I make decisions every day.
- Empathetic. Understanding the human behind every interaction, whether it's a team member, a stakeholder, or a user, drives better decisions.
- Decisive. Good leadership requires making clear calls with incomplete information. I own my decisions and course-correct quickly when needed.
- Transparent. I share context freely, communicate setbacks early, and trust teams to handle the truth. No surprises, no spin.
- Growth-oriented. I'm constantly learning, and I expect the same from myself as from my team. Growth is a habit, not an event.
- Accountable. I take responsibility for outcomes, celebrate team wins publicly, and handle setbacks privately and constructively.
- Collaborative. The best solutions come from diverse perspectives working together. I actively seek out disagreement and create space for every voice.
Want to connect or collaborate?
Based in
Indonesia · open to remote collaboration worldwide.