Consider Talent Platform

• About Consider — ## What it covers Consider is a recruiting and talent platform. Through this connector you reach the user's Consider workspace as them: the people, jobs and companies they already see in Consider, which they can now ask about in plain language and have you weigh, for example who in their talent pool fits a job, rather than only filter and list. ## How to present it Open with two or three sentences in the user's terms: what Consider is, and that through this connector they can ask about the pe
• Find companies to help recruit — Which of the portfolio's companies have open jobs that people in the talent pool fit, and who those people are. For deciding which company to approach and which candidates to bring; it needs a portfolio. Call it to read the instructions to follow and the names of the tools they use; it searches nothing itself.
• Find similar people or a cofounder — For when the user gives a person, a LinkedIn link, a resume or a pasted profile, and wants others in the talent pool who resemble them, or who would complement them as a cofounder. The person need not be in the pool; only people in the pool come back. For who fits a job, use the matching guide. Call it to read the instructions to follow and the names of the tools they use; it searches nothing itself.
• Brief the portfolio's hirers — Draft a hiring-market brief for the founders and talent leads at the portfolio's companies: where hiring is concentrated, which levels and skills are in demand, and how remote splits. The readers hire; for job seekers, use the talent newsletter guide. Call it to read the instructions to follow and the names of the tools they use; it searches nothing itself.
• Read a job posting — ## What it covers The posting's text as Consider stored it when it found the job, in plain text, together with the same job card search_jobs returns. It is what the job card leaves out: what the role does day to day, the must-haves and nice-to-haves in the company's words, the team, the interview process, benefits. ## When to use it For the specific jobs the user is asking about or weighing someone against, by their posting URL: a search_jobs result's url, or a link the user gave. It is not a
• Look up search filter values — ## What it covers Turn what the user named, such as a company, role, location or industry, into the ids a search_talent, search_jobs or search_companies filter takes. Each lookup names the search it is for, as search, the filter, as field, by its name in that search's arguments, and what the user called it, as q. The values come from where that search's page gets them: a role or company looked up for search_jobs is one with jobs behind it, the same name looked up for search_talent is anyone's.
• Match talent and jobs — For matching in either direction: who in the talent pool fits an open job, or which open jobs fit a person. Reach for it whenever the user names a person or a job, by name, LinkedIn URL or link, and wants matches. Call it to read the instructions to follow and the names of the tools they use; it searches nothing itself.
• Portfolio hiring dashboard — ## What it covers The figures for a dashboard, snapshot or overview of the whole portfolio, computed from every company at once: open jobs, how many companies are hiring, the remote share, internships, how concentrated hiring is, open jobs by industry, the companies hiring most, and which hidden companies would rank among them. It counts current openings only. Consider keeps no history, so there is no growth, decline or trend to report, and jobs that closed cannot be counted; jobs opened in the
• Look up a LinkedIn profile — ## What it covers What Consider knows about a person, behind their LinkedIn profile: the about section, every position with the description they wrote, education, skills with endorsement counts, honors, publications, patents, projects, certifications, courses, languages and interests. It is the detail a talent card leaves out. With it comes the workspace's own talent card when the person is in the talent pool: colleagues' notes, tags, projects, contacts and the permalink to open them in Consid
• Search portfolio companies — ## What it covers Search the workspace's portfolio companies: the companies whose jobs its job board shows. Returns how many match and a page of them, with what the portfolio page shows for each. With no filters, matches the whole portfolio. ## How to search Filters that take ids need lookup_search_values first, to turn what the user said into ids. A list of ids matches companies that match any of them. Headcount takes plain numbers. Slugs from an earlier result go in slugs, alone, to fetch t
• Search job postings — ## What it covers Search the open jobs of the workspace's companies: the postings Consider finds on their careers sites plus the ones colleagues posted. Returns how many jobs match and a page of them, newest first. With no filters, matches every open job. A workspace with a portfolio of companies searches the jobs of all of them; a workspace without one searches its own company's. ## How to search For which jobs fit a person, read the match_talent_and_jobs guide before searching. Filters tha
• Search talent pool — ## What it covers Search the workspace's talent pool. Returns how many people match and a page of them, best first, with everything a colleague sees on their talent card. With no filters, matches everyone in the pool. The talent pool is everyone the workspace has, however they came in: board sign-ups, job applications, ATS imports, CSV uploads or the Chrome extension. The talent network is only the people who signed up on the workspace's job board; only they have signup preferences. ## How to
• Show companies — ## What it covers Draws portfolio companies as cards in the reply, one per company slug you pass, in that order, with the facts from Consider: the name linked to the company on the workspace's job board, industries, stage, size, offices, website and open job counts. Up to 12 companies; above 5 they are drawn compact. A slug with no portfolio company behind it comes back under missing. ## What to pass For companies the user asked to see, their slugs from the search_companies result, bare. For
• Show jobs — ## What it covers Draws jobs as cards in the reply, one per posting url you pass, in that order, with the facts from Consider: the title linked to the posting, with your match percentage beside it when you pass one, company, seniority, years, location, work mode, pay, date and skills. Up to 12 jobs; above 5 they are drawn compact, without skills or details. A url with no open job behind it comes back under missing. ## What to pass For jobs the user asked to see, their urls from the search_job
• Show people — ## What it covers Draws people as cards in the reply, one per profileId you pass, in that order, with the facts from Consider: the name linked to the person in Consider, with your match percentage beside it when you pass one, then title, company, years, location, which colleagues know them, when they were added, and their LinkedIn, GitHub and verified email as links. Up to 12 people; above 5 they are drawn compact. A profileId with nobody behind it comes back under missing. ## What to pass Fo
• Draft a talent newsletter — Draft a newsletter for the job seekers in the workspace's talent network: recent postings chosen for them, employers to know, and what is being hired for. For the whole network or one member; the readers are job seekers, not the companies hiring. Call it to read the instructions to follow and the names of the tools they use; it searches nothing itself.

Schemas and invoke metadata: Directory API