The Board Shows One Role, Not Two
Gojiberry AI posted a single opening this week: a remote Sales Development Representative role banded at $55,000–$80,000, median $80,000, Zero G Talent's board data shows. The listing appears twice in the feed with identical details, and the board shows just two salaried roles total, Zero G Talent's data shows. Zero G Talent ingests this data directly from the source; third-party aggregators often lag or duplicate.
Industry chatter cites two "AI positions." The board shows none. No machine learning engineer, research scientist, or applied researcher appears in the current window. That doesn't mean those roles don't exist internally. Companies in this cohort often run technical searches through referrals, recruiter pipelines, or a separate careers page before posting publicly. The board captures only what's live today.
The disconnect between the announced AI roles and the verifiable SDR posting is the story. Early-stage AI startups frequently hire commercial roles before or alongside research talent, and the public job board may lag behind private recruiting channels, referral pipelines, or stealth postings that never hit aggregators. For candidates, the drill is procedural: check the board, check the company careers page, check the recruiter. The SDR role is real, posted, and priced. The AI research roles exist in conversation, not yet in the feed.
How AI Screening Works in the Industry
Most early-stage AI companies start filtering before a human opens a resume. Firms from Meta and Netflix to Mastercard and Domino's have folded AI interviewers into initial screens, a March 2026 investigation found. Vendors (Humanly, Eightfold, CodeSignal) pitch the same core value: their customers cannot get human recruiters in front of roughly 95 percent of applicants, The Verge's investigation found, so an AI agent runs a one-on-one video call with virtually everyone who applies.
The format is consistent. Candidates face an avatar that asks a fixed set of questions; every applicant receives the same prompts and is scored on the same rubric. Humanly reports its interviewer elicits an average of 200 words per response, substantially more than a typical phone screen. Eightfold, whose clients include Activision, Salesforce, and Dolby, says its system evaluates only spoken content. Keywords and measurable metrics embedded in answers carry weight, much as they do when an AI parses a resume.
A resume submitted for an AI-focused role at a startup this size will almost certainly hit an automated parse first: the model scans for specific frameworks (PyTorch, JAX, TensorFlow), deployment artifacts (Docker, Kubernetes, ONNX), and evidence of production-scale work (model serving, latency optimization, data-pipeline ownership). Candidates who clear that gate enter the AI interview, where the same keyword logic applies to spoken answers. "Speak clearly, use keywords and metrics when you can, and maybe ask a question or two at the end," the investigation's reporter summarized as the consensus advice from vendors themselves.
Evaluation criteria center on consistency and claimed bias reduction. Every candidate gets identical questions; scoring is algorithmic. Humanly, CodeSignal, and Eightfold each say they run third-party bias audits annually. Eightfold notes an internal industrial-organizational psychology team, called a talent science team, that partners with customers on ongoing audits. Ethics and security certifications (SOC 2, ISO) are cited as standard practice.
Yet the black-box problem remains. A lawsuit against Eightfold, filed by two plaintiffs demanding credit-agency-style transparency into how scores are generated, underscores that no vendor fully discloses weighting logic. Training data drawn from "large swaths of the internet" inevitably absorbs sexism, racism, and other biases, the vendors acknowledge. Audits mitigate but cannot eliminate the risk.
For an applicant targeting Gojiberry, the takeaway is straightforward: optimize the resume for the parse, then treat the AI screen as a structured behavioral interview where quantified impact statements, such as "cut inference latency 40 percent by quantizing to INT8 on A100s," outperform narrative flair. The human conversation, if it comes, starts only after the model says yes.
What Clears the Screen in Two Minutes (Industry Pattern)
The hiring signal across early-stage AI companies has shifted decisively toward shipped production work. A hiring manager who screens for multiple AI startups put it bluntly: "Every serious wreck we just read is allergic to notebook-only candidates." The term "wreck" — shorthand for job requisition — appears repeatedly in current hiring discussions as the filter document that separates builders from experimenters. Certifications don't clear the screen. A single project that hits four or five of the wreck's stated bullets does.
The market now distinguishes three flavors of AI engineer:
| Role | Focus |
|---|---|
| App & LLM Engineer | APIs, RAG, agents, product features |
| Platform Engineer | Infrastructure, deployment, MLOps |
| Domain-Locked Engineer | Finance, healthcare, operations — same builder skills |
The common denominator: "AI engineer builds with models, ships LM features, RAG, agents, product integration, evaluation inside production workflows." That sentence, drawn from a hiring manager's breakdown, is the competency spec.
What clears the screen in under two minutes? The manager's rule: "If I can't map your proof to the wreck bullets in under 2 minutes, you're not ready to apply yet." Proof means a GitHub repo, a deployed demo, or a write-up showing end-to-end ownership, including data ingestion, embedding strategy, retrieval pipeline, agent orchestration, evaluation harness, monitoring, and cost control. One strong end-to-end project beats eight unfinished tutorials.
A 30-day preparation path circulating among serious candidates allocates days 1–7 to API fundamentals and prompt engineering, days 8–18 to embeddings and vector databases ("the RAG spine"), days 19–25 to orchestration (one retrieval pipeline, one tool-using agent workflow), and days 26–30 to shipping a single portfolio project proving Python structure, LLM integration, and retrieval over real documents.
Salary bands confirm the premium on shipped work:
| Level | Base Salary |
|---|---|
| Mid-level (ships LLM features end-to-end) | $130k–$180k |
| Senior (production RAG, agents, Python that survived users) | $175k–$250k + significant bonus |
| VP AI Engineering | $300k–$350k + equity |
The jump between levels isn't years of experience; it's the production scars.
Transition paths reveal which adjacent competencies transfer fastest. Software engineers moving to AI engineer is "pretty much the fastest path"; they already write production Python, understand APIs, testing, and deploy, and they add LLM systems, RAG, agents, and evals. Data scientists transitioning need to close the software engineering discipline and production shipping gap. Adjacent technical roles face a higher bar: "need a sharp portfolio and tighter proof." The hiring manager's advice: "Match the language exactly. Don't apply to both with the same resume store."
The board's single data point — an SDR role at $55k–$80k, median $80k — suggests Gojiberry is building a go-to-market motion alongside its research core. Technical applicants should signal they understand that context. A one-line addition to your cover letter or intro call, such as "I've read the SDR opening and it looks like you're scaling commercial traction; my last project cut inference latency 40% which directly supports that," proves you've done the homework most candidates skip.
Market Pressure Shows in the Numbers
Gojiberry's single SDR posting sits inside a hiring environment with little precedent. The company shows two salaried roles total, one new listing in seven days, according to Zero G Talent's board data, a modest pace compared with hiring bursts at better-funded AI labs. But the salary band tells a story about where early-stage companies set the floor for commercial talent.
Across the AI startup tier, compensation for non-research roles has climbed sharply since late 2022. Sales, solutions engineering, and developer-relations positions that once topped out around $70,000 base now routinely open at $80,000–$100,000 with equity packages attempting to close the gap with Big Tech offers. Gojiberry's $55k–$80k range aligns with the lower end of that shift, suggesting the company is either calibrating to an earlier funding stage or treating the role as a pipeline builder rather than a senior quota-carrier. The $80k median matches the midpoint where many seed-stage AI companies anchor their first commercial hire.
Demand for applied AI talent, specifically engineers who ship model-backed products rather than just publish papers, continues to outstrip supply. Recruiters at growth-stage AI firms report candidates with production ML experience receive multiple offers within weeks; counteroffers from incumbent employers have become standard. That pressure pushes early-stage founders to move faster, compress interview loops, and raise compensation bands before revenue supports them. Gojiberry's single new posting in a week suggests a deliberate, measured approach rather than the panic hiring seen at peers who add five or six roles in a single sprint.
Salary transparency laws in California, New York, Colorado, and Washington have forced bands into the open, giving candidates leverage to compare. Gojiberry's posted range complies and provides a benchmark: a remote SDR at an AI startup now commands a floor that would have been unusual for a Series A SaaS company three years ago. The premium reflects both the technical literacy required to sell AI products and competition from better-capitalized rivals who can pay $120,000–$150,000 OTE for the same profile.
Equity remains the variable board data cannot capture. Early-stage AI grants vary wildly, ranging from 0.1% to 0.5% for early employees, with strike prices that move every financing round. Candidates who evaluate only base salary miss the upside that aligns risk with reward. Gojiberry's two-role total headcount implies a cap table where early hires still receive meaningful ownership, but without published option details the calculation stays opaque.
The broader signal: AI hiring has bifurcated into three tiers.
| Tier | Profile | Total Compensation |
|---|---|---|
| Top labs | PhDs | $300k–$500k |
| Well-funded application companies | Engineers who deploy models | $180k–$250k |
| Seed / pre-Series A startups | Equity, autonomy, product direction | $80k–$120k base (technical), $55k–$80k (commercial) |
Gojiberry sits in the third tier. Its next hire will clarify whether the company is building a research core or a commercial engine first.
Where Gojiberry Fits in Frontier Tech
Frontier-tech hiring across space, defense, robotics, energy, and biotech follows a recognizable sequence. Capital-intensive sectors such as launch vehicles, satellite constellations, fusion, and advanced manufacturing typically front-load engineering hires: propulsion, guidance/navigation/control, thermal, structures, and increasingly, autonomy and onboard compute. Defense-adjacent firms add cleared-software and systems-engineering tracks early. Robotics companies blend mechanical, electrical, and perception stacks from day one. Biotech and energy ventures often lead with wet-lab or process engineers before scaling data and ML teams. In all these domains, the first five to ten hires are overwhelmingly technical; commercial roles appear once a prototype exists or a contract vehicle is in sight.
Gojiberry's visible board footprint, a single sales role in a $55k–$80k band, suggests either a pre-product team building pipeline ahead of launch, or a board snapshot that misses technical hires already made off-platform. The salary band aligns with early-stage commercial hires at seed or Series A companies across frontier tech: comparable SDR roles at space-data startups, robotics integrators, and defense-software shops have listed $50k–$85k base with variable on-target earnings in the same range over the past year. The $80k median sits at the upper end of that bracket, which may indicate a well-capitalized seed round or a founder team with prior exits that can afford above-market cash for early revenue traction.
What the board cannot show — and what no public aggregator reliably captures — is the shadow hiring that defines frontier-tech talent markets. SpaceX, Anduril, Relativity, and their tier-two peers fill 60–80% of technical roles through referrals, university pipelines, and cleared-candidate pools before a requisition ever posts. AI-native startups compound this effect: the "two new AI positions" may exist only in a Notion board shared with a handful of trusted researchers, or in direct outreach to authors of specific papers at NeurIPS, ICRA, or RSS. The screening criteria discussed earlier, including publication record, open-source contributions, and GPU-cluster experience, are the currency of that hidden market, not the public job description.
The divergence lies in Gojiberry's apparent decision to surface a commercial role publicly while keeping technical hiring private. That pattern appears more often in applied-AI companies targeting enterprise or defense contracts, where a named SDR can start conversations that clear the path for technical demos, than in pure research labs or hardware-first ventures. Whether that represents a deliberate go-to-market strategy or a timing artifact of the board's crawl window remains an open question. The only grounded conclusion the data supports: Gojiberry's visible hiring footprint today is commercial, modestly compensated, and singular — a snapshot that tells more about what the company chooses to publish than about the team it is building.
How to Tailor Your Application
The public record on Gojiberry's specific screening rubric for its two newly announced AI roles is thin. The company's careers page and major job boards show only the SDR opening, with no detailed breakdown of how technical candidates are evaluated. Applicants must triangulate from broader signals: the tooling candidates use, public writing of hiring managers at comparable startups, and peer-to-peer chatter on forums where engineers debrief actual interviews.
Start with the interview-prep stack candidates are actually running. Final Round AI, which claims 10 million users, markets a real-time "Interview Copilot" that listens to live sessions and suggests follow-ups, plus customized mock interviews with performance reports. The tool is built for the exact loop Gojiberry-style startups run: phone screen, technical deep-dive, system-design or research-discussion round. Candidates who treat the copilot as a rehearsal partner — not a cheat sheet — report tighter answers on model-architecture tradeoffs and cleaner whiteboard code. The platform's "why this answer works" breakdowns map directly to rubric items that show up in debriefs: clarity of problem framing, awareness of compute constraints, honesty about what the candidate would Google versus derive.
Noam Segal's guide on Lenny's Newsletter offers a concrete prompt pattern applicants can copy. Feed the job description and your resume to a large language model and ask for five tailored, non-generic questions, each with the rationale, the likely interviewer, the probable follow-up, and a prepared reversal answer. Run this for every distinct round: recruiter screen, hiring-manager conversation, peer technical interview, founder or CTO chat. The output becomes a personal briefing doc you review the night before. Segal's method works because it forces you to articulate the "why" behind every project on your resume, the exact muscle Gojiberry's screen tests.
Reddit's r/interviews thread on AI-assisted prep surfaces a caution: candidates who memorize LLM-generated answers get caught when interviewers pivot one layer deeper. The consensus: use the model for structure and vocabulary, then rehearse aloud until the narrative sounds like yours. Several commenters note that early-stage AI startups, Gojiberry's peer set, weigh "research taste" as heavily as coding speed. That means your prep should include a two-minute story for each project: what you tried, what failed, what you'd do differently with hindsight. Senior interviewers spot rehearsed perfection and prefer a candid rough edge that signals real iteration.
Career coaches who specialize in frontier-tech placements consistently advise three concrete steps for this profile of company. First, publish a 500-word technical note on a decision you made in the last six months, such as quantization strategy, data-curation pipeline, or eval-framework choice, and link it in your application. Second, map your GitHub contributions to the specific stack mentioned in the job description (PyTorch, JAX, Triton, vLLM, whatever appears) and pin those repos. Third, reach out to one current engineer — not a recruiter — with a specific question about their latest paper or blog post. The response rate is low, but a single reply puts you in the "referred" pile before the screen even starts.
None of these steps guarantee an offer. They do align with the measurable behaviors that separate candidates who clear the first two rounds from those who stall at the resume review. The research on Gojiberry's exact process is sparse; the pattern across its peer group is not.
The board still shows one SDR role. The two AI positions exist in the chatter, not the feed. When they finally post, the wreck bullets will look familiar: shipped work, production scars, proof that maps in two minutes. The candidates who clear the screen won't be the ones who guessed the keywords. They'll be the ones who already built the thing the wreck describes.
Working in frontier tech? Zero G Talent tracks the openings: see every open Gojiberry AI role, browse frontier tech jobs, the companies hiring, and the people building the field.