How to Set Experience Requirements When a Role Is New to the Company

When a role is new to the company, set experience requirements by defining the work, expected outcomes, constraints, risks, and acceptable evidence before choosing a years-of-experience threshold. Require prior experience only when the team can explain what capability or exposure it represents. This approach replaces assumptions with explicit criteria, gives candidates more than one way to demonstrate readiness, and creates checkpoints for revising requirements as the hiring team learns.

Start With Outcomes and Evidence, Not an Arbitrary Number of Years

Without an internal precedent, it is tempting to copy a requirement from another company or choose a familiar number of years. That may make a job description look complete, but it does not explain why the experience is necessary for this particular role.

Start by writing down what the person must be able to accomplish. Focus on meaningful outputs rather than a list of activities. For example, “coordinate customer onboarding tasks” is less informative than “identify stalled onboarding steps, organize the relevant information, and communicate a clear next action to the customer-facing team.”

For each output, ask:

• What knowledge or judgment does the work require?
• Which situations must the person have encountered before?
• What mistakes would be difficult to correct?
• Which capabilities can be developed through onboarding?
• What evidence could a candidate provide to demonstrate readiness?

Possible evidence includes a comparable outcome in another role, a structured example, a relevant work sample, or adjacent experience involving similar constraints. None is automatically sufficient. Its value depends on how closely it reflects the work the employer needs done.

Years of experience can still appear in the requirement when the team has a clear rationale. If the rationale is simply “this sounds like a senior role,” the requirement needs more work. If the team can explain that the role requires repeated exposure to a specific kind of high-consequence situation, a prior-experience threshold may be more defensible.

Define the Work, Constraints, and Risk Behind the Requirement

Experience requirements should reflect the conditions in which the person will work, not just the job title. Two positions with the same title can demand different levels of prior exposure because the complexity, support, pace, and consequences of mistakes differ.

Document the following before finalizing the qualification list:

• Expected outputs: What should the role reliably produce or improve?
• Recurring work: Which tasks and situations will appear regularly?
• Judgment demands: Where will the person need to interpret incomplete information or choose between competing priorities?
• Operating constraints: Will the person face specialized tools, strict timelines, complex customer needs, or limited documentation?
• Available support: How much training, subject-matter guidance, and manager attention can the company realistically provide?
• Consequences of mistakes: Are errors easily corrected, or could they create significant customer, financial, operational, or reputational problems?

The answers help determine how closely a candidate’s prior experience should match. When consequences are substantial and support is limited, closely comparable experience may matter more. When the work is learnable and strong support is available, adjacent experience or demonstrated skills may be reasonable alternatives.

Risk should not be converted mechanically into a fixed number of years. Instead, identify the specific situations the candidate needs to recognize and handle. A person with repeated relevant exposure may be better prepared than someone with a longer career that did not include those situations.

Separate Essential Experience From Trainable Skills and Preferences

A practical qualification review places each item into one of four categories:

1. Essential on entry: The candidate needs this experience to perform safely or credibly from the start.
2. Trainable: The capability can reasonably be developed through the company’s onboarding and support.
3. Contextually useful: Familiarity would shorten the learning curve but is not necessary for effective performance.
4. Preferred: The item may be helpful, but the team cannot connect it to an essential outcome or material risk.

Test each proposed requirement with two questions: What would happen if the candidate lacked it on day one? Could onboarding reasonably close the gap?

Suppose a role uses a company-specific workflow tool. Familiarity with that exact tool may be trainable if the underlying work is straightforward. By contrast, experience handling sensitive customer escalations may be essential when the new hire must manage those conversations immediately and limited coaching is available.

Avoid treating a title, degree, certification, former employer, or exact career path as proof of ability. Those details can add context, but evaluators should still connect them to evidence of the required work. Candidate profiles may contain experience, projects, education, skills, languages, and certifications; the hiring team must determine which information is relevant and why.

Compare Direct Experience, Adjacent Experience, Demonstrated Skills, and Learning Capacity

There is no universally best experience model. The appropriate choice depends on the role’s complexity, risks, candidate market, and the support available after hiring.

Closely matched experience may be appropriate when the person must operate independently, specialized context is needed immediately, or mistakes would be costly. Its tradeoff is a narrower candidate pool, and an exact title match still does not establish that the candidate handled comparable work.

Adjacent experience can be useful when another role involved similar outcomes, stakeholders, constraints, or judgment. A customer support specialist, for example, might have relevant evidence for an onboarding role if they have investigated customer problems, coordinated internal follow-up, and communicated next steps. The evaluation should focus on the transferability of that experience rather than the title alone.

Demonstrated skills allow candidates to show how they approach realistic work. A short work sample, structured case discussion, or detailed account of a past situation can reveal how a candidate organizes information and reasons through a problem. Keep exercises proportionate to the role and evaluate them with criteria established in advance.

Learning capacity with added support may be reasonable when the employer has enough time and resources to help someone develop. Relevant evidence could include examples of learning a new domain, applying feedback, or becoming effective in an unfamiliar environment. This option becomes less practical when the company cannot provide the support on which the hiring choice depends.

A balanced job description can state the required capability and offer several acceptable forms of evidence. For example: “Experience coordinating multi-step customer work, demonstrated through onboarding, implementation, customer success, operations, or another comparable setting.”

Turn the Requirements Into Consistent Evaluation Criteria and Checkpoints

Convert each requirement into a criterion that evaluators can apply consistently. A simple planning table can make assumptions visible before sourcing and interviews begin.

An evaluator should know what a strong answer contains, what evidence is incomplete, and which follow-up question to ask. Candidates being considered for the same position should receive the same core prompts, even when additional questions are needed to understand different backgrounds.

Requirements should also have a review trigger. Revisit them when candidates repeatedly misunderstand the role, the qualified pool is unexpectedly narrow, interviewers cannot apply a criterion consistently, or a requirement does not help distinguish readiness. Track practical signals such as application relevance, reasons candidates are screened out, work-sample results, and recurring candidate questions. These measures do not prove the original criteria were right or wrong, but they can reveal where assumptions need examination.

Worked Scenario: Setting Requirements for a Newly Introduced Customer Onboarding Analyst

Consider a hypothetical company introducing a customer onboarding analyst role. Related onboarding work has previously been distributed among customer-facing and operations employees, but the company has never hired for this exact position.

Step 1: Define the goal. The team states that the role should monitor active onboarding work, identify missing information or stalled steps, and communicate a clear follow-up. This is more useful than beginning with a title or seniority label.

Step 2: Examine constraints and risks. The analyst will work with incomplete information and multiple stakeholders. Most process details can be learned, but failure to recognize a serious delay could affect a customer relationship. The company can provide training on its systems but has limited capacity to teach basic customer communication and task coordination.

Step 3: Classify the requirements. Experience organizing multi-step customer work and communicating next actions is marked essential. Knowledge of the company’s software is trainable. Familiarity with the company’s industry is contextually useful. Prior possession of the exact “customer onboarding analyst” title is removed as a requirement.

Step 4: Define acceptable evidence. Candidates may demonstrate readiness through onboarding, customer success, implementation, project coordination, support operations, or another setting with comparable work. The team asks for a structured example of a stalled process and uses a short exercise involving incomplete onboarding information.

Step 5: Apply consistent evaluation criteria. Evaluators look for how the candidate identified the problem, prioritized the next action, involved other people, and communicated with the customer. A candidate with an adjacent background is not advanced merely for telling a persuasive story; the example must address the same criteria used for candidates with direct experience.

Step 6: Review the assumptions. After the initial candidate conversations, the team checks whether the requirements are producing relevant evidence. If several capable candidates lack the exact background originally expected but demonstrate the required judgment, the wording can be broadened. If candidates consistently struggle with an essential situation, the evidence standard may need clarification.

This scenario does not guarantee a successful hire. It illustrates how a team can make its reasoning visible and revise it using information from the market instead of defending an arbitrary starting assumption.

Use Direct Candidate Conversations to Explore Evidence Without Lowering the Standard

A resume-first application can make adjacent experience difficult to interpret. Direct conversation gives candidates room to explain the context behind their work, including the outcome they were responsible for, the constraints they faced, and how their actions relate to the new role.

MeeBoss connects employers and job seekers through profiles, recommendations, and direct conversations. Chat to Apply lets a job seeker reach a hiring team directly rather than relying only on a cold or one-click application. The MeeBoss Recommendation Engine uses information such as profiles, preferences, job descriptions, and platform activity to support relevant recommendations. AI and other tools can support matching, job posts, conversation starters, and recommendations, while people remain responsible for hiring decisions.

Conversation should complement structured evaluation, not replace it. Employers can prepare a small set of consistent prompts, such as:

• “Describe a situation in which a multi-step process stalled. What information did you use to decide what to do next?”
• “Which part of this role is most similar to work you have already done, and where would you need support?”
• “Show us an example of learning an unfamiliar workflow and applying it in practice.”

Evaluate the answers against the documented criteria rather than confidence, conversational style, or similarity to the interviewer. Follow up when evidence is incomplete, but do not quietly change the standard from one candidate to another.

Before publishing the role, complete this final review:

• Can every experience requirement be linked to a specific outcome, constraint, or risk?
• Has the team separated essential experience from trainable skills and preferences?
• Are multiple relevant forms of candidate evidence accepted where appropriate?
• Is someone identified to evaluate each criterion?
• Will candidates receive consistent core questions?
• Are market signals and reasons for rejection being tracked?
• Is there a defined point or signal for revisiting the requirements?

The goal is not to predict the perfect background. It is to create a clear, explainable standard that can be tested against relevant candidate evidence and improved as the hiring process progresses.

Join MeeBoss and start a real hiring conversation.