Remote Proxy Architect: Build From Scratch at Scale

pWe are looking for an engineer who can build proxy infrastructure from scratch. Not configure existing solutions. Build. Residential networks, ISP proxies, rotation systems, session management. If you understand the difference between a high-level integration and writing a reverse proxy yourself, this role is for you.brstrongAbout SearchApibr/strongSearchApi is a real-time SERP API delivering structured data from 100+ search engines and sources, including Google Search, Google Shopping, Google Jobs, Bing, Baidu, YouTube, Amazon, and many more. We power production workloads for Fortune 500 companies and fast-moving startups who need reliable search data at scale.brWe're a lean, profitable, bootstrapped team. No VC pressure, no bloat. Just engineers shipping real products to real customers.brstrong Why Join Us?br/strongulliBuild from scratch. Not glue existing tools together. Design and implement proxy infrastructure. /liliGreenfield project. You'll shape the architecture from day one. No legacy to work around. /liliDeep technical work. Networking, protocols, performance optimization. The hard stuff. /liliReal scale. Billions of requests. Your infrastructure needs to handle it. /liliBootstrapped and Profitable. We answer to customers, not investors.br/li /ulWe are searching for someone who can build high-quality proxy infrastructure. We use existing solutions today. We want someone who understands their limitations and can build something better.brstrong Tech Stackbr/strongulliLow-level networking (TCP/UDP, sockets, connection handling) /liliHTTP/HTTPS/SOCKS5 protocols /liliHTTP/2, HTTP/3 /liliReverse proxy implementation (not just nginx/squid configuration) /liliLinux networking stack /liliCloud infrastructure (provider TBD based on IP policies and networking speed) /liliTerraform is a plus (for autoprovisioning)br/li /ulWe use Cursor, Claude, ChatGPT, GitHub, and Slack daily.brstrong🤖 You Control AI, AI Doesn't Control Youbr/strongWe ship faster because we use AI tools aggressively. Cursor and Claude. But you own the output. If you can't evaluate what AI produces, you're not ready for this role.brstrong

What You'll Do
br/strongulliBuild proxy infrastructure from scratch. Not integrate existing solutions. Write the core systems yourself. /liliDesign and implement rotation systems. IP rotation, session management, sticky sessions, intelligent routing. /liliManage IP reputation and quality. Monitor, track, score, and optimize IP health across pools. /liliBuild bandwidth reporting and metering. Track usage, report stats. /liliWrite reverse proxy systems. High-performance, optimized for our use case. Not just configure squid or nginx. /liliHandle multiple proxy types. Residential, mobile, datacenter, ISP. Understand the differences, characteristics, and when to use each. /liliImplement geo-targeting. Country, city, ASN level targeting. /liliOptimize for performance. Every millisecond matters. Every connection matters. /liliWork with networking fundamentals. Routing, DNS, TCP/UDP tuning, connection pooling, concurrent connection limits. /liliSupport multiple protocols. SOCKS5, HTTP, HTTPS. Different session types and authentication methods. /liliUnderstand HTTP/2 and HTTP/3 differences. And how they affect proxy behavior. /liliBuild monitoring and health checks. Track proxy pool health, failover, redundancy. /liliHandle IPv4 and IPv6. Understand the differences and implications.br/li /ulstrongYou define the architecture. /strong We have requirements, not a blueprint. You'll decide how to build it.brstrong The Hard Partsbr/strongThis role is not for everyone. Here's what makes it hard:brulliNo existing codebase. You're building from zero. No one to ask how it was done before. /liliPerformance is everything. Slow proxies are useless proxies. You'll obsess over latency and throughput. /liliComplexity at scale. Managing thousands of IPs, tracking reputation, handling failures gracefully. /liliDeep debugging. When something breaks at the network level, you need to figure it out. Packet captures, connection traces, protocol analysis. /liliUnderstanding trade-offs. We use existing solutions now. You should understand what they do well, where they fall short, and what could be done better.br/li /ulIf you prefer working with existing tools and frameworks without understanding what's underneath, this isn't for you.brstrong✨ About Youbr/strongulliDeep networking knowledge. TCP/UDP, sockets, connection handling, routing. Not surface-level. /liliProtocol expertise. HTTP, HTTPS, SOCKS5. You understand them at the byte level. /liliCan write a reverse proxy from scratch. Not just configure squid or nginx. Write the proxy. /liliPerformance obsessed. You profile, measure, and optimize. You know where the bottlenecks are. /liliUnderstand proxy types. Residential, mobile, datacenter, ISP. Their characteristics, use cases, and limitations. /liliExperience with IP reputation. How it works, how to manage it, how to recover from bla