01
The Architect
AAAA
Conceptual · Design-First · Independent · Stability
Was dieser Test misst
Engineer Type
16 engineer types determined from 4-axis scores
02
The Visionary Architect
AAAB
Conceptual · Design-First · Independent · Innovation
03
The Technical Lead
AABA
Conceptual · Design-First · Collaborative · Stability
04
The CTO Type
AABB
Conceptual · Design-First · Collaborative · Innovation
05
The Algorithm Engineer
ABAA
Conceptual · Code-First · Independent · Stability
06
The Research Engineer
ABAB
Conceptual · Code-First · Independent · Innovation
07
The Core Engineer
ABBA
Conceptual · Code-First · Collaborative · Stability
08
The Platform Engineer
ABBB
Conceptual · Code-First · Collaborative · Innovation
09
The System Craftsman
BAAA
Pragmatic · Design-First · Independent · Stability
10
The Product Engineer
BAAB
Pragmatic · Design-First · Independent · Innovation
11
The Project Lead
BABA
Pragmatic · Design-First · Collaborative · Stability
12
The Agile Lead
BABB
Pragmatic · Design-First · Collaborative · Innovation
13
The Specialist
BBAA
Pragmatic · Code-First · Independent · Stability
14
The Hacker
BBAB
Pragmatic · Code-First · Independent · Innovation
15
The Full-Stack Engineer
BBBA
Pragmatic · Code-First · Collaborative · Stability
16
The Startup Engineer
BBBB
Pragmatic · Code-First · Collaborative · Innovation
Beispielergebnis
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Architect
Conceptual · Design-First · Independent · Stability-Focused
Your Style
Conceptual Designer
Building unshakeable structures with time-tested foundations.
The Architect, in one line.
Building unshakeable structures with time-tested foundations.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Design-First
Independent vs Collaborative
Independent
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Architect）
This type deeply internalizes established patterns like DDD, layered architecture, and hexagonal design, then works alone to produce robust system structures grounded in proven engineering principles. They resist the pull of hype, applying patterns like CQRS or Event Sourcing only when genuinely appropriate, guided by deep understanding rather than novelty. They document every significant design decision as an ADR, ensuring that their architectural reasoning outlives any single project or team.
You are the quiet foundation that systems are built on. Your ability to choose proven patterns with precision — rather than chasing trends — becomes most valuable when projects stretch across years and teams change. The ADRs and design documents you leave behind are enduring gifts to every engineer who inherits your work.
You — Conceptual
Building unshakeable structures with time-tested foundations.
You — Design-First
This type deeply internalizes established patterns like DDD, layered architecture, and hexagonal design, then works alone to produce robust system structures grounded in proven engineering principles. They resist the pull of hype, applying patterns like CQRS or Event Sourcing only when genuinely appropriate, guided by deep understanding rather than novelty. They document every significant design decision as an ADR, ensuring that their architectural reasoning outlives any single project or team.
You — Independent
Brings exceptional precision to abstract design tasks such as DDD domain modeling, API interface contracts, and module boundary definitions. Deep familiarity with stable technologies enables trustworthy design decisions that account for long-term maintainability and legacy system integration.
You — Stability
Once a month, re-read your own past ADRs and ask whether each decision still holds given what the system has become. Living ADRs that reflect current understanding serve as active design guidelines, not just historical artifacts.
Brings exceptional precision to abstract design tasks such as DDD domain modeling, API interface contracts, and module boundary definitions. Deep familiarity with stable technologies enables trustworthy design decisions that account for long-term maintainability and legacy system integration.
Identifies service boundary issues, circular dependencies, and schema design trade-offs before implementation begins, minimizing costly rework. Thorough knowledge of patterns like CQRS and the Saga pattern — including their limitations — prevents over-engineering while still solving the right problems.
Sustained solo focus enables detection of architectural inconsistencies and hidden coupling that others miss during high-paced sprints. Careful reading of RFCs and design specifications surfaces specification contradictions early, dramatically reducing downstream correction costs.
Systematically captures design rationale in Architecture Decision Records (ADRs), allowing future engineers to understand not just what was decided but why. This ability to articulate design intent in writing reduces knowledge silos and protects the team from repeated debates about resolved questions.
Naturally practices contract-first design using tools like OpenAPI and Protocol Buffers, creating stable interface agreements that reduce integration friction between teams. Strong instincts for dependency direction and module decomposition produce codebases that remain navigable as they grow.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Startup Engineer
Pragmatic · Code-First · Collaborative · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Full-Stack Engineer
Pragmatic · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Reading classic computer science texts (SICP, TAOCP, Design Patterns) cover to cover
Studying architectural history and urban planning theory as an analogy for software structure
Strategy games that reward long-term structural thinking, such as chess or Go
DIY home server builds and custom keyboard projects that span design through construction
Recommended Certifications
AWS Certified Solutions Architect – Professional
TOGAF Enterprise Architecture Certification
IASA CITA-P (Certified IT Architect Professional)
Japan Information-Technology Engineers Examination: Systems Architect (情報処理技術者試験 システムアーキテクト)
Recommended Roles
Enterprise Architect (large-scale core system structural design)
Principal Engineer / Staff Engineer (technical strategy and design review)
Platform Engineer (internal shared infrastructure design and standardization)
Technical Lead (maintaining design quality and architectural consistency)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Visionary Architect
Conceptual · Design-First · Independent · Innovation-Driven
Your Style
Conceptual Designer
Designing tomorrow's architecture before the world catches up.
The Visionary Architect, in one line.
Designing tomorrow's architecture before the world catches up.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Design-First
Independent vs Collaborative
Independent
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Visionary Architect）
This type dives deep into the architectural implications of pre-mainstream technologies — WebAssembly component models, eBPF kernel extensions, edge computing paradigms — tracing each back to its theoretical foundations rather than accepting surface-level descriptions. They work alone to develop original architectural thinking that goes far beyond what trend articles cover, identifying design-level limitations of current stacks before most teams recognize the problem. Their greatest satisfaction is not in deploying today's best practice, but in constructing a coherent vision of the architecture that will be necessary next.
You walk ahead of the engineering horizon, seeing architectural possibilities in technologies that most engineers haven't noticed yet. Your ability to trace a new paradigm back to its first principles — and then reason forward to its design implications — is exactly what organizations need when a technology transition is approaching. The moment when 'too early' becomes 'just in time' will come, and you'll already have the blueprint ready.
You — Conceptual
Designing tomorrow's architecture before the world catches up.
You — Design-First
This type dives deep into the architectural implications of pre-mainstream technologies — WebAssembly component models, eBPF kernel extensions, edge computing paradigms — tracing each back to its theoretical foundations rather than accepting surface-level descriptions. They work alone to develop original architectural thinking that goes far beyond what trend articles cover, identifying design-level limitations of current stacks before most teams recognize the problem. Their greatest satisfaction is not in deploying today's best practice, but in constructing a coherent vision of the architecture that will be necessary next.
You — Independent
Understands the architectural implications of emerging technologies — such as the WebAssembly component model or eBPF's kernel extension architecture — at a theoretical rather than surface level. This depth enables genuine contribution to technology selection discussions, not just advocacy based on hype.
You — Innovation
Read one systems research paper per month from top venues like OSDI, SOSP, or HotOS, and maintain a personal 'emerging architecture notebook' in Notion or Obsidian to track design ideas not yet in production. A curated personal knowledge base grounded in primary sources makes every future proposal more credible.
Understands the architectural implications of emerging technologies — such as the WebAssembly component model or eBPF's kernel extension architecture — at a theoretical rather than surface level. This depth enables genuine contribution to technology selection discussions, not just advocacy based on hype.
Clearly articulates the design-level limitations of current mainstream approaches (REST, relational databases) and proactively designs migration pathways toward alternative architectures like GraphQL federation or event-driven systems. Migration cost is considered and minimized from the very beginning of the design process.
Deeply researches emerging distributed systems paradigms such as edge computing and service mesh, and independently constructs phased integration plans for introducing them into existing systems. Theoretical grounding allows scalability limits to be identified at the PoC stage rather than discovered in production.
Reads advanced RFCs and systems research papers (OSDI, SOSP) and evaluates pre-production architectural ideas for applicability to current systems. A strong theoretical foundation enables clear-eyed distinction between a technology's hype phase and its genuine value phase.
When writing ADRs for new architectural patterns, traces back to source specifications, reference implementations, and design documents before committing to a position. Design rationale grounded in primary sources — rather than blog posts and case studies alone — provides future engineers with genuinely transferable knowledge.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Full-Stack Engineer
Pragmatic · Code-First · Collaborative · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Startup Engineer
Pragmatic · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Reading systems research papers (OSDI, SOSP) and building a personal archive of pre-production architectural ideas
Independent research into the design implications of future technologies like quantum computing and neuromorphic chips
Reading science fiction and technology philosophy books to study patterns in how transformative technologies are socially adopted
Experimental implementation of emerging architectural patterns in personal open-source projects
Recommended Certifications
CNCF Certified Kubernetes Administrator (CKA) / Application Developer (CKAD)
Google Cloud Professional Cloud Architect
AWS Certified Advanced Networking – Specialty
Linux Foundation Certified System Administrator (LFCS)
Recommended Roles
Distinguished Engineer / Fellow (setting long-term technical direction)
Cloud Native Architect (Kubernetes, service mesh, and edge infrastructure design)
Technical Strategist (evaluating new technology for business applicability)
OSS Core Contributor (participating in design discussions for frontier projects)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Technical Lead
Conceptual · Design-First · Collaborative · Stability-Focused
Your Style
Conceptual Designer
The team's architectural compass, built on proven foundations.
The Technical Lead, in one line.
The team's architectural compass, built on proven foundations.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Design-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Technical Lead）
Deeply versed in design principles, this type excels at translating architectural intent into shared understanding across the team. Grounded in proven technology stacks, they maintain system coherence through rigorous type definitions, interface design, and boundary reviews. They continuously maintain ADRs and design documents to ensure the team's design philosophy stays consistent across sprints and personnel changes.
You are the irreplaceable memory of your team's architecture. The ADRs and type definitions you carefully craft become the safety net that keeps new team members from getting lost six months from now. Your deep expertise in proven technologies, combined with your dedication to sharing that knowledge, is what sustains system quality over the long term.
You — Conceptual
The team's architectural compass, built on proven foundations.
You — Design-First
Deeply versed in design principles, this type excels at translating architectural intent into shared understanding across the team. Grounded in proven technology stacks, they maintain system coherence through rigorous type definitions, interface design, and boundary reviews. They continuously maintain ADRs and design documents to ensure the team's design philosophy stays consistent across sprints and personnel changes.
You — Collaborative
You anchor team alignment in concrete design artifacts — from DDD domain models to OpenAPI specs — turning abstract concepts into shared language. Your grounding in stable technology means interface decisions are made with long-term maintainability in mind, not just short-term convenience.
You — Stability
Make it a habit to record the 'why' behind every significant architectural decision in an ADR immediately after it's made. When the same debate resurfaces six months later, a single ADR entry can replace hours of re-litigated discussion.
You anchor team alignment in concrete design artifacts — from DDD domain models to OpenAPI specs — turning abstract concepts into shared language. Your grounding in stable technology means interface decisions are made with long-term maintainability in mind, not just short-term convenience.
During architecture reviews, you consistently identify type mismatches and module boundary violations before they compound into regressions. Your feedback pairs specific code examples with clear tradeoff explanations, making reviews a genuine learning opportunity for the whole team.
You keep design documents, ADRs, and sequence diagrams up to date, preserving the rationale behind every major architectural decision as institutional knowledge. When new engineers join the team, this living documentation becomes the foundation of a smooth, structured onboarding experience.
Your deep familiarity with established runtimes and frameworks — Spring Boot, Rails, PostgreSQL, and their internals — lets you trace performance issues and data-consistency bugs back to their architectural roots. Because you can explain the 'why' behind design choices, you naturally mentor junior engineers toward deeper technical understanding.
You facilitate design discussions by anchoring debate in principles rather than preference, steering the team toward decisions that hold up under scrutiny. Using RFC-style proposals and structured async communication, you sustain design quality even in distributed or remote team settings.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Startup Engineer
Pragmatic · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Board games and war-strategy simulations (exercising long-horizon planning instincts)
Reading history and classic computer science texts (tracing the evolution of design thinking)
DIY woodworking or electronics (designing before building, in physical form)
Contributing design proposals and documentation to open-source projects
Recommended Certifications
AWS Certified Solutions Architect – Professional
TOGAF Enterprise Architecture Certification
Google Cloud Professional Cloud Architect
Certified Kubernetes Administrator (CKA)
Recommended Roles
Tech Lead / Lead Engineer (product engineering team)
Software Architect (mid-to-large scale web services)
Senior Backend Engineer with design quality ownership
Player-Manager Engineering Lead (hands-on engineering manager)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The CTO Type
Conceptual · Design-First · Collaborative · Innovation-Driven
Your Style
Conceptual Designer
Charting the technology map and leading the team into new territory.
The CTO Type, in one line.
Charting the technology map and leading the team into new territory.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Design-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The CTO Type）
This type envisions technology strategy at an architectural level while actively driving modernization — new stacks, revised architectures, fresh engineering practices — together with the team. They use RFCs and ADRs to make decision-making transparent, and publish tech blog posts to project engineering culture outward. By theoretically evaluating new technology adoption and articulating 'why this tech, why now,' they build organizational consensus around change rather than mandating it.
You draw the map of what technology can become, and you lead your team toward summits they didn't know were reachable. The RFCs and tech posts you write shape how fellow engineers make decisions, steadily raising the technical bar across the organization. Your instinct to push toward new frontiers is what teaches your team that change is something to move toward, not away from.
You — Conceptual
Charting the technology map and leading the team into new territory.
You — Design-First
This type envisions technology strategy at an architectural level while actively driving modernization — new stacks, revised architectures, fresh engineering practices — together with the team. They use RFCs and ADRs to make decision-making transparent, and publish tech blog posts to project engineering culture outward. By theoretically evaluating new technology adoption and articulating 'why this tech, why now,' they build organizational consensus around change rather than mandating it.
You — Collaborative
You can design large-scale architectural transformations — microservice decomposition, migration to Event-Driven Architecture — as structured RFCs, and drive them forward with team buy-in at each stage. Because you can articulate 'what today's architecture can no longer handle, and what the new design solves,' you communicate technical rationale convincingly to PMs and leadership, not just engineers.
You — Innovation
When evaluating a new technology, always publish the PoC repository to internal GitHub and share a frank post-mortem — what worked, what didn't — with the team. A transparent PoC culture raises the team's technology evaluation skills and accelerates the next selection process.
You can design large-scale architectural transformations — microservice decomposition, migration to Event-Driven Architecture — as structured RFCs, and drive them forward with team buy-in at each stage. Because you can articulate 'what today's architecture can no longer handle, and what the new design solves,' you communicate technical rationale convincingly to PMs and leadership, not just engineers.
You move quickly from identifying a promising technology — GraphQL, gRPC, a new managed cloud service — to designing a PoC and distilling actionable findings for the team. Technology selections are always backed by a specific architectural rationale ('this fits our system's characteristics') rather than trend-following, which means team commitment to the decision is genuinely earned.
As a designer of engineering culture, you have the drive to embed code-review norms, RFC culture, and tech-blog practices into the organization. Rather than mandating new culture from above, you model it yourself and design conditions where others naturally follow.
You track CNCF, IETF, and TC39 working groups closely enough to sketch a credible 1-to-2-year technology roadmap. Anticipating future technical constraints and incorporating them into current architecture decisions significantly reduces the organizational cost of large rewrites down the road.
Your technical vision and publishing voice double as recruiting assets. Tech blog posts and conference talks that demonstrate the company's engineering standards directly strengthen the employer brand that attracts strong engineers to join.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Full-Stack Engineer
Pragmatic · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Architect
Conceptual · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Hackathons and tech conferences as speaker and attendee (experiencing the leading edge firsthand)
Science fiction and futures-thinking books or documentaries (cultivating imagination about what technology can become)
Startup and founder community events (exploring the intersection of technology and business strategy)
Core feature contributions to major OSS projects (direct exposure to frontier design decisions)
Recommended Certifications
AWS Certified Solutions Architect – Professional / Google Cloud Professional Cloud Architect
Certified Kubernetes Administrator (CKA) or CKAD
ITIL 4 Foundation (building IT service management perspective alongside architecture)
Certified Enterprise Architect (TOGAF or equivalent)
Recommended Roles
CTO / VP of Engineering (tech startup or scale-up)
Principal Engineer / Staff Engineer (technology strategy owner)
Engineering Manager with tech culture and recruiting mandate
Technology Consultant / Solutions Architect (consulting firm or systems integrator)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Algorithm Engineer
Conceptual · Code-First · Independent · Stability-Focused
Your Style
Theory-to-Code
Turning theory into code that lasts decades.
The Algorithm Engineer, in one line.
Turning theory into code that lasts decades.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Code-First
Independent vs Collaborative
Independent
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Algorithm Engineer）
This type finds deep satisfaction in translating rigorous theoretical knowledge — algorithms, data structures, complexity theory — directly into reliable, production-grade code. They hand-write memory allocators in Rust or implement B+Trees from scratch, always reaching for proven, battle-tested techniques over new trends. They thrive in long stretches of solitary focus and produce their best work when given the freedom to go deep without interruption.
You see through the surface of a technology and into its mathematical foundation, a skill that very few engineers truly develop. The allocators, sorting algorithms, and data structures you implement will underpin systems that outlast entire technology generations. Your commitment to understanding before shipping is exactly what keeps critical infrastructure from silently breaking.
You — Conceptual
Turning theory into code that lasts decades.
You — Code-First
This type finds deep satisfaction in translating rigorous theoretical knowledge — algorithms, data structures, complexity theory — directly into reliable, production-grade code. They hand-write memory allocators in Rust or implement B+Trees from scratch, always reaching for proven, battle-tested techniques over new trends. They thrive in long stretches of solitary focus and produce their best work when given the freedom to go deep without interruption.
You — Independent
You can derive performance tuning decisions — cache-line alignment, index structure selection, lock-free queue design — from first principles rather than cargo-culting. In database schema reviews or memory profiling sessions, you bring mathematical grounding where others rely on intuition.
You — Stability
Work through one chapter of Knuth's TAOCP or Sedgewick's Algorithms per week, implementing every example by hand in your preferred language. Active transcription of classical algorithms builds the deep vocabulary that sets you apart in technical interviews and architecture discussions.
You can derive performance tuning decisions — cache-line alignment, index structure selection, lock-free queue design — from first principles rather than cargo-culting. In database schema reviews or memory profiling sessions, you bring mathematical grounding where others rely on intuition.
When writing unsafe Rust or low-level C++, you systematically eliminate undefined behavior and memory safety issues at the design stage rather than discovering them in production. Your habit of reading full RFC and spec documents means implementation gaps and misinterpretations are rare.
Because you can implement classic data structures like skip lists, Bloom filters, and LSM-trees from scratch, you understand the internal behavior of OSS libraries rather than treating them as black boxes. This translates to dramatically faster root-cause analysis during on-call incidents.
In code reviews, you can quantify problems concretely — 'this loop degrades to O(n²) on sorted input' — rather than offering vague stylistic feedback. That precision makes your review comments actionable and credible across the team.
You design core library APIs with long-term maintainability in mind, keeping contracts minimal and behavior deterministic. Combined with deep knowledge of stable patterns, you consistently produce foundational components that accumulate little technical debt over time.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Startup Engineer
Pragmatic · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Competitive programming (AtCoder, ICPC)
Writing a toy OS or emulator from scratch
Self-studying discrete mathematics and proof techniques
Reverse-engineering retro hardware and writing ports
Recommended Certifications
LF Certified Rust Developer
Oracle Certified Professional: MySQL Database Administrator
AWS Certified Database - Specialty
Google Hash Code / ICPC participation record
Recommended Roles
Database / storage engine engineer
Systems software engineer (OS, runtime, compiler backend)
Algorithm engineer (search ranking, route optimization)
Embedded / real-time systems engineer
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Research Engineer
Conceptual · Code-First · Independent · Innovation-Driven
Your Style
Theory-to-Frontier
Running tomorrow's research on today's hardware.
The Research Engineer, in one line.
Running tomorrow's research on today's hardware.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Code-First
Independent vs Collaborative
Independent
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Research Engineer）
This type reads an arxiv paper the day it drops and has a working implementation by the following week, driven by an intrinsic need to be at the absolute frontier of what is computationally possible. They independently build POCs of LLM attention variants, diffusion model schedulers, or quantum error-correction algorithms that no production system yet uses — not for immediate deployment, but because understanding something deeply means making it run. Their operating principle is 'show, don't tell': a working demo beats any slide deck.
You are one of the rare engineers who can single-handedly bridge cutting-edge research and working code. Every POC you push redefines what your organization believes is technically possible. The map you draw alone today — through uncharted papers and midnight debugging sessions — becomes the road that an entire industry will travel tomorrow.
You — Conceptual
Running tomorrow's research on today's hardware.
You — Code-First
This type reads an arxiv paper the day it drops and has a working implementation by the following week, driven by an intrinsic need to be at the absolute frontier of what is computationally possible. They independently build POCs of LLM attention variants, diffusion model schedulers, or quantum error-correction algorithms that no production system yet uses — not for immediate deployment, but because understanding something deeply means making it run. Their operating principle is 'show, don't tell': a working demo beats any slide deck.
You — Independent
You can translate mathematical notation in a paper — attention formulations, diffusion schedules, variational objectives — directly into PyTorch or JAX code with high fidelity. During that process you regularly uncover unreported assumptions or reproducibility gaps, giving you standing to engage paper authors and researchers as peers.
You — Innovation
Set up a daily arxiv digest via email or Connected Papers and commit to skimming at least three abstracts per weekday, reading the full paper only for the one closest to your current implementation focus. This keeps your breadth wide without sacrificing the depth that defines your best work.
You can translate mathematical notation in a paper — attention formulations, diffusion schedules, variational objectives — directly into PyTorch or JAX code with high fidelity. During that process you regularly uncover unreported assumptions or reproducibility gaps, giving you standing to engage paper authors and researchers as peers.
You adopt new frameworks like MLX, Triton, or a freshly released Hugging Face library within days of release, reading source code alongside documentation to reach proficiency before official tutorials exist. This speed makes you the team's de-facto antenna for capability shifts in the ML ecosystem.
You can implement from scratch in domains where no OSS baseline exists — a custom quantum circuit simulator, a novel tokenizer, a bespoke retrieval index — treating 'it compiles and produces expected output' as the definitive proof of understanding. This makes you invaluable for feasibility spikes on features the team doesn't yet know are buildable.
By tracking accepted papers at NeurIPS, ICML, and ICLR continuously, you can provide concrete, research-backed answers to 'what will be production-ready in six months' during technology roadmap planning. Your foresight turns abstract conference proceedings into actionable investment decisions for the organization.
You are able to resolve the most ambiguous form of technical uncertainty — 'we don't even know if this is possible' — through focused solo spikes. LLM-assisted code generation, multimodal search, or real-time speech synthesis POCs that would take a team a sprint can leave your desk in days.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Full-Stack Engineer
Pragmatic · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Architect
Conceptual · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Papers With Code implementation hackathons
Kaggle NLP and computer vision competitions
Building a quantum circuit simulator from scratch
Writing paper explainer posts on a personal research blog
Recommended Certifications
AWS Certified Machine Learning - Specialty
Google Professional Machine Learning Engineer
TensorFlow Developer Certificate
JDLA Deep Learning Engineer (E-qualification)
Recommended Roles
ML Research Engineer (LLM / multimodal R&D)
AI Product Engineer (frontier model productization)
Quantum Software Engineer
R&D Engineer (corporate research lab or CTO office)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Core Engineer
Conceptual · Code-First · Collaborative · Stability-Focused
Your Style
Conceptual Implementer
The team's reliability runs on your code.
The Core Engineer, in one line.
The team's reliability runs on your code.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Code-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Core Engineer）
You bring theoretical depth and a hands-on drive — diving into the codebase first, then refining based on solid understanding. You build and maintain the shared libraries, CI/CD pipelines, and test frameworks that keep the entire team shipping with confidence, always reaching for proven technologies. Through code reviews and documentation, you quietly elevate the technical quality of everyone around you.
You are the reason the team can ship without fear — every reliable deploy, every passing test suite, every clear code review comment is your contribution. Your ability to translate theory into maintainable, stable implementations is what turns a group of engineers into a trustworthy product team. That quiet technical foundation you build is what lets innovation happen safely.
You — Conceptual
The team's reliability runs on your code.
You — Code-First
You bring theoretical depth and a hands-on drive — diving into the codebase first, then refining based on solid understanding. You build and maintain the shared libraries, CI/CD pipelines, and test frameworks that keep the entire team shipping with confidence, always reaching for proven technologies. Through code reviews and documentation, you quietly elevate the technical quality of everyone around you.
You — Collaborative
You can design shared libraries and CI/CD pipelines with deep theoretical grounding, producing implementations that hold up under real production load. Because you understand proven tech stacks at a fundamental level, you can trace unexpected failures to their root cause rather than patching symptoms.
You — Stability
For every significant CI/CD or test-infrastructure decision, write an ADR capturing the context, options considered, and rationale before you merge. The compounding value of that record — months later when a teammate asks 'why does this work this way?' — far exceeds the 20 minutes it takes to write.
You can design shared libraries and CI/CD pipelines with deep theoretical grounding, producing implementations that hold up under real production load. Because you understand proven tech stacks at a fundamental level, you can trace unexpected failures to their root cause rather than patching symptoms.
During code reviews, you explain the 'why' behind each suggestion, turning every review cycle into a learning opportunity for the team. You transform implicit knowledge into Coding Guidelines and ADRs, steadily raising the baseline quality across the entire codebase.
You understand the test pyramid and can design an appropriate mix of unit, integration, and E2E tests for each context. A well-structured test suite you build gives the whole team the confidence to refactor and ship new features without fear of regression.
You excel at bridging the gap between DDD or Clean Architecture theory and the actual working code in the repository. Rather than letting design discussions stall in abstraction, you synthesize them into concrete, implementable structures that move the team forward.
You make long-horizon implementation decisions that hold up over years, not just sprints. By cross-referencing commit history and ADRs, you scope refactoring safely and articulate the technical trade-offs in terms stakeholders can act on.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Architect
Conceptual · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Contributing to open-source projects (bug fixes, documentation)
Reading foundational CS texts and classic software-design books
Building and operating a home lab server environment
Speaking at internal tech talks or community meetups
Recommended Certifications
AWS Certified DevOps Engineer – Professional
ISTQB Foundation Level (Software Testing)
Oracle Java SE Developer Certification
CompTIA Security+ or equivalent system-stability credential
Recommended Roles
Platform Engineer (internal shared infrastructure)
Senior Backend Engineer (core libraries / SDK development)
DevOps / Build Engineer (CI/CD and test framework ownership)
Tech Lead (team code quality and review culture)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Platform Engineer
Conceptual · Code-First · Collaborative · Innovation-Driven
Your Style
Conceptual Innovator
The platform you build decides how fast the team can move tomorrow.
The Platform Engineer, in one line.
The platform you build decides how fast the team can move tomorrow.
Conceptual vs Pragmatic
Conceptual
Design-First vs Code-First
Code-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
100
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Platform Engineer）
You pair deep theoretical understanding of distributed systems with a bias for action — spinning up a working prototype first, then refining the design based on what you learn. You work alongside your team to design and implement the infrastructure that fundamentally transforms developer experience: Kubernetes-based platforms, IaC pipelines, and internal developer portals. Your drive to adopt new technologies rapidly and continuously improve speed, reliability, and observability makes you the architect of the team's future velocity.
You are the person who determines whether the team can take its next bold step, through the platform decisions you make today. Whether it's cutting deployment anxiety with ArgoCD or surfacing cross-service latency with OpenTelemetry, your vision and implementation skill make the invisible visible. The combination of insatiable curiosity about emerging tech and genuine dedication to your teammates' productivity is the signature of a world-class platform engineer.
You — Conceptual
The platform you build decides how fast the team can move tomorrow.
You — Code-First
You pair deep theoretical understanding of distributed systems with a bias for action — spinning up a working prototype first, then refining the design based on what you learn. You work alongside your team to design and implement the infrastructure that fundamentally transforms developer experience: Kubernetes-based platforms, IaC pipelines, and internal developer portals. Your drive to adopt new technologies rapidly and continuously improve speed, reliability, and observability makes you the architect of the team's future velocity.
You — Collaborative
You rapidly internalize new platform concepts — Kubernetes Operator patterns, GitOps workflows, service mesh topologies — and translate them into working implementations your team can adopt. Your habit of running the system locally before finalizing the design means you ship platform changes that are both well-reasoned and battle-tested.
You — Innovation
When evaluating a new technology, create an explicit 'Spike' task in the sprint and commit to producing either a Proposal document or an ADR as the deliverable. Recording evaluations — including the options you rejected and why — makes your team's technology selection process auditable and dramatically reduces re-litigation cost in future discussions.
You rapidly internalize new platform concepts — Kubernetes Operator patterns, GitOps workflows, service mesh topologies — and translate them into working implementations your team can adopt. Your habit of running the system locally before finalizing the design means you ship platform changes that are both well-reasoned and battle-tested.
Using Terraform or Pulumi, you design IaC setups that bake in reproducibility, change history, and drift detection as structural properties rather than afterthoughts. You continuously evaluate new CNCF ecosystem tools, ensuring the team always has an up-to-date menu of options when the next architecture decision arrives.
You build observability stacks with OpenTelemetry and Grafana that dramatically cut mean-time-to-resolution when incidents strike. Your understanding of distributed tracing lets you map complex inter-service dependencies into dashboards that make invisible failures immediately obvious to any on-call engineer.
You champion Internal Developer Platform (IDP) initiatives that let product teams self-serve their infrastructure needs without filing tickets. From evaluating Backstage to implementing and customizing it with your team, you create the 'flow state infrastructure' that keeps developers in their productive zone.
You consistently monitor CNCF project momentum, cloud vendor release notes, and upstream RFCs, and you can articulate the rationale for your technology bets in structured Proposal or Spike documents. In architecture discussions, you accelerate team decisions by showing up with pre-synthesized evidence rather than just intuition.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Architect
Conceptual · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Contributing to CNCF open-source projects and exploring upstream issues
Running Kubernetes and GitOps experiments in a home lab cluster
Attending or watching KubeCon, PlatformCon, and cloud-native conferences
Writing technical blog posts or articles about platform engineering experiences
Recommended Certifications
Certified Kubernetes Administrator (CKA)
Certified Kubernetes Application Developer (CKAD)
AWS Certified Solutions Architect – Professional
HashiCorp Certified: Terraform Associate
Recommended Roles
Platform Engineer (Kubernetes / Internal Developer Platform design)
Site Reliability Engineer (observability, reliability, automation)
Cloud Infrastructure Engineer (IaC, multi-cloud architecture)
DevOps Architect (developer experience strategy, CI/CD design)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The System Craftsman
Pragmatic · Design-First · Independent · Stability-Focused
Your Style
Pragmatic Designer
A working system is the ultimate proof of design.
The System Craftsman, in one line.
A working system is the ultimate proof of design.
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Design-First
Independent vs Collaborative
Independent
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The System Craftsman）
A careful architect who writes system diagrams, sequence flows, and ADRs before a single line of code is written, proactively eliminating structural risks that can't be fixed later. A self-sufficient practitioner who can carry an entire project from infrastructure design through batch optimization and slow-query tuning, holding stable production operation as the highest quality standard. Deep mastery of proven technologies combined with long-horizon judgment delivers systems that simply don't break.
You are a craftsman who understands proven technologies to their core and quietly builds structures that will never collapse in production. Your focus when facing design documents and your relentless patience when tuning slow queries may not be flashy, but they form the trust infrastructure that the whole team relies on. The designs you commit to will prove their correctness years later, during the incident response that never becomes a crisis.
You — Pragmatic
A working system is the ultimate proof of design.
You — Design-First
A careful architect who writes system diagrams, sequence flows, and ADRs before a single line of code is written, proactively eliminating structural risks that can't be fixed later. A self-sufficient practitioner who can carry an entire project from infrastructure design through batch optimization and slow-query tuning, holding stable production operation as the highest quality standard. Deep mastery of proven technologies combined with long-horizon judgment delivers systems that simply don't break.
You — Independent
You can resolve DB performance issues at a structural level — index design, partitioning, and execution-plan analysis in MySQL or PostgreSQL are second nature. Given uninterrupted time to analyze an existing schema, you can devise a zero-downtime migration plan that eliminates the root cause entirely.
You — Stability
Spend 15 minutes each week scanning your service's slow-query log and CloudWatch metrics for subtle anomalies. Catching small deviations early sharpens the proactive design intuition that prevents large-scale incidents.
You can resolve DB performance issues at a structural level — index design, partitioning, and execution-plan analysis in MySQL or PostgreSQL are second nature. Given uninterrupted time to analyze an existing schema, you can devise a zero-downtime migration plan that eliminates the root cause entirely.
When designing batch pipelines, you bake in retry strategies, idempotency, and checkpoint logic from the very beginning. Documenting recovery scenarios in advance means catastrophic data inconsistencies in production become a theoretical concern rather than a 3 a.m. crisis.
Your IaC work with Terraform or Ansible produces maintainable, long-lived configurations because you deliberate carefully over module granularity and variable design. The resulting codebase has predictable change surfaces that future operators can reason about confidently.
When adding features to a large legacy codebase, you rigorously audit impact scope, run static analysis, and inspect dependency graphs before touching a line. That craftsman's carefulness — 'never break what's already working' — generates trust across long-running projects.
You can single-handedly design an observability stack from SLI/SLO definitions through alert thresholds to dashboard layouts. Your deep familiarity with production behavior lets you suppress noisy alerts and surface only the signals that genuinely matter.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Startup Engineer
Pragmatic · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Home-lab builds with Proxmox or TrueNAS — running real infrastructure for the joy of stable ops
Strategy board games or chess — long-horizon planning and whole-board resource management
DIY woodworking — draw the blueprint first, then build for structural integrity
Deep technical reading — database internals, OS design, and OSS source-code archaeology
Recommended Certifications
AWS Certified Solutions Architect – Professional
Google Cloud Professional Cloud Architect
Linux Foundation Certified System Administrator (LFCS)
ITIL 4 Foundation
Recommended Roles
Infrastructure Engineer / SRE — reliability design and operational improvement for large-scale services
Backend Engineer — database architecture design and batch-processing platform development
Platform Engineer — internal IaC and CI/CD platform design and stewardship
Tech Lead — guardian of design quality and operational stability, owning technical decision-making
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Product Engineer
Pragmatic · Design-First · Independent · Innovation-Driven
Your Style
Pragmatic Innovator
Wire the latest tech into the design, then ship it alone.
The Product Engineer, in one line.
Wire the latest tech into the design, then ship it alone.
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Design-First
Independent vs Collaborative
Independent
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Product Engineer）
An early-adopter designer who approaches new frameworks, cloud services, and LLM APIs not with 'can I use this?' but with 'how does this fit into the architecture?' A self-sufficient builder capable of taking a SaaS product from zero to launch single-handedly, shipping working software at speed while designing against technical debt from day one. The confidence to revisit technology choices as the market evolves is what keeps the product's competitive edge intact over the long run.
You are an engineer who can design a combination of technologies nobody has tried yet and ship them as a working product for the world to use. That instant mental click when you read a new API release note — 'here's exactly how I'd use this' — is your unique design sensibility speaking. The technical bets you place early become the product's most decisive differentiators six months down the road.
You — Pragmatic
Wire the latest tech into the design, then ship it alone.
You — Design-First
An early-adopter designer who approaches new frameworks, cloud services, and LLM APIs not with 'can I use this?' but with 'how does this fit into the architecture?' A self-sufficient builder capable of taking a SaaS product from zero to launch single-handedly, shipping working software at speed while designing against technical debt from day one. The confidence to revisit technology choices as the market evolves is what keeps the product's competitive edge intact over the long run.
You — Independent
When adopting new frameworks like Next.js, Remix, or Hono, you read the official docs alongside GitHub Issues and Discussions to map their behavioral limits before wiring them into the architecture. 'Understand first, then build' rather than 'build and discover' is what makes your early adoption low-risk.
You — Innovation
Spend 30 minutes each week reading the Issues and PRs in the GitHub repository of any technology you are considering adopting. Known bugs, undocumented limitations, and roadmap signals you find there let you route around design land mines before you hit them.
When adopting new frameworks like Next.js, Remix, or Hono, you read the official docs alongside GitHub Issues and Discussions to map their behavioral limits before wiring them into the architecture. 'Understand first, then build' rather than 'build and discover' is what makes your early adoption low-risk.
You can design, implement, and deploy an architecture that combines LLM APIs, edge computing, and BaaS platforms like Supabase or Convex — end to end, without help. A full-stack perspective that spans tech-stack selection through payments, auth, and notifications gives your product designs uncommon coherence.
When adopting new technology you naturally include abstraction layers and ports-and-adapters patterns from the start, minimizing future replacement cost. The ability to satisfy both 'optimal for today' and 'easy to change later' in a single architecture decision is a genuine competitive advantage.
On solo projects and SaaS launches you can define the MVP scope, make unilateral calls on tech stack, DB schema, and API surface, and move forward with speed. Combining decisiveness with design quality makes you exceptionally effective in short-feedback-loop phases.
You continuously monitor conference talks from JSConf, KubeCon, and re:Invent along with OSS changelogs, and you can rapidly assess new technology for adoption from both technical and design perspectives. The speed at which you convert information into architecture decisions keeps the product ahead of the curve.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Full-Stack Engineer
Pragmatic · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Architect
Conceptual · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Solo SaaS development and launches — shipping to Product Hunt or writing up the build on Zenn or DEV
Hackathons — treating them as a competitive sport for building the fastest prototype on a novel stack
Smart-home and gadget tinkering — wiring new devices to APIs for home automation experiments
Tech podcasts and newsletters — Changelog, Software Engineering Daily, and similar feeds
Recommended Certifications
AWS Certified Developer – Associate
Google Cloud Professional Cloud Developer
Certified Kubernetes Application Developer (CKAD)
CISSP or Information Security Management certification — for embedding secure design into product architecture
Recommended Roles
Product Engineer / Full-Stack Engineer — zero-to-one development at a startup or new business unit
Tech Lead — driving new technology adoption decisions and leading architecture modernization
Independent Developer / Indie Hacker — designing, operating, and monetizing a SaaS or OSS project solo
DevRel Engineer / Technical Evangelist — publishing real-world design use cases for emerging technologies
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Project Lead
Pragmatic · Design-First · Collaborative · Stability-Focused
Your Style
Pragmatic Designer
Ship it solid. Every sprint, every release, every time.
The Project Lead, in one line.
Ship it solid. Every sprint, every release, every time.
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Design-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Project Lead）
A hands-on team leader who maintains design quality without sacrificing delivery. In sprint planning and architecture review sessions, this type aligns the team around a shared design direction, selects proven technology stacks with clear rationale, and manages risk before it becomes a blocker. When incidents occur, they lead the response calmly — from rollback decisions to post-mortem facilitation and action item follow-through.
You are the engineer your team reaches for first when things get uncertain. Holding both the design vision and the hands-on implementation instinct in the same person is genuinely rare. When you say 'let's go with this,' the team moves — and that clarity is your most powerful contribution.
You — Pragmatic
Ship it solid. Every sprint, every release, every time.
You — Design-First
A hands-on team leader who maintains design quality without sacrificing delivery. In sprint planning and architecture review sessions, this type aligns the team around a shared design direction, selects proven technology stacks with clear rationale, and manages risk before it becomes a blocker. When incidents occur, they lead the response calmly — from rollback decisions to post-mortem facilitation and action item follow-through.
You — Collaborative
Can quickly produce ERDs, sequence diagrams, and ADRs at project kickoff, giving the team a solid design skeleton before a single line of production code is written. This front-loaded clarity dramatically reduces rework and keeps the overall schedule intact through each sprint.
You — Stability
Establish a weekly 30-minute design sync with a fixed agenda so the team keeps design alignment tight without large meeting overhead. Regular short check-ins surface misalignments early, before they turn into expensive implementation rework.
Can quickly produce ERDs, sequence diagrams, and ADRs at project kickoff, giving the team a solid design skeleton before a single line of production code is written. This front-loaded clarity dramatically reduces rework and keeps the overall schedule intact through each sprint.
Deeply understands the operational characteristics of proven stacks like PostgreSQL and Kubernetes, enabling evidence-backed technology recommendations in architecture decision meetings. Historical incident data and SLA track records make these recommendations easy for stakeholders and non-technical leadership to trust.
Detects team blockers early in daily standups and sprint reviews, resequences dependent tasks, and clears ambiguity with in-the-moment design decisions that let the team keep moving. When a blocker stems from unclear design, this type resolves it on the spot rather than scheduling a follow-up.
Produces pre-release risk assessments, rollback runbooks, and SLO definitions that account for worst-case scenarios before they happen. Leads incident response with calm precision and takes ownership of post-mortem write-ups and follow-through on prevention items.
Code reviews cover not just correctness but design consistency, module boundary adherence, and naming conventions across the codebase, catching technical debt before it accumulates. Regular availability for pair programming and design discussions quietly raises the overall skill level of the team.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Architect
Conceptual · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Board games and strategy war games (resource management and planning practice)
Hiking and mountaineering (goal completion through careful preparation)
Reading engineering management and project delivery books
DIY and woodworking (end-to-end ownership from design to finished product)
Recommended Certifications
PMP (Project Management Professional)
AWS Solutions Architect – Professional
Google Professional Cloud Architect
CKA (Certified Kubernetes Administrator)
Recommended Roles
Tech Lead (mid-to-large scale web service teams)
Engineering Manager (process and delivery focused)
Staff Software Engineer (design + delivery ownership)
SRE Lead (reliability engineering and infrastructure design)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Agile Lead
Pragmatic · Design-First · Collaborative · Innovation-Driven
Your Style
Pragmatic Innovator
Turn change into momentum. Keep the team at the frontier.
The Agile Lead, in one line.
Turn change into momentum. Keep the team at the frontier.
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Design-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
100
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Agile Lead）
A team leader who transforms shifting requirements and emerging technologies into competitive advantages rather than disruptions. Fluent in Scrum, Kanban, and ShapeUp, this type selects and adapts methodologies to the current context rather than defaulting to habit. Treats a pivot not as a sign of failure but as evidence of learning, and actively designs lightweight processes and psychological safety so the team can change direction quickly without losing confidence.
You are the engineer who pulls out a new map when the team starts questioning whether the current path is right. Your instinct to find opportunity inside change — rather than resist it — is one of the most valuable capabilities an engineering team can have right now. Wherever you say 'let's try it,' that's where your team's next growth is waiting.
You — Pragmatic
Turn change into momentum. Keep the team at the frontier.
You — Design-First
A team leader who transforms shifting requirements and emerging technologies into competitive advantages rather than disruptions. Fluent in Scrum, Kanban, and ShapeUp, this type selects and adapts methodologies to the current context rather than defaulting to habit. Treats a pivot not as a sign of failure but as evidence of learning, and actively designs lightweight processes and psychological safety so the team can change direction quickly without losing confidence.
You — Collaborative
When mid-sprint business requirement changes arrive, can rapidly reconstitute module boundaries and interface contracts to minimize the cost of the design change. Building 'change-tolerant design' into the architecture from day one means pivots absorb cleanly instead of creating cascading rework across the codebase.
You — Innovation
Always schedule new-technology exploration as a named spike task in the sprint, and write a one-page PoC report capturing what was tested and what the outcome was. The team builds reproducible knowledge rather than tribal memory, and each subsequent PoC starts from a higher baseline.
When mid-sprint business requirement changes arrive, can rapidly reconstitute module boundaries and interface contracts to minimize the cost of the design change. Building 'change-tolerant design' into the architecture from day one means pivots absorb cleanly instead of creating cascading rework across the codebase.
When introducing new architectural patterns like GraphQL or Event-Driven Architecture, simultaneously prepares design documentation and hands-on sessions to reduce the team's ramp-up cost. The ability to bridge theory and working implementation means the whole team reaches proficiency faster than they would through documentation alone.
Surfaces the development process itself as a retro improvement item, embedding a 'question the current way' mindset as a team norm rather than a periodic interruption. Proposals around CI pipeline optimization and test strategy revision come with concrete implementation paths, not just abstract suggestions.
Can stand up a PoC for a new SaaS tool or OSS library quickly and bring the team concrete evidence for an adoption decision before the debate bogs down in speculation. The 'try first, then decide' approach replaces groundless objections with empirical data and keeps decision-making moving forward.
Naturally designs releases around feature flags and blue-green deployments, baking incremental rollout plans into the architecture phase rather than treating them as an ops afterthought. Limiting blast radius at the design level gives the team the confidence to ship more boldly and more frequently.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Architect
Conceptual · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Specialist
Pragmatic · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Hacker
Pragmatic · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Hackathons and OSS contribution (rapid hands-on exploration of new technologies)
Tech podcasts and conference talks (staying current on emerging trends)
Band or jam session participation (combining improvisation with ensemble collaboration)
Self-directed learning of new languages and paradigms (Rust, Elixir, etc.)
Recommended Certifications
Certified Scrum Master (CSM) or Professional Scrum Master (PSM I/II)
AWS DevOps Engineer – Professional
CKA (Certified Kubernetes Administrator)
GitHub Actions or GitLab CI professional certification
Recommended Roles
Agile Coach + Tech Lead (owning both process and technical direction)
Platform Engineer (developer experience and CI/CD pipeline improvement)
Full-Stack Product Engineer (fast response to shifting business requirements)
Developer Relations Engineer (internal and external tech adoption and advocacy)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Specialist
Pragmatic · Code-First · Independent · Stability-Focused
Your Style
Pragmatic Implementer
The engineer who masters one domain and delivers with certainty
The Specialist, in one line.
The engineer who masters one domain and delivers with certainty
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Code-First
Independent vs Collaborative
Independent
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Specialist）
This type dives straight into implementation to understand how things actually work, rather than starting from theory or specification. They pick a specific domain — SQL tuning, firmware development, security auditing, or a particular framework — and go deep with proven, battle-tested technology. Working alone in focused silence, they produce reliable output that becomes the backbone of long-running projects.
You have a rare capacity to stay committed to one domain while others chase the next trend — that depth is your greatest asset. When the team hits a wall that nobody else can break through, your accumulated knowledge of proven systems is the key that opens it. Keep building that quiet expertise, because long-lived projects always need someone who truly understands the foundations.
You — Pragmatic
The engineer who masters one domain and delivers with certainty
You — Code-First
This type dives straight into implementation to understand how things actually work, rather than starting from theory or specification. They pick a specific domain — SQL tuning, firmware development, security auditing, or a particular framework — and go deep with proven, battle-tested technology. Working alone in focused silence, they produce reliable output that becomes the backbone of long-running projects.
You — Independent
Possesses deep knowledge of a specific domain — such as PostgreSQL query plan optimization, Linux kernel internals, or a particular framework's source code — acquired by actually reading docs and implementation code. When a hard problem arrives that no one else can crack, this expertise provides a reliable path through.
You — Stability
Make your depth visible by publishing one technical post per month on a blog, Zenn, or Dev.to. Writing forces you to articulate what you know, which reliably surfaces the gaps worth filling next.
Possesses deep knowledge of a specific domain — such as PostgreSQL query plan optimization, Linux kernel internals, or a particular framework's source code — acquired by actually reading docs and implementation code. When a hard problem arrives that no one else can crack, this expertise provides a reliable path through.
A strong grasp of mature technology stacks makes this type invaluable during legacy system refactors and long-term maintenance phases. They naturally know how to change running systems without breaking them and can map safe migration paths that others overlook.
Able to sustain deep, uninterrupted focus on a single problem — tracking down memory leaks, identifying performance bottlenecks, or deciphering obscure stack traces — long after others have moved on. That patient persistence consistently yields root-cause answers, not workarounds.
Brings a disciplined eye to technology selection: evaluating production track record, community maturity, and long-term maintenance cost rather than hype. Can articulate a rational case for choosing 'boring technology' in production, which earns respect in architectural decision meetings.
Because understanding is grounded in actual code behavior, code reviews surface runtime edge cases that look fine on paper. The ability to spot 'spec-correct but runtime-broken' patterns gives this type a distinctive, trusted voice in review discussions.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Architect
Conceptual · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Close-reading and hand-coding technical books (OS internals, compiler construction)
Sustained OSS contribution — bug reports, patch submissions, and code review
Electronics and embedded firmware side projects with microcontrollers
Running benchmarks and publishing detailed tuning write-ups
Recommended Certifications
IPA Database Specialist Examination
Linux Professional Institute Certification (LPIC-3)
AWS Certified Database – Specialty
Certified Information Systems Security Professional (CISSP)
Recommended Roles
Database Engineer / DB Specialist
Embedded Software Engineer (firmware development)
Security Engineer (penetration testing / vulnerability assessment)
SRE / Performance Engineer (stack-specific optimization role)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Hacker
Pragmatic · Code-First · Independent · Innovation-Driven
Your Style
Pragmatic Implementer
Turning new tech into working code before anyone else has read the docs
The Hacker, in one line.
Turning new tech into working code before anyone else has read the docs
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Code-First
Independent vs Collaborative
Independent
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
100
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Hacker）
By the day after a new framework, LLM API, or OSS tool drops, this type already has a working prototype. They start with 'just make it run,' iterate alone and fast, and quickly map both the potential and the limits of any new technology. Personal repositories overflow with experiments, and that raw speed and adaptability makes them the team's de-facto radar for what comes next.
You can sketch the map of a new technology faster than anyone else on the team — and that is genuinely rare. The prototype you build over a weekend can redirect the team's entire next-quarter roadmap, and it often does. Trust that experimental velocity, and keep shipping.
You — Pragmatic
Turning new tech into working code before anyone else has read the docs
You — Code-First
By the day after a new framework, LLM API, or OSS tool drops, this type already has a working prototype. They start with 'just make it run,' iterate alone and fast, and quickly map both the potential and the limits of any new technology. Personal repositories overflow with experiments, and that raw speed and adaptability makes them the team's de-facto radar for what comes next.
You — Independent
Can produce a working demo of a newly released API or framework — LangChain, Hono, Bun, or the latest LLM endpoint — within hours of the announcement. Holding first-hand data at the team's technology selection meeting, rather than a blog summary, is a distinct and decisive advantage.
You — Innovation
Publish weekend prototypes on GitHub with a short README and a demo GIF, then post them on X or Dev.to. Consistent output builds recognition in the technical community and creates inbound opportunities over time.
Can produce a working demo of a newly released API or framework — LangChain, Hono, Bun, or the latest LLM endpoint — within hours of the announcement. Holding first-hand data at the team's technology selection meeting, rather than a blog summary, is a distinct and decisive advantage.
Unconstrained by existing implementations, can start from scratch with a completely different approach and reach a working prototype fast. In hackathons or sprint goals that require a net-new feature, this type finds the shortest path and ships first.
Years of personal project volume have built deep muscle memory for environment setup: boilerplate configuration, CI/CD pipeline initialization, and deploy automation. This makes them the natural first responder at the launch phase of any new project.
Routine scanning of GitHub Trending, Hacker News, and arXiv preprints means emerging tools and approaches reach the team through this person first. A single 'there's a tool for this' comment can cut weeks off a problem the team has been circling.
Repeated early contact with the edge cases and unexpected behaviors of new libraries — discovered during personal experiments before any production pressure — gives this type a rich repository of 'gotcha' knowledge. They can warn the team about landmines before anyone steps on them.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Architect
Conceptual · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Weekend personal projects and hackathons — self-imposed rule: use a different framework every time
Daily review of GitHub Trending, Hacker News, and arXiv with personal tech notes
Building creative automation tools with AI APIs and LLM endpoints
Publishing experiment results on a tech blog or recording a technical podcast
Recommended Certifications
AWS Certified Developer – Associate (demonstrates rapid cross-cloud deployment ability)
Google Cloud Professional Cloud Developer
GitHub Foundations / GitHub Actions Certification
LLM / Generative AI practitioner certification (e.g., DeepLearning.AI Short Courses)
Recommended Roles
Full-Stack Engineer / Solo Developer (early-stage startup)
AI Engineer / LLM Application Developer
Tech Lead (new technology evaluation and PoC ownership)
Developer Advocate / Technical Evangelist
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Full-Stack Engineer
Pragmatic · Code-First · Collaborative · Stability-Focused
Your Style
Pragmatic Implementer
Ships working products reliably, across every layer of the stack.
The Full-Stack Engineer, in one line.
Ships working products reliably, across every layer of the stack.
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Code-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Stability
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
100
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Full-Stack Engineer）
A versatile all-rounder who moves fluidly between frontend, backend, and infrastructure, spotting and filling team bottlenecks before they block delivery. Prioritizes proven, well-understood technology stacks to ensure stable operation and long-term maintainability rather than chasing the latest trends. Finds genuine satisfaction in consistently landing something tangible and working in users' hands at the end of every sprint.
You are the person who starts coding when the team is stuck, and that instinct matters more than you know. Your preference for reliable tech over cutting-edge novelty is what keeps production stable and earns the trust of the people around you. Your hands-on breadth and collaborative instinct are the backbone that lets the whole team keep moving forward.
You — Pragmatic
Ships working products reliably, across every layer of the stack.
You — Code-First
A versatile all-rounder who moves fluidly between frontend, backend, and infrastructure, spotting and filling team bottlenecks before they block delivery. Prioritizes proven, well-understood technology stacks to ensure stable operation and long-term maintainability rather than chasing the latest trends. Finds genuine satisfaction in consistently landing something tangible and working in users' hands at the end of every sprint.
You — Collaborative
Able to build end-to-end features solo — from a React UI to a REST API to Terraform infrastructure — making you immediately effective in small teams or early product phases. Straddling both frontend and backend within a single sprint eliminates inter-layer friction and keeps delivery cadence high.
You — Stability
Once a month, deliberately claim a task in a layer you rarely touch — if you mostly live in backend code, take on an Observability setup or a complex CSS layout challenge. Intentionally stretching your reach is how full-stack breadth becomes full-stack depth.
Able to build end-to-end features solo — from a React UI to a REST API to Terraform infrastructure — making you immediately effective in small teams or early product phases. Straddling both frontend and backend within a single sprint eliminates inter-layer friction and keeps delivery cadence high.
Deep familiarity with battle-tested tools like PostgreSQL schema tuning, Nginx config optimization, and established CI/CD pipelines makes you a reliable force during production incidents. The ability to draw on past failure patterns across projects gives your troubleshooting a consistency others can depend on.
You quickly read where teammates are blocked — in stand-ups, code reviews, or async Slack threads — and jump into a pairing session or screen share to unblock them without waiting to be asked. You naturally take on the 'glue engineer' role that keeps team rhythm steady without disrupting the sprint.
You proactively pick up infrastructure chores — optimizing Dockerfiles, wiring up alerting dashboards, maintaining deployment automation — that directly lift the whole team's productivity. This unglamorous-but-critical work creates compounding returns on engineering velocity over time.
You read existing codebases quickly and shine in long-lived systems: incrementally paying down technical debt in a legacy Rails app, or carefully adding features without breaking existing contracts. You know how to move a codebase forward while keeping the lights on for the business.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Architect
Conceptual · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Platform Engineer
Conceptual · Code-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Agile Lead
Pragmatic · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Solo full-stack side projects (web apps, bots, browser extensions)
HomeLab builds with Raspberry Pi or self-hosted servers
Attending and speaking at local dev meetups and hackathons
Contributing bug fixes and docs improvements to OSS projects
Recommended Certifications
AWS Certified Solutions Architect (Associate / Professional)
Google Cloud Professional Cloud Developer
Certified Kubernetes Application Developer (CKAD)
HashiCorp Terraform Associate
Recommended Roles
Full-Stack Engineer at a startup or scale-up
Backend + Infrastructure Engineer on a web product team
Tech Lead (player-coach in a small delivery team)
Platform / SRE Engineer embedded in a product squad
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
IT Engineer Type Assessment (50 Questions / 16 Types)
Your Type
The Startup Engineer
Pragmatic · Code-First · Collaborative · Innovation-Driven
Your Style
Pragmatic Innovator
Turns zero into one — fast, with the whole team alongside.
The Startup Engineer, in one line.
Turns zero into one — fast, with the whole team alongside.
Conceptual vs Pragmatic
Pragmatic
Design-First vs Code-First
Code-First
Independent vs Collaborative
Collaborative
Stability vs Innovation
Innovation
Scores on 4 Axes
Thinking Style
0
Conceptual ⟺ Pragmatic
Work Style
0
Design-First ⟺ Code-First
Collaboration Style
0
Independent ⟺ Collaborative
Tech Outlook
0
Stability ⟺ Innovation
Each axis shows which side you lean toward, not a score out of 50.
6-Trait Radar
Reflects your engineering characteristics across multiple dimensions from your 4-axis profile.
Your Type Explained（The Startup Engineer）
Converts curiosity about new tech and business models directly into shipping velocity, finding peak fulfillment in landing an MVP in users' hands at startup speed alongside a tight-knit team. Operates with a hybrid lens — equally comfortable debating product hypotheses with a PdM and wiring up a new API integration at the keyboard. Treats pivots and rewrites not as setbacks but as the natural rhythm of learning what actually works.
You are the person whose 'let's just try it' energy moves the whole team from debate to discovery. Your ability to evaluate an unfamiliar framework, spin up a prototype, and report back with real data is the superpower that matters most when speed is the only moat. Your drive to innovate and your instinct to bring the team along are what turn a product idea into something real.
You — Pragmatic
Turns zero into one — fast, with the whole team alongside.
You — Code-First
Converts curiosity about new tech and business models directly into shipping velocity, finding peak fulfillment in landing an MVP in users' hands at startup speed alongside a tight-knit team. Operates with a hybrid lens — equally comfortable debating product hypotheses with a PdM and wiring up a new API integration at the keyboard. Treats pivots and rewrites not as setbacks but as the natural rhythm of learning what actually works.
You — Collaborative
You ramp up on emerging tools — Vercel Edge Functions, Supabase, tRPC — fast enough to have a working prototype in days, turning technology decisions from opinion battles into evidence-based choices. The 'build it to decide it' cycle you naturally run keeps team discussions grounded in reality rather than speculation.
You — Innovation
Spend 15 minutes each week scanning Product Hunt and developer newsletters (TLDR, Bytes.dev) and pick one new tool to run in a minimal proof-of-concept over the weekend. The habit of 'touch it before judging it' sharpens both the speed and accuracy of your technology radar.
You ramp up on emerging tools — Vercel Edge Functions, Supabase, tRPC — fast enough to have a working prototype in days, turning technology decisions from opinion battles into evidence-based choices. The 'build it to decide it' cycle you naturally run keeps team discussions grounded in reality rather than speculation.
You design and ship experiment infrastructure fluently: Feature Flags for staged rollouts, A/B test harnesses, and event instrumentation wired to a metrics dashboard. Keeping the hypothesis-build-measure loop tight maximizes the speed at which the product learns from the market.
You collaborate naturally across disciplines — reading Figma design tokens while building components, querying BigQuery to identify the next feature bet with a data analyst, or pair-writing user story acceptance criteria with the PdM. This cross-functional fluency reduces handoff friction and keeps the whole squad aligned.
When a pivot is called, you can make the call to replace a core part of the stack without mourning the previous work, and your positive framing of rewrites as learning helps the team follow suit. Treating past code as a sunk cost rather than a legacy to protect keeps the codebase aligned with the current product direction.
You are fast at stitching together SaaS ecosystems — integrating an LLM API, wiring Stripe payments, connecting Firebase real-time sync — to deliver user value without building from scratch. The 'compose rather than construct' instinct dramatically accelerates MVP completions and reduces scope risk.
Compatible Types
Shows the top 10 types most likely to complement your blind spots based on 4-axis complementarity.
#1
Architect
Conceptual · Design-First · Independent · Stability
Compat Score100/100
All 4 axes are opposite. The perfect complementary partner who completely covers your blind spots.
#2
Visionary Architect
Conceptual · Design-First · Independent · Innovation
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#3
Technical Lead
Conceptual · Design-First · Collaborative · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#4
Algorithm Engineer
Conceptual · Code-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#5
System Craftsman
Pragmatic · Design-First · Independent · Stability
Compat Score75/100
3 out of 4 axes are opposite. You can leverage each other's strengths in most situations.
#6
CTO Type
Conceptual · Design-First · Collaborative · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#7
Research Engineer
Conceptual · Code-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#8
Core Engineer
Conceptual · Code-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#9
Product Engineer
Pragmatic · Design-First · Independent · Innovation
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
#10
Project Lead
Pragmatic · Design-First · Collaborative · Stability
Compat Score50/100
2 out of 4 axes are opposite. Good partners who bring different perspectives to each other.
Reading the Compat Axis
Shows the top 10 types that are most likely to complement your blind spots based on 4-axis complementarity.
Recommendations
Based on your 4-axis profile, here are 4 recommended hobbies, certifications, and job roles each.
Recommended Hobbies
Competing in (and organizing) hackathons as a team lead
Beta-testing new SaaS and AI tools and writing up the findings
Launching personal products on Product Hunt or AppSumo
Participating in startup community forums (YC Hacker News, Indie Hackers)
Recommended Certifications
AWS Certified Developer – Associate
Professional Scrum Developer (PSD) or SAFe Practitioner
Google Cloud Associate Cloud Engineer
Certified Kubernetes Application Developer (CKAD)
Recommended Roles
Lead Engineer / CTO-track at an early-stage startup
Product Engineer (working closely with or doubling as a PdM)
Growth Engineer (experiment, measure, and iterate loop owner)
AI Product Engineer (LLM integration and RAG pipeline specialist)
Results are based on 50 self-reported answers. Use it as a tool for self-understanding, 1-on-1 conversations, or career reflection. Revisiting every six months helps you track your growth.
Answers (-3 to +3) are aggregated into 4 axes. Each axis is binarized at 0 to classify into one of 16 types. The percentage shown is a 0-100 normalization of the raw axis score.
This assessment shows tendencies, not abilities or rankings. Use it as a reference for self-understanding and growth.
Für wen es ist
Engineers who want to understand their working style objectively.
Voraussetzungen
No prior knowledge required. Takes about 5-10 minutes.
Wie das Ergebnis aussieht
Your 50 answers are scored across 4 axes to determine one of 16 types.
Autoren & Aufseher
- AutorTerumiu EditorialContent team
We design content that measures IT engineering tendencies across 4 axes with 50 questions.
FAQ
How is this different from MBTI?
Specifically designed for IT engineers, measuring 4 work-relevant axes.
Can my result change over time?
Yes. As your projects and experience evolve, your tendencies may shift.
Is one type better than another?
No. All 16 types have distinct strengths.
Dieser Test umfasst 5 Abschnitte und 50 Fragen.
Nach dem Start kann die Sprache nicht mehr geändert werden. Bei Bedarf vorher umstellen.