← All jobs

Browser and Kernel Engineer at SearchApi

Confirmed open

Modify Chromium and Firefox internals in C++ and maintain SearchApi’s browser automation infrastructure remotely from Vietnam.

SearchApi logoSearchApi
Location
Remote
Employment
FullTime
Work arrangement
remote
Technologies
Python, JavaScript, C++, Node.js, AWS

Create a free application profile — Keep your skills and projects in a reusable profile. Private by default; you choose when to share. Apply for this job directly with the employer.

Role overview

This role maintains SearchApi’s patched-browser cloud and modifies browser engines at source level. The work focuses on consistent browser behaviour, automation reliability and detection diagnostics rather than superficial page scripts. The source lists remote work from Vietnam.

Responsibilities

  • Maintain Chromium-based browser builds and carry patches forward as upstream releases change.
  • Modify engine behaviour involving navigator data, graphics, fonts and client hints.
  • Diagnose automation signals associated with Chrome DevTools Protocol while preserving browser control.
  • Keep geolocation, timezone and locale behaviour consistent across browser profiles.
  • Build test harnesses that reveal regressions and document engine-level fixes.

Qualifications

  • Strong C++ skills and experience reading, changing and building a large browser codebase.
  • A shipped browser-engine patch, fork or comparable tooling contribution.
  • Understanding of browser fingerprinting, CDP and headless or headful automation internals.
  • Persistent debugging, clear English writing and self-directed work.
  • Chromium or Firefox build infrastructure, HTTP or TLS fingerprinting and browsers at scale are additional strengths.

Technology in this role

  • Python: Python JavaScript C++ Node.js .
  • JavaScript: Python JavaScript C++ Node.js .
  • C++: Python JavaScript C++ Node.js .
  • Node.js: Python JavaScript C++ Node.js .
  • AWS: Python JavaScript C++ Node.js .
  • C: Python JavaScript C++ Node.js .
  • Go: We are searching for grinders who take ownership and go .
  • Ruby: • Ruby, Node.js, or Python for tooling, plus .
  • CI/CD: We ship multiple times a day with .
  • Playwright: Which file did you touch, why there instead of in JavaScript, and how did you verify it worked? We want the source-level story, not "I configured .
  • CAN: If you can't evaluate what it produces, you're not ready for this .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Browser / Kernel Engineer position at SearchApi is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “This role maintains SearchApi’s patched-browser cloud and modifies browser engines at source level. The work focuses on consistent browser behaviour, automation reliability and detection diagnostics rather than…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the technical area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Maintain Chromium-based browser builds and carry patches forward as upstream releases change.”; “Modify engine behaviour involving navigator data, graphics, fonts and client hints.”; “Diagnose automation signals associated with Chrome DevTools Protocol while preserving browser control.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Strong C++ skills and experience reading, changing and building a large browser codebase.”; “A shipped browser-engine patch, fork or comparable tooling contribution.”; “Understanding of browser fingerprinting, CDP and headless or headful automation internals.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are Python, JavaScript, C++, Node.js, AWS. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with and how.

Benefits

  • The employer lists fully remote work, equity, profit sharing, learning across a growing SaaS product and periodic team retreats.

About SearchApi

SearchApi provides an API for structured, real-time data from web search, shopping, video and other search sources. Its posting describes a small, remote-first engineering team building a Ruby on Rails product.

Employer website

How to apply

Review the original posting and apply through the employer’s careers page.

View source and applyApply directly

Source checked: 2026-10-09

Browse job categories

Related jobs