How to connect MyCulture to Lever for candidate screening

Instead of manually reconciling assessment invitations and candidate records, define a screening handoff that connects the right assessment to the right Lever hiring opportunity. For a myculture lever integration, confirm the supported connection method first, then test invitations, result access, and recruiter review before enabling any automation.

TL;DR

• For a myculture lever integration, verify the supported connection method before configuring candidate screening.
• Myculture assesses candidates’ values, work style, and team compatibility; keep hiring decisions grounded in job requirements.
• Match each assessment to the relevant Lever opportunity, not just a candidate’s email address.
• Start with a controlled handoff; automate only after testing permissions, duplicate prevention, and result updates.

Why this matters

A screening connection needs to preserve context, not merely move a result. Recruiters need to know which role the assessment concerns, whether the candidate completed it, and what evidence deserves follow-up in an interview.

Myculture culture fit assessment is best for HR teams evaluating candidates’ values, work style, and team compatibility. Its role in this workflow is assessment evidence. Lever remains the place where your recruiting team manages the hiring opportunity and records the decision.

Keep those responsibilities separate. An assessment result should support a structured conversation about job-relevant behavior, not become a substitute for skills evidence or an automatic rejection rule.

For your 2026 implementation, write down the connection method, account owner, and screening rules before inviting candidates. That record gives recruiters a shared reference when a hiring stage changes or an assessment needs review.

Before you start

• Accounts and access: Have an authorized administrator for each system, a recruiter who owns the pilot role, and confirmation of the connection method supported for your accounts. Obtain the current setup instructions directly from the providers before configuring authentication or permissions.

• Screening materials: Prepare the role’s behavioral expectations, candidate invitation wording, assessment selection, result-review criteria, and a policy for access and retention. Explain the assessment’s purpose and provide a route for candidates who need assistance or accommodations.

• The identity gotcha: Decide how to distinguish the candidate from the hiring opportunity. A person applying for different roles needs role-specific context; an email match alone is not a sufficient rule for placing assessment evidence.

Do not begin with guessed menu labels or an assumed native connector. Use the controls described in the current provider instructions. The configuration units below define what your setup must accomplish without treating a proposed workflow as an existing product feature.

Connection method and ownership

Choose the handoff you can operate reliably. A manual process is a valid starting point when your team has not established a supported automated route.

The automated option is not a claim that a particular connector, trigger, or writeback feature exists. Select it only after confirming the available actions for your accounts.

1. Verify the supported route. Ask which connection method is available, how authorization works, and which actions it supports. Confirm invitation handling and result handling separately; support for one does not establish support for the other.

1. Assign an owner. Name the person responsible for failed handoffs, permission changes, and candidate questions. Give that person a backup so screening does not depend on an absent recruiter.

1. Define the source of each record. Keep hiring-opportunity identity and recruiting stage context in Lever. Treat the assessment platform as the source of the assessment evidence, rather than maintaining independently edited copies of the same result.

1. Record the setup boundary. In your 2026 operating notes, list which actions are automated, which remain manual, and which require recruiter approval. Include how to pause the workflow without losing track of pending candidates.

Expected result: Your team can name the connection method, its supported actions, and the person responsible for operating it. No step depends on an unverified feature.

Screening entry rules

Start with 1 pilot role. This is a rollout recommendation, not a limit on either platform; a narrow scope makes it easier to inspect each handoff before expanding.

1. Choose the entry point. Define the recruiting event that makes a candidate eligible for assessment. Use an event your confirmed connection supports, or have the recruiter perform that handoff manually.

1. State the eligibility conditions. Specify the relevant role, active hiring opportunity, and required candidate communication. Exclude withdrawn or closed opportunities from your proposed invitation process.

1. Define duplicate prevention. Before sending an invitation, check whether an assessment is already pending or complete for that candidate and role. If your supported route cannot enforce this check, assign it to the recruiter.

1. Describe the candidate message. Explain why the assessment is being used, how it relates to the role, and who can answer questions. Do not promise a completion time unless it is confirmed for the assessment you selected.

1. Set exception handling. Tell recruiters what to do when a candidate changes an email address, applies to another role, or requests assistance. Preserve the original opportunity context instead of creating another invitation by default.

Expected result: Recruiters can explain exactly who receives an assessment and why. Re-entering the screening stage does not automatically mean sending another invitation.

A useful workflow has an explicit review point between receiving assessment evidence and making a hiring decision. Preserve that boundary in both the manual process and any supported automation.

Recruiter review sits between assessment evidence and the hiring decision.

Candidate matching and result handling

Define your mapping in plain language before entering settings. The labels below describe information your workflow needs; they are not claimed interface field names.

1. Identify the hiring opportunity. Record how your supported route associates an assessment with the correct Lever opportunity. For a manual handoff, have the recruiter verify the candidate and role before recording anything.

1. Limit transferred information. Include only information needed to administer and review the assessment. Keep credentials, unnecessary personal details, and unrelated assessment material out of recruiting notes.

1. Separate progress from evidence. Track whether the assessment is pending, completed, or awaiting review using the mechanisms your accounts support. Do not interpret a missing result as a negative assessment outcome.

1. Choose the review destination. Confirm whether the supported route provides a result reference, attachment, summary, or another permitted destination. If it does not provide result writeback, document a manual review step instead of assuming one.

1. Control visibility. Restrict assessment access to the people who need it for the hiring process. Test access from a recruiter account, not only from the administrator account used during setup.

Expected result: Assessment evidence belongs to the correct opportunity, authorized reviewers can access it, and incomplete assessments remain distinguishable from completed results.

For the 2026 pilot, maintain a short mapping record containing the candidate reference, opportunity reference, assessment reference, and handling rule. These are documentation requirements, not promises that every connection exposes identically named fields.

Pilot testing and release

Use 3 internal test records: a straightforward candidate, a repeat screening entry, and a candidate associated with different roles. These are recommended test cases, not product performance figures.

1. Test the straightforward handoff. Verify the eligible opportunity, intended recipient, assessment selection, and review destination. Follow the process through recruiter review rather than stopping after an invitation appears.

1. Test repeat entry. Run the same opportunity through the entry condition again. Verify that your duplicate-prevention rule either stops another invitation or routes the case to a recruiter for confirmation.

1. Test role separation. Associate the internal test candidate with different roles. Confirm that the evidence remains attached to the intended opportunity and that recruiters understand whether reuse requires review.

1. Test reviewer access. Use 2 reviewer accounts with different responsibilities. Confirm that authorized users can open the evidence and that access restrictions match your written policy.

1. Approve a limited release. Have the workflow owner review the test record, unresolved exceptions, and pause procedure. Expand beyond the pilot only after correcting failures in identity, access, and duplicate handling.

Expected result: The team has observed the complete screening handoff and tested its failure points before involving live candidates.

Record your release date and the tested configuration in the 2026 change log. Repeat the relevant tests whenever you change the entry condition, assessment selection, permissions, or connection method.

Update screening evidence without inviting candidates again

A second useful workflow is a review update, not a second assessment invitation. Apply it when recruiting context changes or previously received assessment evidence needs another look.

Keep this variant manual unless your confirmed connection supports the necessary update action. A change to a hiring opportunity is not, by itself, a reason to reassess the candidate.

1. Determine what changed: the role, team expectations, reviewer, or assessment evidence.

1. Check whether the existing assessment remains relevant to the current job requirements.

1. Ask the recruiter to review the existing evidence and record the role-specific interpretation.

1. Request another assessment only when the hiring process provides a documented reason and appropriate candidate communication.

Expected result: Recruiters update the screening context without repeatedly asking candidates to complete the same task.

For staffing and RPO teams, document the client and role context before reusing assessment evidence. Do not assume that access permission or job relevance carries across assignments.

Troubleshooting

An invitation is sent again

Check whether the entry condition fired again and whether the workflow checked for a pending or completed assessment. Pause the affected route, reconcile the invitation history, and add a duplicate check or recruiter approval step before restarting.

Evidence belongs to the wrong hiring opportunity

Inspect the identity rule first. Replace an email-only match with a verified opportunity association supported by your route, then correct the misplaced reference and review any other handoffs processed under the same rule.

The administrator can open results, but the recruiter cannot

Test the result reference using the recruiter’s own account. Confirm permissions in the relevant systems; do not solve an access problem by copying sensitive assessment material into a broadly visible note.

The candidate completed the assessment, but review is still pending

Separate assessment completion from result delivery and recruiter review. Check the assessment record, inspect any supported delivery history, and use the documented manual handoff if the result did not reach its destination.

A moved or closed opportunity still receives screening activity

Review the eligibility check at the point where the action occurs, not only when the workflow begins. Stop the pending action where possible, reconcile the candidate communication, and require a current-status check before another invitation.

Customize your workflow

Expand the process by role relevance, not by adding more automated decisions. Give recruiters a consistent way to turn assessment evidence into questions about collaboration, feedback, and the actual working environment.

Use the guide to combining personality assessments and interviews to structure that review. Keep culture fit evidence alongside skills evidence and interview observations, with a clear explanation of how each informs the decision.

Myculture culture fit assessment supplies evidence about values, work style, and team compatibility; it does not establish whether a candidate has every skill required for a role. That distinction is the main safeguard against turning a screening workflow into a personality-based gate.

During your 2026 workflow review, inspect exceptions as well as successful handoffs. Check whether candidates received duplicate requests, whether recruiters could access the evidence, and whether hiring decisions recorded job-relevant reasons.

One last thing

The most important connection is between the result and the right hiring opportunity. A delivered assessment with the wrong role context is not a successful screening handoff.

Before expanding the workflow, ask a recruiter to explain an assessment’s relevance without relying on a single fit score. If the explanation cannot connect values or work style to specific job expectations, revise the review criteria before automating more steps.

Related guides

• How to score a culture fit assessment

• Interview scorecards for structured hiring decisions

• How to communicate assessment results to candidates