I came from a small province, Iloilo, in the Philippines with very limited exposure to modern tech companies.
My first real exposure to that world was during my internship at Synacy as a Frontend Web Developer Intern. That experience introduced me to startups for the first time, not just as a concept, but as a real environment where people were building and shipping products quickly.
Through that internship, and conversations with friends already working in the industry, I became aware of how different the startup ecosystem was compared to traditional development paths. Fast-paced, iterative, and deeply collaborative.
That was the moment I decided to intentionally focus on startups.
I believed I would grow faster in environments where I could work closely with engineers, product teams, and real users, where feedback loops are short and learning happens quickly through shipping.
After graduating, transitioning into that world was not straightforward.
Coming from a provincial background, opportunities in modern tech companies in the Philippines were limited, and competition was often shaped by factors beyond just skill. There were moments where it felt difficult to break into the kinds of companies I wanted to work in, especially without coming from more established universities in Metro Manila.
Still, I kept building, applying, and improving.
Eventually, I was fortunate enough to join Quipper at the right time, an opportunity that became my entry point into real production-scale systems and professional software engineering.
Looking back, it wasn’t a straight path. But it was a sequence of small opportunities, timing, persistence, and learning how to adapt quickly once I got in.
Foundation (2012-2016)
Philippines 🇵🇭
📍 West Visayas State University, Iloilo City
Built the base- Software development fundamentals
- First exposure to structured problem solving
- Learned discipline through engineering coursework
In hindsight, formal instruction played a limited role in shaping my direction, with the notable exception of one course in DBMS that stood out for its practical depth.
Most of my real growth during this period came from independent learning rather than structured teaching. I gradually realized that in fast-moving fields like software engineering, relying solely on being “taught” is not enough. You need to actively seek what to learn next.
At the same time, I also learned an important balance: independence does not mean isolation. Without exposure to real industry practices, it is difficult to even know what to learn or which direction to take. Early guidance, even small signals from mentors, peers, or occasional industry exposure, can significantly shape that trajectory.
With limited access to the tech industry at the time, I relied on small exposures and curiosity to gradually guide myself toward areas I found meaningful. Over time, this helped me develop a habit of self-direction: learning proactively, validating through practice, and adjusting based on feedback from real-world work.
Later in my career, this perspective evolved further. I came to appreciate how important early exposure is for students who are in the same position I once was.
Because of that, I reached out to my college dean and several professors to help organize online talks with alumni and industry professionals, aiming to give students earlier exposure to real-world software engineering and career paths, something I personally lacked during my studies.
First Job (2017-2021)
Philippines 🇵🇭
📍 Quipper, Makati City
My first real step into production systems.What I worked on:
- Migrated legacy systems (Backbone.js → React + TypeScript)
- Built reusable frontend architecture used across teams
- Delivered features for teachers and students (Quipper Create, Chat systems)
- Introduced observability with Datadog + scaling improvements
- Helped onboard and mentor new engineers
What changed here:
- I learned how real users break things
- I learned scale is not theoretical
- I learned that frontend architecture is also system design
Growth & Ownership (2021-present)
Singapore 🇸🇬
📍 eyos → StashAway → Glints, Singapore
This is where I shifted from “building features” to owning systems.🧾 eyos
- Built SmartShopper (mobile-first web app)
- Led frontend architecture decisions
- Built scalable admin systems
💰 StashAway
- Shipped MVP (Reserve) in a regulated fintech environment
- Worked with React Native + Node.js + event-driven systems
- Learned speed under constraint
👥 Glints
This is where I operated on systems-level ownership.
Built and scaled:
- Multi-tenant Employer of Record (EOR) platform from scratch
- Backend services in Rust (APIs, workers, cron systems)
- Event-driven integrations (HRIS, CRM, ERP like HubSpot & NetSuite)
- Internal operational platforms used by HR, Finance, Ops, Sales
- Design system (`glints-aries`) used across multiple products
Impact:
- Reduced manual onboarding workflows significantly
- Improved cross-team operational efficiency
- Enabled expansion into new markets
- Improved system reliability via observability (Grafana, Datadog)
Next Phase: System Ownership at Scale
🌍
Open to opportunities around EU
Looking for environments where I can take end-to-end ownership of systems that directly impact how people and teams operate.
Interested in roles that are:
- Autonomous and outcome-driven (not feature factories)
- Product and technically ambiguous
- Focused on real-world workflows, not just surface-level features
- Closely tied to business and operational impact
I’m open to relocation and opportunities in EU where I can continue building systems that meaningfully improve people’s lives, while growing through complex, real-world challenges.
If you’re building something where engineering directly shapes real-world outcomes, I’d be happy to connect.
🧠 What I’ve Learned Along the Way#
- Growth in engineering comes less from being taught everything, and more from learning how to actively find what to learn next
- Independent learning is essential, but early guidance and exposure are just as important in shaping direction
- Without context of real industry practices, it is difficult to even know what “good” looks like. Small signals and mentorship can change that trajectory significantly
- Systems matter more than isolated features. Long-term impact comes from how parts connect, not just what is built
- Real-world engineering is rarely about clear requirements. Interpretation, clarification, and alignment are part of the job
- Good engineering is often invisible (automation, observability, workflows, internal tooling that reduces friction)
- Cross-functional alignment is where most meaningful product impact happens, especially in operational-heavy systems
- Speed and correctness are not opposites. With the right architecture and discipline, they reinforce each other
🌱 How I Work Now#
I do my best work in environments that are:
- Autonomous where engineers are trusted to take ownership end-to-end
- Product and technically ambiguous where problems are defined through exploration rather than fixed specs
- Focused on outcomes rather than output not feature factories, but systems that meaningfully improve how people work or live
- Close to the business where engineering decisions directly influence operational efficiency, user experience, or revenue impact
- System-oriented where ownership spans frontend, backend, and infrastructure rather than isolated layers
I prefer building and owning entire problem spaces, from understanding the problem, to designing the system, to delivering and iterating based on real usage.
I use modern tools, including AI, as leverage to accelerate understanding and delivery, not as shortcuts, but as part of a thoughtful engineering workflow.
🚀 Closing Thought#
From Iloilo to Singapore, the direction has always been the same:
To use modern technology and continuous learning to create meaningful impact in people’s lives