The Filter: What Middesk's Screen Catches
Middesk, a San Francisco business identity infrastructure company founded by Kurt Ruppel and Kyle Mack, has 12 open roles across engineering, go-to-market, and operations: Data Scientist, Forward Deployed Engineer, Lead Data Scientist, two Enterprise Account Executive positions, Software Engineer, Account Manager for Enterprise Banking, Account Manager for Mid-Market, Account Executive, Partner Manager, Solutions Architect, and Software Engineer, Infrastructure. Salary bands run $145K–$340K Zero G Talent's board data shows with a median of $230K according to Zero G Talent. The roles are the frame. The picture is the filter.
A frontier-tech company hiring at speed faces a problem that looks like a luxury: too many applicants, too little signal. The screen becomes the product. This article examines Middesk's documented interview process, reported candidate outcomes, and live role slate as a case study in how a well-capitalized, early-stage team filters for the profile it cannot afford to miss, revealing what frontier-tech companies now prioritize when a bad hire threatens the roadmap. Evidence comes from candidate-reported interview guides (Dataford, Prachub, updated August–October 2026) and Zero G Talent's board data. Where research is thin, notably on go-to-market interview mechanics versus engineering, we say so rather than extrapolate.
Middesk's screen runs three rounds over three to five weeks: a recruiter fit call, a CoderPad pair-programming session, then a multi-stage panel covering system design, product collaboration, and conversations with engineering leadership. The topic map is specific: Kubernetes, infrastructure engineering, developer experience, observability, security engineering, DevSecOps, Terraform, and reliability or high-availability patterns. But the screen is not a knowledge check. Candidates report practical coding and data-handling tasks, prioritizing across projects, JSON parsing and validation, rather than algorithm puzzles. Later rounds ask for system designs like tracking business identity verification status across multiple data sources. Collaboration discussions probe how you balance technical debt against speed given business constraints, and how you work with non-technical stakeholders.
The through-line is a concept Middesk calls "Velocity" — defined internally not as shipping speed but as the rate at which the team effects realized value. Engineering culture documentation emphasizes self-motivated problem solvers willing to tackle messy, real-world data challenges. Preparation guides stress a "customer-first engineering mindset." Candidates who struggle share a common failure mode: they demonstrate the how of coding without the why of the business problem. Candidates are advised to think aloud, ask clarifying questions, be candid about gaps, review past work for trade-offs, write tests unprompted, and treat the interviewer as a collaborator; these counter-moves all point to the same filter: operational judgment over raw facility.
Why Business Identity Infrastructure Demands This Hiring
Middesk exists because business onboarding is still stuck in the analog era. When Mack and Ruppel founded the company in 2019, they were fixing a bottleneck they had lived. Mack managed solution consulting at Checkr; Ruppel engineered at Zendesk before joining Checkr as an engineering manager. Both saw the same problem: banks, lenders, and fintechs could verify a person in seconds but needed weeks to verify a business. The downstream effects (stalled revenue, compliance gaps, fraud losses) were what Mack described to TechCrunch in 2022.
The product is not a data reseller. It is an identity-as-a-service platform that plugs directly into 400-plus government and authoritative sources — every Secretary of State, the IRS, USPS, OFAC, and hundreds of state, county, and city agencies. That direct-to-source model is the differentiator. Legacy providers like Dun & Bradstreet and LexisNexis aggregate; Middesk connects. The result: 7 million businesses verified annually, one in ten U.S. businesses verified within 90 days of formation, and over $100 billion in revenue flows powered through the platform.
The customer list reads like a fintech index. Plaid, Affirm, Bluevine, Pipe, Novo, Rippling: more than 500 brands across banking, lending, payroll, insurance, and marketplaces. Chris Campano, risk lead at Plaid, said: "When a customer signs up for Plaid, they want to start building on our APIs right away. Middesk has been a critical partner enabling us to quickly and seamlessly onboard new customers." Rho, a banking platform, went from 300–400 applications a month across five analysts to 2,000-plus without proportional hiring after integrating Middesk. Address validation accuracy jumped from 70 percent to nearly 100 percent. Manual proof-of-activation reviews disappeared.
Investors saw the same signal. The $57 million Series B in June 2022 was co-led by Insight Partners and Canapi Ventures, with Sequoia, Accel, and Gaingels following on. Total capital raised: $77 million. Walker Forehand at Canapi called Middesk "the new standard for small business digital identity and trust — orders of magnitude better than legacy competitors." Jeff Horing at Insight Partners framed it as infrastructure for a structural shift: "As more transactions and business-onboarding move online, financial institutions face increasing fraud risk. Simultaneously, business customers demand a frictionless onboarding experience." The a16z fintech infrastructure thesis lists Middesk alongside Alloy, Plaid, Sardine, and Synapse as a key enabler of onboarding and account opening, mission-critical infrastructure where downtime would materially disrupt customers.
That mission criticality shapes the hiring. The 12 open roles cluster around three vectors: data intelligence, customer-facing deployment, and platform depth. Two data science roles feed the purpose-built ML models that detect risk patterns and the AI agents that investigate ownership networks across the 400-plus source graph. The Forward Deployed Engineer and Solutions Architect roles exist because Middesk sits inside regulated workflows (banks, credit unions, lenders) where implementation is compliance work, not just integration. The Software Engineer, Infrastructure and general Software Engineer roles scale the autonomous workflows that resolve, not just score, so analysts handle exceptions instead of every application.
On the go-to-market side, the split is deliberate. Two Enterprise Account Executive roles (with distinct compensation structures), an Account Executive, an Account Manager for Enterprise Banking, and an Account Manager for Mid-Market reflect a sales motion that separates net-new logo acquisition from expansion inside regulated accounts where the sales cycle is a compliance review. The Partner Manager role maps to the Backbase integration and the DocuSign App Center listing: channel partnerships that embed Middesk inside existing banking stacks.
Founders Kyle Mack and Kurt Ruppel have stated the goal plainly: "build the infrastructure to enable instant identity-related decisions between all businesses and counterparties." International expansion (Canada, Europe, APAC through the same Verify integration) and the new lien search and filing product for underwriters extend that infrastructure upward into credit assessment and downward into payroll tax registration across all 50 states. Every open role serves one of those vectors. The hiring is not exploratory. It is execution against a roadmap the capital, the customers, and the competitive position all validate.
What Gets You Past the Screen
Middesk's screen filters for one thing above all: whether you can turn messy, real-world business identity problems into reliable systems without losing the plot. The company calls this "Velocity", not shipping speed, but the rate at which you effect realized value. That definition shapes every round.
Engineering candidates face a three-stage loop over three to five weeks: recruiter screen, a pair-programming session on CoderPad, then a virtual or onsite panel on those topics, followed by a conversation with engineering leadership. The technical screen skips algorithmic puzzles. Instead you work through backend scenarios: designing a database schema for business verification, taking a feature from schema to REST endpoint, handling JSON parsing and validation against external data sources, reasoning through TypeORM or similar ORM trade-offs in production. Interviewers watch for clean, testable code and a clear thought process. Writing tests unprompted signals operational maturity. Candidates who obsess over syntax while ignoring the business "why" tend to stall.
Topic frequency data makes the priority stack explicit. Kubernetes appears in every reported engineering interview. Infrastructure engineering (97%), observability (92%), DevSecOps (86%), Terraform (84%), and reliability engineering (81%) follow. This is not a frontend shop. Depth in distributed-systems fundamentals (high availability, failure-mode reasoning, observability design) carries more weight than framework trivia. Language is flexible; proficiency and readability are not.
Go-to-market roles run a parallel filter. Sales outreach planning and B2B sales strategy each hit 100% and 95% coverage respectively. SDR execution (91%) and outbound prospecting (87%) round out the core. The screen tests whether you can build and run a pipeline, not just close inbound. Enterprise account executive candidates should expect to walk through a full deal cycle (qualification, multi-threaded stakeholder mapping, procurement navigation) with the same rigor engineers apply to system design. Partner managers and solutions architects get evaluated on technical fluency alongside commercial instinct; the solutions architect role in particular sits at the intersection of infrastructure knowledge and customer-facing translation.
Across both tracks, communication is the silent gate. Internal guidance flags it as a key signal: candidates who struggle to articulate trade-offs, ask clarifying questions, or engage collaboratively rarely advance, even with strong code or quota history. Behavioral rounds judge decisions and their costs. "Describe a time you collaborated with a non-technical stakeholder" and "How do you balance technical debt with speed?" are not soft-skills checkboxes; they probe whether you operate at the velocity Middesk defines.
Culture alignment screens for humility, self-motivation, and comfort with ambiguity. The values page (trust, customer-first, win together, embrace ambition, lead with curiosity) reads like a rubric. Interviewers score against it. Candidates who frame past work as solo heroics or who cannot articulate a genuine failure and its lesson tend to score low. Thirty-eight percent negative experience sentiment across 24 reports suggests the bar is real and the process can feel blunt.
Recruiter communication gaps appear in candidate feedback as a consistent friction point. Proactive follow-up on scheduling or missing information keeps your loop moving; passivity reads as a signal. The recruiter is your advocate in debriefs (roughly 80% of the time they push for borderline candidates who impressed them) but they need material to work with.
The screen is not designed to be clever. It is designed to be expensive to fake.
Compensation: What the Numbers Signal
Middesk publishes salary bands on every listing — a practice uncommon enough to matter. Ranges span $145K to $340K depending on function and seniority, with equity attached across the board. That spread tells you more about how the company calibrates risk than any mission statement does.
| Role | Department | Location | Posted Range | Pay Type |
|---|---|---|---|---|
| Software Engineer | Engineering | San Francisco / New York | $148K–$250K | Base |
| Software Engineer, Infrastructure | Engineering | San Francisco | $148K–$230K | Base |
| Forward Deployed Engineer | Engineering | San Francisco / New York | $148K–$255K | Base |
| Data Scientist | Data Science | San Francisco / New York | $175K–$210K | Base + Equity |
| Lead Data Scientist | Data Science | San Francisco / New York | $210K–$250K | Base + Equity |
| Group Product Manager | Product | New York | $190K–$250K | Base + Equity |
| Manager, Product Operations | Product | New York | $150K–$175K | Base + Equity |
| Account Executive, Mid-Market | Revenue | New York | $190K–$220K | OTE + Equity |
| Account Executive | Revenue | New York | $200K–$340K | OTE + Equity |
| Enterprise Account Executive | Revenue | New York | $200K–$340K | OTE + Equity |
| Enterprise Account Executive (alt) | Revenue | New York / San Francisco | $300K–$330K | OTE + Equity |
| Account Manager, Enterprise Banking | Revenue | New York | $200K–$220K | OTE + Equity |
| Account Manager, Mid-Market | Revenue | New York | $135K–$180K | OTE + Equity |
| Partner Manager | Revenue | San Francisco / New York | $170K–$230K | Base + Equity |
| Solutions Architect | Revenue | New York | $145K–$200K | Base + Equity |
| Commercial Counsel | Legal | New York | $160K–$200K | Base + Equity |
Source: Middesk live board data as of September 2026; 11 salaried roles, median $230K.
The board's median of $230K aligns with the $199K median ($177K–$213K) that Recruiting from Scratch calculated across 11 public postings from 2025–2026. Both place Middesk in the upper-middle tier for a Series B company of roughly 150 people, competitive with well-capitalized fintech peers but below the $300K+ medians that late-stage AI labs or public-cloud giants post for equivalent titles.
Three signals deserve attention.
First, the width of each band. Middesk explicitly states that "salary bands may cover several career levels and can narrow during the interview process." A Software Engineer band stretching from $148K to $250K spans junior through staff-equivalent scope. The same pattern holds for Forward Deployed Engineer ($148K–$255K) and the dual Enterprise Account Executive listings ($200K–$340K and $300K–$330K). Candidates should treat the posted range as a ceiling-and-floor framework, not a promise. The practical question in late-stage interviews becomes: which level does the hiring team slot you into, and what evidence moves you toward the top?
Second, revenue roles quote on-target earnings (OTE), not base salary. The Mid-Market Account Executive lists $190K–$220K OTE the live board data puts the floor at $190K; the Enterprise Account Executive lists $200K–$340K OTE. The distinction matters because quota attainment in a regulated-market product, selling identity infrastructure to banks and fintechs, carries longer sales cycles and heavier compliance scrutiny than horizontal SaaS. Candidates should ask how targets are set, what percentage of reps hit them, and whether the equity grant vests on a standard four-year schedule with a one-year cliff.
Third, equity appears on every listing as "stock options" per the benefits page, but no posting discloses strike price, grant size, or the company's current 409A valuation. At a Series B backed by Sequoia Capital, Accel, Insight Partners, and Canapi, the preferred price per share is likely multiples above the common strike. The gap between paper value and realizable value widens if Middesk raises a Series C at a flat or down round, a scenario no one discusses in the offer letter. Ask for the percentage of fully diluted shares your grant represents. If the recruiter cannot answer, that is information.
Benefits round out the package: medical, dental, vision, unlimited PTO, 401(k) (no match disclosed), three months paid parental leave, and an annual learning-and-development budget. The hybrid mandate (two to three days in office depending on role) adds a hidden cost for New York or San Francisco commuters. That time and money do not appear in the OTE figure.
The compensation data, read together, portrays a company that prices talent aggressively for its stage but retains flexibility to calibrate down. It pays like a Series B that expects to reach Series C milestones (revenue growth, product expansion into payroll tax registration and business formation, deeper penetration of the 700+ bank and fintech customer base) without overcommitting on fixed cash. For candidates, the move is to negotiate the level assignment first, the equity percentage second, and the variable-target mechanics third. The posted numbers are the opening bid. The final offer lives in the details the listing omits.
Compensation reported includes a base minimum of $41,184 and a total maximum of $893,000 Dataford reported, with pay varying by level and location. The provided data does not include a single consistent base or total figure for one specific level.
Median $467k / year Dataford's data shows
Base salary · 100%Stock (RSU) · 0%Cash bonus · 0%
25thEntry / smaller markets
$41k
50thTypical offer
$467k
90thTop performers / major metros
$893k
Breakdown by component
Base salary
100% of total
$41k$893k
$467k
median
Stock (RSU)
0% of total
$0$0
$0
median
Cash bonus
0% of total
$0$0
$0
median
Aggregated from 2 self-reported salaries via Glassdoor. Estimates only. Verify against your offer.
The compensation data provided represents the current market range for engineering roles at this level. You should interpret these figures as a guideline, as actual offers will vary based on your specific experience, technical seniority, and the total value of your compensation package, which typically includes base salary and equity components.
Who These Roles Are For — And Who They're Not
The 12 openings cluster into three distinct constituencies: mid-level engineers who want to ship infrastructure, data scientists who want to work on identity resolution at scale, and enterprise go-to-market operators who can navigate regulated sales cycles. The split is not accidental. As of October 2026, the company carries 51–200 employees, $77 million in disclosed funding, and a Series B that closed in June 2022. That stage dictates the profile: past product-market fit, pre-IPO discipline, and a burn rate that does not tolerate passengers.
Engineers who build the rails, not the dashboard
Three engineering roles (Software Engineer, Software Engineer, Infrastructure, and Forward Deployed Engineer) all sit in San Francisco at mid-level seniority. The stack is Go, Python, TypeScript, and LLM integration. The forward-deployed role is the tell: it pays $148K–255K Zero G Talent reported and expects the engineer to sit with customers, debug integrations in production, and feed patterns back to the core platform. That is not a support function. It is a product-velocity lever. Candidates who have only worked on internal tools or greenfield consumer features will not clear the screen. The screen filters for people who have shipped APIs that other companies depend on (authentication, compliance, data pipelines) and who understand that uptime SLAs in fintech are contractual, not aspirational.
Data scientists who treat identity as a classification problem
Two data roles, Data Scientist at $175K–210K Zero G Talent's figures indicate and Lead Data Scientist at $210K–250K Zero G Talent's board data indicates, span both San Francisco and New York. The work is entity resolution, risk scoring, and verification confidence across millions of business records. Middesk's version is narrower: the model must explain its decision to a compliance officer. Candidates need production experience with probabilistic matching, not just notebook experiments. The lead role expects someone who has built a modeling lifecycle (training, monitoring, retraining) and can defend feature choices to an auditor. Academic publications help; a GitHub repo with a deployed fraud or KYC model helps more.
Enterprise GTM operators who sell to risk committees
Seven of the 12 roles sit in sales, account management, solutions, and partnerships, all based in New York except Partner Manager, which is dual-location. The compensation bands tell the story: Enterprise Account Executive at $200K–340K Zero G Talent's figures put the floor at $200K, Account Executive at the same band, Account Manager for Enterprise Banking at $200K–220K Zero G Talent found, Account Manager for Mid-Market at $135K–180K, Solutions Architect at $145K–200K. These are not cold-call roles. The buyers are compliance, risk, and operations heads at banks and fintechs. It likewise filters for those who have carried a quota into a regulated vertical, managed a proof-of-concept that required legal review, and expanded an account after the initial deployment. Partner Manager at $170K–230K adds channel experience, someone who has built integration partnerships with core banking platforms or KYC vendors.
The geography constraint is real
Sixty-seven percent of roles are marked remote-eligible, but the company maintains offices at 85 2nd Street in San Francisco and 1239 Broadway in New York. Engineering roles are SF-only or dual-location. GTM roles are NY-only or NY-preferred. Forward-deployed and partner roles span both. A candidate who cannot travel to a customer site or a quarterly offsite will hit a ceiling. The research does not state a relocation policy; the screen effectively imposes one.
Who this story is not for
Junior candidates. Only two of 15 open roles are tagged junior, and none of the 12 on the board carry that label. The median days open is 41 — the company can afford to wait for the right mid-level hire.
Generalists. The tech stack tags (API, Compliance, B2B SaaS, FinTech, Data Platform, Analytics, Authentication) describe a specialized surface area. A full-stack engineer who has never touched an identity-verification flow or a compliance audit will not map to the interview rubric.
Equity-only optimists. The Series B was $57 million in June 2022. The board shows equity for every full-time employee, but the liquidity horizon is not the seed-stage lottery. Salary bands (median $230K across 11 salaried roles) reflect a company pricing for retention, not upside speculation.
Visa-dependent applicants. The research contains no mention of sponsorship. The screen does not advertise it.
People who want consumer scale. Middesk processes business identity for financial institutions. The traffic is high-value, lower-volume, and heavily regulated. The engineering challenges are correctness, auditability, and latency under compliance constraints — not feed ranking or ad targeting.
Founders Kurt Ruppel and Kyle Mack built the company on the premise that trust is foundational to how businesses operate. The hiring screen extends that premise: every role exists to make business identity reliable, transferable, and usable at scale. If your resume does not show you have already operated inside that constraint (regulatory, technical, or commercial), the screen will not pass you.
What This Case Study Does Not Claim
This piece treats Middesk's 12 open roles and the screening logic behind them as a single-company case study — not a sector survey. The distinction matters. 6sense data shows Middesk at 0.52% market share in the Identity Verification and Protection category, ranking #36 behind AWS Secrets Manager (25.92%), Early Warning (7.25%), and ID.me (6.13%). That positioning alone limits how far any hiring pattern here can generalize. A company fighting for share against an incumbent cloud provider and two identity specialists makes different talent bets than the market leaders do.
Several domains this article does not cover deserve explicit naming. No product deep-dive: research describes Middesk's architecture in broad strokes but does not document the internal stack, the data pipeline latency, the model training loop, or the infrastructure behind the "confidence-scored decision with a complete evidence trail" that marketing materials claim. No peer-company comparisons: research names competitors — Trulioo, Persona, Onfido, Ekata, Baselayer, Alloy, Socure, Veriff, Sumsub — but provides no side-by-side hiring data, compensation bands, or screening criteria for any of them. No broader market analysis: 6sense figures show 94 companies using Middesk globally as of 2026, with 76 in the United States. That is a snapshot, not a trend line.
Where evidence is thin, the article flags it. Screening criteria come from job postings and the pattern across the 12 roles on the Zero G Talent board, but no interview transcripts, recruiter interviews, or rejected-candidate feedback exist in the research. Salary bands come from the board's first-party data, not from an offer letter or compensation philosophy document. The founders appear in board data and a 2025 YouTube interview where Mack describes shipping hard drives to state agencies and the pivot from fintechs to banks — the only first-person account of company strategy in the research. No Glassdoor reviews, no employee testimonials, no investor memos. The 50% onboarding-time reduction, 5x verification volume, and Cherry's manual-review drop from 85% to 25% are vendor-reported outcomes; independent verification is absent.
Middesk's stated expansion into Canada, Europe, and APAC as of Summer 2026 and its early creditworthiness features signal product direction, but research contains no roadmap, no hiring plan tied to those geographies, and no revenue attribution. The claim that this hiring screen reveals what frontier-tech companies prioritize when they cannot afford a bad hire is the article's framing hypothesis — supported by the specificity of Middesk's roles and the constraints of its market position — not a conclusion backed by comparative data. Readers should treat it as a detailed illustration, not a sector rule.
The screen is the subject. The company is the context. The roles are the proof. When the next cohort of 12 roles opens, the filter will have shifted — but the question it answers will not: can you operate inside the constraint, or do you only know how to code around it?
Working in frontier tech? Zero G Talent tracks the openings: see every open Middesk role, browse frontier tech jobs, the companies hiring, and the people building the field.