What it does

cmdHire turns the profile on screen into a recruiter-ready decision.

Open a candidate profile, summon cmdHire, and ask the question every desk really cares about: “Which of my jobs does this person fit, and what should I do next?”

Passive profile context Explainable Match Radar Submission-ready output
cmdHire Live desk
Captured from LinkedIn ⌘ ⇧ H
Captured from LinkedIn
Yuko Kawata

Yuko Kawata

Staff AI Platform Engineer - Tokyo

LLM serving Kubernetes Platform APIs
cmdHire next action
Match Radar
84%

LLM, Kubernetes, Tokyo, backend systems

Best next move: verify Kubernetes ownership, LLM serving scale, and Tokyo availability. Then draft client-ready outreach.
Built to move candidates

Your ATS stores candidates. cmdHire moves them.

While a candidate profile is open, cmdHire keeps the context in view, compares it with every active job, and helps the recruiter take the right next step without losing momentum.

01

Capture the active profile

cmdHire uses browser context from the active page so recruiters are not screenshotting, pasting, or rebuilding profile summaries by hand.

Chrome contextPassive profile context
Chrome context Session has active candidate context
Captured from LinkedInCaptured profile
Yuko Kawata

Yuko Kawata

Staff AI Platform Engineer - Tokyo / Hybrid

LLM serving Kubernetes Bilingual teams
02

Rank matching jobs

Match Radar compares the candidate with active jobs and explains the signal: skills, seniority, location, domain, and gaps to verify.

Local DBExplainable Match Radar
Match Radar 3 ranked jobs
Match Radar3 ranked jobs
84%
Senior AI / ML Platform Engineer

LLM, Kubernetes, Tokyo, backend systems

Evidence: LLM, infra, Tokyo, API scale
72%
Staff Rust Systems Architect

Systems depth present; confirm Rust ownership

Check: Rust depth and recent production scope
61%
Growth Product Lead

Adjacent signals, needs recruiter judgment

03

Run the role desk

See which candidate follow-ups and client roles need attention today, with coverage signals that keep the desk moving.

Local DBSubmission-ready output
Next desk action Local DB
Next desk action7 Next desk action
High priority outreach6 candidates need follow-up
01
FOLLOW-UPYuki Ito

35 days untouched

Draft next move ↗
02
COVERAGEStaff Rust Systems Architect

6 saved candidates mapped

Plan sourcing ↗
Client job sourcing health5 active roles
3 need attention
04

Draft the next move

Ask for outreach, screening questions, fit summaries, or submission notes using the candidate and job context already in memory.

OllamaSubmission-ready output
Ask anything Ollama
Do they match any of my active jobs?
Strongest fit is Rakuten Group's Senior AI / ML Platform Engineer. Evidence is infrastructure depth, LLM systems, and Tokyo availability.
Next desk action
Move Yuko while the signal is fresh.
01Save candidate to DB
02Draft outreach
03Create submission packet
Ask about gaps, outreach, salary, fit...Send
Not an ATS.

Your ATS stores candidates. cmdHire moves them.

cmdHire works alongside Greenhouse, Lever, and the system you already use. No migration required.

Example recruiter prompts

Ask it like a teammate, not a database.