Agentic intelligence for recruiters.

The intelligence layer on your desk. Every requirement, candidate, interview and fee on one board, AI that reads every resume and scores every fit, and your own agents working the same board.

  • Candidates
  • Pipeline
  • Interviews
  • Placements and fees
  • AI and agents

For job seekers

Today

Your candidates, today

In tabs, inboxes and sheets. Some are already lost.

The board

Every candidate is a card. Moving it is the record. Switch to the table when you want to work the list, or ask an agent to.

The rinkats pipeline board inside the app: two requirements as rows, candidate cards in stage columns, the rail on the left

Candidates, interviews, placements and fees, on the product page.

AI does the reading. You make the call.

Resume parsing, a candidate summary, a fit score against the requirement and interview questions arrive as drafts for your team. Nothing moves a card, nothing reaches a candidate.

  • Off is a real setting

    Turn any AI feature off and the tool keeps working. Turn it on and the first pass on every resume is done before you open it.

  • The score is loud on purpose

    The fit score is the one thing on the card meant to pull your eye. It never moves the card.

  • Each organisation stands alone

    Candidates, resumes and AI spend belong to one organisation. Nothing learned about your candidates is shared with another.

  • Your keys, your models

    Bring your own provider keys; a recruiter can carry a personal key, the organisation can hold shared ones, and usage is visible per key.

Ananya Krishnan0.86Senior Backend Engineer, payments
Strengths
  • Distributed systems — designed the ledger service that handles 40k TPS at Bramble Commerce (2024–26)
  • Ownership — on-call lead for payments for two years; wrote the incident playbook the team still uses
  • Mentoring — grew two juniors into SDE-2 in under 18 months
Career arc

Started in a services firm (Orrin Systems, 2019), moved product-side at Tessellate in 2021, then Bramble Commerce in 2024 — each move a step up in scale and scope.

Concerns
  • Two roles in 18 months (2021–22) — worth a question, both moves read as growth, not churn
  • No hands-on Go, which the client lists as preferred
Verification flags
  • Verification checkoverlap-datesTessellate end (Mar 2024) overlaps Bramble Commerce start (Feb 2024) by one month — Check: Ask which was the notice period (low confidence)
AI-drafted from the current resume — verify important details against the resume. Updated Today, 9:12 AM.

What it drafts, what it never does, and the research behind the first pass.

Your agents, on the board

Your assistant already reaches your calendar, your mail and your documents. Over MCP it reaches your board too, so one request can book the slot, move the card and draft the invite. rinkats adds what nobody gathers by hand: every resume read, every fit scored, every move recorded as you.

Your assistantClaudeChatGPTGeminiCursorCopilotWindsurfPerplexityMistraln8nZapierLangChainyour agent
Your board
SrcScrSubIntOff

Reads and writes, as you

The same agent already reachesCalendarMailDriveNotionSlackTeams

Things people ask their agent

  • Which candidates on the Payments role have not moved in ten days? Draft a follow-up note for each.
  • Show me everyone screened for Meridian Pay with Kafka experience and more than five years.
  • Move Ananya to client interview and note that the client confirmed Thursday at eleven.
  • Create a requirement for Kestrel Capital: senior product designer, Bengaluru hybrid, two openings, target end of month.
  • Broader intelligence

    The agent brings the context it already has, from mail, calendar, documents and the web, and rinkats brings the board. Together they answer questions neither could alone.

  • Recorded as you

    A key belongs to a person in an organisation. What the agent reads and writes is what that person could, and the history says who asked.

Connecting an agent, step by step.

Applying takes a resume, not an account

There is no candidate login, no password and no portal to remember. The resume is the application.

  • A name, an email, a resume

    And a phone number if the candidate wants to give one. The resume is parsed for your team, not for the candidate, and nothing asks them to come back.

  • One sentence back

    The candidate sees that the application went through, and nothing else. Stage names, notes and scores stay inside your workspace.

  • Duplicates join their card

    An application with a known email joins the existing candidate. Any other arrives as a new card your team can merge.

Application submitted.

Thank you. The team will be in touch if there is a fit.

The whole reply.

Start with one requirement.

Tell us about your desk and we will set your workspace up with you, with your own roles on the board from the first day.