When a job board, a LinkedIn dropdown, or an employer survey asks which best describes your job role, it is not hunting for the title on your badge. It wants a category other people already search for. That's the entire game.
Pick the family that matches the work you get paid to do. Then keep that same family on LinkedIn, on applications, and in every career quiz you take.
Do hybrid jobs make those lists feel blunt?
They do. You still pick one primary bucket. Explain the mix in your headline and summary instead, where nobody's running filters.
A sourcer usually filters by job family first, then maybe opens a few summaries. File a software lead under Management and that profile never shows up in the engineering list they actually pull that morning. Not because the work isn't engineering. It's engineering in the tasks, engineering in the stack, engineering through and through, just not in the dropdown.
What that question is sorting you into
Three workflows reuse basically the same prompt, so your answer has to survive all three. Job boards need a function filter. LinkedIn needs an experience title people can search. Applicant tracking systems map you to whatever job family sits on the requisition.
Call yourself a Partner on Slack if you want. The market still looks for sales, customer success, or account management. Those are three different filters. Mixing them costs you views.
A lot of the serious taxonomies trace back to U.S. statistical systems. The O*NET program describes occupations with tasks, skills, and knowledge, and it draws on occupational data from agencies such as the Bureau of Labor Statistics. HR software often borrows that logic, even when the screen just says "Job function."
Common role families on surveys and job sites
Labels change from form to form. The clusters underneath don't.
| Role family | Titles that usually belong | Where platforms file it |
|---|---|---|
| Healthcare | Nurse, nurse practitioner, medical assistant, therapist | Healthcare, health care practitioner |
| Technology | Software engineer, IT support, systems admin, data analyst | Information technology, engineering |
| Engineering (non-software) | Mechanical, electrical, civil, manufacturing engineer | Engineering, manufacturing |
| Business and finance | Accountant, financial analyst, underwriter | Finance, accounting |
| Sales | Account executive, sales development, retail supervisor | Sales |
| Marketing | Brand manager, content marketer, demand generation | Marketing, advertising |
| Human resources | Recruiter, HR generalist, people operations | Human resources |
| Education and training | Teacher, instructional designer, corporate trainer | Education, training |
| Operations | Supply chain analyst, project coordinator, office manager | Operations, administrative |
| Management | Director or VP when the form has no function field | Management, executive |
Some forms ask for both a function and an industry. If so, set function to the work and industry to the employer type. A hospital software engineer is still technology, not healthcare. Unless the only options are industry names, anyway.
How LinkedIn, job boards, and ATS read your pick
LinkedIn treats the Experience title as a high-weight search field, which makes the exact words matter more than most people assume. The headline under your name is the longer pitch. LinkedIn's own title guidance pushes a role people can recognize, not a slogan.
Thing is, job boards are pickier. Many boards and company career sites open with category checkboxes. Sit in "Other" and you sit nowhere.
ATS matching is messier. Some systems score keywords across your resume. Others map you to a job family before any recruiter opens the file, which means a mismatched family can bury a strong resume before a human ever sees it.
Watch these traps:
- Picking Management because you have direct reports, when the open jobs are filed under your craft
- Using a unique internal title the market never types
- Switching families from one application to the next
- Stuffing AI into a title you can't defend in an interview
How to choose the best description
Work through these in order, and don't skip the first one. It's the boring step, and it decides everything after it.
- Write one sentence of duties, not a title. "I diagnose production incidents and ship backend fixes" beats a nickname.
- Circle the occupation a stranger would search. Use the O*NET career tools if you're stuck between two names.
- Match that occupation to the closest dropdown on LinkedIn and on the job board you use most.
- Put the searchable title in Experience. Save the nuance for your headline and About section.
- Repeat the same family on surveys, career quizzes, and resume headers.
- If a large-employer application uses its own job family or code list, follow that codebook for that form.
Clear duties help more than clever labels. Promova's notes on role language make the same point from the employer side: vague titles pull the wrong applicant pool.
When two categories both look right
Split jobs are the usual headache. A product designer who runs the research. A nurse who implements the records system. Or the teacher quietly building the district's dashboards.
Turns out the tie-breaker is the work you'd be hired to repeat next year, not the project that ate last Tuesday.
If most of your week is clinical and a slice is systems work, healthcare is the honest family. Put the systems project in the bullets. If you're hunting informatics roles instead, flip it: technology as the family, clinical background in the summary. And don't run both stories at full volume on the same profile, because recruiters skim.
People stretch into new-sounding titles because postings mention new tools. Stretching only works if you can point to tasks. Using a chatbot on the side doesn't make you a machine learning engineer. If your real occupation is marketing, stay in marketing and name the tools under skills.
Occupation data versus the title you wish you had
ONET is not a job board. It's the federal occupation database behind a lot of career quizzes and labor statistics. The [ONET database](https://onetcenter.org/database.html) is updated on a regular cycle and includes skills, knowledge, and work activities, not just job names.
Career quizzes on hiring platforms often map your answers onto that kind of taxonomy. That's why "which best describes your job role" shows up in onboarding surveys and skills assessments, not only on public profiles.
You don't need to memorize occupational codes. You do need a title a codebook would recognize. "Content strategist" maps. "Brand wizard" does not.
Self-reported polls are the sloppy cousins of this system. People pick whichever option sounds most senior. Matching tools don't care about senior-sounding. They care about collision with a requisition.
If you're the one writing the survey
Offer function and level as separate fields. Don't force a single list that mixes intern with healthcare.
Write the role so people and software both get it
Once the category is set, describe the job like a human who ships work. Big Interview's samples for describing a current job keep a short scope line, then results. That pattern survives ATS parsing and recruiter skimming.
Most profiles lead with adjectives and hide the verbs, to be honest. Flip that.
"I own inbound pipeline for mid-market SaaS and beat quota last year" reads as sales. "I coordinate care plans for a 24-bed unit" is nursing, plainly. And "I maintain Python services that price claims" is technology, even if your HR system says business analyst.
Keep the Experience title boring on purpose. Add proof in bullets. If you want extra keywords, put occupations in the headline with care so search still finds a real job name in the first line.
The category should match. The family should match. The bullets can change from board to board, since each site parses text a little differently. Tailor the sentence, not your occupation.
FAQ
What if none of the dropdowns fit? Pick the closest function, then clarify in a free-text title field if the form has one. "Other" is a last resort. It hides you.
Should my LinkedIn title match the survey box? The family should match. The exact string can differ. LinkedIn can say "Senior Recruiter, Technical" while a survey only offers Human Resources.
Do I pick the emerging title or the standard one? Use the standard occupation for the category. The newer title can go in the headline, but only if you already do that work. Interviews will test it.
*How do ONET labels compare with HR software?* ONET describes occupations for statistics and counseling. HR tools add employer-specific job families and skills. Start with the occupation, then accept the employer's family when you apply.
Can I choose different roles on different apps? You can, and it usually backfires. Inconsistent families look like a messy history. Keep one primary occupation. Tailor bullets, not identity.
Open LinkedIn and the last job board where you keep a profile. Compare the role family on each. If they disagree, fix the weaker one today so the next search lands on a single category you can defend.