The Count, Close Up
Zero G Talent's board shows 19 salaried roles for Tennr as of the latest pull, three added in the past week alone. The board's salary band runs $120k–$230k with a $190k median. A claim circulates that Tennr has 21 open positions — a number that would put this AI startup ahead of most peers its size, but the headline matters less than what sits behind it: which functions are growing, what seniority levels are targeted, whether the list has been static or churning.
This piece tests whether the 21-role claim holds, details the advertised positions, and reconstructs the likely screen from the only evidence available: the roles themselves, a handful of candidate accounts, and the company's own hiring velocity.
| Role | Location | Salary Band |
|---|---|---|
| Enterprise Account Executive | New York City Office | $330k–$370k |
| Senior Backend Engineer (ML) | New York City Office | $200k–$230k |
| Senior Infrastructure Engineer | New York City Office | $200k–$230k |
| AI Operations Lead | New York City Office | $170k–$220k |
| Senior Backend Software Engineer | New York City Office | $190k–$215k |
| Senior Product Engineer | New York City Office | $190k–$215k |
The two-role gap between the board's 19 and the cited 21 likely reflects timing: the board snapshots daily; a careers page refresh may catch a posting or removal hours earlier or later. It could also reflect categorization: the board counts salaried roles; contract, part-time, or internship slots might not appear. Tennr's public careers page at tennr.com remains the definitive source for a point-in-time count. The board data aligns closely enough to treat "roughly 20" as the working reality.
What the Roles Reveal
Engineering dominates the visible slate. Four of the six newest postings carry "Senior" in the title and sit in a tight band between $190k and $230k. The Senior Backend Engineer (ML) and Senior Infrastructure Engineer both top out at $230k, Zero G Talent's board data shows, signaling that machine-learning infrastructure and platform reliability command a premium. The Senior Backend Software Engineer and Senior Product Engineer share a $190k–$215k range, according to Zero G Talent's board figures, still well above the board's $120k floor. All four demand the judgment layer that recent peer-reviewed work identifies as the widening gap in AI-assisted development: specification, design, testing, and responsibility for the result, not the typing.
The AI Operations Lead, listed at $170k–$220k, Zero G Talent's board found, straddles engineering and operations. Its band overlaps the senior engineering roles at the top end but extends lower, hinting at a hybrid profile: someone who can run models in production, monitor drift, and coordinate retraining cycles without necessarily owning the model architecture. That function has grown distinct from traditional DevOps as more startups ship LLM-backed features; the salary spread reflects the market's uncertainty about where the role settles.
The lone non-engineering role in the visible set is the Enterprise Account Executive at $330k–$370k, Zero G Talent's board reported, the highest band by a wide margin. Enterprise sales in AI document automation commands a premium because the sales cycle involves security reviews, compliance questionnaires, and pilot negotiations that pure product-led growth cannot absorb. The $330k floor implies a quota-carrying rep with existing healthcare or legal-tech relationships; the $370k ceiling suggests accelerator structures for multi-year deals.
Seniority across the board skews heavily experienced. Five of six roles carry "Senior" or "Lead" in the title. No junior, associate, or new-grad positions appear in the named six, and the board's $190k median reinforces that the aggregate 19-role pool weights toward mid-to-senior ICs and leads. Search queries surface a "Tennr machine learning intern role" and "Tennr product manager opening," but neither returned verifiable listings in the first-party feed (either filled, never posted, or living only on the company's own career page outside this ingest).
Functionally, the visible six break down as: backend/ML engineering (two), infrastructure/platform engineering (one), product engineering (one), AI/ML operations (one), and enterprise sales (one). If the missing 13 roles follow the same pattern (and the board's $120k–$230k band suggests they do), Tennr is building a classic Series B/C execution layer: heavy on engineers who can ship and maintain production ML systems, light on pure research, adding a single high-leverage sales hire to convert pipeline. That velocity, three roles in seven days, is the only benchmark the data supplies.
The Screen, Inferred
No public documentation of Tennr's hiring funnel exists. The career page lists open roles but publishes no recruiter blog posts, no interview-process FAQ, no engineering-team write-ups describing take-home assignments or on-site loops. Glassdoor shows one interview review; Levels.fyi and Blind have no Tennr-specific data in the research. The primary sources a candidate would mine for screen details are absent.
What we can observe comes from the roles themselves. The titles and bands imply a screen that weights two distinct tracks: a go-to-market track hunting enterprise sales talent, and a technical track hunting engineers who can ship production ML systems on cloud infrastructure.
For the engineering track, the role names — Senior Backend Engineer (ML), Senior Infrastructure Engineer, Senior Product Engineer — signal a screen that likely probes three layers. First, backend fundamentals: API design, database modeling, concurrency, observability. Second, ML-systems fluency: model serving, feature stores, training-pipeline orchestration, GPU utilization, evaluation loops. Third, product judgment: scoping ambiguous problems, trading off latency versus accuracy, shipping iteratively behind feature flags. A typical AI-startup phone screen at this stage runs 45–60 minutes: background discussion, a live coding exercise or system-design sketch, and domain questions such as "How would you version a model that serves legal-document extraction?" But that template is an inference from peers such as Harvey, Casetext, and EvenUp; Tennr has not confirmed it.
The AI Operations Lead role adds a fourth lens: operationalizing model quality at scale. That suggests the screen may include a scenario question about monitoring drift, building human-in-the-loop review queues, or designing eval sets for legal NLP tasks. The salary band ($170k–$220k) sits below the senior engineering bands, hinting the screen weighs process design and tooling over deep research novelty.
On the sales side, the Enterprise Account Executive band ($330k–$370k OTE) matches mid-market legal-tech quotas. A first screen there typically tests pipeline discipline and qualification frameworks. Again, no Tennr-specific account confirms this.
The absence of first-party process detail means applicants should prepare for the union of these peer patterns: backend depth, ML-systems pragmatism, product intuition, and, for the ops role, eval and monitoring rigor. Candidates who reach the on-site will likely face a system-design round, a code-review exercise, and a cross-functional panel. Until Tennr publishes its own rubric, that composite is the only evidence-based proxy available.
What Candidates Say
Public candidate accounts of Tennr's interview process are scarce. One Glassdoor review for an unspecified engineering role describes a live technical round where the candidate walked the interviewer through "the entire logic and code execution" of a standard optimal solution. The interviewer's response, the review states, was "repeatedly blindly insisting: 'Wrong, this is wrong, this won't work.'" The candidate wrote that no counterproof, valid edge case, or alternative approach was offered, just blanket rejection of a widely accepted answer. The review characterizes the interaction as disorienting and suggests the interviewer may have been working from a rigid answer key or lacked the depth to evaluate deviations from an expected script.
A Reddit thread in r/developersIndia asked whether Tennr's AI-driven interview for an Implementation Engineer role was legitimate. The research captures only the subreddit's automated welcome message; the thread's content is not available in the sources.
Neither source identifies the reviewers by name, role, or date beyond platform timestamps. No successful-candidate writeups — offer acceptance posts, "how I passed" breakdowns, or referral testimonials — appear in the first page of search results for Tennr interview experiences. The absence of positive reports could reflect low offer volume, a non-disclosure culture, or simply the early stage of Tennr's hiring surge; the company's own career board shows three new roles posted in the past week. That pace suggests the interview process is actively running, but the public record hasn't caught up.
What the available anecdotes share is a theme of opacity. Candidates describe screens, whether AI or human, that feel deterministic rather than conversational, with little visibility into evaluation criteria. The Reddit thread's core question ("is this legit?") and the Glassdoor reviewer's bafflement at a "standard optimal solution" being dismissed both point to a process that candidates struggle to reverse-engineer. For job-seekers, that means the usual preparation signals — LeetCode patterns, system-design frameworks, behavioral STAR stories — may not map cleanly to what Tennr's screen actually measures. Until more candidates document outcomes, the screening bar remains a black box inferred from a handful of frustrated data points.
Scope and Limits
This article examines Tennr's hiring claims: specifically whether the company currently lists 21 open roles, what those roles are, and what candidates encounter in the initial screen. It does not evaluate Tennr's product, its clinical-document-automation technology, or the competitive field for AI-powered medical coding. The live feed lists 19 salaried roles with a median band of $190k. Whether those 19 map to a public claim of 21 is the question this piece tests; the product those hires would build is outside scope.
No financials appear here. The story does not report Tennr's revenue, burn rate, runway, or valuation history. It does not analyze funding rounds, investor composition, or cap-table dynamics. Board compensation bands are cited only to illustrate what the company signals for specific functions (engineering, product, go-to-market, and AI operations) not to model total compensation cost or compare against peers' spend.
The piece also sidesteps the broader legal-AI category. It does not survey Harvey, Casetext, EvenUp, or other legal-focused LLM applications. It does not assess Tennr's position relative to general-purpose foundation-model providers or vertical SaaS incumbents. The screening discussion stays bound to what applicants and public sources describe for Tennr specifically (take-home assignments, recruiter phone screens, technical interviews) and does not extrapolate a universal "AI startup interview playbook."
Finally, the article makes no hiring recommendations. It presents the roles the board shows, the screen patterns candidates report, and the benchmark context from similar-stage companies. Readers evaluating an application should treat the findings as signal, not prescription.
The next board pull will show whether the three roles added this week become six, or whether the list churns. Until Tennr publishes its rubric, the screen stays a black box, and the 21-number stays unconfirmed.
Working in frontier tech? Zero G Talent tracks the openings: see every open Tennr role, browse frontier tech jobs, the companies hiring, and the people building the field.