This is a submission for the Notion MCP Challenge
What I Built
Most hiring teams don't have a talent problem. They have a signal problem.
1000 applications come in. 950 gets ignored because nobody has time to look. The 50 that get a call, half are wrong fits. The whole process runs on gut feel and availability, not data.
Candidates aren't winning either. They spend 45 minutes filling out an application for a job that ghosts them in 3 days.
Hirely kills the screening bottleneck entirely.
Post a job in Notion, and candidates receive a link. An AI conducts a live 5-minute interview based on your exact job requirements. You wake up to a ranked list of candidates, each with a Match Score showing how well their skills align with the job description. Skill gaps, salary fit, and any red flags are automatically documented in Notion.
No scheduling. No forms. No resume pile.
You spend your time on the 5 candidates who actually fit, not the 995 who don't.
How it works
- HR creates a job page in Notion. Title, skills, salary range, match threshold. Set status to "Published."
- An apply link is generated. The system reads the published job via MCP and writes the link back to the Notion page. HR shares this link for an interview with potential candidates.
- Candidates interview in a chat UI. The AI fetches the JD live from Notion before each session. If you update the JD in Notion, candidates will start seeing updated questions. No redeployment. No release.
- A scored candidate card appears in Notion. Match score, skill signals, salary fit, competing offers, a quick-take recommendation, and the full transcript.
You can also do all these steps entirely through AI chat. Any chatbot with Notion MCP connected can create job pages from a plain English description and query scored candidates after interviews wrap up. Say "Create a Node.js developer role with 3 years of experience," and the job page is ready to publish. Come back later and ask "Show me candidates above 80% match" and you get a filtered shortlist without opening a single dashboard.
The stack: Next.js on Vercel, n8n Cloud for automation, Notion as the sole database (via MCP), and OpenAI for interview generation.
Live site: hirely-tan.vercel.app
Get started guide: Hirely on Notion
Video Demo
Show us the code
Hirely
Post jobs in Notion. AI runs the interviews.
Hirely is an AI-first hiring workflow built on Next.js + Notion MCP. It lets teams publish roles from Notion, run candidate chat interviews automatically, and write scored candidate summaries back to Notion for fast decision-making.
What Hirely does
- For HR teams: publish jobs from Notion and share one interview link.
- For candidates: apply through a conversational interview experience (no long forms).
- For hiring managers: review structured candidate cards (match score, skill signals, salary fit, summary) directly in Notion.
Core workflow
- Define role in Notion (title, required skills, experience, salary range, threshold).
- Publish role and share the generated interview link.
- AI interviews candidates with job-aware questions sourced live from Notion.
- Transcript is sent to n8n for scoring.
- Candidate card is written to Notion with key decision data.
Architecture
Notion (Jobs + Candidates DB)
↑ ↓
MCP read MCP…Solo submission. I am the only team member.
How I Used Notion MCP
Notion is not just where HR works. It is the database that runs the whole product. MCP makes that possible with four steps:
- Read the job. HR marks a job as "Published." The system reads the job details from Notion and generates an apply link.
- Read the JD before each interview. Every interview pulls the latest job description fresh from Notion. If HR updates something, the next interview automatically uses the new version.
- Write the candidate card. After the AI scores an interview, it creates a candidate page in Notion with scores, ratings, a recommendation, and the full transcript.
- Write the apply link back. The apply link gets saved back to the job page so HR can share it right away.
Since these are standard MCP calls, they work from any chatbot with Notion connected too. HR can ask Claude or ChatGPT to create jobs, check candidates, or pull shortlists. The chatbot talks to the same Notion pages the product does.
Notion becomes a live, two-way database for the app. HR never has to leave Notion. Without MCP, I would have needed a separate database, a sync layer, and a custom dashboard. MCP removes all of that.
Top comments (1)
give people a chance you know xD