Senior Infrastructure Engineer at SearchApi

Confirmed open

Own AWS, Terraform and container infrastructure for SearchApi’s high-volume browser and search-data services.

SearchApi

Location: Remote
Employment: FullTime
Work arrangement: remote
Technologies: AWS, Docker, Linux

Create a free application profile — Keep your skills and projects in a reusable profile. Private by default; you choose when to share. Apply for this job directly with the employer.

Role overview

The senior infrastructure engineer owns SearchApi’s cloud stack, including browser workloads, network connections, observability and multi-region growth. The source names AWS Fargate, ECS, EKS, RDS, Redis, Terraform and Docker. It lists remote work from Vietnam.

Responsibilities

Build metrics, logs, alerts and dashboards across production infrastructure.
Operate browser containers with session isolation, crash recovery and autoscaling.
Tune WebSocket and CDP tunnels, TCP networking, capacity and infrastructure cost.
Maintain Terraform configuration, extend deployments to new regions and evaluate serverless options.
Debug memory leaks, process and network failures; create disaster-recovery and incident runbooks.
Lead infrastructure design and mentor engineers on reliable operations.

Qualifications

Deep production AWS experience with ECS, EKS, Fargate, RDS, VPC and IAM, plus fluency in Terraform.
Linux, Docker, orchestration and high-concurrency browser or similar container workloads.
Networking knowledge including TCP, WebSockets, load balancing and multi-region services.
Experience building usable observability with Prometheus, Grafana, Datadog or similar tools and solving difficult production faults.
Clear English writing and a computer science degree or equivalent technical foundation; browser clouds, connection pooling and cost optimisation are useful extras.

Technology in this role

AWS: The source names AWS Fargate, ECS, EKS, RDS, Redis, Terraform and .
Docker: The source names AWS Fargate, ECS, EKS, RDS, Redis, Terraform and .
Linux: Linux, Docker, orchestration and high-concurrency browser or similar container .
Go: 60 minutes, discuss your solution and go .
Ruby on Rails: • Ruby on Rails 8.1, Ruby .
Ruby: • Ruby on Rails 8.1, Ruby .
Redis: The source names AWS Fargate, ECS, EKS, RDS, Redis, Terraform and .
Terraform: The source names AWS Fargate, ECS, EKS, RDS, Redis, Terraform and .
CI/CD: We ship multiple times a day with .
Playwright: • Experience running headless browsers or similar workloads at scale (Playwright, Puppeteer, raw .
CAN: We are looking for an infrastructure engineer who can own our entire cloud .
Rails: • Ruby on Rails 8.1, Ruby .
Prometheus: Experience building usable observability with Prometheus, Grafana, Datadog or similar tools and solving difficult production .
Grafana: Experience building usable observability with Prometheus, Grafana, Datadog or similar tools and solving difficult production .
Datadog: Experience building usable observability with Prometheus, Grafana, Datadog or similar tools and solving difficult production .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Senior Infrastructure Engineer position at SearchApi is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “The senior infrastructure engineer owns SearchApi’s cloud stack, including browser workloads, network connections, observability and multi-region growth. The source names AWS Fargate, ECS, EKS, RDS, Redis, Terraform and…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the platform and infrastructure area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Build metrics, logs, alerts and dashboards across production infrastructure.”; “Operate browser containers with session isolation, crash recovery and autoscaling.”; “Tune WebSocket and CDP tunnels, TCP networking, capacity and infrastructure cost.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Deep production AWS experience with ECS, EKS, Fargate, RDS, VPC and IAM, plus fluency in Terraform.”; “Linux, Docker, orchestration and high-concurrency browser or similar container workloads.”; “Networking knowledge including TCP, WebSockets, load balancing and multi-region services.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and.

Benefits

The employer lists fully remote work, equity, profit sharing, learning across a growing SaaS product and periodic team retreats.

About SearchApi

SearchApi provides an API for structured, real-time data from web search, shopping, video and other search sources. Its posting describes a small, remote-first engineering team building a Ruby on Rails product.

Employer website

How to apply

Review the original posting and apply through the employer’s careers page.

View source and apply Apply directly

Source checked: 2026-10-13

Browse job categories

AWS