Who Gets Hired and Onto Which Teams
Seven salaried roles. That's the entire public headcount on Zero G Talent's board for Crux, and the distribution tells candidates more about their odds than any marketing page could.
The split runs two-and-two-and-two-and-one: two seats in commercial functions (Sr. Director of Partnerships, Director of Marketing Strategy/Capital Solutions), two in operations (Business Operations Lead, Revenue Strategy & Insights Lead), one in IT, and one technical seat on the engineering side (AI Product Engineer). Go-to-market leads on one end, product and platform engineering on the other, with operations and IT threading between them. Across those seven postings, the board-aggregated band runs $118,000 to $290,000 with a median of $200,000. That median sits closer to the senior individual-contributor and director tier than to entry-level. The hiring mix skews toward people who already operate with autonomy, not toward people being trained into the role.
What the board doesn't show matters as much as what it does. There's no posted design role, no posted people-ops role, no posted finance role. That doesn't mean those teams don't exist; it means the hiring funnel is currently aimed at revenue, operations, and a single product-engineering seat. Candidates in adjacent functions shouldn't read the board as a closed door, but they should read it as a directional signal about where Crux is spending its hiring dollars this quarter.
The functional breakdown has practical consequences. Partnerships and marketing hires will work against the Capital Solutions surface of the business, the part of Crux that turns tax-credit and incentive workflows into revenue. The operations leads will sit closer to the platform and customer-success side, even if their titles don't say "CS." And the AI Product Engineer role is the clearest indicator that Crux is staffing for production AI work, not research. The title is engineer, not scientist, and the band tops out at $250,000, which is product-engineer territory rather than research-staff territory. A research engineer looking for a lab won't find one here.
The team a new hire joins depends almost entirely on which seat they're filling. A partnerships hire drops into the commercial org and inherits the Capital Solutions motion. An AI Product Engineer drops into the platform team and inherits whatever the current product surface is. Operations leads sit closer to revenue enablement than to internal corporate ops. None of these are lateral moves into a generic "Crux." They're moves into a defined lane, with a defined counterpart set, and a defined revenue line attached.
What It Pays
Crux pays competitively across the functions it's actively hiring for, and the company's own postings back that up. Even the entry-tier IC roles clear $140,000, and director-level positions open at $250,000 or more at the top of the band. The table below maps the seven roles to their posted ranges. Bands run wide because Crux hires for both staff- and director-level depth within the same requisition, and because base pay scales with location, experience, and the specific scope negotiated at offer.
| Role | Posted Band (USD/yr) | Level signal |
|---|---|---|
| Sr. Director of Partnerships | $250,000–$350,000 | Director+ |
| AI Product Engineer | $150,000–$250,000 | Staff IC |
| Director, Marketing Strategy / Capital Solutions | $180,000–$200,000 | Director |
| Business Operations Lead | $150,000–$200,000 | Senior IC / Lead |
| IT Lead | $140,000–$200,000 | Senior IC / Lead |
| Revenue Strategy & Insights Lead | $130,000–$180,000 | Senior IC |
A few patterns are worth pulling out. Director-level work pays a premium of roughly $100,000 over the senior-IC midpoint in the same functional area; the Business Operations Lead tops out at $200,000, while the Sr. Director of Partnerships opens at $250,000 for comparable scope. Technical roles track commercial roles closely: the AI Product Engineer band overlaps the Director, Marketing Strategy band on the low end and the Sr. Director of Partnerships band on the high end. That overlap suggests Crux weighs business and technical hires on a single internal leveling rubric rather than running two separate pay scales.
The one to watch: the board data is the floor, not the ceiling. The aggregated band across all seven roles sits inside the envelope of any single high-end posting, which means senior candidates with equity, signing, or bonus components layered on top of base will land above $300,000 total comp. Candidates evaluating offers should anchor on the band midpoint, then push for the upper third of the range if they bring directly relevant prior experience; Crux's posting structure leaves room for that negotiation without requiring a level change.
One caveat: these figures come from Zero G Talent's own board data, not from a third-party salary survey.
The Hiring Funnel
Crux runs a five-step hiring cycle, and from application to signed offer it runs roughly one to two months, sometimes longer. A Life Work Balance walkthrough of the standard five-step process breaks the stages into a fixed sequence: apply, screen, interview, deliberate, negotiate. Each stage has its own gate, and most candidates who fall out do so at one of the first two.
The screening step is where the funnel narrows hardest. Recruiters open every application against the minimum qualifications listed in the posting, and the first question is binary: does this candidate meet the minimum qualifications required to be successful in this job? If the answer is no, the candidate is removed. Each Crux posting spells out those minimums explicitly, so this filter runs cleanly rather than on gut feel.
Candidates who clear the bar but don't yet stand out get parked. Candidates who hit some or all of the preferred qualifications get pulled onto the "interview rank list," described in the source as the people the hiring team is most eager to get to know better because this is likely someone who will make a great employee. In practice, your application has to do more than clear the bar; it has to show the specific signals the posting calls out as preferred. Generic resumes that hedge across the wishlist rarely make the rank list.
Once interviews start, Crux's process is flexible on count but disciplined on structure. The interview phase may run zero extra rounds if the team is confident, or two, three, or four rounds if they are not. The stated preference is two interviews, framed as enough rounds to learn who a person is without dragging the cycle out. Candidates can usually self-schedule from a set of predetermined slots, which speeds the back-and-forth.
What the interview rounds actually measure is the part candidates can prepare for. The source recommends entering the loop having done mock interviews, written out answers to common questions, and reread the posting closely enough to design role-specific behavioral and technical questions. On the Crux board right now that looks like preparing system-design talking points for the AI Product Engineer loop, partnership-economics examples for the Sr. Director of Partnerships interview, and IT-operations scenarios for the IT Lead screen. The strongest candidates treat the posting as a study guide and rehearse against it, not against generic leadership prompts.
The deliberation stage is where the hiring team reviews how the interviews went and decides who moves forward. In a well-run version of the process, the team notifies candidates they are not advancing before, or at the same time, as they notify candidates who are. Candidates who are passed over here usually hear it cleanly, which is itself a signal that the earlier screening was honest rather than performative.
After deliberation, the final stage folds in background checks, reference checks, and negotiation. Negotiation is broader than salary: it covers paid time off, starting 401(k) contributions, start date, and whether the role is remote, hybrid, or fully in person. Candidates who only prep on base pay leave value on the table. Once both sides agree, the organization drafts the official acceptance letter, the candidate signs, and the process concludes at the agreed start date.
Where the Work Happens
Crux runs remote-first. Every open role there is listed as "Remote (US)," and the company treats that posture as the default, not the exception. Hiring, compensation, and team structure are built around distributed employees who live and work wherever they choose inside the United States.
Distributed workforces don't eliminate physical infrastructure; they change what the infrastructure has to do. When engineers, operators, and program staff are scattered across time zones, the buildings a company still owns have to absorb the work that can't ship through a Slack thread. For a Crux that builds hardware-adjacent systems, that means the permanent sites on the ground are not day-to-day offices. They are the places where the hands-on work happens: labs where prototypes get assembled and torn down, test cells where components run until they fail or prove out, machine shops that turn raw stock into the parts the design files specify, and integration floors where subsystems meet the larger system before anything ships.
Crux's postings hint at why those spaces exist. The AI Product Engineer role sits inside a software organization that can run almost entirely in the cloud, but the Business Operations Lead, IT Lead, and Capital Solutions roles point to a company with real physical assets to coordinate, secure, and account for. You don't staff an IT Lead at $140,000–$200,000 to manage remote laptops alone; you staff them because there are sites, networks, and systems that need someone accountable for them.
The practical effect for a candidate is a split schedule. Most weeks, you work from wherever you are, whether that's a home office, a coworking space, or a city you moved to for reasons unrelated to work. You show up to the permanent sites for the work that requires them: build cycles, qualification campaigns, integration milestones, the kind of meetings where pointing at the hardware is faster than describing it. The cadence varies by team, but the rule holds across functions.
That split has implications for how candidates should think about location. The "Remote (US)" tag on every listing is real; Crux is not quietly steering hires toward a headquarters city. But remote-first is not office-free. The labs, test cells, machine shops, and integration floors still anchor the operation, and the people who staff them, or who travel in to use them, are the ones who keep the rest of the remote workforce honest about what the hardware actually does. For candidates evaluating Crux, the honest question is not "where will I sit every day." It's "how often will I need to be at a site, and which site." Engineering-heavy positions tied to build and test cycles will pull someone in more often than a Revenue Strategy & Insights Lead focused on dashboards and quarterly planning.
Who Thrives Here
Four of the seven salaried postings, including Sr. Director of Partnerships, Director of Marketing Strategy/Capital Solutions, Business Operations Lead, and Revenue Strategy & Insights Lead, are explicitly strategy, partnerships, or operations seats rather than narrow technical specialist roles. The other three (AI Product Engineer, IT Lead, and a third ops-flavored role) carry functional engineering scope, but they all sit inside a salary band that tops out around $290,000 (with the Sr. Director of Partnerships stretching to $350,000). That mix, heavy on cross-functional leadership, lighter on deep specialists, and uniformly remote, points to a specific kind of employee: someone who operates across boundaries rather than owning a single technical domain.
Comfort with remote-first execution shows up in the geography, not just the work. Candidates who do well here are the ones who can run a project, a partner relationship, or a revenue model without needing a manager looking over their shoulder, and who can write the kind of Slack message, doc, or Loom that replaces the meeting. The Sr. Director of Partnerships role in particular rewards someone who can own a counterparty conversation end-to-end: the band tops out at $350,000, the highest of any open seat, which suggests Crux pays a premium for people who close ambiguity in the interfaces between the company and external counterparties.
The functional breadth of the openings also implies that long-tenured employees tend to be generalists with depth in one area, rather than pure specialists. A candidate who has shipped a model in production and then turned around and built the business case for it, or who can move between a SQL question and a partner negotiation in the same week, fits the shape of the org. The reverse profile, someone who wants to own a narrow technical layer for years without touching commercial decisions, will likely find the role mix thin.
Three behaviors surface from the descriptions of these openings. First, ownership of outcomes rather than deliverables: the leadership-titled seats all carry P&L-shaped responsibility (revenue, capital, partnerships, operations), not task lists. Second, willingness to work in the open: the entire org is distributed, so writing things down clearly is the default mode of collaboration, not a backup for when meetings fail. Third, comfort with a relatively flat surface area, because seven salaried roles visible on the board is a small headcount, and the people who thrive are the ones who don't need a large support structure around them to ship.
Compensation scales with scope and ambiguity rather than tenure. Candidates who do well tend to negotiate from the value of the problem they solve, not from years of experience. Candidates who struggle are usually the ones looking for a clearly defined ladder to climb; Crux's current shape, with a leadership-heavy mix and a small number of seats, rewards problem-solvers over process-followers.
For someone evaluating an offer, the practical question is whether their last few roles look more like the Sr. Director of Partnerships seat or more like a single-track IC position. The board data suggests the former profile stays and grows. The latter tends to plateau or leave within a year or two as the available scope runs out.
Working in frontier tech? Zero G Talent tracks the openings: see every open Crux role, browse frontier tech jobs, the companies hiring, and the people building the field.