Software Engineer, Developer Infrastructure

Quilt•Redwood City, CA

4h•$150,000 - $200,000•Hybrid

About The Position

Our mission is to move humanity off of fossil fuel heating. 20% of US global warming emissions come from homes (that's more than cars!). The largest driver of home emissions is burning fossil fuels for heat. To stop climate change, over 80M US homes need to transition from combustion to efficient, electric heat pumps over the coming decades. We believe for this to happen the world needs fantastic products that are easy to purchase. Today's heat pumps lack great design, make limited use of software, and are difficult and stressful to adopt. We are building a next generation, beautifully designed, AI optimized home heating and cooling system that is 10x better than what is on the market today. AI agents can generate code 100x faster than humans. But at Quilt, generating code was never the bottleneck, verifying it is. We build software that runs on physical hardware in people's homes. A bug isn't a broken pixel; it's a family without heat. Our code spans embedded C++ on custom devices, cloud infrastructure, and mobile apps. Right now, too much of our verification depends on a human walking to a test bench and pressing a button. We need to build the factory that builds the code. We're looking for a software engineer to own our developer infrastructure: the simulators, test harnesses, CI/CD pipelines, and verification systems that let our engineering team (and our AI agents) ship fast with confidence. Your work will directly determine how quickly Quilt can move: not by writing features, but by making every feature easier to build, test, and trust. This is a high-leverage infrastructure role. You'll be the engineer who makes every other engineer on the team more productive. You'll build the systems that close the feedback loop between code generation and code verification, so that an engineer (or an agent) can write a change, get an automated signal on whether it works, and iterate without waiting on manual testing. We already have hardware-in-the-loop test rigs and some device simulators in place. Your job is to expand them, make them robust, and build the scaffolding that lets the whole team write and run tests with minimal friction.

Requirements

You have 4–7 years of software engineering experience, with significant time spent on test infrastructure, developer tooling, CI/CD systems, or platform/infrastructure engineering
You're a strong Python developer (pytest preferred) and comfortable reading/modifying C++ test code (gtest)
You've owned CI/CD pipelines end to end; not just maintained them, but designed them to be fast, reliable, and trusted
You think about testability as an architecture problem, not just a coverage metric. You've influenced engineers to refactor code so it can be tested
You're comfortable in Linux/Unix environments and can debug complex issues across hardware and software boundaries
You care about developer experience: you notice when something is painful and you build the tool to fix it
You can work independently, identify the highest-leverage infrastructure gaps, and make the case for fixing them
You have experience with or interest in how AI agents can be integrated into testing and verification workflows

Nice To Haves

Experience building or maintaining hardware-in-the-loop test systems, device simulators, or integration test environments for IoT or embedded products
Experience with device communication protocols (Modbus, serial, gRPC)
Experience testing firmware OTA updates or device provisioning flows
Bazel build system experience
Docker and containerization for test environments
Mobile test automation (Appium for iOS/Android)
Web E2E automation (Cypress/Playwright)
HVAC, home automation, or similar IoT domain experience
Embedded Linux or Raspberry Pi development

Responsibilities

Build the Verification Machine (50%)
Design and extend device simulators and mocks that reduce our dependency on physical hardware for testing
Build and maintain CI/CD pipelines across embedded, cloud, and mobile (GitHub Actions, Bazel)
Extend our hardware-in-the-loop (HIL) test infrastructure for device commissioning, OTA updates, and telemetry validation
Automate the manual test scenarios that currently block releases (pairing flows, firmware upgrades, cloud integration)
Debug and eliminate flaky tests, CI must be a source of truth, not noise
Make Testing Easy (35%)
Build reusable test fixtures, libraries, and templates that lower the barrier for engineers to write unit and integration tests
Design testable interfaces and mock layers for embedded device features
Collaborate on architecture decisions to ensure new code is testable by default
Provide patterns and examples (pytest, gtest) that engineers and agents can copy and adapt
Improve the local development and CI experience so tests are fast and reliable
Document testing patterns and best practices, especially for embedded systems
Strengthen Release Confidence (15%)
Validate critical release paths with automated and exploratory testing (device pairing, OTA, mobile app integration)
Support mobile app testing (iOS/Android) for key user flows
Turn customer-reported issues into new automated test cases, closing gaps in the verification machine so the same bug never ships twice