check_resume
ChatGPTCheck resume text before it is saved: what changed against the seeker's uploaded resume (added, reworded, removed, moved lines), every number, skill or name in a changed line that their stored resume and profile don't contain (flagged "verify", for the seeker to confirm or take out, never to fill in), and, for a posting (give its slug), which of its skills the version shows, which are in their profile but left out, and which they have no evidence for. Under an employer's AI policy it lists the lines in new wording for the seeker to write themselves. Show the seeker the changes and every flag; save_resume takes the review_hash it returns. Only when they have shared their full profile with this assistant.
get_company
ChatGPTAn employer's open data and AI roles plus its hiring record: how many roles are open, how many we first saw in the last 30 days, the median days open, and the mix by role category.
get_connections
ChatGPTWho the signed-in seeker knows at an employer, from the LinkedIn connections they added to their profile: names, LinkedIn profile links, positions and why each is a good first ask (people doing similar work first, then recruiters). Give a posting's slug to rank people for that role. Only first-degree connections; it never contacts anyone. Suggest a short ask the person can send themselves.
get_job
ChatGPTOne posting's details: our record of when we first saw it and whether it is still listed, pay and working pattern where the posting states them, for US postings what comparable postings stated as pay, responsibilities, the description, and the apply link.
get_profile
ChatGPTThe signed-in seeker's full application profile, only when they have shared it with this assistant: their resume (text, roles with dates and descriptions, education, skills), links, job preferences, the cover letters and answers saved for their applications, and resume versions saved earlier. Use it to judge fit and write in their own words. Contact details, demographic answers and work authorisation are never included. When it isn't shared, it says where the seeker turns it on.
get_profile_summary
ChatGPTThe signed-in seeker's job preferences: role categories, tools, work setting, locations and work to avoid. Contact details, demographic answers and the resume are never included.
list_applications
ChatGPTThe signed-in seeker's applications board: saved jobs, and tracked applications with their stage, next step and follow-up date.
list_categories
ChatGPTThe role categories we classify data jobs into, by what the job actually involves rather than its title.
list_updates
ChatGPTWhat changed in the last 14 days in the signed-in seeker's watched searches, saved jobs and applied-to jobs: new postings, postings that closed, went missing or were reposted, and changes to a saved job's title, pay, work setting or location. Also follow-ups due on applications sitting at applied, each with a drafted note for the seeker to edit and send themselves (never send it for them), the seeker's alert settings, and the watched searches and whether each sends email.
match_jobs
ChatGPTOpen data and AI jobs ranked against the signed-in seeker's preferences, with the reasons each one fits and anything to check.
prepare_application
ChatGPTDraft the signed-in seeker's application for one posting: a cover letter and answers to the employer's free-text questions, written from their profile and resume. Questions on the employer's form we know are included; add any others the person shares. The drafts are saved for them: the posting's page shows them, and our Chrome extension fills them into the employer's form after the person checks each one. Pass the person's own edits in answers or cover_letter to save their wording. It never applies; the person reviews and submits. Contact details, demographic, work-authorisation, pay and consent questions are left to the person. When the employer has a policy on candidates using AI (ai_policy), nothing is drafted from scratch: the person writes first drafts, you pass them in my_drafts, and they come back refined.
prepare_interview
ChatGPTAn interview prep pack for one application the seeker tracks, usually once it reaches the interview stage. It returns the employer's interview rules first (show them before anything else), what the role asks for, which of its skills the seeker's profile shows and which it doesn't, their experience to draw stories from (only when they have shared their full profile with this assistant), and the employer's hiring record. From it, write a question bank (technical, behavioral and role questions), each mapped to one of their stories by its label or to none, and honest framing for the gaps: never invent experience they don't have. Offer a mock interview: one question at a time, wait for their answer, then give specific feedback. Save the bank with questions, gaps and notes to keep it on the application; each save replaces what was saved. Prep is for before the interview, never during it.
review_application
ChatGPTLay out the signed-in seeker's application for one posting exactly as submit_application would send it: every field on the employer's form with the value that goes out (contact details from their profile, saved drafts, their own answers), the resume file, and anything still blank. Show the person all of it, word for word, before asking to send. Questions marked person_answers (legal terms such as arbitration, AI-policy acknowledgments, EEO and other self-identification, work authorisation, visas, consent) are never filled for them: ask each one with its options as written and pass their own answer back in answers. Call again with answers to apply their edits; a new payload_hash comes back each time anything changes. Only postings whose employer takes applications through the board can be sent from the chat; for others it returns send_from_chat false with apply_url, the employer's own application page, and extension_url, our Chrome extension that fills that form in for them. When fill_in_browser is true, fields is the fill plan for that page: if you can use a browser, open apply_url, fill each question by its label with value (value_label for a choice), leave person_answers questions to the person, attach the resume file named in resume (or ask the person to attach it), and show the person the filled form. When fill_plan is answer_sheet we don't hold that form: match each answer to the page's question that asks for it, and ask the person every question on the page that isn't on the sheet. Press the employer's submit button only after they say "yes, submit" to it, then call update_application with stage applied. Stop and hand the page to the person at any CAPTCHA or sign-in; never get around one.
save_job
ChatGPTSave a posting to the signed-in seeker's saved jobs, the same list as the Save button on the site. Saving again changes nothing.
save_resume
ChatGPTSave resume text to the signed-in seeker's profile as a new version: a general rewrite, or one tailored to a posting (give its slug). Only when the seeker asks, after check_resume on that exact text and the seeker has seen its changes and flags (pass its review_hash), and only when they have shared their full profile with this assistant. Each call adds a version; their uploaded resume stays their main one, and they manage versions on their profile page.
save_search
ChatGPTSave a search to the signed-in seeker's watched searches, so new matching postings show in their updates. Takes the same filters as search_jobs. Email alerts stay as they are: a new watch starts with email off, and the seeker turns email on from their updates page.
search_jobs
ChatGPTSearch open data and AI job postings. All filters combine (AND). Results are newest first, with our first-recorded date and listing status for each.
submit_application
ChatGPTSend the signed-in seeker's application to the employer, exactly as the last review_application showed it. Only call this after the person has seen that review in full and said "yes, submit" to it in this conversation; never on your own judgement, never for several postings at once. Pass the same answers and the payload_hash from that review: if anything changed since (the posting, the form, their profile, or an answer), nothing is sent and you review again. One application per posting: a posting already applied to is never sent twice. On success the application is tracked as applied.
update_alerts
ChatGPTTurn change alerts on or off for one saved job or for all of them, and set how many days an application sits at applied before list_updates suggests a follow-up (null turns those reminders off). Alerts show in list_updates and on the updates page; follow-up notes are drafts the seeker sends themselves. Only the fields given change. Use only when the seeker asks.
update_application
ChatGPTTrack a posting in the signed-in seeker's applications, or change a tracked one: its stage, next step, follow-up date or notes, and what happened (outcome), whether they were referred, and the resume version they sent, only as the seeker tells you. Only the fields given change. It never applies to the job; applying happens on the posting's page.
update_preferences
ChatGPTChange the signed-in seeker's job preferences, the ones match_jobs and fit scores use: role categories, tools, work setting, places and things to avoid. Only when the person asks. Each field given replaces that preference whole, so read get_profile_summary first and keep what they still want; fields left out stay as they are. Contact details, resume and application answers are not changed here.
verify_job
ChatGPTCheck whether a job is real before anyone spends time applying: give any job link (the employer's own careers page, LinkedIn, Indeed, Glassdoor or our site) and get our record of the employer's own posting: when we first saw it, whether it is still on the employer's site, how often it was reposted, what it pays, and how the employer's postings usually end. Free, no sign-in. For a job board link that doesn't name the job (Indeed), also pass the title and company as the listing shows them, and the location when the employer lists the title in several cities.