Automating Recruiting Workflows with Claude Desktop: A Case Study
A developer has shared a detailed case study of automating recruiting workflows using Claude Desktop. The system handles the repetitive first layer of recruiting for a global customer support operation where a single job post can generate hundreds to over a thousand applications.
Technical Setup
The entire system runs on a single Windows workstation with this configuration:
- Claude Desktop
- Chrome + Claude browser extension
- Google Calendar integration via MCP
- One carefully written prompt
The technical setup took a few hours, but prompt engineering required four days of work to handle edge cases.
Workflow Details
The agent runs every two hours and performs these tasks:
- Logs into the recruiting platform
- Reviews new candidate profiles
- Scores candidates based on experience and communication skills
- Checks Google Calendar for free time
- Messages qualified candidates
- Schedules Zoom interviews automatically
Edge Cases and Challenges
Most of the four days of prompt engineering was spent fixing these edge cases:
- Candidates with no availability
- Duplicate outreach
- Time zone mismatches
- Recruiting platform UI quirks
- Infinite scrolling pages
- Random modals covering buttons
The developer noted an interesting behavior: when Claude couldn't click a button properly in the browser, it started injecting JavaScript into the page to trigger the action, such as document.querySelector('.apply-btn').click(). This was not explicitly instructed but emerged from the agent's problem-solving.
Model Comparison
Three models were tested:
- Haiku → not strong enough for complex browser workflows
- Opus → great but too expensive for repetitive tasks
- Sonnet 4.6 → the sweet spot with reliable reasoning, good UI navigation, and affordable enough to run every two hours
Limitations and Results
The system isn't perfect. Claude Desktop occasionally crashes, and sometimes the browser extension randomly asks for re-authentication mid-task. However, after four days of refinement, the workflow handles about 95% of scenarios correctly.
The developer's key lesson: "Don't try to write the perfect prompt. Write a basic one, watch it fail, then patch the failures."
Despite the limitations, this automation replaces hours of manual recruiting work per day. The developer has shared a prompt template on GitHub for others to adapt for their own recruiting platforms.
📖 Read the full source: r/ClaudeAI
👀 See Also
Using Claude with MCPs for Automated B2B Outbound Campaigns
A Reddit user shares their workflow using Claude with Model Context Protocol (MCP) servers to automate B2B outbound campaigns, replacing Clay with custom API integrations for lead discovery, enrichment, verification, and email sending.
Building a Persistent Personal OS for Claude: Psychology Profile, Goals, and Live Context Injection via Notion + Shortcuts
A developer built a persistent Personal OS in Notion that injects a compressed 800-word psychological profile, goals, relationships, and live context (location, time, calendar, weather) into every Claude API call via iOS Shortcuts, with a nightly debrief loop to keep context fresh.
Claude + MCP Builds Running Routes, Syncs to Garmin Watch
A Reddit user hooked Claude up to a route builder via MCP and Garmin API. Claude finds flatter routes in hilly SF that the runner missed for a year. Routes are viewable, adjustable, and push directly to the watch.
Claude Code Agents Orchestrator Pipeline: Work Queues, Agent Spawning, Verification Gates
A Reddit post from r/clawdbot details how Claude Code agents operate an AI-run store, handling design, marketing, QA, and ops 30 times daily. It links to Episode 9 of a blog series that explains the orchestrator pipeline in production, including issues not shown in demos.