# Write an honest engineering hiring post on LinkedIn with GitHub Copilot

Source: https://finchreach.com/blog/github-copilot-linkedin-hiring-post
Published 2026-10-28 by Finchreach team. Tags: github-copilot, linkedin, mcp, hiring, engineering-managers.

Use GitHub Copilot agent mode in VS Code to draft a LinkedIn hiring post grounded in your real stack and work, then queue it for approval.

## The short answer

GitHub Copilot’s agent mode in VS Code can write a LinkedIn hiring post that describes the job as it actually is, because it can read the repository the new hire would work in. Connected to Finchreach, a remote MCP server for LinkedIn (MCP is a standard plug that lets AI apps use outside tools), it can queue the post with `linkedin_create_post` and later help you read the replies.

With approval mode on, which is the default, the post waits in your [approval queue](https://finchreach.com/approvals). You read it once more, approve it, and it goes live on your personal LinkedIn profile.

## Why write a hiring post from the codebase?

Most engineering job posts are interchangeable: “fast-paced”, “modern stack”, “passionate”. Good engineers skip them. The posts that work are specific: what the team is building this quarter, which problems are hard, what the stack really is, how code gets reviewed and shipped.

Those details live in the repo and its surroundings, and Copilot can read them:

- The real stack, from `package.json`, `go.mod`, Dockerfiles and CI config.
- How the team works, from the contributing guide, the PR template and the CI checks.
- What is hard, from open issues labeled performance, scaling or tech debt.
- What shipped recently, from the changelog.

An engineering manager posting from their own profile, with these specifics, reads like a person describing their team rather than a job board listing.

## How does Copilot draft and publish the hiring post?

1. Open the repository in VS Code and switch Copilot Chat to agent mode.
2. Give it the basics a codebase cannot know: title, level, location or remote policy, salary range if you publish one, and how to apply.
3. Ask it to read the stack, the contributing guide and a sample of open issues, and summarize what a new hire would actually do in their first months.
4. It drafts the post in the chat. You cut what is confidential and adjust the tone.
5. It calls `linkedin_create_post` with `Anyone` visibility, since a hiring post should reach beyond your connections. The result is `pending_approval`.
6. You approve it in Finchreach. Afterwards, Copilot can read replies in your inbox with `linkedin_get_conversations` and help you answer candidates.

> Do not let the post mention internal project names, customers or security issues just because they appear in the repo. Tell Copilot explicitly what is off limits.

## What should I ask GitHub Copilot?

> Ask your assistant: “We are hiring a senior platform engineer, remote in US time zones, salary range $X to $Y, apply via the link I will add. Read this repo’s build files, CI config, CONTRIBUTING.md and the 20 most recent open issues labeled "infra". Summarize the stack and the three hardest problems a new hire would work on. Do not mention customer names.”

> Ask your assistant: “Draft a LinkedIn post from me, the engineering manager, under 220 words. Open with the problem, not the company. One short list: stack, how we ship, what you would own. End with how to apply. No buzzwords like "rockstar" or "fast-paced".”

> Ask your assistant: “Queue the final version with linkedin_create_post, visibility Anyone, and give me the action id.”

> Ask your assistant: “A week later: list LinkedIn conversations from the last 7 days that mention the platform engineer role. Summarize each candidate’s message and draft a reply that thanks them and points to the application link. Show drafts before queueing.”

## How do I connect GitHub Copilot in VS Code to LinkedIn?

1. [Create a Finchreach account](https://finchreach.com/sign-up) and connect your LinkedIn account on the Accounts page.
2. Create an API key on the API keys page.
3. In VS Code, run “MCP: Add Server” and choose HTTP, or create `.vscode/mcp.json` as below. VS Code asks for the key the first time the server starts and stores it securely.
4. Open Copilot Chat in agent mode and check that the Finchreach tools are listed in the tools picker.
5. More detail: the [GitHub Copilot guide](https://finchreach.com/guides/github-copilot), the [integration page](https://finchreach.com/integrations/github-copilot) and the [docs](https://finchreach.com/docs).

.vscode/mcp.json:
```json
{
  "inputs": [
    { "type": "promptString", "id": "finchreach-key", "description": "Finchreach API key", "password": true }
  ],
  "servers": {
    "finchreach": {
      "type": "http",
      "url": "https://mcp.finchreach.com/mcp",
      "headers": { "Authorization": "Bearer ${input:finchreach-key}" }
    }
  }
}
```

Note the top-level key is `servers`, not `mcpServers` as in many other clients. Because the key comes from a prompt, this file is safe to commit: each teammate enters their own key. On Copilot Business and Enterprise, administrators can restrict or disable MCP servers, so ask your admin if the tools do not appear. Source: [VS Code MCP configuration reference](https://code.visualstudio.com/docs/agents/reference/mcp-configuration), as of October 2026.

## What makes a LinkedIn hiring post work?

- Specific work over adjectives: “move our job queue off cron” beats “solve hard problems”.
- The salary range, where you are allowed or required to share it.
- One clear way to apply. Do not ask people to comment “interested”.
- Your own voice. You are the person they will work with.
- A short follow-up later, such as what the first interviews taught you, rather than reposting the same text.

## Is it risky to post a job on LinkedIn through an agent?

> Automating a personal LinkedIn account carries risk under LinkedIn’s User Agreement. Finchreach’s approval queue and a human pace lower that risk; they do not remove it.

A single hiring post is a normal thing for an engineering manager to publish; what matters is that you read it before it goes out. The bigger risk is content: a draft built from a repository can leak things the repo knows and the public should not. That is what the approval step is for.

## Frequently asked questions

Can Copilot post the job on our company page or LinkedIn Jobs? No. Finchreach publishes text posts on your personal profile only. Link to your careers page or job listing from the post.

Can it attach the team photo? No, posts are text only.

Can it reach out to candidates directly? `linkedin_search` with the people vertical finds profiles and `linkedin_send_invitation` sends an invitation with a note of up to 300 characters, each after approval. Keep it personal and low volume. For handling incoming invitations, see [reviewing invitations with Claude](https://finchreach.com/blog/claude-linkedin-invitation-review).

Is this the same as Microsoft Copilot? No. Microsoft’s Copilot apps are covered in [the Copilot Studio post](https://finchreach.com/blog/copilot-linkedin-monday-briefing).