AuthZed weighs this skill as heavily as your resume

Three Openings, One Filter

AuthZed has posted three senior roles, two engineering and one developer advocacy, after securing a $12 million Series A. The move reflects a tightening labor market for authorization infrastructure: the engineers who understand distributed permissions at scale are the same ones building them, and they rarely leave. At 31 people, AuthZed needs hires who can operate inside SpiceDB, its open-source permissions database, without a ramp-up period on the underlying Zanzibar model.

The roles split across two engineering tracks and one product-facing track. The Senior Software Engineer position, Y Combinator's data shows it listed at $150,000–$190,000, carries the "Database Engineer" descriptor in its detailed posting. That framing is deliberate: the hire will work on SpiceDB's core, including query planning, execution correctness, materialized views, incremental view maintenance, indexing, partitioning, and caching, across both the open-source and enterprise distributions. The stack is Go, TypeScript, Kubernetes operators, CockroachDB, Cloud Spanner, and PostgreSQL, with Prometheus, Thanos, and ArgoCD for observability and deployment.

The Sr. Site Reliability Engineer, Y Combinator reported at $150,000–$195,000, shares the same remote footprint (United States and Canada) and experience floor (five-plus years). While the public posting is lighter on detail, the technology stack and the company's reliance on managed Kubernetes, Pulumi, and multi-database topologies imply the role owns the reliability surface for SpiceDB Cloud — the managed service layer that turns the open-source engine into a planet-scale authorization backend. That surface includes the control plane, the data plane, and the upgrade paths between them.

The Sr. Developer Advocate, Y Combinator's figures put it at $140,000–$170,000 with a three-year experience minimum, is the only role restricted to U.S.-based candidates. It lives in the product organization, not engineering, and its mandate is community growth: helping developers model permissions in SpiceDB, producing integration examples, and closing the gap between Zanzibar's academic paper and a team's first production schema. AuthZed's founders have said publicly that the hardest part of adoption isn't the database — it's the modeling step where customers realize their access-control requirements don't map cleanly to role-based or attribute-based systems. The advocate role exists to shorten that realization curve.

All three positions are full-time remote. The company has operated that way since its 2020 founding, with employees distributed across the United States and Europe. The interview process runs roughly four hours total, spread over several days, verbal-first, with no take-home assignments — a structure that favors candidates who can articulate distributed-systems trade-offs in conversation rather than in a weekend coding exercise.

The common thread across the openings is SpiceDB itself. Each hire is expected to contribute to the open-source project, not just the commercial wrapper. That expectation filters for engineers who have already operated in open-core environments and understand the friction between community velocity and enterprise stability. It also means the screening criteria weigh public contribution history as heavily as any resume bullet.

What Gets You Past the Screen

AuthZed publishes its interview structure in plain language — a rarity for a 31-person, fully remote startup, and the signal is consistent across its engineering blog and the three open roles: candidates advance when they demonstrate ownership of hard technical problems in distributed systems, a track record of shipping in open-source ecosystems, and the written-communication discipline that remote-first work demands.

The company structures its engineering loop around three panels, each filtering for a different dimension. The Background Panel, a one-hour conversation with two engineers, walks the resume chronologically from the most recent role. Interviewers aren't checking boxes; they want the "why" behind every major architectural choice — database selection, messaging queue, consistency model, and they press on the trade-offs you rejected. "We're going to poke at the edges of your decisions," the team writes, "not to trip you up, but to see if you've considered the trade-offs inherent in engineering." Candidates who reach the next stage come prepared with two to three projects they can dissect from ideation through production, using a STAR-style frame but dialing the technical volume up: the bottleneck you hit, the distributed-systems failure you debugged, the specific change that fixed it.

The Technical Skills Panel evaluates practical system-building, not algorithmic puzzles. AuthZed explicitly disavows "abstract LeetCode grind" in favor of exercises that mirror the authorization infrastructure it ships. A candidate who has contributed to SpiceDB enters with a visible proof of work that no take-home assignment can replicate.

The Culture Panel tests the attributes that keep a 31-person, trans-Atlantic team aligned without a shared office. High Agency & Ownership means spotting a gap, scoping a fix, and driving it to done without a perfect spec. Pragmatic Perfectionism means shipping "good enough for the business today" while knowing where the technical debt lives. Exceptional Communicators write design docs that a colleague in Berlin can execute on without a synchronous call. AuthZed's blog states it directly: "Our culture is written-first. Whether it's a design doc or a panel interview, your ability to explain complex technical issues in plain English is key."

For the non-engineering operations role, the same filters apply — remote collaboration fluency, comfort with async decision-making, and a portfolio (or public writing) that shows you've operated at the intersection of developer-facing product and high-velocity startup execution. The company's Y Combinator profile frames its strategic pillars as "fortify our reputation as authorization experts, accelerate our open-source community growth, and scale revenue with robust enterprise products." Candidates who map their experience to those three vectors — deep authZ knowledge, community contributions, enterprise-grade delivery, are the ones who clear the screen.

Inside the Panels

AuthZed has published detailed breakdowns of each stage on its blog, giving applicants unusual transparency into what happens after a resume clears the initial review.

Background Panel: Past Decisions Under a Microscope

The first substantive conversation is the Background Panel, which AuthZed describes as "a deep dive into your past experience and technical decision-making." This is not a behavioral interview in the generic sense. Interviewers want to understand the architecture you worked on, the constraints you operated under, and the trade-offs you made — and why you rejected the alternatives. The company advises candidates to "treat your career history like a technical doc" and be ready to whiteboard past systems verbally or via screen share. Candidates should prepare two to three projects that demonstrate technical depth and ownership, using a structure like STAR (Situation, Task, Action, Result) but with the "technical volume dialed up." Critically, AuthZed wants to hear about the mess: "Engineering is rarely perfect. We value candidates who can candidly discuss what went wrong and what they learned." The panel evaluates whether you can articulate the reasoning behind major decisions, recall what you didn't choose and why, and own the outcomes — good and bad.

Technical Skills Panel: Building and Reasoning in Real Time

The second pillar shifts from retrospective to prospective. As AuthZed frames it: "If the Background Panel is about where you've been, this session is about where you can go. We want to see how you approach new, ambiguous problems in real-time." The panel is intentionally open-ended. Interviewers present a scenario — often drawn from AuthZed's own domain of distributed authorization systems, and expect the candidate to drive the conversation, thinking out loud while navigating ambiguity.

The rise of AI coding agents has changed what this panel tests. "With the rise of AI coding agents, the 'cost' of generating syntax has dropped to near zero. Anyone can prompt an LLM to write a boilerplate function," the company notes. Syntax is no longer the differentiator. Instead, the panel probes for architectural intuition: high-level trade-offs, reasoning under ambiguous requirements, accounting for real-world constraints like latency, cost, and failure modes, and relating technical solutions to product and business context. Candidates are advised to strengthen core fundamentals, study real systems (including open-source projects), practice thinking out loud, and get comfortable with ambiguity. "Drive The Conversation: Don't wait for us to ask questions. Remember, you are the lead during the interview!"

Culture Panel: Collaboration, Ownership, and Team Dynamics

The third pillar is the Culture Panel, described as "a conversation focused on how you collaborate, your drive for ownership, and how you'll add to our team dynamics." This is where AuthZed evaluates whether a candidate thrives in its specific environment: fully remote, high-velocity, open-source-centric, and built around distributed systems. The panel looks for signals of proactive communication, comfort with asynchronous workflows, and a track record of taking ownership beyond assigned tickets. While the company hasn't published a granular rubric for this panel, its public writing emphasizes that "we are looking for engineers who thrive in the intersection of distributed systems, open source, and high velocity startup life" and "strong engineers who can thrive in our culture." The Culture Panel is the filter for whether a technically capable candidate will actually succeed in AuthZed's day-to-day operating model.

Progression and Signals

The three panels run sequentially for candidates who advance. A resume screen precedes them, as AuthZed's job posts stress remote collaboration experience and open-source contributions as baseline qualifiers, but the published material focuses on the panel structure itself. Candidates who reach the Background Panel have already cleared a paper filter; those who reach the Technical Skills Panel have demonstrated sufficient depth in past work; those who reach the Culture Panel have proven they can reason through novel systems problems. The pipeline is designed to be mutually reinforcing: technical depth validated by the Background Panel, problem-solving approach validated by the Technical Skills Panel, and cultural alignment validated by the Culture Panel. AuthZed's transparency about this structure, including explicit preparation guidance for each stage, signals that the company optimizes for signal over surprise, and expects candidates to meet it with comparable rigor.

Remote-First: The Daily Reality

AuthZed has operated as a fully remote company since its founding in 2020, with a 31-person team distributed across the U.S., Canada, and Europe. The structure is not a pandemic adaptation — it is the founding condition. The company's culture page reduces its operating philosophy to a single sentence: "Trust each other." That trust manifests in three explicit values: agency, collaboration, and open-mindedness. Agency means every employee has the "capability, freedom, and confidence to bring about changes to our business and product." Collaboration means success is multidimensional and no single person owns all the expertise. Open-mindedness means the team tests assumptions and questions biases rather than defending them.

These values shape how AuthZed hires. The interview process screens for candidates who can operate without the guardrails of a physical office. The company's BuiltIn profile describes an "engineering-first identity and deep, specialized authorization domain, including expectations of technical fluency even in non-engineering roles." That bar is deliberate. In a remote, async environment, a product manager who cannot read SpiceDB code or a marketer who cannot trace a permission check through the Zanzibar paper becomes a bottleneck. The culture page warns that "cultural misalignment" often appears when generalists encounter this technical density.

Communication runs on writing. Daily stand-ups happen in a shared document, not a video call. Decision records are written, not spoken. The BuiltIn profile notes that "complex topics routinely shift to in-depth video calls to dive deeply and reach better solutions," but the default is async. Meetings are "intentional, minimal," a phrase that appears in both the culture and workplace-perception pages. Candidates who need synchronous presence to unblock work will struggle. The company explicitly flags "heavy async writing" as a defining tradeoff: decisions and code are debated in public, so clarity, self-direction, and resilience matter.

The remote model also dictates the on-call rhythm. AuthZed runs an "operate what you build" rotation tied to its open-source SpiceDB project. Engineers own their code in production, which means pages can arrive at any hour across three continental time zones. The workplace-perception page acknowledges that "operating security-critical infrastructure with ambitious reliability goals entails on-call rotations and high ownership" and that "a small, early-stage team plus OSS and customer demands can increase context switching and intensity." The company says it works to keep tension productive and prevent burnout, but the burden is real and the hiring filter accounts for it.

Twice a year, the team meets in person for onsites. The rest of the year, the company covers coworking space for employees who want it. But the daily reality is distributed. AuthZed's own growth — sevenfold since 2021, per a founder's blog post, suggests the model compounds.

For candidates, the signal is clear: demonstrate that you have shipped in a distributed, async, open-source environment. Show public writing, such as RFCs, design docs, blog posts, and GitHub discussions. Prove you can own a component end-to-end without a manager checking in. The screening pipeline rewards evidence of those behaviors over credentials. A resume that lists "remote work experience" without artifacts loses to one that links to a merged SpiceDB PR or a decision record you authored for a distributed team.

Compensation: What the Market Shows

AuthZed publishes salary bands for its three open roles on Y Combinator and its Ashby portal: Senior Software Engineer $150K–$190K, Sr. Site Reliability Engineer $150K–$195K, Sr. Developer Advocate $140K–$170K. Early-stage infrastructure startups often benchmark privately against peers and adjust offers case by case based on a candidate's experience, location, and the equity they're willing to trade for cash. We can triangulate from the broader market for authorization and distributed-systems talent in 2025–2026.

The most relevant comparable data comes from the Stott and May 2025 U.S. Software Engineering Salary Guide, which lists market bands for related titles. A Senior Software Engineer at a venture-backed SaaS or infrastructure company typically commands $150,000–$250,000 base, with a median around $200,000. Product Engineers sit in a slightly tighter $150,000–$200,000 band. Forward Deployment Engineers range $150,000–$250,000.

These figures align with broader aggregates: Glassdoor's 712,000-submission dataset (March 2026) puts the average U.S. software engineer at $148,764 base, while Built In reports $139,749 base and $159,212 total compensation when bonuses are included. According to DataGod, the Bureau of Labor Statistics' OEWS 2024 median of $130,160 reflects the full industry spectrum, including non-tech employers, so it understates what a specialized auth startup pays.

Equity grants at this stage typically vest over four years with a one-year cliff. Private-company options require a strike-price purchase, and the value only materializes at a liquidity event. Candidates should ask for the current 409A valuation, the total fully diluted share count, and the most recent preferred price per share to model upside.

Benefits follow the remote-first playbook AuthZed's structure demands. The company's careers page and public job posts emphasize fully distributed work. Health, dental, and vision coverage is standard; employer-sponsored plans typically save substantially versus individual-market premiums. A 401(k) match adds compounding value over a career horizon. Professional development budgets, equipment stipends, and generous PTO policies appear in most competing offers at this tier.

One variable that matters acutely for a remote team: location-based versus location-independent pay. Two camps exist. GitLab, Zapier, Automattic, and many startups pay the same cash compensation regardless of where an employee lives. Traditional giants adjust bands 10%–30% downward for lower-cost metros. AuthZed has not stated its policy publicly. Candidates should clarify this before final-round negotiations, because a $200,000 offer in San Francisco versus the same $200,000 in Raleigh represents a significant real-income delta after housing and state taxes; Texas, Florida, Washington, Tennessee, and Nevada have zero state income tax.

The bottom line: AuthZed's offer will likely land in the published ranges for each role, with equity grants that reflect a Series A cap table and a benefits package built for distributed work. Candidates who treat the equity as a negotiable variable, asking for refresh grants, accelerated vesting triggers, or a higher percentage in exchange for a modest base reduction, tend to move the needle more than those who focus solely on the cash number. The market data says total compensation, not base salary, is the figure that separates a market-rate offer from a top-decile one.

Market Context: Where the Roles Sit

No public candidate reviews, forum threads, or social-media discussions specific to AuthZed's current hiring push appear in the available record. That silence is itself a signal: at 31 people post-Series A, AuthZed is still small enough that its hiring cycles don't generate the volume of public feedback that larger, consumer-facing startups do.

What we can observe is the market context those three roles enter. The authorization infrastructure niche is tightening. AuthZed's job listings explicitly cite the scale target: fine-grained permissions that scale to billions of objects for AI agent platforms and multi-tenant cloud services.

Compensation signals are public and competitive. The Senior Software Engineer and Sr. Site Reliability Engineer roles both post $150K–$190K/195K base ranges for five-plus years' experience; the Sr. Developer Advocate lists $140K–$170K for three-plus years.

The remote-first structure shapes the candidate pool. AuthZed describes itself as "fully remote with employees across the US and Europe" and emphasizes a "software-driven culture" where even sales understands the tech. That filters for engineers who have shipped production systems in distributed teams and who can demonstrate open-source fluency; SpiceDB is the company's primary calling card, and the Developer Advocate role explicitly exists to grow that community. Candidates without a track record of async collaboration, public code contributions, or technical writing will struggle to signal fit.

Market timing matters. The broader tech labor market has softened from 2021–2022 peaks. Candidates who might have defaulted to FAANG or late-stage unicorns are now evaluating Series A infra plays more seriously. AuthZed's pitch, featuring an open-source standard, $12M runway, 31-person team, and biannual on-sites, lands in that window.

The net assessment: AuthZed is fishing in a specialized, growing pond with competitive bait. The lack of public candidate reaction data means the company's hiring signal travels through private networks. For applicants, that means the resume screen is likely the only anonymous step; after that, reputation in the authorization ecosystem carries more weight than a cover letter. The engineers who stay are the ones who built the thing.

Working in AI? Zero G Talent tracks the openings: see every open Databricks role, browse AI jobs, openings at Anthropic and Harvey AI, and the people building the field.