PpWe 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. /p h3About SearchApi /h3 pSearchApi 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. /p pWe're a lean, profitable, bootstrapped team. No VC pressure, no bloat. Just engineers shipping real products to real customers. /p h3Why Join Us /h3 ul liBuild from scratch. Not glue existing tools together. Design and implement proxy infrastructure. /li liGreenfield project. You'll shape the architecture from day one. No legacy to work around. /li liDeep technical work. Networking, protocols, performance optimization. The hard stuff. /li liReal scale. Billions of requests. Your infrastructure needs to handle it. /li liBootstrapped and Profitable. We answer to customers, not investors. /li /ul pWe 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. /p h3Tech Stack /h3 ul liLow-level networking (TCP/UDP, sockets, connection handling) /li liHTTP/HTTPS/SOCKS5 protocols /li liHTTP/2, HTTP/3 /li liReverse proxy implementation (not just nginx/squid configuration) /li liLinux networking stack /li liCloud infrastructure (provider TBD based on IP policies and networking speed) /li liTerraform is a plus (for autoprovisioning) /li /ul pWe use Cursor, Claude, ChatGPT, GitHub, and Slack daily. /p h3You Control AI, AI Doesn't Control You /h3 pWe 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. /p h3What You'll Do /h3 ul liBuild proxy infrastructure from scratch. Not integrate existing solutions. Write the core systems yourself. /li liDesign and implement rotation systems. IP rotation, session management, sticky sessions, intelligent routing. /li liManage IP reputation and quality. Monitor, track, score, and optimize IP health across pools. /li liBuild bandwidth reporting and metering. Track usage,



report stats. /li liWrite reverse proxy systems. High-performance, optimized for our use case. Not just configure squid or nginx. /li liHandle multiple proxy types. Residential, mobile, datacenter, ISP. Understand the differences, characteristics, and when to use each. /li liImplement geo-targeting. Country, city, ASN level targeting. /li liOptimize for performance. Every millisecond matters. Every connection matters. /li liWork with networking fundamentals. Routing, DNS, TCP/UDP tuning, connection pooling, concurrent connection limits. /li liSupport multiple protocols. SOCKS5, HTTP, HTTPS. Different session types and authentication methods. /li liUnderstand HTTP/2 and HTTP/3 differences. And how they affect proxy behavior. /li liBuild monitoring and health checks. Track proxy pool health, failover, redundancy. /li liHandle IPv4 and IPv6. Understand the differences and implications. /li /ul pbYou define the architecture. /b We have requirements, not a blueprint. You'll decide how to build it. /p h3The Hard Parts /h3 ul liNo existing codebase. You're building from zero. No one to ask how it was done before. /li liPerformance is everything. Slow proxies are useless proxies. You'll obsess over latency and throughput. /li liComplexity at scale. Managing thousands of IPs, tracking reputation, handling failures gracefully. /li liDeep debugging. When something breaks at the network level, you need to figure it out. Packet captures, connection traces, protocol analysis. /li liUnderstanding trade-offs. We use existing solutions now. You should understand what they do well, where they fall short, and what could be done better. /li /ul pIf you prefer working with existing tools and frameworks without understanding what's underneath, this isn't for you. /p h3About You /h3 ul liDeep networking knowledge. TCP/UDP, sockets, connection handling, routing. Not surface-level. /li liProtocol expertise. HTTP, HTTPS, SOCKS5. You understand them at the byte level. /li liCan write a reverse proxy from scratch. Not just configure squid or nginx. Write the proxy. /li liPerformance obsessed. You profile, measure,



and optimize. You know where the bottlenecks are. /li liUnderstand proxy types. Residential, mobile, datacenter, ISP. Their characteristics, use cases, and limitations. /li liExperience with IP reputation. How it works, how to manage it, how to recover from blacklisting. /li liGeo-targeting knowledge. Country, city, ASN level. How it works, accuracy limitations. /li liLinux networking. iptables, routing tables, network namespaces. Comfortable at this level. /li liSelf-directed. You don't need someone to tell you what to build next. /li liGreat writer. Documentation, architecture decisions, protocol specs. Clear communication matters. /li liFluent in English, written and spoken. /li liBSc or higher in CS or equivalent technical field. /li /ul h3Required experience /h3 ul liBuilt proxy or networking infrastructure before (not just used it). /li liDeep understanding of HTTP/HTTPS/SOCKS5 protocols. /li liExperience with high-throughput, low-latency systems. /li liTCP/UDP programming at socket level. /li /ul h3We're especially looking for /h3 ul liExperience building residential or ISP proxy networks. /li liUnderstanding of ISP relationships and mobile carrier specifics. /li liIP rotation and session management systems. /li liIP quality scoring and reputation management. /li liGeo-targeting implementation (country, city, ASN). /li liMulti-tenancy and customer isolation. /li liHTTP/2 and HTTP/3 proxy experience. /li liTerraform for infrastructure provisioning. /li liExperience at massive scale. /li /ul h3What We Look For /h3 h3Signals we look for /h3 ul liNetworking projects you've built. /li liLow-level systems experience. /li liTechnical blog posts about protocols or networking. /li liOpen-source contributions to proxy or networking tools. /li liEvidence you understand this domain deeply. /li /ul h3Hiring Process /h3 ul li45-minute interview call. Discuss your experience with proxy and networking systems. /li liTechnical deep-dive. Architecture discussion, protocol knowledge, design questions. /li liTake-home challenge. Realistic networking problem. /li liMeet the team. 30 minutes. /li liReference check + Offer. /li /ul h3What You Get /h3 ul liFully Remote. Work from anywhere. /li liEquity share. Own a piece of what you're building. /li liProfit sharing. When we win, you win. /li liGreenfield project. Build something from scratch. /li liAnnual team retreats (last one in Spain). /li /ul /p #J-18808-Ljbffr

📌 Proxy network engineer (Italia)
🏢 SearchApi
📍 Italia