Software Engineer, Deployed
Job description
About the role
Factory develops and ships AI solutions that redefine engineering workflows. In this position, you report to the CEO and own the execution of high-impact customer implementations and specialized engineering initiatives. You serve as the primary technical interface between Factory and its enterprise customers.
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
You design, build, and maintain integrations that embed Factory into customer engineering environments and streamline developer workflows. The team executes end-to-end implementation to optimize workflows and accelerate delivery for enterprise clients.
Customer engagements are led with hands-on technical leadership to solve complex engineering obstacles and reduce time-to-value. On-site visits across customer environments drive rapid adoption and partnership success.
Special engineering initiatives are owned to extend Factory's capabilities and influence the product roadmap. Customer needs are translated into concrete product changes and technical requirements.
Production issues are responded to rapidly across diverse codebases and integration scenarios. Critical problems are troubleshot and Factory is innovated into novel applications that address specific customer needs.
Use cases are documented and tooling is developed to support customer growth at scale. Clear artifacts are built to support long-term adoption and success.
Customer feedback is closed through collaboration with Product, Engineering, Sales, and Operations. Insights from the field are turned into fast, concrete product and workflow enhancements.
Software development practices and emerging technologies are learned continuously.
Requirements
You bring 3+ years of experience from high-impact software engineering environments. A Bachelor's degree or higher is required.
Rapid learning of new technologies and programming languages is demonstrated. You work across a broad tech stack and adapt code across multiple parts of the Factory platform.
Diagnosing and resolving customer-facing technical issues shows strong problem-solving skills. Communication is clear with both technical and non-technical stakeholders.
You thrive in a fast-paced, evolving startup environment and stay self-motivated in ambiguous situations. Office presence in San Francisco occurs five days a week, within walking distance of Caltrain.
Practical notes
The role requires on-site presence in San Francisco with five weekly office days near Caltrain. 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 AI tooling often combine product, engineering, and customer interaction. Teams typically rely on modern software stacks and fast iteration cycles. Continuous learning shapes long term impact in deployment focused positions.
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.