Senior Infrastructure Engineer

Join to apply for the Senior Infrastructure Engineer role at SearchApi We are looking for an infrastructure engineer who can own our entire cloud stack. You’ll build and operate the systems that power billions of requests, improve observability across everything we run, and expand our infrastructure as we grow. About SearchApi SearchApi 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. We’re a lean, profitable, bootstrapped team. No VC pressure, no bloat. Just engineers shipping real products to real customers. Why Join Us? Real Impact: Small team, massive scale. Your infrastructure runs in production serving billions of requests. Hard Problems: Browser clouds, websocket connections, TCP tuning, multi‑region deployments, autoscaling at scale. Full Ownership: You won’t be one of 50 SREs. You’ll own the stack. Fortune 500 Customers: Our API powers production workloads, not just pilots and experiments. Bootstrapped and Profitable: We answer to customers, not investors. Tech Stack AWS: Fargate, ECS, EKS, RDS Postgres, ElastiCache Redis, VPC Terraform Docker Ruby on Rails 8.1, Ruby 3.4 What You’ll Do Own and improve observability across the entire stack: metrics, logging, alerting, dashboards. Architect and operate browser cloud infrastructure: containerized browsers, session isolation, crash recovery, autoscaling. Handle websocket connections, CDP tunnels, and TCP‑level tuning for browser automation. Write and maintain Terraform for all infrastructure. Everything is code. Tune autoscaling, capacity planning, and cost optimization. Expand to new regions as we grow. Experiment with Lambdas, new cloud providers for custom scraping needs. Debug production issues: memory leaks, zombie processes, network failures. Build disaster recovery and incident response runbooks. Work with Linux systems, Dockerfiles, container orchestration daily. This is a senior role You’ve done this before at scale. You can architect systems, not just maintain them. You mentor other engineers on infrastructure best practices. Hard Parts Things break without warning. Proxies fail, browsers crash, cloud providers have outages. You’ll debug production issues under pressure. No hand‑holding. We don’t assign tasks or write detailed specs. You identify problems and fix them. Small team, big scope. There’s no platform team to escalate to. You own it end‑to‑end. Written communication is everything. Remote‑first means if you can’t write clearly, you’ll struggle. Fast pace. We ship daily. We expect results, not activity. About You Grinder. You don’t wait for instructions. You find work that matters and do it. Results‑driven. You ship. You measure. You iterate. Great writer. Docs, runbooks, post‑mortems, PRs. Writing is thinking. Strong work ethic. Startup pace. We work hard because that’s how you win against incumbents. Deep production experience with AWS: ECS, EKS, Fargate, RDS, VPC, IAM. Fluent in Terraform. Everything is infrastructure as code. Comfortable with Linux systems, Docker, container orchestration. Experience running headless browsers or similar workloads at scale (Playwright, Puppeteer, raw CDP). Understand networking: TCP, websockets, load balancing, multi‑region. Built observability stacks that engineers actually use (Prometheus, Grafana, Datadog, or similar). Can debug memory leaks, zombie processes, and weird container behavior at 2am. Fluent in English, written and spoken. BSc or higher in CS or equivalent technical field. We’re especially looking for Experience with browser clouds or similar high‑concurrency containerized workloads. Multi‑region and multi‑cloud experience. Cost optimization at scale. Connection pooling experience (PgBouncer or similar). Understanding of database sharding concepts. Experience with Lambdas or serverless for specific workloads. TLS fingerprinting, CDP internals, or browser automation depth. What We Look For Specific examples, not generic claims. Tell us what infrastructure you built, what scale you operated at, what problems you solved. If it looks copy‑pasted, we won’t read it. Signals we look for Stuff you personally built and shipped, not team achievements. Production experience at scale. Technical articles or blog posts. Meaningful open‑source contributions. Hiring Process 45‑minute interview call. Get to know each other, discuss experience. Take‑home challenge. Realistic infrastructure problem. Technical interview. 60 minutes, discuss your solution and go deeper. Meet the team. 30 minutes. Reference check + Offer. What You Get Fully Remote. Work from anywhere. Equity share. Own a piece of what you’re building. Profit sharing. When we win, you win.