How to hire a Chrome extension developer

To hire a Chrome extension developer in 2026, screen for shipped Web Store extensions on Manifest V3 (not just any frontend dev who claims the skill), expect $85 to $160 per hour for senior US contractors, and budget 1 to 3 business days for Google's Web Store review on top of build time. Most JavaScript developers can write a "hello world" content script. Few have actually pushed an extension through Google's review queue and survived an MV3 migration.

This guide is the honest playbook: what the role actually requires now, where to find people who can do it, the five interview questions that separate shippers from claimers, and when to skip the hiring loop entirely and book by the week.

The 2026 reality: Chrome extensions are a niche specialty

Three years ago, "Chrome extension developer" mostly meant "JavaScript developer who read the docs once." That bar moved.

Manifest V3 is mandatory for new submissions and Google fully deprecated V2 across 2024 and 2025. Background pages no longer exist; the runtime is a service worker that wakes on events and dies on idle. The blocking webRequest API that powered most ad blockers and request-modifying extensions is gone, replaced by declarativeNetRequest with a static rules format. Remote code execution is banned by policy: every line of JavaScript must be packaged in the bundle Google reviews.

Then there are the things only specialists know to mention. The side panel API replaced the older popup-only UI as the default for persistent extension surfaces (Chrome 114 and later). host_permissions now triggers user-visible install warnings that tank conversion if you ask for <all_urls> when you only need one domain. chrome.storage.sync has a 100 KB quota; chrome.storage.local has 10 MB; pick wrong and your extension breaks for power users at week two. OAuth via chrome.identity.launchWebAuthFlow has its own redirect URL format that does not match anything else in your stack.

The Chrome Web Store has roughly 200,000 published extensions. The pool of developers who have shipped to it and lived through MV3 is far smaller than the pool who claim "Chrome extension" on their resume. Hiring well in 2026 means screening for the second group, not the first.

What to look for in a Chrome extension developer

Three buckets: hard skills, AI-native baseline, soft signals.

Hard technical skills

Manifest V3 fluency. Knows the service worker lifecycle, why the worker dies after roughly 30 seconds of idle, how to keep state in chrome.storage instead of memory, and when to use alarms instead of setTimeout.
Content scripts and isolated worlds. Can explain why a content script cannot read the page's window object directly and how chrome.scripting.executeScript with world: "MAIN" changes the rules.
declarativeNetRequest rules. Has written static rule files, not just Stack Overflow copy-pastes of the deprecated webRequest blocking pattern.
Storage strategy. Knows when to reach for storage.local (10 MB, fast) vs storage.sync (100 KB, syncs across devices) vs IndexedDB inside an offscreen document.
Permissions hygiene. Defaults to activeTab over host_permissions: ["<all_urls>"]. Understands that broad permissions trigger Web Store review escalation and lower install conversion.
OAuth via chrome.identity. Has shipped a Google OAuth flow without a backend, or knows why launchWebAuthFlow is required for non-Google providers.
Build tooling. Plasmo or CRXJS familiarity is a strong positive signal in 2026; raw webpack with the manifest copied by hand still works but indicates someone who started before the modern ecosystem.

AI-native baseline

Every engineer on Cadence is AI-native by default: Cursor, Claude Code, and Copilot fluency are vetted in a voice interview before they unlock the platform. There is no "non-AI-native" option. For extension work specifically, that baseline matters because the MV3 migration broke nearly every blog post and Stack Overflow answer written before 2024. A developer who can prompt Claude with the current chrome.* API surface and verify the answer against developer.chrome.com ships in days. A developer copy-pasting from 2021 tutorials ships a service worker that quietly crashes in production.

For the same reason we recommend in our guide on how to vet a software developer before hiring, have the candidate live-code one feature in their actual editor with their actual AI setup. You learn more in fifteen minutes than from a take-home.

Soft signals that matter

They can show you a published Web Store listing under their name or their employer's. "Private corporate extensions" count if they can describe the manifest from memory.
They mention review rejections they have lived through. "We got bounced for a vague description on attempt one" is a green flag, not a red one.
They have an opinion on Plasmo vs CRXJS vs vanilla. No opinion means no shipped projects.

Where to find Chrome extension developers

In rough order of signal-to-noise for a 2-to-12 week scope.

1. The Chrome Web Store itself

Open the Web Store, filter to your category, sort by rating, and email the developers of the top 20 extensions in your space. Most include contact in the listing or a linked website. This is the highest-quality channel by a wide margin because every person you contact has, by definition, shipped. Hit rate is 5 to 15 percent for paid pilots; budget two weeks for replies.

2. Plasmo and CRXJS communities

The Plasmo Discord and the CRXJS GitHub discussions are where modern extension developers live. Drop a "looking to hire for a 2-week scope" post with a clear spec and you will get 3 to 8 qualified replies inside 48 hours. The bar is high; the rates run $80 to $150 per hour for US-equivalent contractors.

3. /r/chrome_extensions and Indie Hackers

Smaller and noisier, but real builders post here. Useful for finding indie devs who shipped one popular extension and are open to contract work between projects. Mixed quality; expect to filter.

4. GitHub search

Search GitHub for filename:manifest.json "manifest_version": 3 and sort by recently updated. The contributor graph of any active MV3 repository is a list of warm leads. Cold-email rate is lower (around 3 to 5 percent), but the quality is high.

5. Toptal, Arc, Upwork, Fiverr

Toptal and Arc both list "Chrome extension" as a vetted skill and promise a shortlist in 48 to 72 hours. Rates run $80 to $200 per hour through Toptal, $60 to $120 through Arc. Upwork and Fiverr will return 200 candidates inside an hour, but you do the vetting yourself. Useful when you have time to interview, less useful when the scope is two weeks of senior work and you needed to start yesterday.

6. Cadence

Cadence treats engineering as a booking, not a hiring loop. You write a short scope, the platform auto-matches you against the 12,800-engineer pool, and you have a shortlist in 2 minutes. Median time to first commit across the platform is 27 hours. Every engineer is AI-native by baseline. Weekly billing, 48-hour free trial, replace any week. The trade-off: Cadence is built for 1 to 12 week scopes; if you are committing to a 6-month full-time hire, a traditional recruiter network gives you better culture-fit signal.

How to evaluate a Chrome extension developer

Skip the whiteboard. Use these five questions, in this order. The first three are the gate; the last two are tiebreakers.

The 5 MV3-era interview questions

"Walk me through the service worker lifecycle. Why does my worker keep dying mid-request?" Strong answer mentions the 30-second idle timer, the lack of persistent global state, and using chrome.alarms plus chrome.storage to survive restarts. Weak answer talks about background pages.
"When would you use host_permissions: ['<all_urls>'] vs activeTab?" Strong answer says "almost never <all_urls>; it doubles install drop-off and triggers Web Store review escalation." Weak answer says they are equivalent.
"Why does declarativeNetRequest exist instead of webRequest?" Strong answer mentions privacy (Chrome no longer ships request bodies to extensions), performance, and the move away from blocking JavaScript callbacks on every network request. Weak answer says "it is the new way."
"How do you handle Google OAuth from inside an extension without a backend?" Strong answer reaches for chrome.identity.getAuthToken for Google itself or launchWebAuthFlow for other providers, and names the redirect URL format https://<extension-id>.chromiumapp.org/. Weak answer suggests a popup window with window.open.
"What got your last extension rejected from the Web Store, and how did you fix it?" Any answer with a specific story is green. "I have never been rejected" usually means they have never submitted.

The take-home alternative

If you cannot do a live interview, scope a one-day paid task: "Build a content script that injects a button into LinkedIn profiles, opens a side panel when clicked, and remembers which profiles the user has marked, using chrome.storage.local." Pay $200 to $400 for the day. You will learn more from the code review than from any take-home that uses fake requirements.

Red flags

Cannot name a single extension they have shipped to the Web Store.
Pitches Manifest V2 patterns ("just put it in the background page").
Asks "what's the deadline" before "what's the spec."
Quotes a flat $500 fixed-price for "any Chrome extension." This is the marker of an offshore reseller, not a developer.

What to expect to pay in 2026

Approach	Typical rate	Timeline	Best for
US senior contractor	$85 to $160 per hour	1 to 2 weeks to start	Production extension, MV3 migration
EU senior contractor	70 to 130 EUR per hour	1 to 2 weeks	Same as above, EU timezones
Eastern Europe / LATAM mid	$40 to $80 per hour	2 to 4 weeks	Mid-complexity build, comfortable with timezone gap
Toptal / Arc vetted	$80 to $200 per hour	48 to 72 hours	Faster start, premium rate
Upwork / Fiverr open	$20 to $80 per hour	Same day	Prototype, throwaway, you do the vetting
Agency / consultancy	$150 to $300 per hour	2 to 6 weeks	Compliance-heavy, multi-browser, polished UI
Cadence (booking)	$500 to $2,000 per week	2 minutes to shortlist	1 to 12 week scopes, weekly billing, no recruiter loop

Cadence's published tiers are the simplest market anchor for thinking about a weekly engagement:

Junior, $500 per week. Dependency hygiene, doc-writing, manifest cleanup, integrating an extension with a well-documented backend.
Mid, $1,000 per week. End-to-end small extension shipped to the Web Store, MV3 migration of a small V2 extension.
Senior, $1,500 per week. Owns scope. Side panel architecture, OAuth flow, performance tuning of a service worker, complex content scripts across multiple sites.
Lead, $2,000 per week. Architectural decisions on a multi-extension product, fractional CTO oversight, scale (millions of installs), Enterprise policy management.

For most founder-built extensions (analytics widgets, scraping tools, productivity helpers), a Mid or Senior at $1,000 to $1,500 per week for two to four weeks lands the first shipped version with margin to spare. The same scope at a vetted-network $120 per hour is $9,600 to $19,200; the math favors weekly billing as soon as the scope is more than four days.

A useful comparison frame: this same delta shows up for adjacent niche-skill roles like in our breakdown of how to hire a Solidity developer or hire a Swift iOS developer.

The alternative: book by the week instead of hire

Most Chrome extension scopes are not full-time hires. They are 1 to 4 week projects: ship a thing, get it through review, hand off the manifest, write a runbook, exit. Hiring a 6-month contractor for that work is the wrong shape. So is grinding through a Toptal intake call for what amounts to two weeks of focused effort.

Booking solves the shape problem. You write a one-paragraph spec, get a shortlist in minutes, run a 48-hour free trial, and pay weekly. If the engineer is wrong, replace them next Monday. If the scope ends, stop billing.

When booking is the wrong move:

You are committing to a 6-plus-month roadmap and want culture fit.
The role needs deep institutional context (legacy compliance, regulatory codebase) that takes a quarter to absorb.
You are building a team and want full-time loyalty.

When booking wins:

The scope is 1 to 12 weeks.
You have not validated whether the extension is even the right product.
You need to start this week.

If your scope falls in the second bucket, skip the recruiter loop on Cadence and have a vetted MV3-fluent engineer in your repo by Wednesday.

FAQ

How long does it take to hire a Chrome extension developer?

Vetted networks like Toptal and Arc promise 48 to 72 hours from intake to shortlist. Direct outreach to developers of top Web Store extensions takes 1 to 2 weeks for replies and a kickoff call. Cadence shortlists in 2 minutes against the 12,800-engineer pool with a 27-hour median time to first commit.

What's a fair rate for a Chrome extension developer in 2026?

US senior contractors run $85 to $160 per hour. EU senior contractors run 70 to 130 EUR per hour. Eastern Europe and LATAM mid-level developers run $40 to $80 per hour. On Cadence, weekly rates are fixed at $500 (junior), $1,000 (mid), $1,500 (senior), and $2,000 (lead).

Should I hire a generalist JavaScript developer or a Chrome extension specialist?

For anything past a content-script proof of concept, hire someone who has shipped to the Web Store. Manifest V3's service worker lifecycle, the move from webRequest to declarativeNetRequest, and host_permissions quirks all punish generalists with bugs that only appear in production.

Can one Chrome extension developer also build the backend?

Yes for simple extensions with a thin API or no backend at all. For OAuth-heavy, scraping-heavy, or sync-across-devices extensions that need a real backend, split the role into an extension developer and a backend developer. Doing both well at speed is rare.

How do I evaluate a Chrome extension developer if I'm non-technical?

Ask them to share one of their published extensions and walk you through the manifest.json line by line, in plain English. Five minutes tells you whether they shipped it themselves. Then ask: "What permissions does it ask for and why?" If they pause, you have your answer.

All posts