> For the complete documentation index, see [llms.txt](https://careers-docs.mapademics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://careers-docs.mapademics.com/readme.md). # Mapademics Careers Mapademics Careers helps career-services teams take applicants from intake to coaching to matched job postings, all powered by skills. Mapademics Careers is the workspace where career-services teams move applicants from intake to coaching to a matched job. Resumes become structured profiles. Profiles get scored and coached. Profiles get matched against real postings — both the ones your team uploads and the ones Mapademics curates for your organization. These docs are written for the staff inside an organization that uses Careers. If you work in career services, you're in the right place. *** ## What you'll find here | Section | What it covers | | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Getting started](/getting-started/welcome.md) | What Careers is, who it's for, and a five-minute tour of the app. | | [Working with applicants](/working-with-applicants/adding-applicants.md) | The day-to-day: adding applicants, working through their profile, coaching with the Skills Report, and matching them to jobs. | | [Jobs & employers](/jobs-and-employers/jobs.md) | Managing the job and employer side of the workspace. Jobs live in two lists — your team's [Uploaded Jobs](/jobs-and-employers/uploaded-jobs.md) and the curated [Public Jobs](/jobs-and-employers/public-jobs.md) feed — while [Employers](/jobs-and-employers/employers.md) combines both. | | [Setting up your workspace](/setting-up-your-workspace/inviting-your-team.md) | One-time setup tasks: inviting teammates, embedding the Resume Upload Widget on your site, and bulk-importing data. | | [Reference](/reference/glossary.md) | Glossary, the proficiency scale, the seven coaching axes, and how to ask Arlo or contact Support. | *** ## A few key ideas A handful of concepts come up across the whole product. Skim these and you'll have the vocabulary for everything else. * **Applicants and resumes.** Each applicant has one or more resume versions; the **active resume** is the one Careers analyzes right now. See [The applicant profile](/working-with-applicants/applicant-profile.md). * **Skills come from a shared library.** Every skill on a resume, on a job, or in a Skills Report references the **Mapademics Skills Library** so comparisons stay meaningful. Levels follow a five-point scale — see [Skill proficiency levels](/reference/proficiency-levels.md). * **Public vs Uploaded.** Both jobs and employers split between a Mapademics-curated **Public** feed and **Uploaded** records your team adds. Jobs are split across two sidebar items — **Uploaded Jobs** and **Public Jobs** — while employers stay in one list with a **Source** column. The two behave differently. See [Jobs — Public vs Uploaded](/jobs-and-employers/jobs.md). * **Coaching is opinionated.** Every resume gets scored against seven coaching axes. The score and the per-axis feedback are the foundation of the [Skills Report](/working-with-applicants/coaching-skills-report.md) you share with applicants. *** ## Need help inside the app? Press **⌘K** (or click **Help…** at the top of the sidebar) to open [Arlo](/reference/arlo.md), the in-app AI assistant. For anything Arlo can't answer, see [Support](/reference/support.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://careers-docs.mapademics.com/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.