Preview the full report experience

See exactly what buyers receive after completion, including role-fit insights, strengths, team-health coaching, and growth priorities.

Primary role

Maintainer

Maintainers protect uptime and service trust by designing resilient run states and disciplined incident response systems.

Secondary role

Architect

Architects bring order to complexity by aligning platforms, setting durable standards, and making clear tradeoffs across risk, cost, and speed.

Overall fit signal

Green

Your current fit and skill level are well aligned with this job family. Focus on deepening strengths and expanding scope.

Integrity status

Green

No major answer-pattern concerns detected.

Personality profile

These dimensions show your natural work style. Strong scores mean a clear preference; middle scores mean you can adjust your style to fit different situations.

Connector ↔ Concentrator
🔥 Strong tilt
Connector
Personality score +3.3 out of a range from -5 to +5
Strong (positive pole): Reliable preference, will show under stress
You show a strong connector tendency in how you communicate and process work.
✨ Strength: Your connector style is a reliable asset for team velocity when used with intent.
🎯 Development: Deliberately practice concentrator behaviors in high-stakes work so communication quality and execution depth stay balanced.
Growth playbook
- Weekly habit: reserve two collaboration blocks and two deep-focus blocks on your calendar.
- Growth move: in one critical task this week, intentionally use concentrator behavior to improve outcome quality.
- Watchout: style overuse can create either meeting overload or visibility gaps.
Connector
Tendencies: Thinks out loud, collaborates quickly, builds momentum through interaction.
Strengths: Fast alignment, strong cross-team coordination, high social energy.
Growth edge: Can over-meet, dilute deep focus, or commit before full analysis.
Concentrator
Tendencies: Processes internally, prefers uninterrupted blocks, works deeply before sharing.
Strengths: High focus quality, careful reasoning, strong independent execution.
Growth edge: Can under-communicate progress or miss early stakeholder alignment.
Concrete ↔ Conceptual
🔥 Strong tilt
Concrete
Personality score -3.3 out of a range from -5 to +5
Strong (negative pole): Reliable preference, will show under stress
You strongly prefer concrete thinking when framing problems and solutions.
✨ Strength: Your concrete orientation helps you make clear decisions in ambiguous situations.
🎯 Development: Build a repeatable counterbalance: add one conceptual check in every major decision before committing.
Growth playbook
- Weekly habit: write one decision note with a practical action and a long-term implication.
- Growth move: add one conceptual checkpoint before final sign-off.
- Watchout: over-leaning can produce either tactical churn or strategic drift.
Concrete
Tendencies: Grounds decisions in practical details, examples, and immediate implementation reality.
Strengths: Execution clarity, realistic estimation, reliable near-term delivery.
Growth edge: Can underweight long-term abstraction or architectural leverage.
Conceptual
Tendencies: Frames problems through models, principles, and future-state design.
Strengths: System-level thinking, scalable abstractions, strategic direction setting.
Growth edge: Can over-index on theory and delay practical delivery details.
Systems ↔ Stakeholders
🔥 Strong tilt
Systems
Personality score -3.3 out of a range from -5 to +5
Strong (negative pole): Reliable preference, will show under stress
You consistently default toward the systems side when tradeoffs get difficult.
✨ Strength: This gives your decisions coherence and protects quality in the areas you value most.
🎯 Development: Reduce blind spots by explicitly testing decisions through a stakeholders lens before rollout.
Growth playbook
- Weekly habit: for each major decision, capture one technical risk and one adoption risk.
- Growth move: ask one teammate with a stakeholders bias to challenge your draft decision.
- Watchout: one-sided tradeoffs can be technically elegant but operationally fragile.
Systems
Tendencies: Optimizes for technical correctness, consistency, and logical rigor.
Strengths: Strong quality bars, robust tradeoff analysis, technical integrity.
Growth edge: Can miss adoption risk or interpersonal friction during change.
Stakeholders
Tendencies: Prioritizes user impact, team dynamics, and communication outcomes.
Strengths: High trust, better adoption, smoother cross-functional collaboration.
Growth edge: Can defer hard technical calls or accept costly compromise.
Planner ↔ Adaptor
🔥 Strong tilt
Planner
Personality score -3.3 out of a range from -5 to +5
Strong (negative pole): Reliable preference, will show under stress
You show a clear planner default in how you manage uncertainty and execution rhythm.
✨ Strength: Your planner style gives your team predictability and directional clarity.
🎯 Development: Intentionally rehearse adaptor responses during live work so you can stay effective when conditions shift.
Growth playbook
- Weekly habit: start with a short plan, then schedule one deliberate adaptation checkpoint.
- Growth move: practice one adaptor response path before you need it in real time.
- Watchout: extreme planning or adapting can either slow momentum or create avoidable rework.
Planner
Tendencies: Prefers structure, sequencing, and predictable execution paths.
Strengths: Risk control, dependable delivery, strong operational discipline.
Growth edge: Can move slowly under ambiguity or resist needed pivots.
Adaptor
Tendencies: Responds fluidly to change, iterates quickly, and adjusts in motion.
Strengths: Resilience in uncertainty, fast recovery, creative problem solving.
Growth edge: Can create inconsistency or rework without enough planning guardrails.

Competency profile

These scores estimate your current skill level in each role style. Higher levels mean you can apply that style more consistently in real work.

Supporter
✅ Solid
L3 Specialist
Competency score 3.0 out of 5
You are independently effective in Supporter work and ready for cross-team influence growth.
✨ Strength: Identifies recurring pain patterns and drives service improvements.
🎯 Development: Lead support operations that improve user outcomes and cross-team collaboration.
📘 Curriculum: Customer success principles for technical support. + Data-informed support operations and service quality metrics.
🪪 Certifications: HDI Support Center Team Lead, Microsoft 365 Certified: Endpoint Administrator
Maintainer
✅ Solid
L3 Specialist
Competency score 3.0 out of 5
You are independently effective in Maintainer work and ready for cross-team influence growth.
✨ Strength: Finds systemic causes and drives prevention instead of repeated firefighting.
🎯 Development: Lead reliability initiatives that reduce systemic risk across services.
📘 Curriculum: Incident command systems and postmortem facilitation. + Resilience engineering and chaos testing fundamentals.
🪪 Certifications: Google Professional Cloud DevOps Engineer, CKA
Builder
✅ Solid
L3 Specialist
Competency score 3.0 out of 5
You are independently effective in Builder work and ready for cross-team influence growth.
✨ Strength: Unblocks delivery by debugging deeply across stack boundaries.
🎯 Development: Lead delivery in complex domains and mentor peers on engineering rigor.
📘 Curriculum: Advanced testing strategy and reliability-aware engineering. + Architecture for engineers: scalability and maintainability patterns.
🪪 Certifications: CKAD, Azure Developer Associate (AZ-204)
Architect
✅ Solid
L3 Specialist
Competency score 3.0 out of 5
You are independently effective in Architect work and ready for cross-team influence growth.
✨ Strength: Creates patterns and standards that raise quality across teams.
🎯 Development: Lead cross-team architecture efforts that balance delivery pressure and long-term maintainability.
📘 Curriculum: Distributed systems, event-driven architecture, and resilience engineering. + Platform strategy and governance operating models.
🪪 Certifications: Google Professional Cloud Architect, TOGAF Foundation

Placement interpretation

Overall fit signal combines fit and skill into practical guidance. Use it to plan your next move, not as a fixed label.

Your strongest style is Maintainer, supported by Architect. For this role family, focus on growing this strength while closing key gaps in architect skills.

✨ Strength assets

Builds stable operations through strong runbooks and observability.
Connects business intent to long-horizon technical direction.
Pinnacle benchmark: At your pinnacle, you institutionalize reliability culture, prevent major incidents through proactive controls, and keep mission-critical systems trustworthy at scale.

🧭 Jobs to Grow Into

Vice President, IT
Sr Manager, IT
Director, IT
Enterprise Architect
Solutions Architect

🎯 Development priorities

Translate architecture decisions into delivery guardrails teams can execute this quarter.
Secondary gap check (Builder): build more consistent performance when things are unclear.
Primary growth focus (L3): Lead reliability initiatives that reduce systemic risk across services.

🚀 Career growth next steps

Curriculum for next level: Incident command systems and postmortem facilitation. + Resilience engineering and chaos testing fundamentals..
Certifications to pursue: Google Professional Cloud DevOps Engineer, CKA.
Weakest-path accelerator: Distributed systems, event-driven architecture, and resilience engineering. (cert: Google Professional Cloud Architect).

Inferred overlay

Team Health Assessment

moderate confidence

These Team Health Assessment observations are inferred from IT-PCM responses as behavioral coaching hypotheses. They are not personality diagnoses or a licensed external assessment; validate them with work examples, manager feedback, and team context.

Healthy teams turn vulnerability-based trust into productive conflict, clear commitment, peer accountability, and collective results. Use this section as a conversation starter, not as a label.

Team health

Peer accountability

83/100

Strength

You may help teams make standards clear enough that peers can challenge misses without waiting for a manager.

Evidence: Planner and systems signals suggest standards, ownership, and quality expectations may be visible. Maintainer fit and current skill are aligned, so these prompts can be practiced in broader team settings.

Watchout: Accountability can feel like inspection if it is not balanced with context and help.

Practice next: Pair every standard with an escalation path and a help path.

Organizational clarity

Purpose

30/100

Growth edge

Purpose may remain implicit unless you deliberately connect tasks to customer, team, or business impact.

Evidence: Systems, concrete, or concentrator signals suggest purpose may need deliberate translation beyond the work itself. Maintainer fit and current skill are aligned, so these prompts can be practiced in broader team settings.

Watchout: People may hear only activity, not meaning.

Practice next: Ask 'who is better off if this works?' before defining scope.

Leadership discipline

Accountability over popularity

70/100

Strength

You may be able to maintain standards without relying on approval.

Evidence: Planner, systems, and concentrator signals suggest willingness to hold standards even when the conversation is not easy. Maintainer fit and current skill are aligned, so these prompts can be practiced in broader team settings.

Watchout: Direct accountability still needs empathy and context.

Practice next: Give feedback with the standard, observed gap, impact, and support offer.

Organizational clarity

Business definition

37/100

Growth edge

The team may need stronger language for the customer, service, or business problem behind the work.

Evidence: Systems, concrete, or concentrator signals suggest the business definition may need deliberate translation beyond tasks and technical scope. Maintainer fit and current skill are aligned, so these prompts can be practiced in broader team settings.

Watchout: Technical activity can look productive while drifting from the reason the work exists.

Practice next: Before sizing work, name the customer served and the visible outcome they should experience.

Full principle map

Team health

How your current IT-PCM pattern may support trust, conflict, commitment, accountability, and shared outcomes.

Vulnerability-based trust: Growth edgeProductive conflict: DevelopingCommitment: StrengthPeer accountability: StrengthCollective results: Developing

Organizational clarity

How you may help a team clarify purpose, values, business definition, strategy, priorities, and ownership.

Purpose: Growth edgeValues in action: DevelopingBusiness definition: Growth edgeStrategic anchors: DevelopingCurrent priority: StrengthOwnership: Strength

Leadership discipline

How your default style may behave under classic leadership tradeoffs around trust, conflict, clarity, and accountability.

Results over status: DevelopingAccountability over popularity: StrengthClarity over certainty: Growth edgeConflict over artificial harmony: StrengthTrust over self-protection: Growth edge

Work contribution

How your work energy may show up through humility, hunger, interpersonal smartness, and Working Genius-style cues.

Humble: DevelopingHungry: StrengthInterpersonally smart: Developing

Work energy hints

Discernment/Enablement: concrete energy may show up as testing ideas against practical constraints and helping work become usable.
Galvanizing: connector energy may help pull people into action through conversation, momentum, and shared visibility.
Tenacity: planner energy may show up as follow-through, sequencing, and durable execution habits.

Growth blueprint by role style

Clear coaching for each role style so you know what to build on, what to improve, and which habits help you grow faster.

Supporter

Current level: L3 Specialist

Assessment signal: 3.0/5 at L3 indicates solid independent execution with meaningful upside through deliberate practice.
Strength to amplify now: Builds trust through clear communication in high-friction moments.
Growth edge to close: Increase root-cause depth so repeated issues become permanent fixes.
Big Five: Agreeableness plus emotional stability supports trust-building in high-friction interactions. Applied here: De-escalate user stress while preserving issue clarity and momentum to resolution.
MBTI: NF/SF empathy orientation strengthens communication and service recovery quality. Applied here: Translate technical issues into user-centered language that improves adoption and confidence.
DISC: High I + S blend emphasizes rapport, patience, and collaborative support rhythms. Applied here: Create consistent support experiences while surfacing recurring pain patterns to product teams.
Assertive habit: Facilitate a weekly support-to-engineering handoff review with trend data and one agreed service improvement experiment.
Pinnacle target: At your pinnacle, you turn frontline signals into service improvements, raise customer confidence, and build durable enablement systems that scale.
Next-level growth focus: Lead support operations that improve user outcomes and cross-team collaboration.
Curriculum path: Customer success principles for technical support. + Data-informed support operations and service quality metrics.
Certification path: HDI Support Center Team Lead, Microsoft 365 Certified: Endpoint Administrator

Maintainer

Current level: L3 Specialist

Assessment signal: 3.0/5 at L3 indicates solid independent execution with meaningful upside through deliberate practice.
Strength to amplify now: Builds stable operations through strong runbooks and observability.
Growth edge to close: Shift from reactive incident handling to proactive reliability engineering.
Big Five: High conscientiousness and lower impulsivity support operational consistency. Applied here: Build reliable run states through repeatable controls, runbooks, and preventive checks.
MBTI: SJ reliability orientation emphasizes process discipline and risk containment. Applied here: Operationalize incident response and change management with clear escalation and closure loops.
DISC: High C profile favors precision, compliance, and error prevention. Applied here: Tighten monitoring, SLO governance, and post-incident corrective action follow-through.
Assertive habit: Run a weekly reliability review that tracks SLO drift, alert noise, and closure of top preventive actions.
Pinnacle target: At your pinnacle, you institutionalize reliability culture, prevent major incidents through proactive controls, and keep mission-critical systems trustworthy at scale.
Next-level growth focus: Lead reliability initiatives that reduce systemic risk across services.
Curriculum path: Incident command systems and postmortem facilitation. + Resilience engineering and chaos testing fundamentals.
Certification path: Google Professional Cloud DevOps Engineer, CKA

Builder

Current level: L3 Specialist

Assessment signal: 3.0/5 at L3 indicates solid independent execution with meaningful upside through deliberate practice.
Strength to amplify now: Transforms ambiguous goals into executable increments.
Growth edge to close: Increase architectural reasoning so implementation choices age well.
Big Five: Conscientiousness predicts follow-through, quality habits, and disciplined delivery. Applied here: Translate requirements into consistent execution rhythms with strong test and release hygiene.
MBTI: ST/SP execution styles prioritize practical action, rapid iteration, and concrete outcomes. Applied here: Bias for shipping validated increments while preserving maintainability and observability.
DISC: D + C profile combines delivery urgency with technical precision. Applied here: Move fast with guardrails by pairing speed targets to quality and reliability checks.
Assertive habit: Own one high-impact delivery stream each sprint and publish cycle-time, defect, and recovery metrics to the team.
Pinnacle target: At your pinnacle, you drive high-velocity delivery with low defect escape, coach teams on execution excellence, and repeatedly ship complex outcomes.
Next-level growth focus: Lead delivery in complex domains and mentor peers on engineering rigor.
Curriculum path: Advanced testing strategy and reliability-aware engineering. + Architecture for engineers: scalability and maintainability patterns.
Certification path: CKAD, Azure Developer Associate (AZ-204)

Architect

Current level: L3 Specialist

Assessment signal: 3.0/5 at L3 indicates solid independent execution with meaningful upside through deliberate practice.
Strength to amplify now: Connects business intent to long-horizon technical direction.
Growth edge to close: Translate architecture decisions into delivery guardrails teams can execute this quarter.
Big Five: High openness supports systems-level abstraction and long-range scenario planning. Applied here: Use conceptual modeling to turn ambiguous business strategy into technical architecture guardrails.
MBTI: NT-style pattern orientation emphasizes logic, models, and future-state design. Applied here: Stress-test architecture decisions through tradeoff mapping before committing teams to irreversible paths.
DISC: C + D blend favors quality standards plus decisive direction under complexity. Applied here: Set non-negotiable engineering standards while still making timely cross-team calls.
Assertive habit: Lead one cross-team tradeoff forum every two weeks and end with a decision, owner, and follow-through metric.
Pinnacle target: At your pinnacle, you shape enterprise direction, align multiple engineering domains, and make architecture choices that compound business leverage for years.
Next-level growth focus: Lead cross-team architecture efforts that balance delivery pressure and long-term maintainability.
Curriculum path: Distributed systems, event-driven architecture, and resilience engineering. + Platform strategy and governance operating models.
Certification path: Google Professional Cloud Architect, TOGAF Foundation

Recommendations

Practical moves you can use this week to sharpen fit, execution, and career momentum.

Maintainer growth plan (next 90 days)

Long-term direction: At your pinnacle, you institutionalize reliability culture, prevent major incidents through proactive controls, and keep mission-critical systems trustworthy at scale.
Focus your learning here: Incident command systems and postmortem facilitation. + Resilience engineering and chaos testing fundamentals..
Certification targets to validate growth: Google Professional Cloud DevOps Engineer, CKA.
Behavior shift to practice: Increase root-cause depth so repeated issues become permanent fixes.
Personality habit to use this quarter: In Connector ↔ Concentrator, use your connector strength first, then add one concentrator behavior before final decisions.
Team-health habit: name one risk, one decision, one owner, and one shared outcome in weekly progress updates.

Manager alignment plan

How your manager can frame your growth in Maintainer: Sponsor should judge growth by downtime reduction, incident recurrence trend, and maturity of preventive controls.
Immediate manager actions: Lead post-incident reviews with prevention tracking. Own reliability roadmap for a multi-service domain.
Secondary-path leverage (Architect): Place in architecture review boards with measurable decision outcomes.
Fit context (Aligned and ready): align assignment scope to this pattern so challenge stays high and realistic.
Personality context for coaching: Clear connector tendency in Connector ↔ Concentrator; coaching should preserve that strength while building concentrator range.
Team-health context: use the report as a behavioral conversation starter about trust, clarity, accountability, and collective results.

Career trajectory toward archetype pinnacle

Primary trajectory: choose roles that repeatedly demand builds stable operations through strong runbooks and observability.
Progression target: move from maintainer toward builder by proving transforms ambiguous goals into executable increments.
Secondary trajectory: add range through architect assignments while keeping your maintainer core.
Fastest weak-path accelerator: Customer success principles for technical support. (certification: HDI Support Center Team Lead).
Reassess after one completed project that clearly demonstrates maintainer pinnacle behaviors.
Interview narrative tip: Show one story where your connector strength delivered results and one where you used concentrator behavior to improve the outcome.

Preview the full report experience

Personality profile

Competency profile

Placement interpretation

Team Health Assessment

Growth blueprint by role style

Recommendations

Integrity checks