@forwardimpact/map 0.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (83) hide show
  1. package/LICENSE +201 -0
  2. package/README.md +67 -0
  3. package/bin/fit-map.js +287 -0
  4. package/examples/behaviours/_index.yaml +8 -0
  5. package/examples/behaviours/outcome_ownership.yaml +43 -0
  6. package/examples/behaviours/polymathic_knowledge.yaml +41 -0
  7. package/examples/behaviours/precise_communication.yaml +39 -0
  8. package/examples/behaviours/relentless_curiosity.yaml +37 -0
  9. package/examples/behaviours/systems_thinking.yaml +40 -0
  10. package/examples/capabilities/_index.yaml +8 -0
  11. package/examples/capabilities/business.yaml +205 -0
  12. package/examples/capabilities/delivery.yaml +1001 -0
  13. package/examples/capabilities/people.yaml +68 -0
  14. package/examples/capabilities/reliability.yaml +349 -0
  15. package/examples/capabilities/scale.yaml +1672 -0
  16. package/examples/copilot-setup-steps.yaml +25 -0
  17. package/examples/devcontainer.yaml +21 -0
  18. package/examples/disciplines/_index.yaml +6 -0
  19. package/examples/disciplines/data_engineering.yaml +68 -0
  20. package/examples/disciplines/engineering_management.yaml +61 -0
  21. package/examples/disciplines/software_engineering.yaml +68 -0
  22. package/examples/drivers.yaml +202 -0
  23. package/examples/framework.yaml +73 -0
  24. package/examples/levels.yaml +115 -0
  25. package/examples/questions/behaviours/outcome_ownership.yaml +228 -0
  26. package/examples/questions/behaviours/polymathic_knowledge.yaml +275 -0
  27. package/examples/questions/behaviours/precise_communication.yaml +248 -0
  28. package/examples/questions/behaviours/relentless_curiosity.yaml +248 -0
  29. package/examples/questions/behaviours/systems_thinking.yaml +238 -0
  30. package/examples/questions/capabilities/business.yaml +107 -0
  31. package/examples/questions/capabilities/delivery.yaml +101 -0
  32. package/examples/questions/capabilities/people.yaml +106 -0
  33. package/examples/questions/capabilities/reliability.yaml +105 -0
  34. package/examples/questions/capabilities/scale.yaml +104 -0
  35. package/examples/questions/skills/architecture_design.yaml +115 -0
  36. package/examples/questions/skills/cloud_platforms.yaml +105 -0
  37. package/examples/questions/skills/code_quality.yaml +162 -0
  38. package/examples/questions/skills/data_modeling.yaml +107 -0
  39. package/examples/questions/skills/devops.yaml +111 -0
  40. package/examples/questions/skills/full_stack_development.yaml +118 -0
  41. package/examples/questions/skills/sre_practices.yaml +113 -0
  42. package/examples/questions/skills/stakeholder_management.yaml +116 -0
  43. package/examples/questions/skills/team_collaboration.yaml +106 -0
  44. package/examples/questions/skills/technical_writing.yaml +110 -0
  45. package/examples/self-assessments.yaml +64 -0
  46. package/examples/stages.yaml +191 -0
  47. package/examples/tracks/_index.yaml +5 -0
  48. package/examples/tracks/platform.yaml +47 -0
  49. package/examples/tracks/sre.yaml +46 -0
  50. package/examples/vscode-settings.yaml +21 -0
  51. package/package.json +49 -0
  52. package/schema/json/behaviour-questions.schema.json +95 -0
  53. package/schema/json/behaviour.schema.json +73 -0
  54. package/schema/json/capability-questions.schema.json +95 -0
  55. package/schema/json/capability.schema.json +229 -0
  56. package/schema/json/defs.schema.json +132 -0
  57. package/schema/json/discipline.schema.json +123 -0
  58. package/schema/json/drivers.schema.json +48 -0
  59. package/schema/json/framework.schema.json +68 -0
  60. package/schema/json/levels.schema.json +121 -0
  61. package/schema/json/self-assessments.schema.json +52 -0
  62. package/schema/json/skill-questions.schema.json +83 -0
  63. package/schema/json/stages.schema.json +88 -0
  64. package/schema/json/track.schema.json +95 -0
  65. package/schema/rdf/behaviour-questions.ttl +128 -0
  66. package/schema/rdf/behaviour.ttl +130 -0
  67. package/schema/rdf/capability.ttl +466 -0
  68. package/schema/rdf/defs.ttl +396 -0
  69. package/schema/rdf/discipline.ttl +313 -0
  70. package/schema/rdf/drivers.ttl +84 -0
  71. package/schema/rdf/framework.ttl +166 -0
  72. package/schema/rdf/levels.ttl +357 -0
  73. package/schema/rdf/self-assessments.ttl +147 -0
  74. package/schema/rdf/skill-questions.ttl +155 -0
  75. package/schema/rdf/stages.ttl +166 -0
  76. package/schema/rdf/track.ttl +225 -0
  77. package/src/index-generator.js +65 -0
  78. package/src/index.js +44 -0
  79. package/src/levels.js +553 -0
  80. package/src/loader.js +608 -0
  81. package/src/modifiers.js +23 -0
  82. package/src/schema-validation.js +438 -0
  83. package/src/validation.js +2136 -0
@@ -0,0 +1,111 @@
1
+ # yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/skill-questions.schema.json
2
+
3
+ professionalQuestions:
4
+ awareness:
5
+ - id: devops_pro_aware_1
6
+ text:
7
+ What do you understand about CI/CD pipelines? How have you used them?
8
+ lookingFor:
9
+ - Understands that pipelines automate build, test, and deploy steps
10
+ - Describes personal experience using pipelines, even basic usage
11
+ expectedDurationMinutes: 5
12
+ foundational:
13
+ - id: devops_pro_found_1
14
+ text: Describe how you would set up a basic CI pipeline for a new project.
15
+ lookingFor:
16
+ - Identifies key pipeline stages like build, test, and feedback
17
+ - Considers what checks provide the most value early in the pipeline
18
+ - Thinks about developer experience and fast feedback loops
19
+ expectedDurationMinutes: 5
20
+ working:
21
+ - id: devops_pro_work_1
22
+ text:
23
+ How do you design a deployment pipeline that balances safety with speed?
24
+ followUps:
25
+ - How do you handle pipeline failures?
26
+ - How would AI tools change your approach to pipeline design?
27
+ lookingFor:
28
+ - Designs pipelines with progressive confidence stages
29
+ - Builds in rollback mechanisms and monitoring gates
30
+ - Considers the developer experience of the pipeline
31
+ expectedDurationMinutes: 8
32
+ practitioner:
33
+ - id: devops_pro_pract_1
34
+ text: How have you improved deployment practices in your team?
35
+ followUps:
36
+ - How did you measure improvement?
37
+ lookingFor:
38
+ - Identifies specific bottlenecks and addresses them with data
39
+ - Drives measurable improvements in deployment frequency or reliability
40
+ - Mentors team members on DevOps practices and tooling
41
+ expectedDurationMinutes: 8
42
+ expert:
43
+ - id: devops_pro_expert_1
44
+ text: How have you shaped DevOps practices across an organization?
45
+ followUps:
46
+ - What cultural changes did you drive?
47
+ lookingFor:
48
+ - Defines DevOps standards that teams adopt because they reduce pain,
49
+ not because they're mandated
50
+ - Drives cultural shift from ops-as-separate-team to shared operational
51
+ ownership
52
+ - Measures transformation success through deployment frequency and
53
+ recovery time, not compliance
54
+ expectedDurationMinutes: 10
55
+
56
+ managementQuestions:
57
+ awareness:
58
+ - id: devops_mgmt_aware_1
59
+ text:
60
+ How do you ensure your team understands the importance of CI/CD
61
+ practices?
62
+ lookingFor:
63
+ - Communicates pipeline value in terms of team confidence and speed
64
+ - Ensures the team understands pipeline stages and their purpose
65
+ expectedDurationMinutes: 5
66
+ foundational:
67
+ - id: devops_mgmt_found_1
68
+ text: How do you support team members in developing DevOps skills?
69
+ lookingFor:
70
+ - Creates hands-on learning opportunities for DevOps skills
71
+ - Pairs less experienced engineers with DevOps-strong colleagues
72
+ - Makes DevOps work visible and valued, not just ops burden
73
+ expectedDurationMinutes: 5
74
+ working:
75
+ - id: devops_mgmt_work_1
76
+ text:
77
+ How do you establish deployment practices and standards in your team?
78
+ followUps:
79
+ - How do you balance deployment speed with risk?
80
+ lookingFor:
81
+ - Creates deployment standards that improve confidence rather than slow
82
+ teams down
83
+ - Communicates deployment risk in terms stakeholders can act on
84
+ - Uses progressive rollout and feature flags to manage risk without
85
+ blocking releases
86
+ expectedDurationMinutes: 10
87
+ practitioner:
88
+ - id: devops_mgmt_pract_1
89
+ text:
90
+ How do you drive DevOps culture and continuous improvement in your team?
91
+ followUps:
92
+ - How do you communicate deployment metrics to stakeholders?
93
+ lookingFor:
94
+ - Makes deployment metrics visible and uses them to drive improvement
95
+ conversations
96
+ - Creates psychological safety around deployment failures so the team
97
+ learns rather than hides
98
+ - Coaches team members to own the full lifecycle from commit to
99
+ production
100
+ expectedDurationMinutes: 8
101
+ expert:
102
+ - id: devops_mgmt_expert_1
103
+ text: How do you shape organizational DevOps strategy and transformation?
104
+ lookingFor:
105
+ - Defines DevOps maturity models that meet teams where they are and
106
+ guide progression
107
+ - Creates shared platform investments that accelerate all teams without
108
+ constraining them
109
+ - Influences organisation-wide culture toward continuous delivery and
110
+ operational ownership
111
+ expectedDurationMinutes: 10
@@ -0,0 +1,118 @@
1
+ # yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/skill-questions.schema.json
2
+
3
+ professionalQuestions:
4
+ awareness:
5
+ - id: fs_pro_aware_1
6
+ text: What layers of a typical web application are you familiar with?
7
+ lookingFor:
8
+ - Understands the main layers (frontend, backend, data) and their roles
9
+ - Describes how layers communicate and depend on each other
10
+ expectedDurationMinutes: 5
11
+ foundational:
12
+ - id: fs_pro_found_1
13
+ text:
14
+ Walk me through building a simple feature that touches the UI, API, and
15
+ database.
16
+ lookingFor:
17
+ - Thinks through the full flow from user action to data storage
18
+ - Considers how changes in one layer affect others
19
+ - Plans the implementation order pragmatically
20
+ expectedDurationMinutes: 5
21
+ working:
22
+ - id: fs_pro_work_1
23
+ text:
24
+ How do you approach delivering a complete feature end-to-end across the
25
+ stack?
26
+ followUps:
27
+ - How do AI tools help you work across unfamiliar layers?
28
+ lookingFor:
29
+ - Delivers independently across all layers without specialist handoffs
30
+ - Makes pragmatic technology choices based on the feature needs
31
+ - Identifies and addresses gaps in their own stack knowledge
32
+ expectedDurationMinutes: 8
33
+ practitioner:
34
+ - id: fs_pro_pract_1
35
+ text:
36
+ How do you rapidly deliver complete solutions without depending on
37
+ specialists?
38
+ followUps:
39
+ - How do you handle areas outside your expertise?
40
+ lookingFor:
41
+ - Delivers end-to-end features in days by working across the full stack
42
+ confidently
43
+ - Uses AI tools to accelerate work in less familiar layers rather than
44
+ blocking on others
45
+ - Knows when their cross-stack work needs specialist review versus when
46
+ it's solid enough
47
+ expectedDurationMinutes: 10
48
+ expert:
49
+ - id: fs_pro_expert_1
50
+ text: How do you enable rapid full-stack delivery across teams?
51
+ lookingFor:
52
+ - Creates shared tooling and patterns that make cross-stack work
53
+ accessible to all engineers
54
+ - Removes specialist bottlenecks by building team capability rather than
55
+ centralising expertise
56
+ - Shapes hiring and development to value versatility alongside depth
57
+ expectedDurationMinutes: 10
58
+
59
+ managementQuestions:
60
+ awareness:
61
+ - id: fs_mgmt_aware_1
62
+ text:
63
+ How do you ensure your team understands the full scope of features they
64
+ deliver?
65
+ lookingFor:
66
+ - Encourages engineers to trace features end-to-end, not just their
67
+ layer
68
+ - Ensures demos show the complete user experience, not just isolated
69
+ components
70
+ expectedDurationMinutes: 5
71
+ foundational:
72
+ - id: fs_mgmt_found_1
73
+ text: How do you help team members develop skills across the full stack?
74
+ lookingFor:
75
+ - Assigns cross-layer tasks that stretch engineers beyond their comfort
76
+ zone
77
+ - Pairs specialists together so knowledge transfers through real work
78
+ - Creates safety for engineers to work in unfamiliar layers without fear
79
+ of judgment
80
+ expectedDurationMinutes: 10
81
+ working:
82
+ - id: fs_mgmt_work_1
83
+ text:
84
+ How do you balance specialist depth with full-stack breadth in your
85
+ team?
86
+ followUps:
87
+ - How do you assign work to build versatility?
88
+ lookingFor:
89
+ - Maps the team's skill portfolio and identifies risky concentrations
90
+ - Assigns work deliberately to build versatility while respecting
91
+ delivery commitments
92
+ - Uses AI tools' ability to fill knowledge gaps as a lever for
93
+ cross-stack confidence
94
+ expectedDurationMinutes: 10
95
+ practitioner:
96
+ - id: fs_mgmt_pract_1
97
+ text:
98
+ How do you build a team culture of end-to-end ownership and delivery?
99
+ lookingFor:
100
+ - Creates expectations that engineers own features from commit to
101
+ production
102
+ - Removes structural barriers that force specialist handoffs between
103
+ layers
104
+ - Celebrates engineers who step outside their primary expertise to
105
+ unblock delivery
106
+ expectedDurationMinutes: 10
107
+ expert:
108
+ - id: fs_mgmt_expert_1
109
+ text:
110
+ How do you shape organizational approaches to full-stack delivery and
111
+ team structure?
112
+ lookingFor:
113
+ - Designs team topologies that minimise cross-team handoffs for feature
114
+ delivery
115
+ - Creates organisational patterns for building versatile teams at scale
116
+ - Influences hiring practices to value T-shaped engineers over narrow
117
+ specialists
118
+ expectedDurationMinutes: 10
@@ -0,0 +1,113 @@
1
+ # yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/skill-questions.schema.json
2
+
3
+ professionalQuestions:
4
+ awareness:
5
+ - id: sre_pro_aware_1
6
+ text: How do you know when a service is healthy enough for your users?
7
+ lookingFor:
8
+ - Thinks about health from the user's perspective, not just uptime
9
+ - Shows awareness that different users have different expectations
10
+ - Recognizes that monitoring and alerting help detect problems early
11
+ expectedDurationMinutes: 5
12
+ foundational:
13
+ - id: sre_pro_found_1
14
+ text: How would you set up basic monitoring and alerting for a service?
15
+ lookingFor:
16
+ - Monitors the metrics users care about, not just system internals
17
+ - Sets alert thresholds that catch real problems without alert fatigue
18
+ - Builds dashboards that help someone unfamiliar diagnose issues quickly
19
+ expectedDurationMinutes: 8
20
+ working:
21
+ - id: sre_pro_work_1
22
+ text:
23
+ How do you approach handling incidents in production? What is your
24
+ process?
25
+ followUps:
26
+ - What do you learn from incidents and how do you apply it?
27
+ lookingFor:
28
+ - Follows a structured incident response process, not ad-hoc
29
+ firefighting
30
+ - Documents findings and drives follow-up improvements
31
+ - Communicates incident status clearly to affected stakeholders
32
+ expectedDurationMinutes: 8
33
+ practitioner:
34
+ - id: sre_pro_pract_1
35
+ text: How do you balance reliability with feature velocity in your team?
36
+ lookingFor:
37
+ - Uses error budgets to make objective speed-vs-reliability decisions
38
+ - Adjusts reliability investment based on user impact data, not fear
39
+ - Coaches team to treat reliability work as enabling velocity, not
40
+ opposing it
41
+ expectedDurationMinutes: 8
42
+ expert:
43
+ - id: sre_pro_expert_1
44
+ text:
45
+ How have you established reliability culture and practices across an
46
+ organization?
47
+ lookingFor:
48
+ - Creates reliability standards and SLO frameworks adopted across the
49
+ business unit
50
+ - Builds organisational capability for incident response and learning
51
+ - Influences engineering leadership to invest in reliability as a
52
+ business enabler
53
+ expectedDurationMinutes: 10
54
+
55
+ managementQuestions:
56
+ awareness:
57
+ - id: sre_mgmt_aware_1
58
+ text:
59
+ How do you ensure your team understands reliability concepts and their
60
+ importance?
61
+ lookingFor:
62
+ - Connects reliability to user impact in team discussions, not abstract
63
+ metrics
64
+ - Makes reliability part of feature discussions rather than a separate
65
+ concern
66
+ expectedDurationMinutes: 5
67
+ foundational:
68
+ - id: sre_mgmt_found_1
69
+ text:
70
+ How do you support team members in developing reliability engineering
71
+ skills?
72
+ lookingFor:
73
+ - Creates hands-on learning through incident response participation and
74
+ on-call rotations
75
+ - Pairs less experienced engineers with SRE-skilled colleagues on
76
+ reliability tasks
77
+ - Reviews reliability practices in design discussions and code reviews
78
+ expectedDurationMinutes: 8
79
+ working:
80
+ - id: sre_mgmt_work_1
81
+ text: How do you handle incidents and facilitate post-incident learning?
82
+ followUps:
83
+ - How do you communicate incidents to stakeholders?
84
+ lookingFor:
85
+ - Runs blameless incident reviews that produce actionable improvements
86
+ - Communicates incident status and impact clearly to non-technical
87
+ stakeholders
88
+ - Tracks whether post-incident actions are completed and effective
89
+ expectedDurationMinutes: 10
90
+ practitioner:
91
+ - id: sre_mgmt_pract_1
92
+ text:
93
+ How do you drive reliability culture and balance it with feature
94
+ delivery pressure?
95
+ lookingFor:
96
+ - Uses error budgets to make transparent trade-off decisions with
97
+ stakeholders
98
+ - Frames reliability investment as protecting delivery velocity, not
99
+ slowing it
100
+ - Creates team norms where reliability is everyone's responsibility, not
101
+ an SRE team's
102
+ expectedDurationMinutes: 8
103
+ expert:
104
+ - id: sre_mgmt_expert_1
105
+ text: How do you shape organizational reliability strategy and practices?
106
+ lookingFor:
107
+ - Defines reliability practices and SLO frameworks adopted across
108
+ organisational boundaries
109
+ - Creates incident response capabilities that work across teams and
110
+ business units
111
+ - Influences organisational culture so reliability is valued as a
112
+ business differentiator
113
+ expectedDurationMinutes: 10
@@ -0,0 +1,116 @@
1
+ # yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/skill-questions.schema.json
2
+
3
+ professionalQuestions:
4
+ awareness:
5
+ - id: stk_pro_aware_1
6
+ text:
7
+ Who are the key stakeholders you work with and how do you keep them
8
+ informed?
9
+ lookingFor:
10
+ - Identifies who depends on their work and who they depend on
11
+ - Keeps stakeholders informed proactively rather than waiting to be
12
+ asked
13
+ expectedDurationMinutes: 5
14
+ foundational:
15
+ - id: stk_pro_found_1
16
+ text:
17
+ How do you set expectations with stakeholders about timelines and
18
+ deliverables?
19
+ lookingFor:
20
+ - Sets realistic expectations early rather than over-promising
21
+ - Communicates changes to timelines proactively with reasons and
22
+ alternatives
23
+ - Builds trust through consistent follow-through on commitments
24
+ expectedDurationMinutes: 5
25
+ working:
26
+ - id: stk_pro_work_1
27
+ text:
28
+ How do you manage conflicting priorities from different stakeholders?
29
+ followUps:
30
+ - How do you decide whose priorities take precedence?
31
+ lookingFor:
32
+ - Identifies the underlying needs behind each stakeholder's position
33
+ - Facilitates trade-off discussions rather than unilaterally deciding
34
+ - Communicates decisions and reasoning back to all affected parties
35
+ expectedDurationMinutes: 8
36
+ practitioner:
37
+ - id: stk_pro_pract_1
38
+ text:
39
+ How do you build trust with senior stakeholders and influence their
40
+ decisions?
41
+ lookingFor:
42
+ - Builds credibility through consistent delivery and transparent
43
+ communication
44
+ - Influences decisions by framing technical choices in business terms
45
+ - Adapts their communication style to match each stakeholder's
46
+ priorities and preferences
47
+ expectedDurationMinutes: 10
48
+ expert:
49
+ - id: stk_pro_expert_1
50
+ text:
51
+ How do you manage complex stakeholder landscapes across an organization?
52
+ lookingFor:
53
+ - Maps and navigates complex stakeholder networks with competing
54
+ interests
55
+ - Builds coalitions to drive organisational change across boundaries
56
+ - Resolves conflicts between powerful stakeholders while preserving
57
+ relationships
58
+ expectedDurationMinutes: 10
59
+
60
+ managementQuestions:
61
+ awareness:
62
+ - id: stk_mgmt_aware_1
63
+ text: How do you ensure your team understands who their stakeholders are?
64
+ lookingFor:
65
+ - Makes stakeholder context visible to the team during planning and
66
+ execution
67
+ - Helps team members understand how their work impacts other teams and
68
+ users
69
+ expectedDurationMinutes: 5
70
+ foundational:
71
+ - id: stk_mgmt_found_1
72
+ text: How do you help team members develop stakeholder management skills?
73
+ lookingFor:
74
+ - Creates opportunities for engineers to interact directly with
75
+ stakeholders
76
+ - Coaches team members on communication style for different audiences
77
+ - Models effective stakeholder communication in their own interactions
78
+ expectedDurationMinutes: 5
79
+ working:
80
+ - id: stk_mgmt_work_1
81
+ text: How do you manage stakeholder expectations on behalf of your team?
82
+ followUps:
83
+ - How do you shield your team while maintaining transparency?
84
+ lookingFor:
85
+ - Manages expectations proactively by surfacing risks and trade-offs
86
+ early
87
+ - Shields team from context-switching without hiding information from
88
+ stakeholders
89
+ - Maintains trust through transparency even when delivering difficult
90
+ news
91
+ expectedDurationMinutes: 8
92
+ practitioner:
93
+ - id: stk_mgmt_pract_1
94
+ text:
95
+ How do you navigate conflicting stakeholder priorities and build trust
96
+ across groups?
97
+ lookingFor:
98
+ - Facilitates alignment discussions rather than choosing sides
99
+ unilaterally
100
+ - Builds trust with multiple stakeholder groups through consistent and
101
+ fair treatment
102
+ - Creates transparent decision frameworks so stakeholders understand how
103
+ priorities are set
104
+ expectedDurationMinutes: 10
105
+ expert:
106
+ - id: stk_mgmt_expert_1
107
+ text:
108
+ How do you shape organizational approaches to stakeholder engagement?
109
+ lookingFor:
110
+ - Defines stakeholder engagement practices adopted across organisational
111
+ boundaries
112
+ - Creates frameworks for managing complex stakeholder landscapes at
113
+ enterprise scale
114
+ - Influences organisational culture toward transparent, trust-based
115
+ stakeholder relationships
116
+ expectedDurationMinutes: 10
@@ -0,0 +1,106 @@
1
+ # yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/skill-questions.schema.json
2
+
3
+ professionalQuestions:
4
+ awareness:
5
+ - id: tc_pro_aware_1
6
+ text: How do you work with your team to complete shared tasks?
7
+ lookingFor:
8
+ - Communicates progress and blockers to teammates without being asked
9
+ - Shows willingness to help others even when it's not their direct
10
+ responsibility
11
+ expectedDurationMinutes: 5
12
+ foundational:
13
+ - id: tc_pro_found_1
14
+ text: How do you help a teammate when they're stuck on a problem?
15
+ lookingFor:
16
+ - Offers support proactively without waiting to be asked
17
+ - Shares knowledge in a way that builds the teammate's capability
18
+ - Balances helping others with their own delivery commitments
19
+ expectedDurationMinutes: 5
20
+ working:
21
+ - id: tc_pro_work_1
22
+ text: How do you facilitate effective collaboration within your team?
23
+ followUps:
24
+ - How do you handle remote collaboration?
25
+ lookingFor:
26
+ - Creates practices that make collaboration easy, like shared
27
+ documentation and regular syncs
28
+ - Adapts collaboration approach for remote and distributed team members
29
+ - Identifies and removes collaboration friction points proactively
30
+ expectedDurationMinutes: 8
31
+ practitioner:
32
+ - id: tc_pro_pract_1
33
+ text: How do you build high-performing team dynamics?
34
+ lookingFor:
35
+ - Creates conditions for psychological safety and productive conflict
36
+ - Addresses interpersonal friction before it undermines collaboration
37
+ - Builds shared goals that unite diverse working styles
38
+ expectedDurationMinutes: 10
39
+ expert:
40
+ - id: tc_pro_expert_1
41
+ text:
42
+ How do you create collaborative culture across multiple teams or an
43
+ organization?
44
+ lookingFor:
45
+ - Creates cross-team collaboration practices adopted beyond their own
46
+ teams
47
+ - Breaks down silos by establishing shared goals and mutual dependencies
48
+ - Influences organisational culture so collaboration is the default, not
49
+ the exception
50
+ expectedDurationMinutes: 10
51
+
52
+ managementQuestions:
53
+ awareness:
54
+ - id: tc_mgmt_aware_1
55
+ text: How do you ensure your team communicates effectively?
56
+ lookingFor:
57
+ - Creates clear team communication norms for standups, async updates,
58
+ and escalations
59
+ - Notices when communication breaks down and addresses it promptly
60
+ expectedDurationMinutes: 5
61
+ foundational:
62
+ - id: tc_mgmt_found_1
63
+ text: How do you help team members develop collaboration skills?
64
+ lookingFor:
65
+ - Creates opportunities for pair and mob programming to build
66
+ collaboration habits
67
+ - Gives specific feedback on collaboration behaviours in 1:1s and retros
68
+ - Models effective collaboration in their own cross-functional
69
+ interactions
70
+ expectedDurationMinutes: 5
71
+ working:
72
+ - id: tc_mgmt_work_1
73
+ text: How do you facilitate team collaboration and handle conflicts?
74
+ followUps:
75
+ - How do you build psychological safety?
76
+ lookingFor:
77
+ - Addresses conflicts early through facilitated discussion rather than
78
+ avoidance
79
+ - Creates psychological safety by responding constructively to mistakes
80
+ and disagreements
81
+ - Builds team practices that encourage healthy debate and productive
82
+ conflict
83
+ expectedDurationMinutes: 8
84
+ practitioner:
85
+ - id: tc_mgmt_pract_1
86
+ text:
87
+ How do you build high-performing team dynamics and sustain them over
88
+ time?
89
+ lookingFor:
90
+ - Creates conditions where teams maintain high performance through
91
+ personnel changes
92
+ - Addresses team health issues before they impact delivery
93
+ - Builds self-managing teams that sustain their own collaboration
94
+ practices
95
+ expectedDurationMinutes: 10
96
+ expert:
97
+ - id: tc_mgmt_expert_1
98
+ text: How do you shape organizational collaboration culture across teams?
99
+ lookingFor:
100
+ - Defines cross-team collaboration practices adopted across the business
101
+ unit
102
+ - Creates organisational norms that break down team silos and encourage
103
+ knowledge sharing
104
+ - Influences how the organisation values and rewards collaborative
105
+ behaviour
106
+ expectedDurationMinutes: 10
@@ -0,0 +1,110 @@
1
+ # yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/skill-questions.schema.json
2
+
3
+ professionalQuestions:
4
+ awareness:
5
+ - id: tw_pro_aware_1
6
+ text: How do you approach documenting your code and work?
7
+ lookingFor:
8
+ - Documents work consistently, not just when asked
9
+ - Understands that documentation helps future maintainers
10
+ expectedDurationMinutes: 5
11
+ foundational:
12
+ - id: tw_pro_found_1
13
+ text: What makes a good README file? Walk me through what you'd include.
14
+ lookingFor:
15
+ - Structures READMEs for the reader's needs, not the author's
16
+ - Includes essentials like purpose, setup, usage, and contribution guide
17
+ - Keeps documentation concise and up-to-date
18
+ expectedDurationMinutes: 5
19
+ working:
20
+ - id: tw_pro_work_1
21
+ text:
22
+ How do you write technical specifications that enable others to
23
+ implement features?
24
+ followUps:
25
+ - How do you write specs that AI tools can also use effectively?
26
+ lookingFor:
27
+ - Writes specs that reduce ambiguity and enable independent
28
+ implementation
29
+ - Calibrates detail level based on audience and feature complexity
30
+ - Structures specs so they can be verified against implementation
31
+ expectedDurationMinutes: 8
32
+ practitioner:
33
+ - id: tw_pro_pract_1
34
+ text:
35
+ How do you establish documentation standards and practices in your team?
36
+ lookingFor:
37
+ - Creates documentation standards that the team actually follows because
38
+ they're practical
39
+ - Champions spec-driven development where documentation precedes
40
+ implementation
41
+ - Reviews documentation quality with the same rigour as code reviews
42
+ expectedDurationMinutes: 8
43
+ expert:
44
+ - id: tw_pro_expert_1
45
+ text: How do you create organizational documentation culture and systems?
46
+ lookingFor:
47
+ - Creates documentation systems and practices adopted across the
48
+ business unit
49
+ - Defines knowledge management approaches that reduce information silos
50
+ at scale
51
+ - Influences organisational culture so documentation is valued as a
52
+ first-class engineering output
53
+ expectedDurationMinutes: 10
54
+
55
+ managementQuestions:
56
+ awareness:
57
+ - id: tw_mgmt_aware_1
58
+ text: How do you ensure your team maintains adequate documentation?
59
+ lookingFor:
60
+ - Sets clear expectations about what must be documented and when
61
+ - Checks for documentation as part of feature completion criteria
62
+ expectedDurationMinutes: 5
63
+ foundational:
64
+ - id: tw_mgmt_found_1
65
+ text: How do you help team members improve their technical writing skills?
66
+ lookingFor:
67
+ - Reviews documentation and provides specific, actionable feedback on
68
+ clarity and structure
69
+ - Creates pair-writing or review opportunities to build writing skills
70
+ through practice
71
+ - Models clear writing in their own specs, emails, and documentation
72
+ expectedDurationMinutes: 5
73
+ working:
74
+ - id: tw_mgmt_work_1
75
+ text: How do you establish documentation standards and ensure consistency?
76
+ followUps:
77
+ - How do you balance documentation effort with delivery?
78
+ lookingFor:
79
+ - Creates practical documentation standards that reduce inconsistency
80
+ without overhead
81
+ - Balances documentation effort against delivery by focusing on
82
+ high-value documentation
83
+ - Ensures documentation stays current through process integration, not
84
+ manual enforcement
85
+ expectedDurationMinutes: 8
86
+ practitioner:
87
+ - id: tw_mgmt_pract_1
88
+ text:
89
+ How do you drive documentation culture and spec-driven development in
90
+ your team?
91
+ lookingFor:
92
+ - Creates team expectation that specs are written before code, not after
93
+ - Makes documentation quality a visible part of team health metrics and
94
+ retrospectives
95
+ - Builds a culture where engineers view documentation as an investment,
96
+ not a chore
97
+ expectedDurationMinutes: 8
98
+ expert:
99
+ - id: tw_mgmt_expert_1
100
+ text:
101
+ How do you shape organizational documentation practices and knowledge
102
+ management?
103
+ lookingFor:
104
+ - Defines documentation practices and knowledge management systems
105
+ adopted across the business unit
106
+ - Creates organisational standards that reduce information fragmentation
107
+ at enterprise scale
108
+ - Influences how the organisation values and invests in documentation
109
+ infrastructure
110
+ expectedDurationMinutes: 10