
Use Boolean operators in the query bar to cut result lists by 60–80%: combine quoted phrases (“data engineer”), required terms with AND, exclusions with NOT, and alternatives with OR, then wrap synonyms in parentheses, e.g. (“python” OR “pyspark”) AND “etl” NOT “intern”. Add site: to restrict to a single board (site:linkedin.com/in “staff engineer” “kafka”) and use intitle: to target headline fields. Save each string as a named filter so you can rerun it weekly without retyping.
Filter by recency and salary before scanning titles. Set the posting window to 7 days, apply a minimum compensation threshold if the platform supports it, and sort by date rather than relevance. On boards that expose URL parameters, append ranges directly (e.g. &salary_min=90000&posted=7d) to skip the UI. For remote roles, filter by timezone overlap instead of the generic “remote” tag, which mixes incompatible schedules.
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.
Build a shortlist of 5–7 target employers and pull their openings via structured sources: company career pages, ATS endpoints (Greenhouse, Lever, Ashby), and RSS feeds where available. Monitor these with a feed reader or a scheduled script that flags new postings containing your keywords. Cross-check titles against internal leveling charts, since “Senior” at one firm maps to “Mid” elsewhere – compare scope, team size, and reporting line, not just the label.
Track every query string and its hit rate in a simple spreadsheet: columns for keywords, platform, results returned, qualified leads, and response rate. After two weeks, drop strings with under 10% qualified yield and expand the ones above 30%. Refresh saved filters monthly, because boards change taxonomies and stale parameters silently return zero results.
Job Advanced Search
Use Boolean operators and field-specific filters to cut result sets by 70–90%. On LinkedIn, type (“data engineer” OR “analytics engineer”) AND (Spark OR Flink) NOT intern and restrict results with Experience Level and Date Posted: Past 24 hours. On Indeed, apply quotes for exact phrases, parentheses for grouping, and the minus sign to strip recruiter spam. On Google, chain site:boards.greenhouse.io (“backend” OR “platform”) (“Go” OR “Rust”) location:”Berlin” to hit company career pages directly. Save each string as a preset in your browser or an ATS like Huntr; reusing vetted queries beats rewriting filters every morning by 15–20 minutes per session.
Set salary, headcount, and remote-type filters before scanning listings, because default rankings bury mid-size employers under sponsored posts. On Otta and Wellfound, toggle company size 50–500 and funding stage Series B–C; on LinkedIn, add f_TPR=r604800 to the URL for the last seven days and f_WT=2 for remote roles. Track response rates: queries returning 40–80 hits convert roughly three times better than those returning 500+. Build a weekly cadence of three saved queries per platform, and refresh keywords monthly against your application log.
Automate alerts with RSS feeds from company career pages via tools like Feedly, and route Greenhouse, Lever, and Ashby endpoints into a single inbox filter. Use the LinkedIn URL parameter keywords combined with geoId codes to skip manual location entry, and mirror the same logic in Zapier to push new postings into a Notion board with columns for fit score and deadline.
Using Boolean Operators and Exact Phrases to Filter Job Listings
Type quoted strings into the query field to lock word order and block irrelevant matches: “machine learning engineer” returns postings containing that exact sequence, while the unquoted version drags in ads about learning machines, e-learning, or engineering managers. Recruiters and applicant tracking systems index phrases literally, so quotation marks alone can cut your result pool by 40–70% on aggregator sites.
Combine terms with AND to force co-occurrence–”Python” AND “SQL” AND “remote” keeps only ads that mention all three. Use OR inside parentheses to widen a single slot without flooding the rest of the query: (“React” OR “Vue” OR “Angular”) AND “TypeScript”. This structure tells the parser to treat the framework options as one interchangeable unit rather than three loose keywords scattered across unrelated postings.
Exclude noise with NOT or the minus sign: “data analyst” NOT “sales” (or -sales in Google-style syntax) strips commission-driven listings that merely mention analytics in passing. Stack exclusions carefully–too many NOT clauses on some boards silently return zero results because the engine evaluates them against the full ad body, including boilerplate. Test one exclusion at a time and watch the count.
Wildcards cover spelling variants: analy* catches analyst, analytics, analysis, and analyzing in a single pass, while a question mark replaces exactly one character for regional spellings (organi?ation). Reserve asterisks for stems of four or more letters; shorter roots balloon into false positives like “cat” matching “category”.
Parentheses control precedence, and getting the nesting wrong quietly sabotages results. (“project manager” OR “program manager”) AND “PMP” AND (“healthcare” OR “hospital”) works; “project manager” OR “program manager” AND “PMP” does not, because AND binds tighter than OR in most engines, leaving the first phrase unfiltered. Build the query from the inside out, run it, then add layers.
Combining Location, Salary, and Seniority Filters in Job Search Queries
Set salary as a hard floor before you touch anything else. Enter the minimum figure you’d actually accept, not a hopeful range, then add 10–15% headroom so employers who post bands like “£70k–£85k” still surface when your floor sits at £75k. Pair that number with a single radius value – 25 miles for hybrid roles, 50 for on-site, or “remote only” if commuting is off the table – and save the query. A saved combination of three constraints cuts irrelevant listings by roughly 60–70% compared with location-only filtering, based on typical board behaviour.
Treat seniority as a bracket, not a single title:
- Match two adjacent levels (e.g., “Senior” and “Lead”) to catch employers who label the same scope differently.
- Exclude junior markers explicitly – add “-intern -graduate -trainee” to the query string.
- Check the years-of-experience field where the board offers one; a 5–8 year band filters harder than any keyword.
- Watch for inflated titles: a “Head of” at a 12-person startup often pays less than a “Senior Manager” at a 2,000-person firm.
Order matters more than most people expect. Apply location first because it shrinks the candidate pool fastest, then salary because compensation data is the sparsest field, then seniority last to trim the remainder. On boards that support Boolean strings, combine all three in one line – (“Senior” OR “Lead”) AND (“remote” OR “Berlin”) AND salary>=80000 – and test it against a known-good posting to confirm the syntax behaves.
Audit your saved combination every two weeks. Salary bands drift with inflation and hiring cycles, radius assumptions break when a company shifts to remote-first, and title inflation quietly reshuffles what counts as senior. If a query returns fewer than five fresh results per week, loosen one constraint at a time – usually seniority first, since adjacent level labels vary most between employers – and log which change produced better leads.
Searching by Company Size, Industry, and Remote Work Options
Filter by headcount bands before anything else – 1–10, 11–50, 51–200, 201–1000, 1001–5000, 5000+. A 12-person startup and a 4,000-person enterprise post the same title with wildly different scope, pay bands, and decision speed, so treating “company size” as a vague checkbox wastes screening time. Most boards expose this filter directly; on smaller platforms, use the company page or LinkedIn headcount range as a proxy.
Industry filters pay off when you combine them with function, not when you use them alone. A data analyst opening inside a hospital network, a logistics firm, and a fintech differs in tooling (Epic vs. SAP vs. Snowflake), compliance load, and hiring cadence. Layer two industry tags where the platform allows it – healthcare plus SaaS, manufacturing plus robotics – and you catch hybrid employers that single-tag queries miss.
Reading the table below
Remote options deserve their own dimension because “remote” is not one thing. Pull the three signals apart: workplace policy (on-site, hybrid, fully remote), geographic constraint (country-locked, timezone-bounded, global), and employment structure (direct hire, EOR, contractor).
| Remote signal | What to type or toggle | Why it matters |
|---|---|---|
| Workplace policy | “remote”, “hybrid”, “on-site” tags; filter to “fully remote” | Hybrid roles often hide a 3-day office requirement in the body text |
| Geographic constraint | “remote (US)”, “remote (EU)”, “worldwide”, “anywhere” | Country-locked postings fail fast if you sit outside the listed region |
| Employment structure | “EOR”, “contractor”, “direct hire”, “1099” | Contractor setups change tax handling and equity eligibility |
| Timezone window | “UTC+2”, “EST overlap”, “4-hour overlap” | Overlap requirements drive meeting load more than policy labels do |
Run the three filters as a stack, not a menu: pick a headcount band, add one or two industry tags, then apply the remote policy and geography toggles. Save that combination as a recurring alert – headcount bands shift quarterly, and a 180-person company crossing into the 201–500 bracket unlocks new budget lines and new postings you would otherwise never see. Review saved filters every 6–8 weeks and prune the industry tags that keep returning irrelevant results.
Quick sanity check before you apply
Cross-reference the posting’s stated headcount against the company’s careers page and funding history; a “Series A, 40 employees” label paired with 15 open roles signals aggressive hiring and likely process churn, while a stable 800-person firm with 3 openings usually means slower, more structured loops. Check whether the remote tag survives into the offer stage by scanning recent employee posts on professional networks – policy reversals show up there months before job descriptions get updated.
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
what auto-apply actually does with your profile and which boards actually carry the roles.
