
Use the employer’s own taxonomy before guessing. Most companies assign an internal identifier to each opening, and that string often appears in the URL of the listing, in the application confirmation email, or in the footer of the PDF description. Grab that exact value first – it is the single most reliable key for tracking an application through an applicant tracking system, and it lets you match the posting across aggregators that sometimes rename the title.
Cross-reference the identifier against at least two sources. If you found REQ-20481 on the company careers page, paste it into LinkedIn, Indeed, and Glassdoor to see whether the same role is mirrored, reposted by a recruiter, or duplicated under a slightly different title. Mismatches usually mean the requisition was reissued, which tells you the hiring manager restarted the process – useful signal about urgency and turnover.
If you would rather have the applications sent for you, JobHunter matches vacancies from 17 platforms, writes a letter for each posting, checks the resume against the posting before sending and keeps the history in one place. The first day is free and needs no card.
Filter by structured fields, not free text. A query like site:careers.example.com “REQ-” “Berlin” returns tighter results than typing a job title, because titles vary wildly (“Analyst II” versus “Senior Analyst”) while requisition prefixes stay consistent. On aggregator portals, switch to advanced filters for department, location, and posting date; keyword boxes index marketing copy and produce noise.
Track everything in a spreadsheet with columns for the employer, the requisition identifier, the source URL, the date you applied, and the recruiter’s name. Duplicate requisitions are common after mergers or seasonal hiring pushes, and a plain list of titles will not distinguish a live opening from an archived one. When a recruiter calls, quoting the exact requisition number shortens the conversation and confirms you applied to the correct team.
Job Code Search
Use the employer’s own identifier, not the job title, as your primary lookup key. Titles vary between companies and even between teams at the same company. The identifier is assigned once and stays stable in payroll, requisition, and applicant tracking systems. Copy it exactly as shown, including leading zeros and suffixes like “-R2” that mark a revised requisition.
Where to find it: on the requisition page, in the confirmation email after you apply, and on any recruiter correspondence. Cross-check all three. If they disagree, the requisition page wins because it reflects the current state of the record.
- Search internal career portals by the requisition number, not by keyword. Most portals have a dedicated field for it.
- On external boards, paste the identifier into the site’s query bar with quotes to prevent partial matches.
- Check the employer’s own careers domain first; aggregators often truncate or rewrite identifiers.
- Keep a log of every identifier you query, the date, and the result. Duplicate requisitions under different numbers are common after reorganizations.
Watch for the two-format trap. Large employers frequently run parallel numbering schemes: one for the HR system and one for the public posting. A query that returns nothing may simply mean you are using the wrong scheme. Try the format from the confirmation email before concluding the posting is gone.
If a lookup returns an expired record, check the archive or cached version of the posting page. Many career sites keep filled positions accessible by direct link for months. The archived text still gives you the requirements, the hiring team, and the location, which is useful for tailoring a future application.
- Open the employer’s careers site directly.
- Enter the identifier in the dedicated field or quoted in the query bar.
- Compare the result against your confirmation email.
- Save the page or a screenshot with the date visible.
Recruiters can pull a record by identifier in seconds, so include it in the subject line of any follow-up message. A subject like “Application status – req 4471-B” gets routed faster than a title-only subject, because the recruiter can paste the string straight into the tracking system. Keep the identifier in every reply to preserve the thread’s context.
Automate repeated lookups with a simple saved query or a browser bookmark that pre-fills the identifier field. For high-volume hunting across many employers, a spreadsheet with columns for employer, identifier, date found, status, and link turns a chaotic process into a sortable list. Review it weekly and retire entries older than ninety days, since stale identifiers waste time and mislead you about what is still open.
How to Find the Correct SOC and O*NET Code for a Job Title
Start with the SOC system when you need a broad occupational classification, then map to O*NET for granular detail. Go to the Bureau of Labor Statistics SOC directory (bls.gov/soc), use the “Search” box in the upper-right corner, and type the exact title from your posting–”revenue cycle analyst,” for example. The system returns a six-digit SOC identifier such as 13-1111 (Management Analysts) with a definition you can check against your duties. If the title is ambiguous, cross-reference the occupational definition and the “Sample of Reported Titles” list instead of relying on the label alone. O*NET’s crosswalk tool (onetonline.org/crosswalk) converts any SOC number into the corresponding O*NET-SOC identifier, which carries eight digits and adds work context, tasks, and skills data. Verify the match by comparing three to five listed tasks against your actual job description; a 70% overlap signals a solid fit.
Use O*NET’s own occupation search when the SOC match is unclear. Enter the title at onetonline.org, filter by “Bright Outlook” or specific knowledge domains if relevant, and open the summary report to confirm the O*NET-SOC number–for instance, 13-1111.00 for Management Analysts. Check the “Also Called” field, which lists alternate titles employers use; this often resolves mismatches faster than keyword guessing.
Document your final selection with the SOC number, the O*NET-SOC number, the matched title, and the date you verified it, because these classifications update periodically and an audit trail prevents rework. When two classifications seem equally plausible, choose the one whose tasks cover more of the role’s core responsibilities, not the one whose label sounds closest.
Using Vacancy Identifier Query Filters by Industry, Salary Range, and Location
Set the industry filter first, before touching any other parameter. Recruiters on LinkedIn report that narrowing by sector cuts irrelevant results by roughly 60–70%, because a “data analyst” title in fintech, healthcare, and logistics describes three different jobs with three different skill stacks. Pick the sector that matches your actual experience, not the one with the most postings.
Salary sliders deserve a specific tactic: set the minimum at 15–20% above your current compensation and leave the maximum open. Platforms like Indeed and Glassdoor populate pay bands from employer-submitted data, and those bands skew low because companies underreport. Anchoring your floor slightly high filters out roles that would waste your time in screening calls while keeping legitimately senior openings in view.
Location filters reward precision over breadth. A 25-mile radius around a specific ZIP performs better than a metro-wide selection, since most hiring pipelines cap commutes at 45–60 minutes. If remote work is acceptable, add a separate saved query with the location field cleared and the remote flag enabled – mixing both in one query produces noisy, duplicated listings.
Combine all three dimensions in a single saved query and name it by intent, for example “Senior QA – fintech – $95k+ – hybrid Boston.” Portals such as Indeed, Glassdoor, and LinkedIn let you save up to 10–25 such presets depending on account tier, and each saved combination re-runs automatically, pushing fresh matches to your inbox daily or weekly. Review those alerts once a week and delete any preset that returns fewer than three relevant results per month.
Watch for filter drift. Employers tag sectors inconsistently – a payments company might file itself under “financial services,” “software,” or “technology” – so run the same query with two or three sector labels and compare outputs. Salary fields also expire: a posting scraped six months ago may show an outdated band, so cross-check promising listings against current market data from sources like Levels.fyi or the BLS Occupational Employment Statistics.
Use exclusion filters where the platform allows them. Blocking staffing agencies, commission-only sales roles, or specific companies keeps result quality high without manual scanning. On LinkedIn, the “Exclude” option in saved alerts handles this; on aggregators, boolean operators inside the keyword box (NOT recruiter, NOT agency) accomplish the same trimming.
Measure each preset’s yield. Track how many applications from a given saved query convert to interviews – a 5–10% response rate is a healthy benchmark. If a preset produces clicks but no callbacks, the salary floor is likely misaligned with the titles it surfaces, or the sector tag is pulling adjacent industries. Adjust one variable at a time and re-measure after two weeks.
Refresh your filter set quarterly. Salary thresholds shift with inflation and demand, sector labels get reorganized by platforms, and your own target radius may change with a move or a remote-work policy update. Ten minutes of tuning every three months keeps your saved queries delivering relevant openings instead of stale noise.
Want to see the whole chain end to end — matching, letter, check, sending? It is on the main page. No card for the first day.
Related reading
which boards actually carry the roles and what auto-apply actually does with your profile.
