Efficient Computer is rethinking computing from the ground up to solve one of AI's biggest challenges: energy. Our Fabric architecture delivers a 10–100x improvement in energy efficiency for general-purpose computation, including AI, while supporting familiar programming languages and software frameworks—unlocking new possibilities for autonomous machines, intelligent infrastructure, wearables, and space systems. With our first processor, Electron E1, now shipping in volume and more than $97 million in Series B financing recently announced, we're accelerating customer deployments and scaling our architecture to data center performance. Join us to build the hardware and software that bring intelligence wherever it's needed and help shape the next generation of computing.

Efficient is looking for a Software Build & Release Engineer to own the GitHub-based build environment that every engineer on the team depends on to build, test, and ship software. That means developing and running the CI/CD pipelines, executing our testing and release processes, and being the first person to dig in when a build or the infrastructure behind it breaks.

This is a hands-on senior role. Success looks like fast, reliable builds, predictable releases, and a build system that other engineers can understand because it is clearly documented.

What you'll do

Build environment

• Design, develop, and maintain the GitHub-based build environment, including GitHub Actions workflows, runners, and repository automation.
• Manage build compute across providers such as Namespace, Google Cloud, and AWS, balancing speed, reliability, and cost.
• Improve build times and stability through caching, parallelization, and dependency management.
• Keep the build environment secure: secrets handling, access controls, and dependency and artifact integrity.

Testing and release

• Execute and continuously improve the testing process, including automated test pipelines and reporting on results.
• Run the release process end to end: branching, versioning, packaging, artifact publishing, and release notes.
• Reduce flaky tests and manual release steps so that releases are repeatable and low-risk.

Triage and debugging

• Triage build, test, and infrastructure failures, and determine whether the cause is in code, configuration, tooling, or the provider.
• Debug problems to root cause and put fixes in place that prevent them from recurring.
• Monitor the health of builds and infrastructure, and act on trends before they become outages.