I Hired My First Engineer Without Leaving a Claude Chat

Hiring your first engineer usually means five tabs: a website builder, a form tool, a spreadsheet, your inbox, your calendar. Every handoff between them is a place to lose a candidate.

I wanted to see how far I could get without ever leaving Claude. Turns out: the whole way. A careers page built and published, applications captured, resumes screened and ranked, interview invites drafted and scheduled — all in a single conversation. Claude drives Sitelas through its MCP connector, and reaches into your Google connectors in the same breath.

Here's exactly how it works.

What an MCP connector actually is (30-second version)

Claude can connect to outside tools through something called MCP connectors. Once you add one, Claude can do things in that tool on your behalf — not just talk about it.

You probably use a few already: the Google Drive, Gmail, and Calendar connectors let Claude read your files, draft emails, and schedule events. Sitelas has one too. Add it, and Claude can design websites, publish them, and read your form submissions — all from chat. That's what turns this from "Claude gives me hiring advice" into "Claude runs my hiring pipeline."

Step 1: Connect Sitelas to Claude

This is the only setup, and it takes about a minute:

1. Open Sitelas in Claude's connector directory and choose Add — one click.
2. On Claude Code or Claude Desktop, which read a config file instead, use this URL: https://sitelas.com/api/mcp
3. Sign in to Sitelas when prompted — that's it. Start chatting.

While you're in there, switch on the Gmail and Google Calendar connectors too — we'll use both later. From here, everything happens by just asking.

Step 2: Ask Claude to design and publish the careers page

You describe the page in plain language:

"Using Sitelas, build and publish a careers page for my startup, Northwind. We're hiring a founding backend engineer. Modern, technical, confident tone. Include an application form with name, email, resume upload, GitHub link, years of experience, and a 'project you're proud of' question."

Claude picks a fitting design, customizes it to the brief, builds the form with exactly those fields, and publishes it live — then hands back the URL. No drag-and-drop, no template wrestling, no separate "now go publish" step. Want changes? "Make the hero darker." "Add a second role for a designer." You say it; Claude edits and republishes.

One message in, you have a real, branded careers page on the web.

Screenshot The published careers page, side by side with the Claude message that returned its URL.

Step 3: The applications collect themselves

There is nothing to wire up. Every application submitted through the form lands in your Sitelas inbox automatically — timestamp, source, every field, and the resume stored as a secure download link.

Ask for it whenever you want:

"Read the applications that came in for the backend engineer role."

Claude reads them straight from the inbox. If you also want each one as a spreadsheet row, add a webhook to the form and point it at Zapier or Make, then on to Google Sheets — the inbox stays the source of truth either way.

Step 4: Let the applications roll in — then ask Claude to screen them

Post the link wherever you'd normally say "email us your resume." As applications arrive, you don't open a single PDF. You ask:

"Read all the applications for the backend engineer role. Open each resume, then score the candidate 1–10 on: production Go/Rust experience, has shipped at scale, startup background, and the quality of their 'project you're proud of' answer. Give me a ranked table with a one-line reason per score, and flag your top 5."

Claude reads the submissions, opens each linked resume from the inbox, and returns a ranked shortlist with reasoning — an evening of resume-reading compressed into the time it takes to refill your coffee. Then you interrogate it like a hiring partner:

• "Compare #2 and #4 on distributed systems."
• "Who am I underrating because their resume is plain but their project answer is excellent?"

Screenshot Claude's ranked candidate table, exactly as it came back in the chat.

Step 5: Bring in your other connectors to close the loop

This is where one connected conversation beats five tabs. Gmail and Calendar are already on, so you keep going in the same chat:

"Draft warm interview-invite emails to my top 5 candidates, and suggest three interview slots next week from my calendar."

Claude drafts the emails through your Gmail connector and proposes slots through your Calendar connector. You review, approve, and you've gone from "job is live" to "interviews booked" without ever leaving the window.

The connectors compose: Sitelas captures the candidates and stores their resumes, Gmail sends the outreach, Calendar books the time. Claude orchestrates all three.

The whole pipeline, in one window

You:"Build & publish a careers page for a backend engineer role."

Claude → (Sitelas) designs + publishes it, returns the URL.

…applications come in, collected in your Sitelas inbox…

You:"Read the applications, open each resume, score and rank them."

Claude → (Sitelas) returns a ranked shortlist with reasons.

You:"Draft invites to my top 5 and find interview slots next week."

Claude → (Gmail + Calendar) drafts emails, proposes times.

Four messages. One window. A careers page, a live applicant database, AI screening, and scheduled interviews.

What makes this different

It's not that any single piece is new — it's that there are no handoffs. Normally the website lives in one tool, the applications in another, the screening in your head, the emails in a third tab, the calendar in a fourth. Every gap is friction, and a chance to drop a candidate.

Routing it all through Claude's connectors collapses that into one conversation where the context never resets. Claude already knows who your top 5 are when it drafts the invites — because it's the same chat that scored them.

	The usual patchwork (form tool + sheet + inbox)	Claude + Sitelas connector	A full ATS
Tabs / tools to juggle	4–5	1 (Claude)	1, after days of setup
Build + publish careers page	Separate tool	In chat	Yes
Auto-collected applications	Maybe	Yes → your Sitelas inbox	Yes
AI resume screening	No	Yes	Premium tiers
Email + schedule from one place	No	Yes (Gmail + Calendar)	Partially

The honest caveat

This is a lightweight, conversational pipeline — not Workday. No formal interview-stage board, no compliance reporting, no fifty-reqs-a-year scale. If you're a large org, you'll want a dedicated ATS — and that's fine. Outgrowing this means you're winning.

But for hiring your first 1–10 people — where the real pain is just having somewhere to apply, and then reading the pile — this gives you the whole loop, careers page through scheduled interviews, without leaving a chat window.

Try it

1. Add the Sitelas connector in Claude (plus Gmail and Calendar).
2. Ask Claude to build and publish your careers page.
3. When applications land, ask Claude to read the resumes and rank candidates.
4. Ask it to draft invites and find interview times.

The job that used to span five tools and a long evening now fits in one conversation.

Set up an account at sitelas.com, connect it to Claude, and let it run the whole pipeline for you.