interviewing
invitingBuilt for · Recruiting & people
Less admin.More hires.
Bash reads the profile before you do, writes the fit brief in your words, books the four-person panel and drafts the offer, inside LinkedIn, Gmail and Calendar, as you. Nami keeps every candidate, so nobody waits a week for an answer.
Signed in as you · 1,000+ moreOne ask. The whole loop.
Pick a delegation. Bash plans it, works across your tools on its own machine, and comes back with the result, held for your word where it matters.
WhatsAppBrief Owen on the backend candidate↵Delegate
linkedin · profile · Ines Marchetti · 7 yrsgithub · repos · 3 · Go, Postgresnotion · scorecard · Screen · 4 of 5gmail · sent · owen@ · 1 pageEvery scene is a real delegation. The plate plays itself — pick a row to jump.
Text it between interviews. It’s done before the next one.
Hiring happens in the gaps, so your agent works there too. Bash answers from WhatsApp, Slack, Gmail, iMessage, Telegram, or a key on your desk.
WhatsApp11:06 AM#hiringMon 9:14GmailFwd
or press ctrl ctrl anywhere on your MacWorks inside your stack, as you.
Connect the inbox, the calendar and wherever the pipeline lives. Your ATS, your job boards, a thousand more are a click away when the req calls for them.
X
InstagramDelegate in plain words.
Paste any of these into Vestra. No setup, no syntax — it already knows your reqs, your panels and how you write to candidates.
Screen the twelve new applicants on the Senior Backend req against the scorecard, shortlist five, and give me one line each on why.
Book Ines’s four-person panel across Tuesday and Wednesday, send the invites with each stage, and email her the schedule in her timezone.
Draft the offer for Ines at the approved band with a warm three-sentence note from Owen. Hold it for me.
Chase the four scorecards from Ines’s panel, write the debrief, and post it to #hiring before Friday’s huddle.
Run Nadia’s day one: channels, her week-one page, a buddy, and five meetings booked on Monday.
Rewrite the Senior Backend job post to sound like us, cut it to 300 words, and tell me which requirements are scaring people off.
On a schedule, or on a signal.
Set it once. You hear about it when it’s done — and only then.
It remembers every candidate. So nobody waits a week.
People, reqs, stages, what the panel said, what she asked about on-call. Filed once, in its place — and noticed when something changes.
Two candidates have sat in screen for nine days. Send them an answer?
Sami Okada, Bea Lindqvist · req R-114 · nothing since Aug 10Ines asked about on-call twice and nobody answered. Draft the answer?
Screen on Aug 4, panel on Aug 12Ines set her profile to open to work. Worth moving the offer today?
LinkedIn · 40 minutes agoIt sends nothing you haven’t seen.
Offers, rejections, anything a candidate reads — held until you say go. Scheduling, chasing and notes keep moving.
Send Ines the offer from Owen?
Ines — the panel was unanimous, and Marina has not stopped talking about your payments walkthrough. We would love you here. The numbers are attached, and you can call me on any of it…
Install the Recruiting playbook. Or teach it yours.
An Ability is everything the job needs — the skills, the specialist agents, the tool connections, the guardrails. Bundled, and installable in a click.
Candidate careA reply inside a day, scheduling without the back-and-forth, an honest update when the loop slips — in your voice, every time.RepliesSchedulingUpdates
Job posts & briefsJob posts that sound like your company, scorecards worth filling in, hiring-manager briefs that fit on one page.Job postsScorecardsBriefs
Create your ownYour playbook, encoded. Teach it how you screen, when you reject, what a strong hire looks like here — in plain words.Your rulesYour voiceRecruiting & people · FAQ
Questions, answered.
Does it message candidates on its own?
Does it work with our ATS?
Will it screen fairly?
What does it know about our hiring on day one?
Where does the work run?
Built for the way the rest of the office works, too.
The door
Come back to hired.
Tell us which reqs are open. We’ll show you what Bash would own, what Nami would keep, and how many days come off your loop.