Eleven years in production software with a frontend focus. I have led teams, shaped component architectures, resolved performance issues in enterprise-scale apps, and worked across product, design, and engineering to deliver systems that still hold up after launch.
I define component boundaries, module structure, and patterns that hold up as teams and features grow. The goal is systems that stay understandable at scale.
Complex UIs, regulated workflows, long-lived codebases. I have spent years in the kind of work where design decisions from two years ago still matter today.
Heavy tables, unnecessary re-renders, tangled component trees. I focus on real bottlenecks, not abstract performance theory.
I have owned frontend direction for teams, not just written code in them. That means setting standards, reviewing work, mentoring, and aligning with product and engineering leadership.
Senior-level frontend engineer based in Kidapawan City, North Cotabato, Philippines.
I have been building software for eleven years, mostly on the frontend. Most recently as a senior engineer, and before that as a frontend lead responsible for delivery quality and team direction.
My focus is scalable component architecture, improving code quality, and reducing technical debt without blocking the roadmap. I care about performance, stability, and UIs that actually work under real enterprise conditions, not just in staging.
I work closely with product, design, backend, and QA. I mentor developers, review code, and take ownership from design feasibility through production support. I have done this across multiple companies and team sizes.
I have seen what happens when frontend systems scale without clear structure. Components become unmanageable, teams slow down, and technical debt compounds faster than anyone expects. That experience drives how I design and build today.
Roles where I owned frontend direction, improved system structure, and delivered in complex environments.
Senior Frontend Developer
Lead Frontend Developer
Senior Angular Developer
Senior Angular Developer
Frontend Developer
Frontend Developer
Application Developer
System-level problems I solve repeatedly across enterprise teams and codebases.
Shared modules, consistent patterns, and clear boundaries. When the system is structured well, teams spend less time re-solving problems they have already solved.
ArcGIS-driven interfaces alongside dense enterprise screens. The real problem is keeping complex views performant and usable as data and interactions grow.
Enterprise grids get slow fast. I tune AG Grid for real-world row counts, simplify configuration, and make grid setups reusable across features.
Shipping on time is expected. The real test is whether the team can still move fast six months later. I structure code so post-launch velocity does not collapse.
Technical debt slows teams more than missing features do. I identify the debt that actually blocks velocity, prioritize it, and tie the work to outcomes the org cares about.
Leadership that shows up in daily work: setting standards, unblocking developers, aligning with product and engineering, and making sure the team delivers consistently.
The stack I build with. Angular and TypeScript are the core, supported by backend and tooling experience.
Beliefs I have formed from years of building, debugging, and shipping with real teams.
I do not write code until the problem is clear. Most wasted engineering effort traces back to unclear requirements, not bad implementations.
Clean code is not enough. Structure is what keeps systems from collapsing over time. I design with explicit boundaries and patterns that survive team turnover and scope growth.
Performance problems in grids, maps, and data-heavy views need to be caught during development, not reported by users. I treat performance in complex UI surfaces as a design constraint, not a late optimization task.
Consistent code reviews, honest feedback, and regular check-ins with QA, backend, and stakeholders. That is what makes delivery predictable, not individual heroics.
I am open to senior, lead, and architect-track conversations. If your team needs someone who can own frontend direction, make architecture decisions that hold up, and deliver reliably in complex environments, let's talk.
Kidapawan City, North Cotabato, Philippines · romnick.rojas75@gmail.com