Web scraping, anti blocking, browser automation, proxy strategy and extraction infrastructure.

We are looking for one of the strongest technical people in the world at web data extraction resilience.

This is a rare role for someone who has already operated at the deep end of web scraping, anti blocking, browser automation, proxy strategy, fingerprinting, detection analysis and production scale data extraction.

We are only interested in candidates who have solved hard real world blocking problems at scale.

If your experience is limited to scripts, basic Selenium, simple proxy rotation, scraping APIs or freelance extraction jobs, this role is too advanced.

The mission

The modern web is dynamic, protected, personalized, unstable and increasingly hostile to automation.

Our job is to turn that environment into reliable, structured, enterprise grade data.

You will own the technical layer that makes this possible. This includes browser strategy, proxy strategy, fingerprinting resilience, site failure diagnostics, automated recovery, data quality validation and production scale extraction reliability.

What you will own

You will lead the architecture and execution of our web data resilience layer.

• Browser automation strategy across Chrome, Firefox, Brave, mobile browsers, headless and non headless environments

• Proxy strategy across residential, mobile, ISP, datacenter, geo targeted and vendor managed networks

• Fingerprinting resilience across browser, device, network, TLS, HTTP, canvas, WebGL, fonts, headers, cookies and behavioral signals

• Blocking diagnostics across CAPTCHA, JavaScript challenges, throttling, soft blocks, poisoned responses, geo restrictions, session decay and bot scoring

• Automated recovery systems that choose the right browser, proxy, session, region, timing and retry strategy per target

• Observability that explains why extraction failed, not only that it failed

• Systems that distinguish real success from fake success, partial success, stale data, delayed data or intentionally degraded data

• Vendor evaluation across proxy networks, browser infrastructure, CAPTCHA workflows and anti bot intelligence

• A long term technical roadmap for making our platform one of the strongest web data extraction systems in the market

What excellence looks like

You can diagnose a failed extraction and quickly separate proxy failure, browser fingerprint mismatch, TLS signature issues, JavaScript execution problems, session reputation, geo mismatch, rate pattern detection, extractor logic failure and target side layout changes.

You understand that page loaded does not mean data is correct.

You know when to use raw HTTP, browser automation, mobile emulation, API discovery, session reuse, proxy routing or managed extraction.

You have strong opinions because you have scars.

You instrument before guessing.

You can operate hands on, but you can also design systems that other engineers can use.

Required depth

You should have deep hands on experience with several of the following:

• Large scale web scraping or web data extraction platforms

• Playwright, Puppeteer, Selenium, CDP, browser orchestration or custom automation layers

• Anti blocking systems used in production

• Residential, mobile, ISP and datacenter proxy infrastructure

• IP reputation, session strategy, geo routing, retry logic and failure classification

• Browser fingerprinting and headless detection

• TLS fingerprinting, JA3, HTTP2 behavior, request signatures, headers and network level detection

• CAPTCHA and challenge handling workflows

• Distributed extraction infrastructure

• Queueing, retries, backoff, adaptive routing and recovery automation

• Cloud infrastructure, containers, Kubernetes, logging, tracing and observability

• Python, Node.js, Go, Rust or similar systems oriented languages

• Data quality systems that detect missing, partial, stale, poisoned or degraded output

Strong signals

• You have worked inside a serious scraping, data intelligence, pricing intelligence, competitive intelligence, search, ecommerce intelligence, ad tech, cyber intelligence, AI data or web intelligence company

• You have fought Cloudflare, Akamai, DataDome, PerimeterX, Kasada, Imperva, HUMAN, reCAPTCHA, hCaptcha or similar systems in legitimate production contexts

• You have built browser and proxy selection systems that adapt per site

• You have built dashboards that explain blocking causes with evidence

• You have debugged cases where the site appeared to work but the extracted data was wrong

• You have taken an unreliable extraction operation and made it measurable, recoverable and scalable

• You care about lawful, ethical and compliant web data access

Who should not apply

• Please do not apply if your answer to blocking is rotate proxies

• Please do not apply if you have only used scraping APIs and have never built the underlying resilience layer

• Please do not apply if you need to learn anti blocking fundamentals on the job

• Please do not apply if you cannot explain fingerprinting, proxy reputation, session strategy and soft blocks in technical detail

• Please do not apply if you are uncomfortable being assessed by people who understand this domain deeply

The person we want

You are probably the person other strong engineers call when the normal approach fails.

You may have worked quietly behind the scenes at a company where web data was mission critical.

You may come from scraping, search, pricing intelligence, ecommerce intelligence, fraud detection, ad verification, cyber intelligence, AI training data or large scale data acquisition.

You are practical, precise and allergic to vague explanations.

You know that reliability comes from architecture, instrumentation and feedback loops.

You can go from packet level detail to system architecture without losing the thread.

Application filter

Do not send a generic CV.

Send a short technical write up covering one hard web extraction resilience problem you personally solved.

Include:

1. The scale of the system
2. The type of blocking, degradation or detection involved
3. How you diagnosed the issue
4. What you personally built
5. What failed before the final solution worked
6. How you measured success
7. What you would do differently now
8. Any compliance or ethical constraints you had to account for

We care more about depth than polish. A shallow answer will end the process. A great answer will get our attention immediately.

Compensation and mandate

This is a senior, high impact technical role with direct access to leadership. For the right person, we will structure an attractive package that reflects the rarity of the talent.

You will have the mandate to redesign weak systems, choose tools, influence architecture and build a web data resilience layer that becomes a core strategic advantage.

Mandatory screening question

Describe a production anti blocking problem where the obvious fix failed.

Explain the real root cause, how you proved it and what system change finally solved it.

Final note

This role is intentionally narrow. We are looking for exceptional depth. If you are genuinely world class in this domain, we want to speak with you. If you are not, this will become clear very quickly.