---
name: company-jobs-jobs
description: "Step-by-step job recipes for the Company Jobs Finder MCP server: Find company jobs and careers; Rank company jobs for profile; Brief on one job and tailor resume. Use when the user asks things like \"What jobs is Stripe hiring for right now?\" or \"I'm a senior backend engineer with 7 years of Go and Postgres and I'm open to remote. Which jobs at Ramp, Linear and Supabase fit me best?\""
license: MIT
---

# Company Jobs Finder jobs

Each section below walks through one job with the tools of the `company-jobs` MCP server. The same recipes are MCP prompts (prompts/list) on `https://api.openkrill.app/gateway/mcp`.
Connect the server at `https://jobs.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Find company jobs and careers

Job: Find company jobs and careers, with the Company Jobs Finder MCP server.

Use the `find_company_jobs` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "What jobs is Stripe hiring for right now?"

Steps:
1. Call `find_company_jobs` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `companies`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"companies":["Stripe"]}`
4. For the request "What jobs is Stripe hiring for right now?", a correct answer looks like this: One company entry, status ok, company Stripe, source Greenhouse, up to 10 jobs with title, locations and applyUrl, moreAvailable true.
5. Follow the server's own rules:
   - Use find_company_jobs when the user asks about open jobs, hiring or roles at specific companies.
   - Pass company names as the user wrote them.
   - When the user names a kind of company instead ("startups", "AI labs"), pick up to five well-known companies of that kind and say which ones you checked.
   - Link each job's applyUrl.
   - A not_found company publishes no board on Greenhouse, Lever, Ashby, Workable or SmartRecruiters; suggest its own careers page instead.
   - Show each job's score with its whyFit and gaps and say the ranking is a rule-based match, not a hiring prediction.
   - Present which terms are present and missing, the example search string and the narrative tips, and say add only what is true.
   - The tools return facts; you write any resume or profile text, and only from what the user told you.
   - Do not look up or contact people at the company.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `find_company_jobs`).

## Rank company jobs for profile

Job: Rank company jobs for profile, with the Company Jobs Finder MCP server.

Use the `rank_jobs_for_profile` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "I'm a senior backend engineer with 7 years of Go and Postgres and I'm open to remote. Which jobs at Ramp, Linear and Supabase fit me best?"

Steps:
1. Call `rank_jobs_for_profile` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `companies`, `targetTitles`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"companies":["Ramp","Linear","Supabase"],"targetTitles":["Backend Engineer"],"recentTitles":["Senior Backend Engineer"],"yearsExperience":7,"skills":["Go","PostgreSQL"],"openToRemote":true}`
4. For the request "I'm a senior backend engineer with 7 years of Go and Postgres and I'm open to remote. Which jobs at Ramp, Linear and Supabase fit me best?", a correct answer looks like this: Ranked jobs, best first, each with a score, a fit of strong, possible or weak, a levelFit verdict, whyFit reasons, gaps and an applyUrl, plus one boards entry per company.
5. Follow the server's own rules:
   - Pass company names as the user wrote them.
   - When the user names a kind of company instead ("startups", "AI labs"), pick up to five well-known companies of that kind and say which ones you checked.
   - Link each job's applyUrl.
   - A not_found company publishes no board on Greenhouse, Lever, Ashby, Workable or SmartRecruiters; suggest its own careers page instead.
   - When the user wants to know which jobs suit them, call rank_jobs_for_profile with the profile they gave you (target titles, recent titles, level, years, skills, locations); never invent profile details, ask for what is missing.
   - Show each job's score with its whyFit and gaps and say the ranking is a rule-based match, not a hiring prediction.
   - Present which terms are present and missing, the example search string and the narrative tips, and say add only what is true.
   - The tools return facts; you write any resume or profile text, and only from what the user told you.
   - Do not look up or contact people at the company.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `rank_jobs_for_profile`).

## Brief on one job and tailor resume

Job: Brief on one job and tailor resume, with the Company Jobs Finder MCP server.

Use the `job_fit_brief` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "How should I tailor my resume for the senior backend engineer job at Stripe?"

Steps:
1. Call `job_fit_brief` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `company`, `job`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"company":"Stripe","job":"Senior Backend Engineer"}`
4. For the request "How should I tailor my resume for the senior backend engineer job at Stripe?", a correct answer looks like this: Status ok with the job, its level and level signals, mustHave and niceToHave lists, keywords, stated facts and a tailoring checklist, or job_not_found with the closest titles.
5. Follow the server's own rules:
   - Pass company names as the user wrote them.
   - When the user names a kind of company instead ("startups", "AI labs"), pick up to five well-known companies of that kind and say which ones you checked.
   - Link each job's applyUrl.
   - A not_found company publishes no board on Greenhouse, Lever, Ashby, Workable or SmartRecruiters; suggest its own careers page instead.
   - Show each job's score with its whyFit and gaps and say the ranking is a rule-based match, not a hiring prediction.
   - For one job, call job_fit_brief and turn its must-haves, level signals and tailoring checklist into advice in your own words; credit the checklist as general recruiter practice, not a guarantee.
   - Present which terms are present and missing, the example search string and the narrative tips, and say add only what is true.
   - The tools return facts; you write any resume or profile text, and only from what the user told you.
   - Do not look up or contact people at the company.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `job_fit_brief`).