Senior Software Engineer (AI-native)
# **Senior Software Engineer (AI-native) — Scraping & Proxy Infrastructure**
**Pinobyte** · Full-time · Remote (no location restrictions) · **$3,000–5,500/month**
---
## **Who we are**
Pinobyte is a small, founder-led engineering company that builds **custom data-extraction solutions**.
In practice: we get data out of the hardest places on the internet — sites behind DataDome, Cloudflare, Akamai and friends — at scale, reliably, and turn it into something a business can actually use. Marketplaces, e-commerce, real estate, social media and reviews.
We are a compact senior team, no layers of management. You talk to the people who make decisions, and your work ships the same week.
## **What we're hiring for**
This is **one opening with two possible landing spots** — we'll figure out the better fit together during the process:
**1. Target Engineering (Middle+/Senior).** Own concrete high-value targets end to end: research how a site defends itself, design the bypass, build the extractor, and keep it green. Anti-bot detection, browser fingerprinting, session and cookie strategies, request-level reverse engineering, parsing at scale, and the monitoring that tells you a target broke before the client does.
**2. Proxy Infrastructure (Senior/Principal).** A separate product: proxy platform. A Go service plus the infrastructure around it — high-throughput traffic, connection pooling, routing and rotation logic, IP quality and reputation, latency and failure budgets. There's real accumulated debt and real incidents here; we're looking for someone who wants to take ownership of a system.
Both roles are full-time, long-term, and part of the same engineering culture.
## **What we actually hire for**
We don't care whether your last five years were Python, Go, TypeScript or Rust. Our own stack spans Python (FastAPI, Celery), Go, Postgres, Redis, RabbitMQ, Docker/K8s, OpenTelemetry/Grafana, headless browsers and a lot of network-level tooling — and you'll touch several of them. A strong engineer picks up a language in a week; system design, judgment and ownership take years.
**We're looking for an AI-native software engineer** — someone who works the way this profession works in 2026:
- You use LLMs and coding agents as a real part of your workflow. You know how to get a large, unfamiliar codebase into your head fast, generate and *review* code critically, and where the model will confidently lie to you.
- Speed with a floor under it: you ship fast, and what you ship has tests, logs and metrics.
- You design systems — you think about failure modes, retries, idempotency, cost and what happens at 100x traffic.
- **You're proactive — you bring solutions, not just status updates.** When you see something broken, slow or badly designed, you're expected to propose a concrete fix with trade-offs, and drive it through.
- You're not afraid to debug — code you didn't write, in production, with incomplete information.
- Excellent spoken English is a must — we work and talk in English every day, and you should be comfortable discussing an architecture or an incident live.
**Nice to have (any of these gets our attention):** anti-bot systems and fingerprinting · TLS/JA3, HTTP/2, low-level networking · headless browser automation at scale (Playwright/CDP) · Go services under load · proxy infrastructure or anything that moves a lot of packets · distributed queues and workers · observability done properly · previous experience owning a product surface end to end.
## **What we offer**
- **$3,000–5,500/month**, full-time. The range is wide on purpose — it reflects seniority and which track you land in, and we'll be straightforward with you about where you sit and why.
- Fully remote, no location restrictions, flexible hours, async-first. Reasonable overlap with the team matters more than a fixed schedule.
- We provide paid AI tooling — Claude Code and whatever else makes you faster.
- Genuinely hard technical problems, a short path from idea to production, and no bureaucracy between you and shipping.
## **Process**
Short and to the point: an intro call, then a technical conversation of about 1.5 hours — your past systems, our real problems, how you'd approach them. That's it.
## **How to apply**
Send your CV plus a few sentences on:
- a system you owned end to end — what broke, and what you did about it;
- how you use AI tools day-to-day;
- which track pulls you more, and why.
We read every application and reply to all of them.