The Only Map Is Six Job Postings
Passage Labs publishes no org chart. No former employee has posted a detailed breakdown of its operating cadence on Glassdoor, Blind, or Levels.fyi. The public record amounts to six job postings on Zero G Talent's board — the entire paper trail for how the company structures work.
Those six roles reveal a team distributed across three locations: a headquarters site (listed as "Passage HQ" on four roles), Toronto (two engineering roles), and India (a Global Growth Lead). Functions represented: finance (Director of Finance, Senior Accountant/Finance Manager), data (Director of Data, Senior Analytics Engineer), marketing (Senior Marketing Engineer), and growth (Global Growth Lead). The Director of Finance role shows an hourly range of $8–12, roughly minimum wage, a figure that reads more like a contractor rate than a full-time executive salary, though the posting doesn't clarify employment type.
From this skeleton you can infer the operating shape. Finance and data leadership sit at HQ, suggesting centralized control over capital and metrics. Engineering talent is hired in Toronto, a market where senior AI/ML engineers cost less than in the Bay Area but share Eastern time. The Global Growth Lead in India points to an international go-to-market motion, possibly targeting emerging markets or leveraging cost-effective acquisition. No product, design, research, or operations roles appear — either those functions don't exist yet, they're filled, or they're hired through channels not captured here.
What the board data shows: six live roles, three geographies, four functions. Everything else about pace, structure, and decision rights is inference. Treat the interview loop as your primary diligence — ask how the last three product decisions were made, who approved them, and how long it took. The answer will tell you more than any guide can.
How Work Actually Gets Done
Decision-making flow is not documented. The research corpus contains no founder interviews, internal memos, process write-ups, or employee accounts describing how a feature moves from idea to ship. The PACE framework cited in some summaries (Plan, Analyze, Construct, Execute) is a generic data-analysis methodology from a 2024 blog post, not a Passage Labs operating system. The WARN notices and biotech layoff tracker entries that surface in searches share only a filename coincidence with "Passage."
What this means for a candidate: you are joining a company that operates below the public radar. The absence of leaked process docs, public postmortems, or conference talks isn't inherently negative — many early-stage teams move fast precisely because they don't document externally, but it does mean you cannot verify claims about autonomy, review cycles, or founder accessibility before you talk to them. The postings confirm the team is hiring for senior individual-contributor and lead roles across core functions, which typically signals a shift from founder-led execution to functional ownership. Whether that shift comes with written rituals (weekly planning, OKR cycles, design reviews) or remains informal is an open question you should ask in the first conversation.
Values and Operating Principles: Implicit, Inferred from Hiring Pattern
Passage Labs has not published a formal, numbered values framework comparable to Amazon's 16 Leadership Principles — the internal operating system Amazon codified, interviews against, and uses to run meetings, make promotion decisions, and veto hires via its Bar Raiser process. At Amazon, every interviewer is assigned two to three principles to probe, submits scored feedback mapped to those principles, and the hiring committee debates whether the candidate "demonstrates the Leadership Principles we need at this level." A single Bar Raiser veto can kill an offer even after a unanimous hire vote.
The company's self-descriptions and its hiring pattern point to a tighter, less codified culture. Passage Labs describes itself as "a team of enterprise integrators, innovation engineers, and data scientists with decades of experience future-proofing brands and companies" (passage.xyz) and "a venture-backed product lab on a mission to bridge the gap between the world's leading companies and emerging technologies" founded by "serial entrepreneurs in Commercial AI" who "launched popular products in Blockchain (GYSR.io, PassageProtocol.com) and Data (Fuze, Drillbit, Puller AI)" (pingojo.com). Crunchbase lists founders Meral Arik and Zac Choi.
The job board reinforces a flat structure. Open roles cluster around senior, high-leverage positions — Director of Finance, Director of Data, Senior Marketing Engineer, Senior Analytics Engineer, Global Growth Lead, Senior Accountant/Finance Manager, suggesting individual contributors carry broad scope. A "Director of Data" at a small company isn't managing a hierarchy; they're building the data stack, defining the metrics, and likely answering to the founders directly. Same for a "Global Growth Lead" based in India: that role implies autonomy to run experiments across markets without layers of approval. The compensation signal for the Director of Finance role ($8–12/hour) appears anomalous for a director-level title and may reflect a fractional or contract structure, but the title itself signals that finance strategy sits close to the founding team.
Three behaviors emerge from the hiring pattern:
Founder-proximate decision-making (inferred). With a team small enough that directors report to founders, the loop between insight and action is short. This mirrors Amazon's "Bias for Action" and "Dive Deep" in outcome (speed and detail orientation) but without the fractal interview rubric Amazon uses to certify those traits before day one. At Passage Labs, you demonstrate them by doing them.
Ownership as table stakes (inferred). The roles posted, particularly the senior engineering and analytics positions, require end-to-end responsibility. A Senior Marketing Engineer doesn't hand off tracking to an analytics team; they build the instrumentation, analyze the output, and iterate the campaign. A Senior Analytics Engineer doesn't wait for tickets; they define the data model that product and growth teams rely on. This maps to Amazon's "Ownership" principle ("Leaders act on behalf of the entire company, not just their team"), but at Passage Labs it's a structural requirement, not a cultural aspiration.
Rapid iteration over perfection (inferred). The Global Growth Lead role, the marketing engineering seat, and the analytics engineering role all imply a test-learn-ship cycle. There is no separate "process team" to optimize workflow; the people building the product also refine how it gets built. This aligns with Amazon's "Invent and Simplify" and "Frugality" (constraints breed resourcefulness), but again, it's structural necessity, not a principle you cite in a meeting.
The absence of a public values framework creates both signal and risk. Candidates who need explicit cultural guardrails — "we do X because Principle Y says so", will find less of that here. Candidates who operate by internal compass and want minimal friction between idea and execution will find more. The trade-off: without codified principles, cultural consistency relies entirely on the founders' daily behavior and hiring judgment. Amazon solves this at scale with a 16-point rubric, Bar Raisers, and 25-question interview loops. Passage Labs solves it by staying small enough that the founders can still interview every hire and model the culture directly.
No Glassdoor or Blind corpus for Passage Labs surfaces in the research to contradict or refine this picture. The first-party board data shows a company hiring for leverage roles in a flat structure. The operating system is implicit, enforced by proximity, and legible mainly through who gets hired and what they're trusted to run.
What the Hiring Bar Selects For
The language on a recent product-engineering posting makes the velocity expectation explicit: "Comfort with rapidly defining and executing practical, iterative development cycles are a must." The same listing frames the ideal candidate as someone with "a demonstrated history of effective and efficient product engineering" and "solid experience building production backend systems." Pedigree is not the proxy; shipped, operable systems are. The posting goes on to list a bucket of preferred qualifications, each a concrete technical capability, and treats the collection as a menu, not a checklist. That structure mirrors how the team actually works: pick the tools that move the product forward, discard the rest.
The two senior engineering roles in Toronto, Marketing Engineer and Analytics Engineer, both titled "Senior", suggest Passage Labs is not hiring juniors to be mentored; it is hiring peers who can own a domain immediately. The Global Growth Lead role in India, listed alongside HQ finance and data leadership, indicates the bar includes cross-border operational fluency. A candidate who needs hand-holding on timezone coordination or regulatory nuance will not clear it.
Passage Labs' own site describes its service model: "we identify and present qualified candidates for your review and selection" and "administratively manages all placed personnel, including employment, payroll, and compliance" (passagelabs.in). If the internal hiring bar mirrors the external filter the company applies for clients, then the traits they select for (rapid iteration comfort, production backend depth, ownership of ambiguous scope) are the same traits they vet for when placing engineers elsewhere. The dogfood loop is tight.
Public interview reviews on Glassdoor and Indeed surface under "Passage Health" and "Passages, Inc.", distinct entities from Passage Labs (passagelabs.in). Those reviews describe multi-round processes with technical screens and behavioral questions, but they cannot be attributed to this company with confidence. The research simply does not contain first-hand candidate accounts for Passage Labs proper. What remains is the board, the posting language, and the organizational shape those imply.
The hiring signals framework built by Candidate Labs, which tracks signals like FIRST_HIRE_IN_FUNCTION, LEADERSHIP_BUILD, and GEO_EXPANSION across 112 company boards, would flag Passage Labs' current board for several of those simultaneously. A board showing first hires in marketing engineering, analytics engineering, global growth, and data leadership, plus director-level finance and data roles, is a board in LEADERSHIP_BUILD and GEO_EXPANSION at the same time. Companies in that mode do not hire for potential; they hire for proven capacity to stand up a function and make it reliable within weeks.
The practical upshot: Passage Labs selects for engineers and operators who have already built the thing the company needs next, who can define the iteration cycle without a spec handed down, and who treat compliance, payroll, and cross-border employment not as someone else's problem but as constraints they design around. The bar is not high in the abstract — it is specific to the next six months of organizational construction. Candidates who have only ever worked inside mature, specialized teams rarely clear it. Candidates who have founded, early-joined, or turned around a function from zero do.
The Review Vacuum
Public review data for Passage Labs specifically is thin. Searches of Glassdoor and comparable platforms surface reviews for companies with similar names (Passage Bio, a Philadelphia-based biotech, and Passages Malibu, a treatment center) but no dedicated Passage Labs employer profile with verified employee feedback appears in the research. A Glassdoor entry titled "Passage Bio - Exciting company" carries a review from a senior scientist and former employee in Philadelphia describing a "toxic environment run by people who are not lab based," while a separate "Passages Malibu" listing invites candidates "looking for just a job." Neither reflects Passage Labs, the Toronto- and India-hiring organization posting roles there.
This absence is not unusual for early-stage, founder-driven companies operating below the 50-employee threshold where review platforms typically activate employer pages. The live job board shows active requisitions across multiple functions and geographies. The spread — finance, data, marketing, analytics, growth, suggests a team building out commercial and operational infrastructure in parallel, a pattern consistent with a venture-backed startup moving from product validation toward scale.
Without first-hand review corpus, candidates must triangulate through other signals. The job titles and locations imply a distributed model with engineering and analytics concentrated in Toronto, finance and data leadership at headquarters, and a growth function in India. The presence of both "Director of Finance" and "Senior Accountant/Finance Manager" simultaneously suggests either a layered finance build-out or a replacement search.
Prospective hires should treat the review vacuum as a diligence item, not a red flag. Ask hiring managers directly about team size, turnover in the last 12 months, and how performance feedback works. Request conversations with potential peers — not just the founder, to gauge day-to-day cadence and decision latency. Check LinkedIn for tenure patterns: multiple sub-one-year stints in the same function can signal churn even when Glassdoor is silent. And distinguish Passage Labs from the similarly named entities that do have review footprints; the biotech and rehab reviews describe cultures and management structures that have no bearing on this organization.
Who Thrives Here and Who Burns Out
The research available on Passage Labs specifically contains zero employee voice data. That data shows six recent postings across finance, data, growth, and engineering functions in at least two countries. That footprint, combined with the operating model described above, lets us sketch a provisional profile. Treat what follows as inference from structure and hiring signals, not documented testimony.
Who tends to thrive (inferred)
Owners who need little scaffolding. The board roles are senior, directors and leads, not junior individual contributors. A Director of Finance and a Director of Data at HQ imply the founders delegate whole functions, not tasks. People who have built a finance close, a data stack, or a growth engine from zero and can operate without a playbook will fit.
Cross-border operators. Toronto and India postings alongside HQ roles mean the team already works across time zones. Engineers and marketers who default to async communication, write decisions down, and don't wait for a meeting to unblock themselves will outpace peers who need synchronous alignment.
Generalists with a spike. "Senior Marketing Engineer" and "Senior Analytics Engineer" are hybrid titles. Passage appears to hire people who can write SQL, instrument funnels, and ship frontend experiments, or model revenue, build dashboards, and brief the board. Specialists who refuse to touch the adjacent discipline will frustrate the pace.
Founder-adjacent communicators. "Decisions made close to the founders" means the loop is short. Candidates who can give a 30-second verbal update, a one-pager, and a raw notebook in the same afternoon, and know which the founder actually reads, reduce friction. People who over-polish internal artifacts burn cycles.
Who burns out (inferred)
Process-dependent builders. If you need a Jira ticket, a design review, a security sign-off, and a staging deploy window before you push a config change, the velocity will feel chaotic, not fast. The board shows no DevOps, SRE, or PM roles — those functions are likely absorbed by the engineers and leads themselves.
Boundary rigidists. High-velocity, founder-proximate teams often blur evenings and weekends when a launch slips. General burnout literature notes that "inability to set healthy work boundaries" drives exhaustion in lab settings; the same dynamic applies in early-stage tech. Candidates who treat 6 p.m. as a hard stop will either under-deliver or resent the team.
Status seekers. Titles at Passage are functional (Director of Data, Global Growth Lead), not hierarchical. There is no VP layer to climb into. People who measure progress by org-chart steps will stall; the only lever is scope expansion, which the founders control directly.
Silent strugglers. CDC-sourced material emphasizes burnout "is not just a personal problem for people to solve alone" and that stigma keeps it underreported. In a small, high-trust team, the fastest way to spiral is to hide overload. The culture rewards raising a flag early, "I'm at capacity on the India launch, need help on the analytics spec", not heroics that collapse at 2 a.m.
The tension to watch
The operating model inferred from hiring rewards ownership and rapid iteration. The board data confirms senior, cross-functional hiring. But zero employee voice data exists to confirm whether the support structures (mentorship, sabbaticals, workload caps) that the burnout countermeasures literature prescribes are actually present. Until Passage publishes an engagement survey or former employees speak on record, candidates should ask directly in the final round: "Walk me through the last time someone on the team said they were at capacity. What changed the next week?" That response reveals more than any job description, and more than these six postings ever could.
Working in frontier tech? Zero G Talent tracks the openings: see every open Passage Labs role, browse frontier tech jobs, the companies hiring, and the people building the field.