Sari Wijaya

Sari Wijaya is the Senior Frontend Engineer at HKQS Games and the technical lead behind the platform's instant-play promise. Every game on the catalog loads in a browser tab and is playable within seconds — no app store, no installer, no friction — because of the engineering discipline she has built into the platform's web architecture. She owns the frontend performance budget, the rendering pipeline, and the build tooling that keeps every game loading fast on a phone browser.

Her north star metric is brutally simple: time-to-play. Not time-to-first-paint, not time-to-interactive, but the moment a player can actually make their first move in a game. That single focus reframes every architectural decision — from how assets are bundled to how the game loop is bootstrapped — around the only thing that matters to a casual player waiting on a link to open.

Engineering for the Slowest Device

Sari learned to build for the web the hard way. Early in her career she shipped a feature that ran beautifully on her development laptop and failed catastrophically on a mid-range Android phone over a flaky 3G connection. That experience became a permanent lesson: she now benchmarks every change against the slowest devices in the team's device lab and treats a regression on low-end hardware as a release blocker. Performance, in her view, is an accessibility concern — a page that only loads fast on flagship phones is not actually fast.

Before joining HKQS Games, Sari worked on high-traffic consumer web products where she specialized in the unglamorous work that makes products feel magical: route-level code splitting, image pipeline optimization, service-worker caching strategies, and the patient elimination of layout thrash. She has migrated legacy codebases to modern build tooling, introduced performance budgets enforced in CI, and built internal dashboards that surface real-user metrics so the whole team can feel the impact of their work in production.

The Instant-Play Architecture

At HKQS Games, Sari designed and implemented the instant-play architecture that powers the entire game catalog. Games are loaded as lazily-fetched modules, with critical gameplay code prioritized over decorative assets. She built a progressive boot sequence that renders an interactive placeholder within milliseconds, then streams in the full game engine as bandwidth allows — so even on a poor connection, a player sees something responsive immediately rather than staring at a blank screen.

She is a firm believer in the PWA toolkit and has made the HKQS Games platform installable, offline-capable for returning players, and resilient to network drops mid-session. Her caching strategy distinguishes between immutable game assets (cached aggressively, versioned by content hash), frequently-updated content (stale-while-revalidate), and player state (synced carefully to avoid data loss). The result is an experience that feels native — fast, reliable, and respectful of device resources — while remaining a pure web product.

React, TypeScript, and the Long Game

Sari's stack is built on React and TypeScript, chosen not for fashion but for the long-term maintainability of a platform that ships new games every week. She has established a strict type system, a component library that enforces accessibility and performance standards by default, and a testing strategy that catches regressions before they reach players. She is pragmatic about abstractions: she resists premature generalization, prefers composition over inheritance, and is willing to delete a clever abstraction the moment it stops earning its complexity.

On the rendering side, Sari has pushed the team's use of WebGL for game visuals that would be impossible with the DOM alone — particle systems, shader-based effects, and performant 2D scenes that stay smooth at 60 frames per second even on modest hardware. She treats the boundary between the React UI layer and the WebGL game layer as a first-class architectural concern, with clean interfaces that keep the two from leaking into each other.

Mentorship & Open Source

Sari is a quiet but consistent mentor. She runs the frontend engineering practice at HKQS Games with a focus on code review as a teaching tool — her reviews are known for being thorough, kind, and genuinely educational. She has helped designers transition into frontend roles, paired junior engineers through their first production deploys, and built internal documentation that lowers the onboarding ramp for new hires. She believes the best engineering cultures are the ones where asking a question is always cheaper than shipping a bug.

She contributes to open-source web performance tooling and writes publicly about the techniques she uses at HKQS Games. Her writing is deliberately practical: she publishes the exact budgets, the exact Lighthouse configurations, and the exact trade-offs that go into each decision, because she remembers how hard it was to find that level of specificity when she was learning. You can read her most recent deep-dive — on hitting sub-three-second load times for browser games — in the article below.

What She's Building Next

Currently, Sari is leading an effort to bring the HKQS Games platform to a sub-two-second time-to-play on mid-range Android devices, experimenting with streaming WebAssembly compilation, adaptive asset quality based on device capability, and a shared runtime that lets players jump between games without re-downloading common dependencies. She is also piloting a real-user-monitoring pipeline that will give the team granular visibility into performance across the long tail of devices and networks their players actually use.

Off the clock, Sari is an enthusiastic (if occasionally frustrated) home cook, a long-distance runner who treats her morning route as a debugging session, and the owner of a growing collection of mechanical keyboards she swears she does not need. Find her engineering notes in the article below, or follow her on GitHub for the code behind the metrics.