What Is the Factory AI Interview Process Like? (Round by Round)

Factory does not publish its interview process, and public candidate reports are few. Expect a recruiter call, a technical phone interview (the one stage candidates report), and an onsite of three to four interviews. Companies of this size usually decide in two to four weeks, though no Factory timeline is reported.

The onsite interviews usually cover coding, system design, a past project, and values. Factory works from its San Francisco office five days a week, so a visit to the office is likely before an offer. Every stage below that candidates have not reported is marked as typical, not confirmed.

Factory builds Droids. A Droid is an AI agent that takes a ticket, changes the code, runs the tests, and opens a pull request. Every round tests whether you can build and judge software like that.

Quick Overview

Treat the table as a plan, not a promise. Ask the recruiter for the real list on the first call.

Stage 1: Recruiter Call

A short call about your background and why Factory. The recruiter also checks logistics. The main one is the office.

Factory's team works together in San Francisco five days a week. Say clearly whether that works for you. Prepare the motivation answer with How to answer why Factory AI.

Stage 2: Technical Phone Interview

This is the stage candidates report. It is a live coding session with an engineer. The question content is not reported in public.

At AI startups of this type, expect a practical problem, not a puzzle. A common form is a small tool or parser built in stages. The few public reports that exist rate the difficulty near the middle of the scale.

Talk while you code. Say the time and memory cost of your approach before the interviewer asks.

Stage 3: Coding Round

The onsite coding round is not reported by name. Expect something close to real Factory work. Build a working feature in about an hour with the interviewer as a teammate.

Ask clarifying questions first. Choose a small scope and finish it. Write a test, because clean, tested code counts more than a clever trick.

Stage 4: System Design Round

Factory's design problems come from its own product. Likely topics are agent orchestration, code retrieval over a large repository, safe execution of agent-written code, and evaluation of agents. Orchestration means the loop that plans a task, calls tools, and checks results.

The full list and a worked example are in What to expect in the Factory AI system design interview.

Stage 5: Project and Values Conversation

Factory publishes seven values: Champion the mission, Be relentless, First or Best, Build together, Embrace perspectives, Earn the right, and Create obsessed customers. Expect questions that test these. The strongest material is one project you owned from idea to production.

Factory's job posts ask for people who take "ambiguous research projects from conception to impactful deployment". Prepare the decisions, the alternatives you rejected, the numbers, and what broke.

Stage 6: Office Visit

An in-person stage is not reported, but it is likely. The company describes itself as lean and talent-dense, and its whole team works in one office. Small in-office teams usually want to meet a finalist in person.

Treat every conversation that day as an interview, including lunch.

Timeline and Decision

No candidate reports a full timeline. Companies of this size usually run the whole process in two to four weeks. Decisions often come within a week of the last round.

Factory's own recruiting posts list reducing time-to-hire as a goal. So a slow reply is more likely a scheduling problem than a rejection. The details on waiting and follow-up are in How long does it take to hear back after a Factory AI interview.

Questions to Ask Them

Each round ends with time for your questions. Use it to learn and to show research. Three good questions follow.

How does the team measure whether a Droid finished a task correctly? How much of Factory's own code is written by Droids? What does an engineer own in the first three months?

Factory states that it builds Factory using Factory. Ask what that means in a normal week.

How to Prepare

• Drill practical coding. Grokking the Coding Interview teaches the patterns behind medium and hard problems. Practice explaining the cost of your code as you write it.
• Practice product-shaped design. Grokking the System Design Interview covers the queues, caches, and databases that every agent platform uses.
• Prepare one deep project story. Write down the decisions, alternatives, numbers, and failures before the first call.
• Use the product. Factory offers a terminal version of Droid. Run it on a real repository and note where it succeeds and fails. That gives you concrete material for every round.