Step 1 of 12
💬
The conversation will appear here as you step through →
Call it anything — this is just your label for finding the task later.
Point this at the folder with the resumes.
Select Majk Rabbit — the general assistant.
Start New Task
Name your task, choose where to work, and select a teammate
Task Name *
Screen PM resumes
Working Directory
/Users/yourname/Documents/resumes
Team Member
Majk Rabbit Default General Assistant
···
⚙️ Work Strategy Configuration
Isolated Workspace ▶
Y
You

I have 53 resumes in this folder for a Senior Product Manager role.

Screen every resume against these must-haves:

  • 5+ years of product management experience (not project management)
  • B2B SaaS background — enterprise or mid-market, not consumer apps
  • Evidence of cross-functional team leadership — actually leading engineers, designers, data people

Build a single-page HTML dashboard with a matrix showing each candidate's qualifications against these criteria.

A
AI Assistant Majk Rabbit

I'll read every resume and evaluate each one against your three criteria. Let me work through all 53 systematically...

📄 Read sarah_chen_resume.pdf — 2 pages, extracting role history and SaaS indicators
📄 Read marcus_rivera_cv.pdf — 3 pages, checking PM vs. project management titles
📄 Read priya_sharma_resume.docx — 2 pages, engineering-to-PM transition path
📄 Read james_wilson_resume.pdf — 1 page, scanning for B2B evidence
📄 Read ...reading remaining 49 resumes against all 3 criteria
>_ Bash python3 score_resumes.py — tabulating pass/fail per criterion for all 53 candidates
Write resume_screening_dashboard.html — single-page dashboard with shortlist, scores, and evidence
A
AI Assistant Majk Rabbit
📋
Resume Screening Matrix — Senior Product Manager
53 resumes · 3 criteria · excerpts pulled from each resume
Qualification Matrix (showing 3 of 53)
Candidate PM Experience B2B SaaS Background Cross-Functional Leadership
Candidate 1 8 yrs PM at Salesforce & HubSpot, led 3 B2B product lines Enterprise SaaS entire career — Salesforce (4 yr), HubSpot (4 yr) Managed team of 12 (eng, design, data), shipped enterprise pricing overhaul
Candidate 2 7 yrs PM, 4 at enterprise SaaS startup (Series B → D) Mid-market SaaS — built product-led growth for 200-seat accounts Built PM team from 2 to 8, partnered with eng and design on roadmap
Candidate 3 6 yrs PM (transitioned from engineering), API platform product B2B API platform — developer tools for enterprise integrations Led cross-functional squad of 6 (eng + design), owned API roadmap
…plus 50 more rows in the full dashboard
Every cell is an excerpt from the resume
The matrix doesn't score or rank anyone — it pulls the relevant evidence from each resume so you can see it side by side. You decide who to call. The full HTML dashboard has all 53 candidates in the same format.
Y
You

Compare candidates 1, 2, and 3 side by side. How do they differ on technical depth, stakeholder management, and leadership style?

A
AI Assistant Majk Rabbit

I already have all three resumes in context. Let me pull out the additional dimensions you're interested in...

📄 Read Re-analyzing candidates 1, 2, 3 — extracting leadership style and technical indicators
A
AI Assistant Majk Rabbit
🔍
Deeper Look — Candidates 1, 2, 3
Additional dimensions pulled from resumes: technical depth, stakeholder experience, leadership style
Dimension Candidate 1 Candidate 2 Candidate 3
Technical depth Business-side PM — strong with metrics, no architecture mentions Balanced — resume mentions reading specs and challenging engineers Former engineer — deep API knowledge, built internal tools herself
Stakeholder experience Led board-level product reviews at HubSpot Reported directly to founder, presented to investors Strong with engineering teams, no C-suite mentions
Leadership style Managed team of 12, cross-functional coordination Built PM team from 2 to 8 at a startup Led squad of 6, hands-on technical leadership
Different backgrounds, different strengths
The table surfaces what each resume actually says — not a score. Candidate 1's resume emphasizes executive-level work, Candidate 2's emphasizes building from scratch, Candidate 3's emphasizes technical depth. Which matters most depends on what the role actually needs day-to-day.
Y
You

Export the full matrix as a CSV file so I can open it in Excel and share it with the hiring manager.

A
AI Assistant Majk Rabbit

Done — here's the CSV with all 53 candidates and their qualifications against each criterion.

Write resume_screening_matrix.csv — 53 rows, columns: candidate name, PM experience excerpt, B2B SaaS excerpt, leadership excerpt
Y
You

Give me aggregate stats on this candidate pool — where are they located, what's the education breakdown, how many years of experience on average? Build a dashboard with visualizations and key insights for future recruiting.

A
AI Assistant Majk Rabbit

I'll pull the aggregate data from all 53 resumes and build the dashboard.

📄 Read Re-scanning all 53 resumes for location, education, and experience data
>_ Bash python3 pool_analysis.py — aggregating demographics, geography, education, experience distribution
Write candidate_pool_analysis.html — dashboard with charts: location map, education breakdown, experience histogram, key recruiting insights
A
AI Assistant Majk Rabbit

Key findings across all 53 applicants:

  • Location: 68% Bay Area or NYC, 15% remote-first (no single location), 17% other metros. Very little geographic diversity — if you want that, you may need to post on different boards.
  • Education: 42% MBA, 34% CS/engineering undergrad, 24% other fields. The MBA-heavy pool makes sense for PM but means fewer candidates with deep technical backgrounds.
  • Experience: Median 6.5 years PM experience. The distribution is bimodal — a cluster at 3–4 years (too junior for this role) and another at 7–9 years. Very few in the 5–6 year sweet spot.
  • Source pattern: The strongest candidates by background came through referrals and LinkedIn, not the job board posting. Worth investing more in direct outreach next time.

The full dashboard is at candidate_pool_analysis.html — open it in your browser for the interactive charts.