A hiring intake meeting can sound settled until someone writes the job description. The founder remembers a backend engineer. The engineering lead remembers someone who can own infrastructure. The recruiter has written down both, along with a salary range nobody quite approved.

Better notes preserve that disagreement. A shared draft gives you a chance to resolve it while everyone is still there.

That is the useful hiring experiment in **Claude Meetings**: ask it to build the role brief during the conversation, then have the team correct what it produces. After the call, you can review that brief and use a separately configured Kit MCP connector to create a job draft. The meeting artifact and the hiring record are two distinct steps.

## Put the disputed brief on screen

Anthropic [announced Claude Meetings on November 12](https://claude.com/resources/articles/claude-meetings), with a beta for Team and Enterprise customers using Google Meet. Claude joins as a visible participant. You can address it by voice or meeting chat; it responds in writing by default and can build documents and whiteboards during the call.

For hiring intake, the interesting output is a document everyone can inspect before leaving. A polished recap sent later gives each person another interpretation to read. A live role brief gives them something specific to challenge.

Consider an illustrative intake for a backend engineer. The founder wants faster product delivery. The engineering lead wants fewer interruptions from production incidents. The recruiter needs to know which experience to screen for. Those goals can describe one job, but only if the team agrees on priorities.

Ask Claude to maintain a brief with four sections: expected outcomes, essential experience, constraints, and open questions. Keep it short enough to read together. As the conversation develops, ask it to update the brief and point out statements that conflict.

You might reach this point:

| Topic | Working brief | Correction the team needs to make |
|---|---|---|
| First priorities | Ship backend features and improve reliability | Which takes priority when they compete? |
| Infrastructure | Own the production platform | Own it alone, or work with an existing owner? |
| Experience | Rails and Kubernetes required | Is Kubernetes essential, or simply part of today's stack? |
| Compensation | Salary range discussed | Who approves the range, and on what employment basis? |
| Location | Remote | From which countries, and with what overlap? |

The value is in the last column. A brief that labels an unresolved salary range as approved has made the meeting less useful, however fluent the writing.

Give one person responsibility for checking each open item. If the infrastructure requirement disappears after discussion, remove it from the agreed requirements. If nobody can approve compensation in the room, keep it open. You should leave with a brief that reflects the decisions you actually made.

## Try it in an internal intake first

Claude Meetings requires organization setup. To add Claude to a meeting, connect your own Google Calendar. Anthropic's [setup guide](https://support.claude.com/en/articles/18325154-use-claude-meetings) describes the path: the organization enables Google Calendar, members connect their calendars, then open a meeting and choose **Add Claude**. Team has the feature enabled by default; an Enterprise owner must enable it.

Start with an internal hiring intake. Everyone on the call should agree to transcription; the meeting page is accessible to invited organization members, whose access is separate from access to the eventual Kit record. Check your organization's external sharing settings before inviting Claude to calls with guests: Anthropic's announcement and help documentation describe different defaults for external participation. The beta is unavailable for organizations using Zero Data Retention, HIPAA-ready configurations, or customer-managed encryption keys.

A useful first prompt is specific about the document and its limits:

> Build a working brief for this role as we discuss it. Use four sections: outcomes, essential experience, constraints, and open questions. Separate explicit decisions from suggestions. Flag conflicting requirements and ask us to resolve them. Do not turn a discussed salary range into an approved one. Before we finish, show the brief and list the decisions still missing an owner.

Then read the result together. Ask the recruiter whether it supports a credible job description, and the hiring manager whether it describes work someone can reasonably own. Correct the draft before the conversation moves on.

Anthropic documents a saved recap, outputs and transcript after the meeting; audio is not saved. That gives you material to revisit, but a transcript is still evidence of what people said, not proof that every proposed requirement became a decision. This workflow is a proposal based on documented capabilities, not a hands-on test of the beta.

## Move the reviewed brief into Kit after the call

Once the brief is settled, move to the hiring system. **This is a separate post-meeting workflow through Kit's MCP connector**, not a claimed live Claude Meetings integration or an automatic transcript import.

If you use Claude with Kit, follow [Connecting AI Assistants](/docs/connecting-ai-assistants) and add `https://startupkit.app/api/v1/mcp` as the account connector. Sign in through Kit's browser authorization, select the correct account and grant the Hiring access you need. `hiring_read` permits reads; `hiring_write` permits writes within your existing role permissions. Review Claude's tool controls before enabling writes.

Start by asking Claude to read matching postings. That prevents an intake for an existing role from becoming an accidental duplicate. Then give it the reviewed brief and ask for proposed fields:

> Use this reviewed intake brief to prepare a Kit job draft. Read matching existing postings first. Show the proposed title, description, location, remote eligibility and compensation fields. Keep unresolved items separate; do not invent missing values. Wait for my approval before creating or updating anything. Do not publish the posting or add reviewers.

Kit's `hiring_create_job_posting` creates a **draft** and returns an edit link. It requires Hiring administrator access and an active subscription as well as write permission. Open that link, review the candidate-facing copy and publish it in Kit when it is ready. Keep reviewer assignments for a separate approved step, since adding reviewers can trigger onboarding emails.

For an existing posting, `hiring_update_job_posting` changes the supplied fields and leaves omitted fields unchanged. Check its status first: an existing posting may already be public. Read back the saved result, especially the description, which is replaced as a whole. The [MCP tools reference](/docs/mcp-tools-reference) explains the available operations.

## Keep interview debriefs distinct from scorecards

The same shared-document approach can help a later debrief record factual observations, disagreements and follow-up questions. It should preserve who observed what rather than collapse several interviewers into a single voice.

Have reviewers submit their own assessments independently before discussing the candidate. Kit's [reviews and feedback](/docs/reviews-and-feedback) use blind voting by default: reviewers cannot see peers' completed reviews on the review page until submitting their own. A meeting-generated consensus scorecard would defeat the purpose of collecting those separate judgments.

After reviewing a debrief summary, an authorized member can use `hiring_save_note` to attach it to the correct application under their own identity. That note is distinct from submitting a scorecard or making a hiring decision. For a fuller process, see [how to run a debrief and record a reasoned hiring decision](/blog/interview-debrief-decision-meeting-groupthink).

Begin with the next internal intake. Put the working brief in front of the people who can correct it, settle what you can, and assign the remaining questions. Then carry the reviewed decisions into the job draft. A useful meeting artifact earns its place by making the next hiring action clearer.