Software Engineer, Full Stack

About the role

Sift provides a data infrastructure platform that converts high-frequency telemetry from mission-critical physical systems into engineering insights. The team builds tools for hardware engineering organizations, including aerospace, defense, energy, and autonomous systems. In this role, you will contribute to the full stack of their data platform.

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

Design user interfaces that enable data exploration while maintaining performance with large real-time datasets. Partner with data platform and frontend teams to define and deliver service designs. Write clean, maintainable code and contribute to technical design discussions for scalable solutions.

Requirements

The posting states a bachelor's degree requirement. Bring 3+ years of professional experience in full-stack software development to production systems. Demonstrate experience building applications with React, NextJS, TypeScript, Go, Rust, and Python in live environments. Show familiarity with relational and non-relational databases such as PostgreSQL, Druid, Pinot, and Timescale. Apply strong problem-solving skills and attention to detail to solve demanding engineering problems.

Nice to have

Earn bonus consideration through experience with WebGL, D3.js, and Apache ECharts for technical visualization. Highlight knowledge of WebAssembly and browser-based computation. Contribute from a background in scientific computing or technical data visualization. Build tools for technical users, including dashboards and data-editing environments. Point to side projects that achieved consistent usage traffic.

Skills & tools

Use a modern JavaScript frontend stack with ECharts, React, Redux, and TypeScript. Work with backend technologies such as Go, gRPC, PostgreSQL, Protobuf, and Radix. Process data using Arrow, DataFusion, Flink, Parquet, and Rust. Manage infrastructure on AWS, Docker, Kubernetes, and GitHub Actions with tools like Argo CD, Grafana, and Terragrunt.

Practical notes

citizenship, lawful permanent residency, or protected status such as asylee or refugee is required to comply with ITAR and EAR regulations. 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.

Good to know

Roles in data infrastructure focus on building platforms that store, process, and visualize high-volume telemetry. Teams commonly use a mix of web frontend frameworks, stream processing tools, and cloud infrastructure. Version control, code review, and automated testing are standard practices for maintaining reliability. Hardware engineering domains such as aerospace and defense often require strict compliance and security measures.

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.