Publish the role
Define the role, screening questions, and a versioned hiring pipeline before applications arrive.
Public job · Pipeline v3See the person. See the work. Make the call.
Your entire hiring process, from first application to final offer.
export async function retry(task) { for (const delay of backoff) { try { return await task(); } catch { await sleep(delay); } }}Real code. An exact commit.
Every application lands on a connected candidate record and never leaves it. The work, the conversations, and the judgment all stay attached — that is the whole product.
Answers, history, and context arrive together — not as attachments scattered across inboxes.
Candidates read your stages, descriptions, and effort before they share a single byte.
Candidates push real Git and submit the exact commit they want reviewed. No zips, no screenshots.
Reviewers score against rubrics, the team aligns on evidence, and a human records the outcome.
Stage history, submissions, messages, and decisions persist as an append-only audit trail.
Fit review and code review surface evidence and suggested next steps beside the application. They cannot move a stage, send an offer, or reject a candidate — that authority stays with your team, on your own model keys.
The workflow stays continuous from the public role to the final outcome. Every step adds evidence without losing the context that came before it.
Define the role, screening questions, and a versioned hiring pipeline before applications arrive.
Public job · Pipeline v3Candidates see public stages, descriptions, effort, and challenge context before sharing their information.
6 public stages · ~3h effortNo account is required. Answers, role context, and consent are captured in an immutable submission snapshot.
Alex Morgan · SubmittedThe hiring team owns stage movement while an optional fit review surfaces supporting evidence beside the application.
Human decision · AI advisoryUse a structured assessment, a private repository challenge, or both—pinned to the version the candidate received.
Assessment · Repository challengeCandidates work through Git and submit an exact commit SHA. Evaluators record bounded evidence; reviewers select the final submission.
8f31c2a · 8 checks passedCommunication, interview revisions, invitations, attendance, and outcomes stay attached to the same application.
Systems interview · ScheduledSend a versioned offer, record the outcome, and preserve the stage and audit history behind the decision.
Offer draft · Audit retainedBackend Engineer · Alex Morgan
Define the role, screening questions, and a versioned hiring pipeline before applications arrive.
Public job · Pipeline v3
The application, the assessment evidence, the conversation, the interviews, and the private notes — five views of the same record, never five tools.
hiretea application 0248 overview
Structured assessments and repository challenges live in the same pipeline. Pick the format that matches the signal you need — the evidence lands on the same record either way.
Versioned questions, time limits, passing scores, code execution, and explicit human scoring for written answers.
The repository is the interface. Every candidate gets a private copy, works with normal Git, and submits the commit they want reviewed.
$
$
✓
Automation drafts, scores, and suggests — then waits. Try the approval queue: every button below is a decision only a human can make.
Confidence medium — the system design answer needs a human read before this means anything.
AI proposes, evidence attached. It cannot move a stage or send a decision on its own — the approval queue holds every proposal until an operator rules.
Bring your own provider. Your keys, your usage bill, your data boundary — Hiretea orchestrates, it never resells your hiring signal.
Each AI run records its inputs, model, and output on the audit trail. When a decision is questioned, the reasoning is replayable.
Candidates see a clear, respectful process. Your team sees everything behind it. Both read from the same record, so the story never splits.
Immutable by design. Every application is captured as a snapshot — answers, role context, consent, and the pipeline version it entered. Later edits append new revisions; they never rewrite what the candidate submitted.
Every claim a candidate record makes is backed by evidence your team can replay — who did what, when, and on which version.
Every operator action — stage moves, reviews, offers — lands on an append-only trail with actor, timestamp, and reason.
Retention windows age data out automatically, and a review queue holds anything that needs a human before it goes.
Roles, candidates, repositories, and secrets are scoped per workspace. Boundaries are enforced, not documented.
Seats set the plan. The two things that genuinely scale with hiring — evaluation runs and stored work — come included and are metered past it. No trial period: a workspace is subscribed from the day it is created.
One hiring loop, running end to end.
Create a workspaceGit-native take-homes as the default screen.
Create a workspaceHiring as infrastructure, at the scale you need.
Create a workspace| Compare every plan | Starter$49/ mo | Growth$199/ mo | Scale$599/ mo |
|---|---|---|---|
| Plan limits | |||
| Team seats | 3 | 10 | Unlimited |
| Runner minutes$0.01 per minute beyond the plan, up to a limit you set | 500 / mo | 2,500 / mo | 10,000 / mo |
| Workspace storage$0.25 per GB / month beyond the plan, up to a limit you set | 5 GB | 25 GB | 100 GB |
| Candidates and applications | Unlimited | Unlimited | Unlimited |
| Job postings | Unlimited | Unlimited | Unlimited |
| Repositories | Unlimited | Unlimited | Unlimited |
| Hiring pipeline | |||
| Public job board and application form | Included | Included | Included |
| Versioned hiring pipelinesA published pipeline keeps its shape for the applications already on it | Included | Included | Included |
| Application snapshots and stage history | Included | Included | Included |
| Candidate records, notes, and resume parsing | Included | Included | Included |
| Interviews and offers | Included | Included | Included |
| Bulk pipeline operations | Included | Included | Included |
| Listing on the Hiretea job boardCross-workspace board on the base domain | Included | Included | Included |
| Assessments | |||
| Structured assessments with automatic scoring | Included | Included | Included |
| Inline code questions in a sandboxed runner | Included | Included | Included |
| Repository challengesA private repository per candidate, cloned and pushed with real Git | Included | Included | Included |
| Automated challenge evaluationRunner pipelines with normalized checks and scores | Not included | Included | Included |
| Structured reviewer rubrics | Included | Included | Included |
| AI and automation | |||
| AI fit review on applicationsAdvisory only; it never moves an application on its own | Included | Included | Included |
| Agent code review on submissions | Not included | Included | Included |
| Bring your own model providerYour keys, your provider, your usage bill | Included | Included | Included |
| MCP server for agent access | Not included | Included | Included |
| Scoped API tokens | Included | Included | Included |
| Agent approval policiesProposals wait for an operator decision before they apply | Included | Included | Included |
| Communication | |||
| Bring your own SMTP and IMAPMail leaves from your server, and replies sync back into the application timeline | Included | Included | Included |
| Hosted email sendingHiretea sends on your behalf — no mail server to run, configure, or keep deliverable | Included | Included | Included |
| Recruiting email templates | Included | Included | Included |
| Application acknowledgement emails | Included | Included | Included |
| Interview invitations with calendar files | Included | Included | Included |
| Candidate notification preferences | Included | Included | Included |
| Git and infrastructure | |||
| Bundled Gitea code host | Included | Included | Included |
| Repository browsing, history, and pull requests | Included | Included | Included |
| Git over HTTPS with a scoped CLI token | Included | Included | Included |
| Organization secrets, variables, and runners | Not included | Included | Included |
| Packages and release downloads | Not included | Included | Included |
| Governance | |||
| Audit trail across every operator action | Included | Included | Included |
| Retention windows and privacy review queue | Included | Included | Included |
| Role and workspace isolation | Included | Included | Included |
$0.01 / minute beyond the plan
Compute for automated evaluation: repository challenge pipelines and inline code assessment runs. Measured while a container is actually executing, not while a candidate is working.
$0.25 / GB / month beyond the plan
Candidate repositories, resumes, submissions, and message attachments. Measured as average stored bytes across the month, so a retention sweep or a purge lowers the next bill.
Hiretea, PostgreSQL, and Gitea deployed together, so candidate repositories and company code never leave your environment. The runners and the disks are yours, so nothing is metered. The license is not open yet — pricing, terms, and the deployment documentation land together when it is.
Billed per workspace, monthly, cancel any time. Usage accrues visibly in the workspace billing page, and a plan change takes effect on the next period without touching the hiring already in flight. Canceling keeps your data readable through the end of the period you paid for.
The short answers. The long ones are in the product — create a workspace and read a candidate record end to end.
No. Candidates apply through a public link, answer screening questions, and receive repository challenges by email. Every interaction is captured on their record without a signup step standing between them and your role.
Publish the role. Show the process. Collect real work. Decide with evidence. One record carries it all — start yours today.
NO TRIAL CLOCK · CANCEL ANY TIME · YOUR DATA STAYS YOURS