> Markdown version of [/jobs/ext/4692795-software-engineer-generalist](https://www.wearedevelopers.com/jobs/ext/4692795-software-engineer-generalist). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Engineer, Generalist

- **Company:** BUILD, Inc.
- **Location:** San Francisco, CA, United States
- **Contract:** Permanent contract
- **Skills:** Training Data, Application Programming Interfaces (APIs), Artificial Intelligence, Big Data, C++ (Programming Language), Cloud Computing, Data Infrastructure, Linux, DevOps, Hardware Design, Python (Programming Language), Software Engineering, TypeScript, Scripting, ReactJS, Backend, Data Management, Front End Software Development, Data Pipelines, Golang
- **Published:** November 12, 2026
- **Apply:** https://www.careerbuilder.com/job-details/software-engineer-generalist-san-francisco-ca--144ae3b5-5b83-4cc4-a5e2-95bf825cc55a

## About the Role

Software Engineering, Manufacturing, Training Data Sets, Artificial Intelligence (AI), Logistics, Scripting (Scripting Languages), Software Engineering, Customer Relations, Data Management, Application Programming Interface (API), * Strong full-stack skills; fluency in Python and at least one of TypeScript, React, Go, or C++

 * 1-5+ years shipping software end to end, ideally in a 01 or startup environment
 * You ramp quickly in unfamiliar codebases and problem domains
 * Bias toward action and comfort with incomplete information
 * Experience shipping where the role was not clearly defined

Strong candidates may also have experience with (Nice-to-have qualifications)

 * Experience across backend, frontend, data, infra, and scripting
 * Hardware-adjacent, AI, or large-scale data systems
 * Prior startup experience during hypergrowth
 * Infrastructure or DevOps (Linux, containers, cloud)

## Description

We're hiring generalist software engineers who can work across the company. This seat finds the gap, ships in days not weeks, and moves on. One week you might build a data pipeline; the next a hardware integration script, an internal tool, or a customer-facing API. The only constant is a problem that is time-sensitive and business-critical., * Detect the highest-leverage gap that week - ingest, APIs, orchestration, field tools, hardware glue - and ship production-quality code for it

 * Build backend services and APIs for the data platform and the customer-facing product
 * Write processing and validation pipelines for incoming in-the-wild datasets
 * Script integrations between collection devices, cloud infrastructure, and software services
 * Design interfaces and developer workflows that the rest of the company actually uses
 * Work cross-functionally with research, Shenzhen hardware, and ops without waiting for a spec