Mobile-First Product Engineer

Overview

Mobile-first product engineers design for the reality of most of the world's internet users: a sub-$200 Android device, an intermittent 3G connection, a 4 GB data cap, and a 5-inch screen in bright sunlight. The role is distinct from the standard Mobile Engineer track because the constraints come first and dictate the architecture — offline-first sync, sub-200KB JavaScript bundles, progressive enhancement, lightweight web stacks, and accessibility patterns that work on a screen the size of a deck of cards. The cluster is large and growing in South Asia, Southeast Asia, and Africa, where mobile is not a channel — it is the entire product surface. SFIA 9 maps this cluster across PROG (programming) and USEX (user experience analysis), with a strong USRS (user research) overlap.

“You start by reviewing yesterday's RUM data from your largest market — INP regressed on the sub-$200 Android segment after the latest deploy, so you bisect and roll back a third-party script. Mid-morning, you redesign a sign-up flow to work over flaky 2G: every step persists to IndexedDB, the form submits in the background, and the user sees something useful even before the network responds. After lunch, you pair with a designer on a one-handed-reach pattern for a rural-language interface, then write a service-worker upgrade strategy that won't strand users on old shells when they're offline for days.”