Skip to main content

Pinwheel

Reverse Engineer

New York, NY$115k–$140kmidAdded today

About this role

Pinwheel's Integrations Platform team seeks a mid-level backend engineer to own platform projects that power 1800+ integrations. You'll ship reliability and performance improvements to shared infrastructure, support integration engineers through tooling and libraries, and operate production systems handling proxy management, browser automation, and identity flows.

What you'll do

  • Own platform projects end-to-end from design through production operation and monitoring
  • Reverse engineer and fix integration issues against systems that change frequently
  • Ship reliability and performance improvements to proxy management, browser fleet, and AWS infrastructure
  • Build shared libraries, lint rules, and internal tooling to improve integration engineer productivity
  • Participate in on-call rotation, triage incidents, and write postmortems with preventive fixes
  • Maintain dependency and security hygiene including CVE remediation and crypto updates

What they're looking for

  • Python 3.10+
  • Backend integrations engineering
  • AWS (DynamoDB, S3, IAM, ECR, latency/retry patterns)
  • Production operations and incident response
  • Systems design and failure mode analysis
  • Concurrency and async patterns (async/await, greenlets, threads)
  • Browser automation (Selenium, Playwright, Chrome DevTools Protocol)
  • AI-assisted development tools (Claude, Copilot)
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Pinwheel

Pinwheel builds an integrations platform that supports over 1800 integrations, focusing on performance and reliability. The company is hiring backend engineers to lead projects and enhance their integration infrastructure.

Website
pinwheel.com
View all jobs at Pinwheel

Likely interview questions

  • Describe a reverse engineering or integration project where you had to repeatedly fix issues as an external system changed—how did you approach that cadence?
  • Walk us through a production incident you debugged and fixed under time pressure. What was your process and what did you learn?
Unlock all 7 questions free — and practice them live →