# A Critical Hire: what would working with Alex actually be like?

**FICTIONAL EXAMPLE · COMPLETED ASSESSMENT SCENARIO.** Every person, organisation, quotation, assessment response, document, observation and event is invented. This demonstrates a reporting approach, not a real engagement, validated prediction or client outcome. No real participant data or test scores are used. The advice supports the employer’s decision.

**Candidate Case File · Hiring Dynamics · Alex Moreno, Senior Software Engineer · Hiring manager: Dana Price · Colleagues: Ellis Kim and Robin Cole · Interviewer: João Franqueira**

## Summary to Hiring Manager

**Hire Alex, with two conditions.** Alex is a reliable, thoughtful senior engineer who will make the team better. The risk is not Alex alone. It is what happens between Alex and Dana when things get tense.

**What you get:** someone who finishes what they start, explains hard technical choices so others can follow, and gives credit away easily. Alex wants to be trusted, not admired.

**What to watch:** when Alex is unsure, Alex goes quiet and investigates alone. Dana, under pressure, steps in and takes over. Each makes the other worse. If that loop starts, a good hire becomes a frustrated one within six months.

**The two conditions:** Dana agrees to ask for Alex’s current view instead of taking the work back. Alex agrees to raise a concern early, even half-formed, with a time for the next update.

**Risk level: Low to medium.** Technical skills are for your own process to check; this report covers the person and the fit.

## Case File 01 — Subject Overview

### Identity & Logistics

- **Name:** Alex Moreno
- **Role Applied For:** Senior Software Engineer (individual contributor, no direct reports)
- **Location / Work Eligibility:** Porto, Portugal · EU citizen, no visa needed · hybrid, two office days a week
- **Current Company / Scope:** Senior engineer at a logistics software company; owns the reliability of two customer-facing integrations
- **Current Status:** Employed; approached by the hiring team, not actively searching
- **Availability / Notice Period:** 60 days
- **Salary Expectation / Flexibility:** €78,000–€85,000 base · flexible on salary if given a real voice in planning
- **Constraints / Risks:** Will decline if the role means fixing promises made by others without a say in them

### Snapshot Narrative (neutral, 1 sentence)

> A careful, dependable engineer who earns trust through follow-through and tends to go quiet exactly when others need an update.

## Case File 02 — Behavioural & Personality Patterns

| Dimension | Conclusion | Notes / Observations (evidence, examples, quotes) |
|---|---|---|
| Communication Style | Clear and precise in writing; slower and more guarded out loud. | Decision notes were the best in the process, but the actual decision needed appeared in the last paragraph. In the customer exercise, opened with architecture before asking what the customer needed. |
| Cognitive Style | Analytical, sees trade-offs, prefers to finish thinking before speaking. | Named the one assumption that would break the integration plan. Comfortable holding two explanations at once. Slow to commit when the evidence is incomplete. |
| Emotional Intelligence (self/others/social) | Good self-reading; medium reading of others under pressure. | Knows when stress is building. Missed that product needed an early, rough warning more than a complete one. |
| Self-Awareness & Insight | High. | Unprompted: “People tell me I’m hard to read when I’m busy. They’re right.” |
| Authenticity vs Performativity | Authentic. Undersells rather than oversells. | Previous manager’s account was more positive than Alex’s own. No rehearsed answers on failure. |
| Stress Response Pattern (pressure behaviour) | Withdraws to investigate; cognitive narrowing, not emotional reactivity. | Under the new dependency in the second exercise, stopped talking for several minutes and worked alone before sharing. Calm tone throughout. |
| Conflict Style (avoid / confront / negotiate / appease) | Negotiates on facts; avoids conflict about people. | Challenged a deadline with evidence. Went silent when a colleague’s criticism became personal (“you always overcomplicate it”). |
| Neurochemical Profile — Primary Drive | Serotonin-led: stability, order, being trusted. Dopamine moderate. Oxytocin moderate. | Energy rises when describing systems that “run without me in the room”. Least energy for launches and visibility. |
| Neurochemical Profile — Secondary Drive | Dopamine through mastery, not novelty. Serotonin steady. Oxytocin shows as quiet loyalty to a few people. | Lit up describing a hard bug finally understood. Little interest in new tools for their own sake. |
| Preference Profile (estimation + alternatives) | Inward processing, pattern-focused, logic-led, prefers closure. Alternative: more detail-focused than pattern-focused. | Thinks before speaking, reasons from principles, wants decisions closed. Detail orientation in code reviews suggests the alternative. |
| Core Personality Traits (estimate or test) | Openness medium-high: will question existing designs and accept a better one. Conscientiousness high: finishes work, can over-check. Extraversion low: will not fill silence, so updates must be agreed. Agreeableness medium: kind in style, firm on substance. Emotional volatility low: steady, but stress shows as withdrawal. | Built from the interview, two exercises, written work and two references. Consistent across sources. |
| Shadow Traits & Blind Spots | Needs to be sure before being seen. Over-helping that turns a colleague’s answer into Alex’s. | Admitted preparing “until I can’t be wrong”. Peer: “Sometimes Alex helps a bit too much.” |
| Imposter Syndrome Indicators | Mild. | Discounts own role in successes; credits the team first. Not disabling. |
| Red Flags (behavioural) | None serious. Watch: silence under unclear ownership. | Same pattern reported by the previous manager in one project with disputed responsibility. |
| Dark Triad Markers (if any) | None observed. | Gave credit to a peer whose design replaced Alex’s. No entitlement, no blame-shifting. |

## Case File 03 — Motivations & Inner Drives

| Dimension | Conclusion | Quotes / Evidence (what supports the conclusion) |
|---|---|---|
| Dominant Narrative (their “story frame”) | The reliable one who quietly holds things together. | “I like leaving something people can trust when I’m no longer in the room.” |
| Core Values (stated + observed) | Reliability, honesty about trade-offs, fairness in credit. | Stated and observed: accepted a peer’s design and named its author in a senior review. |
| Type of Motivation (intrinsic/extrinsic/status/security/impact/autonomy) | Intrinsic: mastery and autonomy. Low status drive. | Turned down a team-lead title at the current company to stay close to the work. |
| Personal Mission | Fewer preventable failures; systems others can understand. | “Most firefighting is a decision someone made too fast.” |
| Running *from* | Being blamed for promises made by others. | Strongest emotion of the interview came describing a launch sold before engineering was asked. |
| Running *toward* | Influence over the commitments that create the work. | Asked twice who decides the roadmap. |
| Unmet Psychological Needs (recognition/belonging/control/mastery/safety) | Control over own commitments; a degree of safety to be wrong in front of others. | Current manager re-plans weekly. Alex: “I never know which promise I’m keeping.” |

## Case File 04 — Work Style & Leadership Approach

| Dimension | Conclusion | Key Observations (signals, examples, outcomes) |
|---|---|---|
| Planning & Prioritisation | Strong, as long as priorities stay put. | Built a clean plan in the first exercise; lost time when the dependency changed and nobody re-ranked priorities. |
| Stakeholder Management | Good with engineers, weaker with product and customers. | Patient with Robin. Asked Ellis questions that felt like a test. |
| Temporal Focus (now vs future) | Future-leaning; protects the system over the quick win. | Proposed observability work before more features. |
| Optimal Work Structure (structure/autonomy; chaos tolerance) | Clear ownership plus freedom inside it. Low tolerance for chaos without a decision owner. | Fast and early when responsibility was explicit; slow when disputed. |
| Relationship with Authority (alignment/challenge/dependency/politics) | Respectful challenge with evidence. No politics. | Pushed back on a deadline with numbers, not escalation. |
| Decision-Making Style (speed; data vs intuition; risk appetite) | Data-first, medium speed, low risk appetite. | Chose a reversible pilot when pushed to decide fast. |
| People Management Capability (scope + maturity) | Not required. Strong mentoring and peer influence. | Junior engineer at previous company described Alex as “the person who explains why”. |
| Feedback Receptivity (coachability; defensiveness) | Coachable on specific feedback; explains intent first. | Took the late-warning feedback, explained why, then changed the behaviour in the follow-up. |
| Team Elevation Potential (how they make others better) | High. Raises the reasoning level of the whole team. | Leaves colleagues able to decide without Alex. |
| Handling Mistakes / Failure (ownership, learning, blame) | Owns mistakes; no blame. | Changed a recommendation the moment a dependency error was pointed out. |

## Case File 05 — Cultural Compatibility & Systemic Fit

| Dimension | Conclusion | Key Observations (signals, examples, outcomes) |
|---|---|---|
| Cultural Alignment | Good fit with a team that values reliability and honest limits. | The team’s stated goal for the next six months is fewer repeated incidents. |
| Potential Tension Points | Dana’s need for quick visibility. Ellis’s exploratory talk that sounds like a promise. | Dana took over two unfinished decisions in her own examples. |
| Frustration Threshold (low/med/high; triggers) | Medium. Triggers: shifting priorities, promises made without engineering, being taken over. | Clear irritation describing these three situations; calm about everything else. |
| Likely Integration Speed (fast/med/slow; why) | Medium. Trust builds through delivery, not charm. | Expect 6–8 weeks before the team sees Alex’s full value. |
| System Fit (pace, ambiguity, accountability, collaboration) | Good on accountability and collaboration; medium on pace and ambiguity. | Works best when ambiguity has a named owner. |
| Risk of Disengagement / Misfit (how it would show up) | Medium if Dana does not change. It would show as quieter meetings and longer written defences. | The previous manager saw exactly this before Alex left that team. |

## Case File 06 — Relational Patterns

| Dimension | Conclusion | Key Observations (signals, examples, outcomes) |
|---|---|---|
| Attachment Style (hypothesis) | Secure with an avoidant lean under stress. | Steady relationships over years; pulls back when trust feels questioned. |
| Trust-Building Speed / Rapport | Slow and durable. | Warmed up visibly in the second half of the interview, not the first. |
| Relational Warmth vs Distance | Reserved warmth, shown through help rather than personal disclosure. | Remembered details of a colleague’s project from two years ago. |
| Loyalty Patterns (to people, mission, self-interest) | Loyal to people who are fair and to work done well. | Stayed a year longer at a previous job to finish a migration for the team. |
| Boundary Health (too porous vs too rigid; conflict boundaries) | Healthy, slightly rigid around technical standards. | Separates a must-have safeguard from a preference when asked. |

## Case File 07 — Strategic Forecast & Recommendations

| Scenario | Conclusion |
|---|---|
| If hired, what could go really well? | Fewer repeated incidents within two quarters, better engineering decisions across the team, and a senior person others can learn from. |
| …and what could go really wrong? | A silence–takeover loop with Dana. Alex feels distrusted, Dana feels uninformed, and Alex leaves within a year. |
| Likely relationship with leadership | Productive if Dana asks for provisional answers. Strained if every unfinished answer triggers intervention. |
| Likely relationship with peers / partners | Easy with Robin, perhaps too easy. Needs work with Ellis to connect to the customer. |
| Strategic / behavioural risk level (Low/Med/High) | Low to Medium. |
| What must be true for success (non-negotiables) | Dana stops taking over unfinished work. Alex gives early, incomplete warnings. Engineering has a voice before customer promises are made. |
| What to validate next (questions / references / work sample focus) | Ask a second reference about a high-visibility incident. In the offer conversation, ask Alex how they would flag a risk to Dana in week two. |

## Other Relevant Info

- Alex asked good questions about the team’s on-call load; this matters to them more than salary.
- Technical skills were assessed by the employer, not by Élan.
- Alex will receive personal feedback on the assessment; Dana receives the decision-relevant findings only.
- Scope illustrated: Critical Hire, €4,500 for one candidate, the hiring manager and two colleagues. Each additional assessed colleague is €500. VAT is additional.

## Hidden Information

- **Said without being said:** Alex left the last team because of a manager who took over. That was never stated directly, but it came up three times in different stories.
- **Conflicting information:** Alex describes being “fine with fast pace”. Every example of good work involved stable priorities.
- **Pattern under the surface:** the thoroughness protects quality and also protects Alex from being seen to be wrong. Alex half-recognised this when asked.
- **What Dana did not say:** her description of the ideal hire (“takes problems off my plate”) clashed with her examples, where she took problems back.

## Interviewer Conclusions

**My read.** I trust Alex. The evidence was consistent across the interview, the exercises and two people who worked with them, which is rarer than it should be. What worried me at first, the silence, turned out to have a clear trigger. When Alex knew who owned the decision, the warning came early and the next step was sensible. I would not hire Alex into a team where priorities change weekly. This team, with Dana’s commitment, is not that.

**Where I could be wrong.** Exercises are contained. A real incident at 2 a.m. is not. If Alex stays silent even with clear ownership and a manager who welcomes bad news, my read needs revising.

### Final Recommendation

○ Proceed with confidence · ● **Proceed with caution** · ○ Further assessment needed · ○ Reject

Proceed, on the two conditions above. — *João Franqueira*

## The first 90 days

| When | Who | What to do | What good looks like |
|---|---|---|---|
| Before joining | Dana + Alex | Agree priorities, who decides what, and three situations that need an early warning | Both describe the same expectations. |
| Days 1–30 | Alex + Ellis | Share the current view and open assumptions on the integration every week | Ellis hears about uncertainty before talking to the customer. |
| Days 1–30 | Dana | Welcome an unfinished warning without taking over | Alex can name one concern that stayed theirs to solve. |
| Days 31–60 | Alex + Robin | Alternate decision ownership; stop reviews once the standard is met | Another engineer ships a sound decision without Alex’s sign-off. |
| Days 61–90 | Dana + team | Review two warnings, one disagreement and one handover | Name where this report was right and where it was wrong. |

## Application of the MindFrame Model

How the nine MindFrame lenses were applied to Alex. Each lens has a question, an observation and a prediction we can check later.

| Depth of this assessment | |
|---|---|
| Structured conversation with Alex | 3 h 10 min across two sessions |
| People around the role assessed | 3 (manager and two colleagues) |
| Behavioural examples examined | 24, each tested for a counterexample |
| Work samples and exercises | 2 integration exercises, 1 customer segment, written decision notes |
| Independent accounts | Previous manager and previous peer |

### Personality traits

**What this lens reads:** stable behavioural tendencies across contexts: openness, conscientiousness, social energy, cooperation and emotional volatility.

**Questions we asked:** “Tell me about a piece of work you finished that nobody asked you to finish.” · “When did you last change your mind in a meeting, and what changed it?”

**What we observed:** High conscientiousness in every example; low social energy; steady emotion. Openness showed when Alex dropped their own design for a better one.

**What it predicts here:** dependable delivery and few surprises, provided updates are agreed rather than expected to happen spontaneously.

**Confidence:** High. Interview, exercises and both references agree.

### Cognition

**What this lens reads:** how someone handles nuance and trade-offs, switches between intuition and analysis, and balances now against later.

**Questions we asked:** “Walk me through a decision where both options were reasonable.” · “What did you decide before you had all the data?”

**What we observed:** High integrative complexity; strong analytical mode; slow switch to intuition under time pressure. Future-oriented.

**What it predicts here:** good judgement on reliability work; needs a deadline for deciding, not only for delivering.

**Confidence:** High.

### Metacognition & responsibility

**What this lens reads:** the ability to observe and correct oneself, and whether ownership sits inside or outside the person.

**Questions we asked:** “What would your last manager say you are still learning?” · “Tell me about a failure where part of it was yours.”

**What we observed:** Accurate self-description. Internal ownership: named their own part before the context.

**What it predicts here:** coachable on specific feedback; improvement will be fast once a pattern is named.

**Confidence:** High.

### Motivation

**What this lens reads:** intrinsic versus extrinsic drive, what someone is running toward and away from, unmet needs and work-style drivers.

**Questions we asked:** “What was the best day at work in the last year?” · “What would make you leave this role in twelve months?”

**What we observed:** Mastery and autonomy dominate. Running from blame for others’ promises; toward a voice in planning.

**What it predicts here:** retention depends on access to planning more than salary or title.

**Confidence:** High.

### Stress & self-regulation

**What this lens reads:** whether pressure collapses prioritisation, emotion or relationships.

**Questions we asked:** a new dependency introduced mid-exercise after a deadline was agreed. “What did you notice in yourself just then?”

**What we observed:** Cognitive narrowing and withdrawal. No emotional or relational collapse: tone stayed calm and respectful.

**What it predicts here:** in incidents, Alex will work hard and talk little. The team needs an update rhythm agreed in advance.

**Confidence:** Medium-high. Seen in the exercise and in one reference.

### Relational patterns

**What this lens reads:** trust, conflict style, feedback receptivity and boundaries.

**Questions we asked:** “Who at work do you trust most, and how did that start?” · “What happens in you when criticism feels unfair?”

**What we observed:** Slow, durable trust. Negotiates facts, avoids personal conflict. Healthy boundaries, slightly rigid on standards.

**What it predicts here:** strong peer relationships over time; personal criticism from Dana would push Alex into silence.

**Confidence:** Medium-high.

### Derailment risk

**What this lens reads:** shadow traits and dark-side markers (entitlement, manipulation, low empathy, blame-shifting), always as behaviours, never diagnoses.

**Questions we asked:** “Tell me about a time someone else got credit for your work.” · “What do people get wrong about you?”

**What we observed:** No dark-side markers. Shadow: over-preparation as self-protection; over-helping.

**What it predicts here:** low risk of toxic behaviour; moderate risk of becoming the bottleneck for approvals.

**Confidence:** High for the absence of markers.

### Neurochemical drives

**What this lens reads:** the primary and secondary drives that shape energy and boredom: Dopamine (novelty, reward), Serotonin (stability, status through trust), Oxytocin (connection, belonging).

**Questions we asked:** “When do you lose track of time at work?” · “What kind of week drains you?”

**What we observed:** Serotonin primary, Dopamine secondary through mastery. Oxytocin expressed through loyalty to a few people.

**What it predicts here:** energised by stabilising systems; drained by constant launches and reshuffled priorities.

**Confidence:** Medium. A preference map, anchored in examples, not a medical measure.

### Preference typology

**What this lens reads:** a hypothesis about how someone gathers energy, takes in information, judges and closes decisions. Used to predict communication friction, not competence.

**Questions we asked:** “How do you prepare for a meeting where you need to persuade someone?”

**What we observed:** Inward processing, pattern-focused, logic-led, closure-seeking. Alternative: more detail-focused than pattern-focused.

**What it predicts here:** friction with fast, talk-it-through colleagues such as Ellis unless the conversation is labelled as exploration or commitment.

**Confidence:** Medium. A hypothesis with an alternative, grounded in behaviour.