Senior HarmonyOS Engineer

What you will own

• Ship features end to end — from an API contract and a design spec to a signed AppGallery release.
• Own the architecture — MVVM on ArkUI state management V2, a layered network stack, centralised routing. Early enough that these are still yours to set.
• Build for the live classroom — our virtual-classroom SDK is what a lesson actually runs on. You would carry its HarmonyOS side forward and keep it behaving like the iOS and Android versions of the same product.
• Run the hybrid seam — the native ↔ web bridge, auth handoff, deep links and session expiry: the part most likely to break in odd ways.
• Set the quality bar — unit tests, review standards, CI that blocks bad builds, and a defence of cold start, scrolling and memory.
• Align and mentor — keep product logic, API contracts and design tokens in step with iOS and Android; bring engineers new to ArkTS up to speed.

What we are looking for

• ArkTS and ArkUI on an app you shipped. Declarative ArkUI, state management, the Ability lifecycle, DevEco Studio, hvigor and ohpm — used in production, not in a tutorial. This is the requirement we do not bend on.
• 5+ years of professional mobile or client engineering. The years are mobile overall — we do not expect five of them on HarmonyOS, and we will look seriously at 3+ when the ownership is clearly senior.
• Strong TypeScript fundamentals — typed models, async flows, an eye for where ArkTS is stricter than the TypeScript you know.
• Networking done properly — REST clients, interceptors, token refresh under concurrent requests, sane error and offline behaviour.
• A working grasp of real-time media and WebSockets — audio and video delivery, and long-lived socket connections: latency, reconnection, and state that arrives late or out of order.
• Architecture and testing judgement — logic out of views, tests where they earn their place, CI you trust.
• Product sense and clear communication — you push back when a spec is wrong, and work comfortably in English across markets.

Nice to have

• Production iOS or Android experience — Swift / SwiftUI or Kotlin / Jetpack Compose. The strongest plus here: our HarmonyOS app is a sibling of two existing apps, and engineers from those platforms pick up ArkTS quickly.
• Live classroom or real-time media products — we build and maintain our own virtual-classroom SDK, where a lesson has to hold up on a real network with a teacher and a room full of learners. Experience delivering live audio and video, or integrating a third-party real-time provider, counts for a lot here.
• SDK and library engineering — building something other teams depend on rather than an app screen: a stable public interface, versioning, and keeping one product behaving the same way across HarmonyOS, iOS and Android.
• Hybrid web and JS bridge work — WebView-heavy apps, single sign-on across native and web, server-driven UI and localisation across markets.
• Native or release depth — C/C++ through NAPI, performance profiling, multi-device form factors, AppGallery release engineering, or HarmonyOS community contributions.