Chromium/Blink C++ Engineer - Android Fingerprinting

We develop Device Changer (https://deviceschanger.org), an Android device-testing platform with our own Chromium-based browser. We have an internal development team and need an independent engineer to diagnose and fix browser fingerprinting inconsistencies at Chromium source-code level.

THE PROBLEM

In our Android build, diagnostic tests flag Canvas and AudioContext output as "Spoofed" and detect fingerprinting resistance, even though fingerprint controls are configurable. We need to identify whether these results reflect intended privacy behavior, inconsistent API output, or implementation defects. The aim is reproducible, technically correct browser behavior—not promises of undetectability.

REQUIRED EXPERIENCE

Hands-on C++ development in Chromium/Blink source (not just Chromium usage).

Canvas 2D, Skia, Web Audio/AudioContext; WebGL/GPU experience is a plus.

Understanding of Blink/V8 bindings, renderer processes, JS-exposed APIs and fingerprint consistency.

Building and debugging Chromium for Android ARM64 (GN/Ninja, ADB, native debugging).

Ability to make maintainable patches, add regression tests and explain root causes.

INITIAL FIXED-PRICE MILESTONE

We propose a focused $500 diagnostic milestone, with exact scope and acceptance criteria agreed before work begins:

Reproduce the Canvas/AudioContext findings on our build and a baseline Chromium build.

Identify affected source files/functions and determine the root cause using logs, traces and test cases.

Deliver a concise technical report, reproducible evidence and an actionable fix plan.

If agreed and feasible within scope, provide a small patch/diff and validation results.

Broader implementation or additional fixes will be priced as separate fixed-price milestones through LaborX escrow. No hourly or full-time role is offered. We will only provide authorized test builds and project access after agreeing on scope.

TO APPLY, ANSWER:

What Chromium/Blink C++ changes have you personally implemented? Link an existing Gerrit/GitHub diff or sanitized code example.

Have you debugged Canvas, Skia, Web Audio or WebGL fingerprinting behavior? Describe one specific issue and your evidence.

Have you built Chromium for Android ARM64? Which build/debug tools did you use?

Are you comfortable with fixed-price research and reproducible deliverables?

Please do not apply if your experience is limited to Selenium/Puppeteer, generic Android development, anti-detect browser configuration or JavaScript-only hooks. We value proof of source-level Chromium engineering over a long list of tools.