Hiring Assistant | Join the Talent Community to ask Recruiter or LinkedIn Learning questions, find answers, discover best practices, and share product ideas.

Qualification Best Practices

Explore general guidance, qualification type examples, or role-specific best practices.

Looking for additional guidance? Register for an upcoming Live Qualifications Clinic with our Training Team.

Do this	Avoid this
✓Use specific years, tools, titles, and outcomes — write each qualification like an instruction to a sourcer	✗Vague traits like "strong communicator" or "solid technical background"
✓Use "currently working in…" or "in the past 2 years…" paired with a year range and level signal	✗Open-ended phrasing like "has experience in" with no timeframe or seniority signal
✓Keep to 4–6 focused qualifications that reflect true requirements	✗Long lists of skills and boolean keywords that dilute the signal
✓Use precise exclusions: "not managing a team" or "not focused solely on front-end"	✗Broad or ambiguous exclusions like "not junior" that can eliminate qualified candidates
✓Include implicit criteria: company pedigree, promotion history, tenure signals, or employer type	✗Only using criteria that appear in the job description
✓Iterate — refine qualifications based on the candidates you see; tighten if too broad, loosen if too narrow	✗Treating qualifications as set-and-forget; Hiring Assistant won't change behavior unless you do

We want to hear from you!

Share your best practices for finding talent using Hiring Assistant and earn a community badge!

Core Role Experience & Seniority

Use present or recent-tense phrasing — recency helps with match quality.
Use a year range (e.g., "5–8 years") rather than a hard floor — it signals what's ideal without over-filtering.
Clarify whether you mean total, professional, or domain-specific experience to avoid ambiguity.
Pair years of experience with a title or function so Hiring Assistant knows what kind of work counts.
Add progression cues (promoted, expanded scope) when growth trajectory matters for the role.

Examples

GOOD"5–8 years of recent experience working as a Senior Financial Analyst or FP&A Analyst supporting budgeting, forecasting, and variance analysis."

GOOD"Currently working as an IT Business Analyst, partnering with stakeholders on requirements, process mapping, and UAT."

AVOID"Has experience in finance or IT."

Tools, Systems & Technical Skills

Be clear, concrete, and measurable — avoid opinions or vague descriptors like "strong technical skills."
Name specific tools, languages, or platforms rather than broad categories — "Salesforce" beats "CRM experience."
Indicate how the tool was used (e.g., "developing reports in Power BI" vs. "familiar with Power BI") to signal depth.
Use "or" to offer equivalent alternatives when multiple tools serve the same purpose (e.g., "NetSuite, Oracle, or Workday").
Limit to 2–3 tools per qualification — over-listing dilutes the signal and can narrow results unnecessarily.

Examples

GOOD"Currently using advanced Excel (pivot tables, lookups) and financial systems such as NetSuite, Oracle, or Workday Financials."

GOOD"3–5 years of demonstrated experience developing or supporting applications using SQL and Power BI or Tableau for reporting and analytics."

AVOID"Strong technical skills."

Industry, Environment & Context

Specify industry, environment, or company type rather than leaving it open-ended — context helps Hiring Assistant distinguish relevance.
Name sectors explicitly (e.g., "financial services," "healthcare," "B2B SaaS") rather than relying on implied context from the job title.
Include regulatory or compliance signals when they matter (e.g., SOX, HIPAA, GDPR).
Pair industry context with company scale or growth stage when both matter for the role.

Examples

GOOD"5–10 years of experience working in mid-market or enterprise environments, supporting finance or IT teams."

GOOD"Currently working in a regulated or compliance-driven environment (SOX, audit, internal controls)."

AVOID"Works in a corporate environment."

Role Scope & Delivery Model

Specify level and role context — individual contributor vs. manager, full-time vs. contract — so Hiring Assistant isn't surfacing candidates at the wrong level.
Use exclusion language thoughtfully: "not managing a team" or "not focused solely on strategy" redirect results without being overly broad.
For contract or project-based roles, explicitly note the delivery model.
Describe what the person actually owns day-to-day — "end-to-end ownership of deliverables" beats "responsible for finance tasks."

Examples

GOOD"Individual contributor responsible for end-to-end ownership of deliverables in finance or IT projects."

GOOD"Recent experience working in contract, contract-to-hire, or project-based roles."

AVOID"Responsible for various finance or IT tasks."

Company & Education Background

Specify types of companies by name, size, or sector — "Chase, Wells Fargo, or Citi" is actionable; "large banking institution" is not.
Only use company pedigree as a qualifier when it's a genuine signal of the environment or skills you need.
For education, be specific about field of study when it matters — avoid generic "bachelor's degree required."
Pair degree requirements with "or equivalent experience" for technical roles.
Include certifications or licensure only when legally required or strongly differentiating.

Examples

GOOD"Has recently worked for large banking institutions, such as Chase, Wells Fargo, Citi, or Bank of America."

GOOD"Bachelor's degree in Accounting, Finance, Information Systems, Computer Science, or a related field."

AVOID"Works for a financial services company."

Business Impact

Focus on observable behaviors and outcomes — not personal traits like "strong communicator" or "strategic thinker."
Describe what the candidate has demonstrably done, not what they could potentially do.
Use action-oriented phrasing: "presented insights to…", "collaborated with…", "supported decisions around…"
Avoid requiring specific percentages or figures unlikely to appear on a profile.
Use cross-functional collaboration as a signal of impact breadth when the role requires working across teams.

Examples

GOOD"Demonstrated experience presenting financial or operational insights to non-finance stakeholders and supporting data-driven decision-making."

GOOD"Regularly collaborates with cross-functional teams (finance, IT, operations) to support projects, reporting, or system implementations."

AVOID"Strong communication and presentation skills."

We want to hear from you!

Share your best practices for finding talent using Hiring Assistant and earn a community badge!

Engineering

Be explicit about recency and/or years of experience for each technical domain.
Specify years of "post-grad" or "professional" experience to exclude internship work.
Include tools, frameworks, or environments (e.g., cloud, infrastructure) tied to the role's scope.
Use excluding language thoughtfully (e.g., "not focused solely on front-end" or "not as a manager") to re-direct.
Combine technical depth with collaboration signals (e.g., cross-functional work, mentorship).

Examples of Good Engineering Qualifications

"5–8 years developing in backend systems using Java or Scala."
"Currently building distributed or cloud-native architectures."
"Worked in organizations with strong infrastructure or developer tools teams (e.g., AWS, Microsoft, Meta)."
"4–8 years of post-grad experience in machine learning engineering; must have a PhD or equivalent in CS, applied mathematics, or ML."
"Experience deploying ML models in production environments; not solely focused on research or data science roles."
"Has worked in cross-functional settings with product and engineering stakeholders to translate model results into features."
"3–5 years developing in front-end frameworks like React or Angular."

Emerging Talent

Specify graduation date and degree program to ensure relevance.
Emphasize internship or project experience to infer skills over tenure.
Include growth signals (hackathons, course projects, open-source contributions).
Avoid over-weighting corporate experience — focus on aptitude and curiosity.

Examples of Good Emerging Talent Qualifications

"Currently pursuing a BS or MS in Computer Science or related field, graduating between Dec 2025–June 2026."
"Completed internship or significant project involving Python or Java."
"Actively contributing to open-source or university-level engineering projects."
"Demonstrated ability to collaborate on group projects or cross-functional teams."
"Strong foundation in algorithms, data structures, and software design principles."

Sales & Customer Success

Call out quota-carrying experience, deal size, and industry familiarity.
Indicate promotion patterns or tenure length (signals of sustained success).
Include related titles or functions for search breadth (e.g., "Account Manager OR Relationship Manager").
Include performance indicators like "President's Club" or "consistent overachievement."
Be specific on customer segment (Enterprise, SMB, Agency, etc.).

Examples of Good Sales & Customer Success Qualifications

"3–5 years in B2B SaaS sales, consistently meeting or exceeding quota."
"Experience managing Enterprise or Agency clients with 1M+ annual spend."
"Strong tenure in roles such as Account Executive, Agency Development Lead, or Relationship Manager."
"Proven record of promotion within sales organization (e.g., AE1 to AE2 within 2 years)."
"Track record driving adoption or upsell within existing accounts."
"Experience selling to HR, TA, or Marketing stakeholders."
"Located in Hong Kong or APAC region; fluent in English and Cantonese/Mandarin preferred."
"Experience with advertising or marketing technology products."

Marketing & Communications

Focus on scope and channel expertise — the levers the marketer actually owns (e.g., paid social, lifecycle, brand, events).
Tie qualifications to impact metrics (conversion rates, engagement growth, ROI) rather than subjective traits.
Reflect cross-functional collaboration.
Specify audience type or segment (B2B vs. B2C, enterprise vs. SMB).
Include tool stack familiarity when it signals proficiency, but don't over-list tools.

Examples of Good Marketing & Communications Qualifications

"5–8 years of experience developing and executing multi-channel marketing campaigns across digital, social, and email."
"Experience using marketing automation tools to run and measure demand programs."
"3–6 years managing paid media and performance campaigns across Google, LinkedIn, and Meta."
"8–10 years of experience managing media relations, press releases, and executive communications at global companies with over $100 million ARR."
"Experience leading cross-functional launch planning and internal enablement."
"Ability to craft compelling narratives and simplify complex concepts."

Product

Specify years in product management or related roles (consulting, UX, strategy).
Include cross-functional and stakeholder management language.
Reference impact-oriented outcomes (launches, adoption, metrics).
Include preferred company scale (startup vs. enterprise).
Avoid generic phrases like "strong product sense" — anchor in measurable delivery.

Examples of Good Product Qualifications

"5–7 years in product management or equivalent experience; launched customer-facing features with measurable adoption."
"Experience defining product vision, roadmap, and requirements in partnership with design and engineering."
"Worked in high-growth B2B SaaS or marketplace environments."
"Experience conducting user research and translating insights into actionable product improvements."
"Strong analytical skills; comfortable using data to prioritize and measure outcomes."
"Has managed cross-functional teams and driven projects from ideation to launch."

General & Administrative

Combine strategic and operational indicators (analysis + execution).
Specify industry context (tech, SaaS, marketplace).
Include tenure and progression signals for senior roles.
For legal roles, name practice areas (privacy, commercial, employment).
Use conversational but precise phrasing — "Has advised business partners on…" instead of "responsible for advising."

Examples of Good General & Administrative Qualifications

"5–7 years of experience in strategic finance or FP&A within technology companies."
"Experience building financial models, forecasting, and supporting executive decision-making."
"Has advised business leaders on budgeting, resourcing, and strategic investments."
"JD and active bar membership in one jurisdiction."
"Experience drafting and negotiating SaaS and commercial contracts."
"Knowledge of data privacy and compliance regulations (GDPR, CCPA)."
"3–5 years in business operations, corporate development, or strategy roles."
"Experience driving cross-functional initiatives and optimizing business processes."

Leadership

Emphasize scale and scope of leadership (team size, budget, org complexity).
Include years of experience leading teams or managing functions.
Specify impact and outcomes (growth, transformation, or major launches).
Highlight company pedigree only when relevant to performance signal.
Avoid generic "proven leader" language — specify type of leadership (e.g., scaling early-stage orgs, leading transformation).

Examples of Good Leadership Qualifications

"10+ years in sales leadership, including 5+ years leading SMB or mid-market teams."
"Experience driving double-digit revenue growth and scaling teams across regions."
"Track record of developing managers and building high-performing sales orgs."
"7+ years leading product operations or go-to-market strategy."
"Experience at B2B SaaS companies with over $200 million ARR with focus on operational excellence."
"Ability to translate strategic vision into executable plans with measurable outcomes."

We want to hear from you!

Share your best practices for finding talent using Hiring Assistant and earn a community badge!

Feeling Stuck?

Below are answers to frequently asked questions about Hiring Assistant

Can I add Hiring Assistant to an existing project?

Absolutely! Adding Hiring Assistant to an existing project is easy – and we highly recommend it.

Here’s how:

Go to your project
Open Project Settings
Under Workflow Settings, select Add Hiring Assistant
If you don’t see the option, make sure you’re the project owner first.

And don't worry about Hiring Assistant disrupting your existing work. Hiring Assistant is built to enhance your projects, not interfere.

Why are no candidates appearing after I added Hiring Assistant to my project?

If you add Hiring Assistant to an existing project, you then need to define your qualifications. Without your qualifications, Hiring Assistant does not know who to look for. View our Qualifications Tip Sheet for best practices.

After you set your qualifications, Hiring Assistant works behind the scenes – running multiple sourcing strategies at once. Within about 20 minutes, you’ll see qualified candidates in your first pipeline stage.

Will Hiring Assistant source people who have been recently InMailed or applied to my job?

Hiring Assistant automatically excludes candidates who have InMail history from the last 3 months. You will be able to include more prescriptive qualifications based on recruiting activity soon.

Also, if your Hiring Assistant project is linked to a job post, it will automatically exclude anyone who’s already applied or started an application when sourcing new candidates.

Do I need to provide feedback on every candidate that Hiring Assistant sources?

No. While archiving candidates and providing feedback on why a candidate is unqualified is good practice, you don’t have to repeat the same feedback for every candidate. Remember, providing high-quality feedback is more impactful than focusing on giving feedback in large quantities.

Have additional Hiring Assistant questions?:
Visit our Help Center , Ask a question in the Community. or Register for an upcoming Live Q&A session with a product expert.