Software Engineer, Infrastructure

About the role

This role builds and operates data infrastructure for hardware engineering teams.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Build and operate scalable, resilient infrastructure that serves hardware engineering teams and turns high-frequency telemetry into engineering insights.

Optimize application performance and reliability for hardware engineering teams through close collaboration with software engineers.

Deploy monitoring, alerting, and logging to enable proactive identification and resolution of issues that affect platform reliability.

Streamline infrastructure management and automate deployment processes using modern DevOps tools and methodologies to accelerate delivery for hardware engineering teams.

Evolve backend architecture and infrastructure to support both cloud and on-premise deployments, balancing scalability with operational control.

Requirements

Bring 3+ years of relevant distributed systems experience focused on designing and managing cloud-based environments such as AWS, Azure, and GCP for data infrastructure serving hardware engineering teams.

Demonstrate hands-on experience with containerization technologies such as Docker and Kubernetes, and container orchestration platforms to support consistent deployment and scaling of data pipelines.

Show passion for building and operating developer productivity tools, frameworks, and other aspects of platform engineering to help hardware engineering teams maintain velocity with telemetry and simulation data.

Exhibit familiarity with CI/CD pipelines and version control systems to automate infrastructure changes safely and maintain resilience across multi-region and multi-cloud environments.

Apply knowledge of automated testing best practices and frameworks, ensuring software reliability through integration, performance, and end-to-end testing for distributed systems serving critical hardware platforms.

Thrive in the ambiguity and high-ownership culture of early-stage startups, where infrastructure must evolve quickly to support new missions.

Collaborate effectively with a broad range of job functions and roles, including software engineers, hardware engineers, and product teams, aligning infrastructure priorities with system-level goals.

experience with our tech stack, including Go, Java, React, TypeScript, Kafka/Redpanda, Flink, AWS, Azure, GCP, Docker, Kubernetes, and Terraform/CDK, or equivalent distributed systems.

Maintain strong knowledge of cloud, on-premise, networking, and service architecture in multi-region multi-cloud setups to ensure resilient connectivity for telemetry ingestion and processing.

Practical notes

Citizenship is required for this position due to customer environments, security requirements, and access obligations.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.