open · apply any time
§ careers · engineering
Chrome Extension Engineer
Own the extension — passive observation, ban-avoidance heuristics, and the user-is-principal boundary. Obsessive about reliability.
- team
- engineering
- location
- Remote · EU ±3h
- compensation
- €130–160k + 0.3–0.8% equity
- stack
- TypeScript · MV3 · Playwright
§ 02 · about the role
What you'll own.
The extension is the trust boundary of LinkFetch — it's how we guarantee 'user is principal.' You'll own its architecture end-to-end: Manifest V3, content scripts, background service worker, and the observation/ingest pipeline.
§ 03 · responsibilities
The work, itemised.
- 01Own the MV3 extension: architecture, tests, Chrome Web Store releases
- 02Maintain passive observation heuristics (five ban-avoidance guardrails)
- 03Design the ingestion protocol between extension and API
- 04Write Playwright integration tests; keep the extension boring
- 05Partner with backend on voyager normalisation
§ 04 · who we're looking for
The profile.
- ▸You've shipped a Chrome extension to the Web Store
- ▸Deep familiarity with Manifest V3, content-script boundaries, CSP
- ▸You think in terms of reliability, not features
- ▸You've reverse-engineered a structured API or scraped a complex site
§ 05 · process
How hiring works.
Three rounds. Intro → paired debug session on a real extension bug → team meetings → written offer.
ready?
Apply in one email. No form.
Send a link to your best work (GitHub, portfolio, a post you wrote). Skip the cover letter. Skip the CV format. We read every email and reply within 3 business days.
apply · info@linkfetch.io ↗subject pre-filled
§ 07 · other rooms