1. LandOffer
  2. Blog
  3. All articles
  4. Plum Profile Not Linked to an Employer: Connect Existing Results and Check My Career

Job search

Plum Profile Not Linked to an Employer: Connect Existing Results and Check My Career

Official candidate documentation separates profile reuse, identity linking and application evidence, with completed fictional branch and support-handoff cases.

9 min readLandOffer team

An existing Plum Profile and an employer-linked Plum application are different things. Seeing your results while an employer reports no access can make a retake or public-profile change feel urgent. Identify the missing application connection before taking either step. Check three possible gaps: the employer invitation route, the email identity, and the application record.

Start with the exact employer link and compare the email used for recruiting with the email holding your existing results. Then check the relevant application under My Career. We reviewed Plum's public candidate guidance on October 20, 2026; we did not enter a candidate account, link emails, take an assessment, or submit results. For a separate search, browse recent roles on LandOffer.ai and keep each employer's application instructions with its record.

A candidate compares an existing results folder with a separate employer invitation and application record.

First identify which connection is missing

A completed profile answers whether assessment results exist. An employer invitation identifies a particular route for sharing them. An application record provides a separate place to check the Plum portion of that submission. An employer's recruitment portal may maintain another status outside Plum.

Write down those four items before changing anything: the employer and role, the invitation destination, the recruiting email, and the Plum results email. Use the actual addresses privately, rather than relying on similar display names. A personal address and an application alias can belong to the same person without being the same identity in an employer integration.

This article uses “not linked” as a troubleshooting description. We did not reproduce a particular account warning or verify its exact wording. The advice follows the published branches below, with the limits of each status preserved.

A generic visit to your profile is also different from following the employer's application route. Do not infer employer receipt merely because the survey looks complete when you sign in independently. Equally, an access problem does not establish that your results were lost or that your application was rejected.

Follow the branch for the email in the invitation

Plum's existing-profile guide separates same-email and different-email cases. For the same email, the employer's invitation leads to an Apply login page; Plum recognizes the existing account, and the guide says the profile is submitted for that application on login.

That is a sharing action, not simply a neutral way to inspect your results. Read the employer and role before proceeding. For a different email, the guide describes verifying the new address, creating its password, and choosing to reuse the earlier assessment when offered. We have not tested either flow inside an account.

If you previously applied to that employer, the same guide says it may already have access and invites you to clarify whether another action is needed. Avoid treating a new invitation as proof that your old results must be recreated. Preserve the original message while you establish which application it concerns.

These branches are tied to the employer's route. A public profile URL, a screenshot, or a PDF is not the documented replacement for the invitation-based submission. The guide specifically says those alternatives are unnecessary for employer access through the proper application link.

Linking has an eligibility condition and two identities

The account-linking guide says the destination account must have no profile, including no survey already in progress. Starting a second survey can therefore remove the documented option for linking existing results into that account. Pause if the destination is already in progress or complete; do not assume the standard linking steps still apply.

For the eligible branch, the guide describes choosing that you have taken the survey before, confirming that you want to link it, and identifying the old results email. A six-digit code goes to that old address. Verification of the new email and access to the old results email serve different purposes.

The guide also states that profiles are linked, not applications. An application mistakenly made under another email does not migrate merely because the results become available to the destination identity. After the appropriate employer route, inspect the application record separately.

If you cannot access the old inbox, the published code step is unresolved. Do not guess a code, use somebody else's inbox, or start another assessment as an assumed workaround. Record the blocked step and use Plum's official support route for that specific problem.

Completed branch review: three similar-looking situations

The following cases are fictional and already adjudicated against the public documentation. They illustrate the decision before account changes; none represents a tested candidate account or a successful live repair.

Case record Existing evidence Documented branch or limit Completed decision
Asha: the employer invitation and existing results use the same address Completed results; correct role named in the invitation Same-email Apply login route Retain the employer link and review its sharing context; no new assessment planned
Ben: recruiting uses a different address; destination survey has not started Access to both inboxes; existing results remain under the old address Different-email linking branch with separate identity verification Prepare the two-email map and use the documented reuse path; application remains a separate check
Cara: the new address already has a survey in progress Old completed results and a started destination survey Destination fails the published no-profile condition Stop the standard-linking plan and seek case-specific guidance

Asha's diagnosis is a missing employer-context check, not missing assessment results. Ben's diagnosis concerns identity and reuse. Cara's case cannot be declared fixed by instructions intended for a destination without a profile.

Each case ends with a specific next action and an unresolved completion check. The review does not establish whether the employer invitation is still valid, whether an integration will match the email, or whether a candidate has finished the employer's separate recruitment requirements.

For a real record, keep those unknowns alongside the branch decision. That prevents a later reviewer from interpreting “linking planned” as “application delivered.” A short private note preserves what was observed, so a later follow-up can address the missing receipt instead of repeating an assessment.

Check My Career without overreading its status

Plum's submission-status article directs candidates to Applications under My Career and describes complete and incomplete Plum applications. An unfinished Discovery Survey appears in progress. The article also refers to the Applied page when explaining the application listing.

The public status article uses Applications under My Career and also refers to an Applied page. We did not inspect an authenticated navigation menu or confirm how those labels appear in a particular account. Look for the actual employer-linked entry and its state, rather than assuming the results page itself is the submission receipt.

If the application is listed but the employer still cannot see the profile, the article identifies email mismatch as a possible issue for certain employers. Compare the invitation's email instructions before making changes. A listed record is useful evidence, but it does not prove that every downstream recruitment system displays the expected results.

Likewise, a Plum completion state is not an interview invitation, a hiring decision, or proof that a separate resume or employer-portal step is done. Keep the Plum evidence and the employer's confirmation as distinct records.

A candidate prepares a concise support record while keeping private results and verification details out of the message.

Completed handoff record: linked results are not the final receipt

Diego is a fictional candidate applying to the fictional Harbor Software role HS-42. His private notes say the recruiting portal uses Address B, his existing Plum results use Address A, and an identity-link confirmation has appeared. We stipulate those observations for the example; we did not perform the linking or inspect an account.

In the stipulated scenario, he cannot identify the Harbor Software HS-42 entry in the application list he reviewed. He also has no employer confirmation that results are visible. His completed evidence record is:

Record field Diego's saved observation Interpretation
Intended employer and role Harbor Software, HS-42, as named in the invitation The specific transaction to investigate
Identity map Address A holds results; Address B is used for recruiting A possible integration dependency, not proof of access
Linking evidence Confirmation recorded in the fictional account notes Results-linking step only
Application evidence HS-42 entry not identified in the observed list Submission status remains unresolved
Employer evidence No visibility confirmation received No downstream receipt claim
Decision Hold the “done” label and request targeted clarification No retake or public-profile change

His draft handoff is complete: “I am checking the Plum step for Harbor Software role HS-42. My existing results use Address A and the recruiting application uses Address B. I recorded a profile-link confirmation, but cannot identify the expected role in my application list. Please confirm which employer invitation route and email identity should be used, and what application evidence I should expect.”

This is an unsent fictional message, not outreach performed for a real candidate. In an actual support channel, supply only the identity details necessary for that recipient to locate the record. Do not include passwords, verification codes, a complete assessment report, or unrelated application history.

The handoff is useful because it separates the observed step from the missing evidence and asks a narrow question. It avoids asking support to infer the intended employer from a generic statement that the profile is broken. A reply still needs reading and the relevant account evidence still needs checking. Neither an unsent draft nor a submitted support ticket establishes a repaired application.

Keep email changes, retakes, and privacy separate

Plum's email-change article presents profile linking as an alternative to changing the account email. For an actual email change, it describes messages from both addresses to verify ownership and warns that ongoing applications with other employers may be affected. This is not a routine prerequisite for every visibility issue.

The retake guidance says an existing profile can be reused instead of retaking for a different email. It describes a one-year retake eligibility rule and says a retake replaces the accessible profile results and updates linked accounts, while past applications retain their earlier results. Retaking is therefore a separate results decision, not an identity-link repair.

Public visibility is also separate from employer sharing. Plum's privacy help describes consent for employer access and distinguishes future use from information already received by the employer. Making a profile public should not be treated as a harmless troubleshooting toggle.

The privacy policy says authorized employer sharing transfers information into the employer's handling practices, including assessment information and relevant application documents. Its displayed update date was May 17, 2024. The terms, displayed as updated October 30, 2025, describe sharing existing results through subsequent employer application or invitation links. These are policy descriptions, not a private-account access audit or a guarantee about a particular employer's systems.

Finish with evidence for the right employer

The practical sequence is to identify the employer route, select the correct email branch, respect the destination account's linking condition, and check the application entry afterward. If any step differs from the documentation, preserve the observation and ask for help with that step rather than changing several settings at once.

Use a completion note that names the evidence you actually have. “Existing results visible” is weaker than an identified employer-linked application record, and neither establishes a hiring outcome. When the employer reports an access problem, keep that report visible even if another screen says complete.

For another application, start with its own instructions. Browse recent roles on LandOffer.ai and keep employer-specific links, identities, and receipts together. Reusing assessment results can reduce duplicate effort, provided you verify the sharing route and the application evidence separately.

Sources and Further Reading