fydell

The hiring system forfinding people who canactually do the work.

Get startedSee how it works

Employer

Solutions Engineer

Northstar
  • Review evidence
  • Shortlist
  • Evidence
  • Interview plan
  • Role calibration
  1. C1Candidate 1Evidence reviewed
  2. C2Candidate 2Evidence reviewed
  3. C3Candidate 3Defense complete
  4. C4Candidate 4Interview scheduled

Review evidence

Northstar · Solutions Engineer

Candidate 1

  1. Initial recommendationStructural discovery

    Separated stated requirements from assumptions before recommending an architecture.

  2. Constraint receivedSecurity review

    Acme security team raised a six-week authentication review constraint.

  3. Plan revisedRollout plan

    Revised the rollout plan to accommodate the security review window.

  4. Oral defense completedExecutive review

    Explained tradeoffs in language an executive sponsor could use.

  5. Human reviewFollow-up

    Reviewer rated responses and flagged one assumption for follow-up.

Plan revised

Summary

Revised the rollout plan after the security team introduced a six-week authentication review constraint.

Source

acme_rollout_brief.docx

Changes

Launch in four weeks

Launch in ten weeks, after security review

Reviewer note

Handles the constraint without abandoning the original approach.

Mark as reviewed

Hiring should be based on demonstrated work, not polished claims. Fydell shows how candidates reason, adapt, communicate, and defend decisions in realistic work, before you spend hours interviewing them.

Work, not a test

Candidates handle the ambiguity, tradeoffs, and stakeholder pressure the role contains.

Evidence with limits

Claims stay linked to supporting events, counter evidence, and remaining uncertainty.

A better interview

The final brief resolves the work into the questions most likely to change your decision.

Turn candidate work into hiring evidence.

Candidates work through a realistic customer problem. Their assumptions, decisions, revisions, and explanations become a reviewable trail.

Candidate workbenchCandidate 1 · NorthstarAutosaved 16:13Encrypted

rollout_plan.md

MarkdownRevision 4Saved 16:13Synced
## Rollout
Launch all 1,200 seats in a single production cutover at week six.
The authentication security review can run in parallel with production access.
Weeks 1–6 · sandbox tenant only, while the six-week security review completes.
Week 7 · controlled 200-user cohort in production, after review sign-off.
Then expand by business unit after the first support review.
Phase one can support 200 users while the remaining business units prepare for production access.
Adoption risk should remain low because the sponsor reports strong weekly usage.
Cohort size stays provisional until weekly active-user data is verified.

Current recommendation

Begin with a controlled 200-user deployment, validate identity mapping, then expand by business unit after the first support review.

Sources cited in this revision

  • security_brief.pdf · p.3 · authentication review scope
  • discovery_call.md · 14:02 · 1,200 seats, six-week launch target
  • assumptions.md · 14:22 · weekly_active_users marked unverified
Incoming constraint

The authentication security review takes six weeks

Acme’s security lead confirms the review is sequential, not parallel. Production access cannot be granted until it closes.

Source
Security lead, Acme
Impact
Blocks production access
Reaction time
5m 08s

Define the role before you evaluate the candidate.

Calibrate the situation and the signals with the hiring team first, so evidence is judged against the work the person will actually do.

Role calibration

Solutions EngineerShare

Define what great looks like, connect evidence, and align on judgment.

Discovery

Understand the problem and stakeholders

Architecture

Design the right solution and approach

Rollout

Deliver value and ensure adoption

Executive handoff

Transfer ownership and drive outcomes
Discovery judgment30%
Stakeholder map complete
Problem framed and validated
Risks and assumptions validated
Technical translation20%
Requirements clarified
Solution approach socialized
Solution proven in relevant context
Adaptation30%
Change detected
Plan adapted and tradeoffs updated
Stakeholders aligned on updated plan
Commercial judgment20%
Value and success metrics defined
Business case and ROI validated
Adoption and value tracking in place
Evidence sources Interview Work sample Stakeholder feedback Project artifact
Candidate workbenchCandidate 1 · Acme rollout

Acme technical discovery

  • Discovery notes
  • Architecture brief
  • Rollout plan
  • Customer email
  • Assumptions

Customer thread

Security lead, Acme · 10:44

Please update the rollout plan to reflect this constraint and the revised approach.

Write a reply…Send

Current recommendation

Sandbox now, production access after security sign-off

RequirementSourceConfidenceDecision impact
Security review is mandatory before production access.security_brief.pdfHighBlocks production for six weeks
Production access requires customer success approval.discovery_call.mdMediumAdds an approval step
Adoption tracking depends on weekly active users.sponsor_estimate.xlsxLowAffects the timeline estimate

Evidence

security_brief.pdfpage 4

Unverified

sponsor_estimate.xlsxsheet: usage

Observe what changes when reality changes.

Fydell introduces consequential information during the work. The signal is how the candidate updates the recommendation, not whether they guessed the twist.

Changed-information eventCandidate 1 · Acme rollout
rollout_plan.mdRevision 4 · saved 16:13

## Rollout sequence

10Launch all 1,200 seats in one production cutover at week six.

11Authentication review runs in parallel with production access.

10Weeks 1–6: sandbox tenant while the security review completes.

11Week 7: controlled 200-user cohort after security sign-off.

12Expand by business unit after the first support review.

## Open assumption

18Cohort size remains provisional until weekly active-user data is verified.

  1. assumption_addedweekly_active_users: unverified
  2. constraint_deliveredsecurity_review: six weeks, sequential
  3. artifact_revisedrollout_plan.md → revision 4

Make candidates defend the decisions they made.

Follow-up questions come from the candidate’s own artifacts, assumptions, and limitations. The answer adds evidence; it does not erase uncertainty.

Oral defenseCandidate 1 · generated from the workQuestions from rollout_plan.mdRubric SE-1.4
RecordingQuestion 2 of 3 elapsed

Question source · rollout_plan.md · line 14

Phase one can support 200 users while the remaining business units prepare for production access.

Adoption risk should remain low because the sponsor reports strong weekly usage.

  1. Fydell

    Your adoption assumption comes from the sponsor. How would you test it before using it to size the first production cohort?

  2. Candidate 1

    I would ask for active-user data by team and compare it with license assignment. If that is unavailable, I would keep the first cohort smaller and treat the sponsor’s number as directional.

  3. Candidate 1

    The number I would not move on is the sandbox window, because that one is set by the review

Transcribing

Review evidence, not just a final answer.

A human reviewer sees the event trail, supporting and counter evidence, and the limits that must travel with each claim.

Evidence insightsSolutions Engineer
AdaptationAdapting the customer recommendationEvidence confidenceUncertainSupported with limits

Claim

The rollout plan was adapted to account for a six-week authentication security review, and the tradeoff was defended in the candidate’s own words.

Evidence lineage

Initial planrollout_plan.md · line 18

Six-week timeline assumes no pre-launch security review.

SupportingRevised planrollout_plan.md · line 42

Sandbox-first approach accommodates the six-week review.

SupportingDefense answeroral defense · Q2

Explained the tradeoff and why the constraint was retained.

CounterevidenceShorter rolloutsponsor_estimate.xlsx

Sponsor estimate assumed no extended review.

Supporting evidence

  • Plan revised to sequence a sandbox-first approach.

    Adjusts sequencing so production access follows the security review.

    rollout_plan.md
  • Constraint received from the security team.

    Security review is mandatory before production access.

    security_brief.pdf

Counterevidence

  • Sponsor estimate uses a shorter timeline.

    Estimate assumes no extended security review.

    sponsor_estimate.xlsx
  • Industry benchmark shows longer cycles.

    Similar companies report six to eight week reviews.

    benchmark_2026.pdf

Human review

K. PatelSolutions Engineering lead
Approved

Notes

Tradeoffs explained clearly. Constraint retained and plan updated accordingly.

Reviewed 17:32

Open full evidence
Oral defenseQuestion 2 of 3

Artifact

rollout_plan.mdline 14

Generated question

Your adoption assumption comes from the sponsor. How would you test it before using it to size the first production cohort?

Live transcript

  • Candidate

    I'd look for active-user data from teams similar to the sponsor and compare it to their license assignment.

  • Interviewer

    And if that data isn't available?

  • Candidate

    I'd size the first cohort smaller and treat the sponsor's number as directional, then validate with early usage.

rollout_plan.md · line 14

Competency

Commercial judgment
Evidence confidenceUncertainSupported with limits

Walk into the interview knowing what to ask.

The brief explains why Candidate 1 is worth interviewing, what remains uncertain, and the three questions most likely to change the decision.

Interview briefCandidate 1 · Solutions EngineerReview completed 18 Aug

Interview plan

Candidate 1

Interviewer
MK
Estimated duration
45 minutes
Round
Panel 1 of 2

Reviewer decision

Advance to interview

Candidate 1 shows structured discovery, clear customer communication, and useful adaptation. Probe how they validate adoption assumptions before expanding scope.

  1. Tell me about a time customer urgency conflicted with a security constraint. What did you preserve, and what moved?

    rollout_plan.md · revision 4 · 16:13
    Why it matters
    The Acme revision is the strongest observed signal for Adaptation. A second example shows whether it repeats outside a prompted moment.
    Unresolved assumption
    Whether the sequencing instinct holds when the constraint comes from an internal team rather than the customer.
    A strong answer
    Names what was preserved, what moved, and who was told — not just that the plan changed.

  2. How do you validate an executive sponsor’s adoption claim before committing an implementation team?

    assumptions.md · 14:22 · weekly_active_users unverified
    Why it matters
    Candidate 1 marked the number unverified and still used it to size the first cohort.
    Unresolved assumption
    Rollout sizing still depends on Acme’s self-reported weekly active-user count.
    A strong answer
    Describes a concrete check — usage by team against license assignment — and what they would do when it is unavailable.

  3. Which fact in the Acme brief would most likely change your recommendation again?

    defense transcript · 16:31 · question 2 of 3
    Why it matters
    Tests whether the candidate can rank their own uncertainty instead of defending the plan they already wrote.
    Unresolved assumption
    Whether the six-week review is the only sequencing blocker Acme has not disclosed.
    A strong answer
    Picks a fact with real decision impact and says how they would detect the change early.

Interviewer evaluation · completed after the session

Record what changed your view, and which assumption is now resolved.

Shared with hiring panel · 18 AugExported · brief_candidate-1.pdf

Learn which evidence proved useful later.

Fydell does not claim validated prediction today. The loop preserves evidence and later outcomes so employers can examine useful signals and recalibrate future roles.

Calibration loopNorthstar · no predictive claim1 role · 1 cycle recorded

  1. Hiring evidence

    Keep the evidence claims and their stated limits.

    5 claims · 2 carry limitations
    Recorded

  2. Hiring decision

    Record what the team chose to probe and why.

    Advance to interview · 18 Aug
    Recorded

  3. Observed outcome

    Later, add role outcomes the employer can support.

    Nothing recorded yet
    Awaiting outcome

  4. Calibration review

    Examine which signals were useful; revise the role definition.

    Feeds the next role definition
    Scheduled

The review returns to the role definition. Fydell does not claim validated prediction today; the loop preserves what was seen and what happened next.

Hire based on what people can actually do.

Start with one Solutions Engineer role. Fydell runs the work and returns the people worth interviewing, with the evidence underneath.

Get startedContact sales