Rust Systems Engineer

What you’ll do

• Build and operate a low-latency Rust fast-fetch engine
• Implement JA4/TLS and HTTP/2 frame emulation and fingerprinting
• Design proxy routing matrices and high-concurrency network I/O
• Maintain low-latency data pipelines

What they’re looking for

• Experience with Axum/Tokio and high-concurrency network I/O
• Familiarity with TLS/BoringSSL fingerprinting
• Experience building scrapers or crawling infrastructure
• For browser security role: deep familiarity with Firefox/Chromium internals and fingerprint evasion techniques

Skills

• Rust: Rust, fast-fetch engine, low-latency
• Axum: Axum
• Tokio: Tokio, high-concurrency, network I/O
• TLS / BoringSSL: TLS, BoringSSL, JA4/TLS fingerprinting
• Proxy routing: proxy routing matrices, proxies
• Browser internals: Firefox, Chromium, hardened Firefox, dwx_crawler
• CDP / WebDriver: CDP, WebDriver, stealth
• Web fingerprint evasion: canvas, WebGL, audio fingerprint evasion
• Next.js / React / TypeScript: Next.js 16, React 19, TypeScript
• Databases: SQLite WAL, Postgres
• Linux / Xvfb: Linux, Xvfb

The post

Datamint | Rust Systems Engineer, Browser Security | Remote (Global) | Full-time | $120k–$170k + Equity | https://datamint.xyz

We build high-throughput crawling and structured data extraction infra designed for AI agents and LLM pipelines.

If you’ve built scrapers recently, you already know the state of the market:

- Traditional proxy providers (Bright Data, Oxylabs, Smartproxy, Proxybase) give you raw IPs or massive unparsed HTML blobs, leaving you to deal with DOM bloat, token waste, and brittle parsing pipelines.

- Modern tools like Firecrawl or Jina made clean Markdown extraction easy for hobby setups, but they often struggle when you throw heavy SPAs, high-concurrency jobs, or hardened anti-bot walls (Cloudflare Under-Attack / Turnstile, Kasada, DataDome) at them.

- Rolling your own Playwright / Puppeteer cluster works until target sites deploy new JA4/TLS fingerprints, and your data team ends up spending 30% of their sprints fixing broken crawlers instead of shipping product.

We're tackling this by combining a low-latency Rust fast-fetch engine (JA4/TLS and HTTP/2 frame emulation) with an isolated stealth browser fleet, zero-code schema validation (JSON Schema/Pydantic), and native Model Context Protocol (MCP) support.

Trade-offs / where we fit: If you just need to curl a few static Wikipedia pages, a 10-line Python script is better and cheaper. But if you need reliable, structured data out of bot-defended sites without babying headless browsers, that's what we do.

We're looking for:

1. Rust Systems Engineer: High-concurrency network I/O, Axum/Tokio, TLS/BoringSSL fingerprinting, proxy routing matrices, and low-latency data pipelines.

2. Browser Security Engineer: Deep familiarity with browser internals (Firefox/Chromium source), canvas/WebGL/audio fingerprint evasion, CDP/WebDriver stealth, and familarity with anti-bot defenses.

Our stack: Rust, Next.js 16/React 19, TypeScript, hardened Firefox/dwx_crawler, Linux/Xvfb, SQLite WAL/Postgres.

If interested, shoot an email to jobs@datamint.xyz (or founders@datamint.xyz) with your GitHub, a project you built or broke, and what you find interesting in this space. No formal cover letter needed.