Hiring has two sides. This one is yours.

Compare your experience and preferences with the actual role requirements before you decide.

Explore the example

An illustrative walkthrough. No account or CV needed.

Look at both sides.
Then make your call.

This example follows Alex, a senior engineer considering a role at Northstar. Every profile fact and vacancy detail below is fictional.

Northstar · Berlin, Germany

Senior Backend Engineer

Example vacancy · captured 8 September 2026

1 confirmed conflict
1 match · 1 unknown

Work arrangement

Your profile
Remote onlyHard preference
The role
3 days in the Berlin officeHybrid arrangement
Confirmed conflict

This role conflicts with a requirement you marked as non-negotiable.

Inspect source documents
Profile preferences

example-preferences-001 · v1
· Arrangement

“Remote only. This is a hard requirement.”
Captured vacancy

example-capture-northstar-001 · v1
· Arrangement

“Berlin, Germany. Hybrid: 3 days per week in the office.”

Experience

Your profile
8 years in backend engineering
The role
8+ years of relevant experience
Match

The stated experience meets the requirement.

Inspect source documents
Example profile

example-profile-001 · v1
· Experience

“8 years in backend engineering.”
Captured vacancy

example-capture-northstar-001 · v1
· Experience

“8+ years of relevant backend engineering experience.”

AWS experience

Your profile
No confirmed AWS evidence
The role
Production experience with AWS
Unknown

Add a specific project and its source before treating this as a match.

Inspect source documents
Example profile

example-profile-001 · v1
· Stack

“Python, PostgreSQL.”

A missing mention is not evidence that Alex lacks the skill.

Captured vacancy

example-capture-northstar-001 · v1
· Stack

“Python, PostgreSQL and production experience with AWS.”
A good decision can be “not this one.”

Here, a hard preference conflicts with the role. An unanswered question remains a question, even when other requirements match.

Choose your next step

Add to board
Create a case in To do on your board. Adding it does not submit an application.
Skip
Set it aside when the trade-off isn't worth it. A skipped role can be restored.
Investigate · planned
A separate decision to investigate is planned. Today, review the sources before adding or skipping a role. A note alone doesn't confirm a fact.

Add to board and Skip are available in the app. This demonstration does not save or submit anything.

A reason you can inspect.
A decision you control.

The workbench makes the basis of a recommendation visible. You can separate a confirmed conflict from missing information and see which question to answer next.

Start with the evidence
Compare what the profile says with what the vacancy actually asks for. Keep the source beside the finding.
Keep uncertainty visible
An unknown is an invitation to investigate. It shouldn't quietly become a negative score or an invented strength.
Keep the consequence clear
Choosing a role, preparing an application and submitting it are separate actions. The decision stays with the applicant.

Hiring has two sides.
This one is yours.

Explore the example

A product concept in development. No promises of interviews, offers or automatic submission.