Sync Eng Interview Counts to Your Team Tracker
Pulls completed interview data from Ashby reports and syncs weekly, monthly, quarterly, and YTD counts into your Google Sheet -- one row per interviewer, one tab per team -- then sends a Slack DM with what changed and any names that need review.
Overview
Keeping an engineering interview tracker current means manually pulling data from multiple Ashby reports, locating each interviewer row across team tabs, and typing in updated counts -- a process that takes around three hours and was easy to let slip to monthly. This MCP template automates the whole thing. It pulls completed interview data from your saved Ashby reports, matches each name to the right row and team tab in your Google Sheet, and writes updated weekly, monthly, quarterly, and year-to-date counts in one pass. It also syncs new hires from BambooHR into the roster and updates training completion dates from a Zapier Table, so the sheet stays accurate even as your org changes.
How it works
Configure the skill once with your Google Sheet URL, Ashby report IDs (one monthly and one weekly per team), BambooHR roster report ID, and Zapier Table URL for training completion data. After that, run it daily on demand or on a schedule. Each run syncs new hires from BambooHR into the right team tab, updates training completion dates from the Zapier Table, pulls fresh interview counts from all Ashby reports, and writes W/M/Q/YTD counts to each interviewer row. When finished, it sends a Slack DM summarizing what changed and flagging any Ashby names it could not match to a sheet row.
Who this is for
Built for talent operations teams who maintain an engineering interview capacity tracker across multiple teams. Most useful when your org has structured interview processes and hiring managers need visibility into interview load -- and when keeping that data current has been falling to manual, infrequent updates.
Suggested prompt
Update the Eng interview tracker
Frequently asked questions
What data sources does this pull from?
It pulls completed interview data from saved Ashby reports (one per team, covering weekly and monthly/quarterly/YTD data), syncs new hire roster data from BambooHR, and reads interviewer training completion dates from a Zapier Table. Configure each source in the skill's config file before running.
How do I set this up for my own engineering org?
The skill uses a config file where you provide your Google Sheet URL, Ashby report IDs (one pair per team -- monthly and weekly), your BambooHR roster report ID, and your Zapier Table URL for training completions. Once configured, it handles all the matching, updating, and formatting automatically. If the config is missing or has placeholder values, the skill will stop and ask you to fill it in first.
How does it handle names that don't match exactly?
It first tries an exact name match, then a last-name-only fallback. For known mismatches -- like someone who goes by a nickname in Ashby but has their full name in the sheet -- you can add a name alias mapping in the skill's reference file. It also handles common edge cases like accent marks and special characters automatically.
What does the Slack verification message include?
After each run, it sends you a Slack DM summarizing what was updated: interview counts written per team, new hires added to the roster, training completion dates synced, and any names from Ashby that could not be matched to a sheet row and need manual review.