[Hiring] Chromium Android Engineer @Semrush

Role Description

We're looking for a Chromium Android Engineer to join Datos, a Semrush Company - a global provider of anonymized, aggregated, fully compliant first-party clickstream data. You'll work on the technology behind our mobile data collection panel. You will own and support our mobile browser, which is our Android panel client: a maintained fork of Chromium (Chrome for Android, currently milestone 140), not a WebView wrapper.

• Develop and maintain Android Browser as a long-lived fork of Chromium for Android: features, bug fixes, and merges of upstream stability and security updates.
• Build product UI inside the Chromium Android shell (toolbar, new-tab page, settings, onboarding, dialogs), following existing chrome/android patterns rather than a standalone app architecture.
• Maintain the native content-filtering stack: C++ filter matching, the JNI bridge, cosmetic filtering via script injection into WebContents, and updates of filter lists (including server-delivered rules).
• Maintain compliance with Google Play policies and data privacy regulations (GDPR and similar).
• Own the Android release surface: GN/Ninja builds, app bundles, ProGuard/R8 rules, signing.
• Debug Java and native crashes (logcat, tombstones, Chromium logs) across browser, renderer, and other processes.
• Align with backend and data engineering on event schema, delivery, and pipeline changes.

Qualifications

• 4+ years of commercial experience on a Chromium-based Android browser (e.g. Chrome for Android, Opera, Yandex Browser, or an equivalent fork) or equivalent depth in Chromium's chrome/android and content layers.
• Strong Java skills in a large existing codebase.
• Solid JNI and practical C++: reading and changing browser-side native code, jni_zero bindings (JNINamespace, NativeMethods, CalledByNative), and debugging crashes that cross the Java/native boundary.
• Experience with Git on a large fork, including rebasing or merging a long patch series.
• Knowledge of Chromium on Android internals and process boundaries (browser vs. renderer, WebContents and navigation, UI-to-native calls), including how changes in the browser shell can affect another process.
• Understanding of how Chromium is built using GN, Ninja, and depot_tools, and how an Android App Bundle is built and shipped. Gradle-only Android application experience may not be enough for this role.
• Familiarity with Android platform requirements that commonly arise during Google Play review, including background execution limits, permissions, foreground service types, and ProGuard/R8 keep rules.
• English proficiency sufficient for technical documentation and cross-team communication (B1–B2+).

Benefits

• Unlimited PTO
• Hobby & team building budget allowance
• Employee Support Program
• Loss of family member financial aid
• Employee Resource Groups