Team Builds AI Fluency with Zapier MCP and SDK

This title was summarized by AI from the post below.

Most TA teams don't have time to think, let alone build. But it’s my responsibility as a team leader to ensure the team can prioritize this. Every 3 weeks in Q2, we carve out a full five-hour block of time for the team to build and hone their AI fluency skills. (And yes, we let our hiring teams know!) Last month was choose-your-own-adventure - everybody picked their own project on their back log of “I wish I had time to build X.” But this time we shifted the focus to team best practices. We shipped: 👉 Daily Ashby sweep that scores every new candidate and drops a morning digest into Slack each day 👉 Debrief prep builder that turns Ashby scorecards and BrightHire transcripts into a thread the whole panel reads before an interview 👉 Chrome extension to dodge a LinkedIn Recruiter quirk, saving ~10 seconds per candidate across 30+ tabs...adds up fast! The best part was watching the team pressure-test a skill we thought was ready to launch. Fresh eyes from everyone in the room surfaced all the small friction points it would have hit in the wild. We iterated together and landed on something the whole team could genuinely adopt. These are recruiters, sourcers, and ops folks - not engineers. When people know the work deeply and have space to build, they solve their own problems better than anyone outside the work ever could. Building and maintaining that AI fluency across the team is crucial. The thing making all of this possible? Zapier MCP and SDK. It's taken our building to new heights over the past 2 months.

  • No alternative text description for this image

Great stuff Tracy St.Dic. I’m curious, are you using the new Ashby MCP to do the daily sweep? Or Zapier?

Like
Reply

More power to you Tracy St.Dic , glad to see leader being intentional for upskilling their team.

Love this Tracy! We've been doing similar things at Workfully, including some build competitions which have brought some amazing internal tools to life!

The part that stood out to me wasn’t the tooling. It was the decision to create protected time for building. Most organizations say innovation is important, then measure people entirely on execution. The result is that experimentation gets squeezed into whatever time is left. When leaders deliberately create space for teams to surface friction, test ideas, and improve the work itself, capability compounds much faster than any single tool ever could.

Like
Reply

Shoutout to the leaders who actually give their team time to learn the tools being pushed on them! Love it.

Does this reduce your fraudulent candidates

Like
Reply

Love this, hackathon, build days are great, thanks for sharing your approach at Zapier

👏 Amazing Tracy St.Dic! Would love to know more about your LinkedIn Recruiter work around - it’s been a sore spot for us as recently as well!

I cannot tell you how much I love this.

Love it! Well done on prioritizing this!

See more comments

To view or add a comment, sign in

Explore content categories