Browser / Kernel Engineer

Responsibilities

• Own the browser stack.
• Maintain and evolve our in-house patched-browser cloud and its per-OS fingerprint profiles, kept continuously rebased onto new stable Chromium without regressing the evasions.
• Patch the engine. Fix navigator, WebGL, canvas, fonts, and Client Hints at the implementation level so spoofed values look native, not bolted on.
• Kill CDP leaks. Find and eliminate the signals that give automation away, without breaking normal control.
• Get the details right. Align geolocation, timezone, and locale so the whole picture is consistent.
• Chase detection. When something starts getting flagged, figure out why at the source and fix it.
• Build the tooling. Write the harnesses that test and validate evasions so regressions get caught before customers do.
• You define the work. We don't hand you a ticket queue. You tell us what's getting detected, what's brittle, and what to fix next.
• 🔥 The Hard Parts
• This role is not for everyone. Here's what makes it hard

Languages