NewLaunching String Web Access APIRead the manifesto →

Open roles at String

Engineering
Senior Software EngineerNew York, USApply here
Forward Deployed EngineerRemoteApply here
Scraping EngineerRemoteApply here

Open challenge

Find a site we can't scrape. Build an endpoint (or test deployment) that bypasses it. If it works, you get an automatic interview — no resume required.

  1. Run the target through our playground or the API and watch it fail. Copy the request ID off that run — the playground shows it on the result, the API returns it as x-request-id.
  2. Build an endpoint or deployment that does get the page.
  3. Send us the request ID, the target, and your endpoint.

We look that ID up and re-run it ourselves. If the request shows us succeeding, or we can't find it, the submission isn't reviewed.

Related parsing challenges we want next: faster extraction, structured-output accuracy, and anti-bot detection gaps.

Completed it?

Run the target through the live playground first, copy the request ID off the failed run, and send it with your endpoint. We look that request up in our logs — a submission without an ID we can find isn't reviewed.

Shown on the run in the playground, and returned as the x-request-id header on any String API response.

The roster

A small team in New York City building web access for everyone. Same people, rendered however you like.

Rohit Shenoy
Rohit Shenoy
Company, customers, GTM
Logan Harless
Logan Harless
Agent tooling, infrastructure
Dias Khalniyasov
Dias Khalniyasov
Agentic feed building, platform
Jonathan Mascarenhas
Jonathan Mascarenhas
Marketplace feeds, agent tooling
Ashbin Rai
Ashbin Rai
Portal, anti-bot, deploys
Tufayl Rahman
Orchestration, web discovery
Bruce Magness
Operations
???
Classified

General interest

Don't see the right role? Tell us about yourself and we'll reach out when there's a fit.

© 2026 StringEU and UK GDPR Article 27 representative — appointment verified by EuverifyBuilt in New York City 🗽 🍎