Namespace sells speed to the people and the agents writing code: your CI jobs, container builds, and the coding agents now opening pull requests run faster on its compute than on the default runners most teams reach for. The concrete pieces behind that pitch, per its own site, are GitHub Actions runners described as built for agent scale, remote execution for Bazel with a tiered build cache, fast container image loading, and a fleet of Linux, Windows, and Apple-silicon macOS machines. A newer product, Devbox, gives a coding agent its own cloud development environment instead of a throwaway sandbox, and the company ships an SDK in Go and TypeScript, an nsc CLI, and MCP hooks into Claude Code, Codex, and Cursor.
The round says investors buy the thesis that agent infrastructure is a category worth owning early. Coverage differs on the exact date and the full syndicate, so treat anything beyond the lead and the amount as press-reported (AI Weekly). Reporting says the money goes into expanding the company’s own compute fleet. The bet rhymes with the path Modal took: pick one hard infrastructure problem next to the AI boom, be early, and build the compute yourself rather than reselling someone else’s.
Who Namespace is hiring, and why the roles read the way they do
Namespace lists its openings on its careers page, and in November 2026 the engineering roles are split across its European bases and the new US seats. The visible titles run from an Engineering Lead for the US through Product and Infrastructure Software Engineers, two customer-facing roles, a Security Engineer, a DevOps Engineer, and a Technical Project Manager, alongside go-to-market hires. The shape tells you where the company is going. The infrastructure roles own the compute that runs customer builds, tests, and CI jobs, which is the product itself, so they skew toward low-level systems: virtualization, scheduling, storage, networking, and the caching that makes a build cache fast. The product-engineering roles ask for TypeScript, Go, or Python and sit closer to the SDK, the CLI, and the dashboard.
A couple of signals are worth reading. The customer-facing engineer roles and the US expansion together say Namespace is landing and growing accounts that need hands-on migration help, not a self-serve signup. One outlet covering the raise put the customer base north of a thousand and named companies like Ramp and Vanta; take that as press-reported, not company-confirmed. The standalone Security Engineer role is not decoration at a company whose business is running other people’s code on shared hardware: isolation and tenant boundaries are a first-order problem, and the security engineer interview guides are a fair calibration for how deep that questioning could go. With roles split between the European bases and the new US seats, none of the postings we read states whether visa sponsorship or relocation is on offer, so ask the recruiter early if you would need either.
For an engineer weighing the move, the useful comparison is to other developer-infrastructure startups rather than to a model lab. The “we own the fleet” posture is a familiar infrastructure bet, but the workload here is builds and agents, not model inference, so the wins come from caches, image loading, and scheduler behavior more than from GPU packing.
The Namespace Labs interview process is not public yet
A November 2026 search of Glassdoor, Blind, and Reddit turned up no Namespace Labs engineering interview account (the one Glassdoor hit is a chat-support role at an unrelated company that shares the name), and the company’s own postings describe the work, not the stages. The careers page goes no further than “send us your resume and tell us what you’d love to work on.” So everything in this section is inferred from the roles and from how comparable early, well-funded infrastructure startups tend to run their loops. None of it is reported, and once you are in the pipeline your recruiter is the real source of truth.
The plausible shape for a Series B company is a recruiter or founder screen, a hiring-manager technical conversation, one or two deeper technical rounds matched to the role, a practical or take-home exercise, and a final round with a founder or the broader team. The format, round count, and timeline are all unknown, so prep the substance and ask for the schedule in writing early. Given the founder’s years as a Google principal engineer, a high bar on systems depth and reasoning over trivia is a reasonable expectation, though that is an inference, not a reported fact.
What each Namespace Labs engineering track likely screens for
For infrastructure roles, the subject matter that fits the product is the compute fabric: how you isolate untrusted workloads, how you make a cold build warm, where latency and cost go when a thousand CI jobs land at once. The multi-tenant, high-throughput scenarios in the system design interview guides are closer preparation than algorithm drilling, and since the SDK ships in Go and the infra postings ask for it, brushing up on Go concurrency and the runtime is time well spent. The three prompts below are illustrative, built from the product and the role shape rather than any candidate report, but they show the sort of problem each track would plausibly turn on:
- Build infrastructure: “A customer’s Bazel build is slow on a cold cache and fast on a warm one. Design the remote cache and remote execution path. What do you key cache entries on, how do you keep it correct across toolchain changes, and what breaks first when ten teams share it?” A strong answer ties cache identity to the full action inputs and toolchain version, and names poisoning and eviction under contention as the early failure modes.
- Isolation and security: “You run untrusted build steps from many customers on shared hosts. Walk me through the isolation boundary. What stops one tenant’s job from reading another’s artifacts or escaping to the host, and what is the blast radius if a sandbox is compromised?” A strong answer commits to a concrete boundary such as a microVM or a hardened container, then reasons about the kernel attack surface and what a breakout can reach rather than stopping at the word “container”.
- Agent compute (Devbox): “An AI coding agent needs a fresh, reproducible dev environment in under a second and may spin up hundreds in parallel. How do you make environment creation that fast and that cheap, and how do you reclaim them without losing work the agent still needs?” A strong answer reaches for snapshotting and copy-on-write to keep startup cheap, and separates reclaiming idle environments from preserving an agent’s in-progress state.
The customer-facing engineer sits across a different line. The role suggests a bar split between engineering and judgment: you would build real integrations and also sit with a customer, turn a vague “our CI is too slow” into a concrete migration plan, and own whether it lands. A likely ask is to walk through a time you shipped something directly for a customer and defend the trade-offs you made under their constraints, where a structured STAR answer holds up better than an improvised story. The product-engineering track points back at the SDK and CLI surface, so reasoning about API design and developer ergonomics likely matters as much as raw systems.
| Namespace Labs interview and company facts (as of November 2026) | Detail | How well-sourced |
|---|---|---|
| What it does | Developer compute cloud for AI coding agents and CI: GitHub Actions runners built for agent scale, Bazel remote execution with a tiered cache, fast container image loading, Devbox cloud dev environments for agents, and a fleet of macOS, Linux, and Windows instances, plus an SDK in Go and TypeScript and MCP integration | Reported (namespace.so, read November 2026) |
| Founder and base | Founded 2022 by Hugo Santos, a former Google principal engineer; Zurich-based per trade press, with a US engineering presence being built in New York and the San Francisco area | Reported (AI trade press); careers page lists regions but no HQ |
| Funding | $42M Series B led by Scale Venture Partners, announced early October 2026, with additional investors participating; followed the Series A by about seven months. Reported date and full syndicate vary by outlet | Reported (multiple outlets); amount and lead consistent, finer details press-attributed |
| Open roles | November 2026 engineering roles: Engineering Lead (US), Product Engineer and Infrastructure Software Engineer (Switzerland, Germany, UK, New York, SF area), two Customer-Facing Software Engineer roles, Security Engineer, DevOps Engineer, Technical Project Manager, plus go-to-market hires | Reported (namespace.so/careers and the Ashby board, read November 2026) |
| Interview loop | No published loop and no candidate reports found. Plausible shape for a company this size: recruiter or founder screen, hiring-manager technical round, one to two deeper technical rounds, a practical or take-home exercise, and a founder or team conversation. Format, round count, and timeline unknown | Inferred from roles and comparable infrastructure startups; not reported. Confirm with the recruiter |
| Compensation | Base plus equity, from the postings that state a band: Engineering Lead (US) $200K-$225K, Product Engineer $150K-$225K, Customer-Facing Software Engineer (SF) $150K-$220K, Security Engineer (Switzerland) $200K-$250K. The Infrastructure Software Engineer and DevOps postings, and several others, state no band; bands are set per listing, not by region. No company-wide pay scale published | Reported from Namespace’s own Ashby job board (jobs.ashbyhq.com/namespace), read November 2026; varies by role and location |
Pay, equity, and what you can actually verify
Namespace posts a base band on several engineering roles, listed role by role in the table above. The bands are set per listing, not per region: a couple of Swiss postings carry one, other European and US roles do not. The Infrastructure Software Engineer and DevOps listings are the exception that matters here, with no band on the company’s own job board, so an infra candidate has to get the number from the recruiter rather than read across from the banded roles. There is no company-wide scale, so a European base and a New York seat will not line up. Weigh the whole package rather than a base against a base, since the equity math differs from a big-tech grant, and run the real numbers through a total-comp calculator once you have them; the usual salary-negotiation moves apply.
With no Namespace candidate accounts found, the AI-native company interview guides and the AI-startup interview difficulty index calibrate how a company this size runs its loop better than any big-company playbook. The exact rounds are the one thing no guide can give you, and that gap closes only when the first candidates write it down.
Useful next steps:
