@forwardimpact/schema 0.9.1 → 0.9.2
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.
- package/examples/questions/capabilities/business.yaml +37 -40
- package/examples/questions/capabilities/delivery.yaml +32 -36
- package/examples/questions/capabilities/people.yaml +37 -40
- package/examples/questions/capabilities/reliability.yaml +35 -38
- package/examples/questions/capabilities/scale.yaml +35 -36
- package/examples/questions/skills/architecture_design.yaml +59 -49
- package/examples/questions/skills/cloud_platforms.yaml +53 -41
- package/examples/questions/skills/code_quality.yaml +81 -31
- package/examples/questions/skills/data_modeling.yaml +43 -39
- package/examples/questions/skills/devops.yaml +46 -39
- package/examples/questions/skills/full_stack_development.yaml +41 -36
- package/examples/questions/skills/sre_practices.yaml +40 -37
- package/examples/questions/skills/stakeholder_management.yaml +37 -36
- package/examples/questions/skills/team_collaboration.yaml +39 -33
- package/examples/questions/skills/technical_writing.yaml +39 -35
- package/package.json +1 -1
|
@@ -5,16 +5,17 @@ professionalQuestions:
|
|
|
5
5
|
- id: tc_pro_aware_1
|
|
6
6
|
text: How do you work with your team to complete shared tasks?
|
|
7
7
|
lookingFor:
|
|
8
|
-
-
|
|
9
|
-
-
|
|
8
|
+
- Communicates progress and blockers to teammates without being asked
|
|
9
|
+
- Shows willingness to help others even when it's not their direct responsibility
|
|
10
10
|
expectedDurationMinutes: 5
|
|
11
11
|
foundational:
|
|
12
12
|
- id: tc_pro_found_1
|
|
13
13
|
text:
|
|
14
|
-
|
|
14
|
+
How do you help a teammate when they're stuck on a problem?
|
|
15
15
|
lookingFor:
|
|
16
|
-
-
|
|
17
|
-
-
|
|
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
|
|
18
19
|
expectedDurationMinutes: 5
|
|
19
20
|
working:
|
|
20
21
|
- id: tc_pro_work_1
|
|
@@ -22,15 +23,17 @@ professionalQuestions:
|
|
|
22
23
|
followUps:
|
|
23
24
|
- How do you handle remote collaboration?
|
|
24
25
|
lookingFor:
|
|
25
|
-
-
|
|
26
|
-
-
|
|
26
|
+
- Creates practices that make collaboration easy, like shared documentation and regular syncs
|
|
27
|
+
- Adapts collaboration approach for remote and distributed team members
|
|
28
|
+
- Identifies and removes collaboration friction points proactively
|
|
27
29
|
expectedDurationMinutes: 8
|
|
28
30
|
practitioner:
|
|
29
31
|
- id: tc_pro_pract_1
|
|
30
|
-
text:
|
|
32
|
+
text: How do you build high-performing team dynamics?
|
|
31
33
|
lookingFor:
|
|
32
|
-
-
|
|
33
|
-
-
|
|
34
|
+
- Creates conditions for psychological safety and productive conflict
|
|
35
|
+
- Addresses interpersonal friction before it undermines collaboration
|
|
36
|
+
- Builds shared goals that unite diverse working styles
|
|
34
37
|
expectedDurationMinutes: 10
|
|
35
38
|
expert:
|
|
36
39
|
- id: tc_pro_expert_1
|
|
@@ -38,52 +41,55 @@ professionalQuestions:
|
|
|
38
41
|
How do you create collaborative culture across multiple teams or an
|
|
39
42
|
organization?
|
|
40
43
|
lookingFor:
|
|
41
|
-
-
|
|
42
|
-
-
|
|
44
|
+
- Creates cross-team collaboration practices adopted beyond their own teams
|
|
45
|
+
- Breaks down silos by establishing shared goals and mutual dependencies
|
|
46
|
+
- Influences organisational culture so collaboration is the default, not the exception
|
|
43
47
|
expectedDurationMinutes: 10
|
|
44
48
|
|
|
45
49
|
managementQuestions:
|
|
46
50
|
awareness:
|
|
47
51
|
- id: tc_mgmt_aware_1
|
|
48
|
-
text:
|
|
52
|
+
text:
|
|
53
|
+
How do you ensure your team communicates effectively?
|
|
49
54
|
lookingFor:
|
|
50
|
-
-
|
|
51
|
-
-
|
|
55
|
+
- Creates clear team communication norms for standups, async updates, and escalations
|
|
56
|
+
- Notices when communication breaks down and addresses it promptly
|
|
52
57
|
expectedDurationMinutes: 5
|
|
53
58
|
foundational:
|
|
54
59
|
- id: tc_mgmt_found_1
|
|
55
|
-
text:
|
|
56
|
-
|
|
57
|
-
- How do you prevent conflicts from escalating?
|
|
60
|
+
text:
|
|
61
|
+
How do you help team members develop collaboration skills?
|
|
58
62
|
lookingFor:
|
|
59
|
-
-
|
|
60
|
-
-
|
|
63
|
+
- Creates opportunities for pair and mob programming to build collaboration habits
|
|
64
|
+
- Gives specific feedback on collaboration behaviours in 1:1s and retros
|
|
65
|
+
- Models effective collaboration in their own cross-functional interactions
|
|
61
66
|
expectedDurationMinutes: 5
|
|
62
67
|
working:
|
|
63
68
|
- id: tc_mgmt_work_1
|
|
64
|
-
text:
|
|
69
|
+
text:
|
|
70
|
+
How do you facilitate team collaboration and handle conflicts?
|
|
65
71
|
followUps:
|
|
66
|
-
- How do you
|
|
72
|
+
- How do you build psychological safety?
|
|
67
73
|
lookingFor:
|
|
68
|
-
-
|
|
69
|
-
-
|
|
74
|
+
- Addresses conflicts early through facilitated discussion rather than avoidance
|
|
75
|
+
- Creates psychological safety by responding constructively to mistakes and disagreements
|
|
76
|
+
- Builds team practices that encourage healthy debate and productive conflict
|
|
70
77
|
expectedDurationMinutes: 8
|
|
71
78
|
practitioner:
|
|
72
79
|
- id: tc_mgmt_pract_1
|
|
73
80
|
text:
|
|
74
|
-
How do you
|
|
75
|
-
followUps:
|
|
76
|
-
- How do you onboard new members into the team culture?
|
|
81
|
+
How do you build high-performing team dynamics and sustain them over time?
|
|
77
82
|
lookingFor:
|
|
78
|
-
-
|
|
79
|
-
-
|
|
83
|
+
- Creates conditions where teams maintain high performance through personnel changes
|
|
84
|
+
- Addresses team health issues before they impact delivery
|
|
85
|
+
- Builds self-managing teams that sustain their own collaboration practices
|
|
80
86
|
expectedDurationMinutes: 10
|
|
81
87
|
expert:
|
|
82
88
|
- id: tc_mgmt_expert_1
|
|
83
89
|
text:
|
|
84
|
-
How do you
|
|
85
|
-
influence?
|
|
90
|
+
How do you shape organizational collaboration culture across teams?
|
|
86
91
|
lookingFor:
|
|
87
|
-
-
|
|
88
|
-
-
|
|
92
|
+
- Defines cross-team collaboration practices adopted across the business unit
|
|
93
|
+
- Creates organisational norms that break down team silos and encourage knowledge sharing
|
|
94
|
+
- Influences how the organisation values and rewards collaborative behaviour
|
|
89
95
|
expectedDurationMinutes: 10
|
|
@@ -5,87 +5,91 @@ professionalQuestions:
|
|
|
5
5
|
- id: tw_pro_aware_1
|
|
6
6
|
text: How do you approach documenting your code and work?
|
|
7
7
|
lookingFor:
|
|
8
|
-
-
|
|
9
|
-
-
|
|
8
|
+
- Documents work consistently, not just when asked
|
|
9
|
+
- Understands that documentation helps future maintainers
|
|
10
10
|
expectedDurationMinutes: 5
|
|
11
11
|
foundational:
|
|
12
12
|
- id: tw_pro_found_1
|
|
13
13
|
text: What makes a good README file? Walk me through what you'd include.
|
|
14
14
|
lookingFor:
|
|
15
|
-
-
|
|
16
|
-
-
|
|
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
|
|
17
18
|
expectedDurationMinutes: 5
|
|
18
19
|
working:
|
|
19
20
|
- id: tw_pro_work_1
|
|
20
21
|
text:
|
|
21
|
-
How do you write technical specifications that enable others to
|
|
22
|
-
|
|
22
|
+
How do you write technical specifications that enable others to implement
|
|
23
|
+
features?
|
|
23
24
|
followUps:
|
|
24
|
-
- How
|
|
25
|
+
- How do you write specs that AI tools can also use effectively?
|
|
25
26
|
lookingFor:
|
|
26
|
-
-
|
|
27
|
-
-
|
|
27
|
+
- Writes specs that reduce ambiguity and enable independent implementation
|
|
28
|
+
- Calibrates detail level based on audience and feature complexity
|
|
29
|
+
- Structures specs so they can be verified against implementation
|
|
28
30
|
expectedDurationMinutes: 8
|
|
29
31
|
practitioner:
|
|
30
32
|
- id: tw_pro_pract_1
|
|
31
33
|
text:
|
|
32
34
|
How do you establish documentation standards and practices in your team?
|
|
33
35
|
lookingFor:
|
|
34
|
-
-
|
|
35
|
-
-
|
|
36
|
+
- Creates documentation standards that the team actually follows because they're practical
|
|
37
|
+
- Champions spec-driven development where documentation precedes implementation
|
|
38
|
+
- Reviews documentation quality with the same rigour as code reviews
|
|
36
39
|
expectedDurationMinutes: 8
|
|
37
40
|
expert:
|
|
38
41
|
- id: tw_pro_expert_1
|
|
39
42
|
text: How do you create organizational documentation culture and systems?
|
|
40
43
|
lookingFor:
|
|
41
|
-
-
|
|
42
|
-
-
|
|
44
|
+
- Creates documentation systems and practices adopted across the business unit
|
|
45
|
+
- Defines knowledge management approaches that reduce information silos at scale
|
|
46
|
+
- Influences organisational culture so documentation is valued as a first-class engineering output
|
|
43
47
|
expectedDurationMinutes: 10
|
|
44
48
|
|
|
45
49
|
managementQuestions:
|
|
46
50
|
awareness:
|
|
47
51
|
- id: tw_mgmt_aware_1
|
|
48
|
-
text:
|
|
52
|
+
text:
|
|
53
|
+
How do you ensure your team maintains adequate documentation?
|
|
49
54
|
lookingFor:
|
|
50
|
-
-
|
|
51
|
-
-
|
|
55
|
+
- Sets clear expectations about what must be documented and when
|
|
56
|
+
- Checks for documentation as part of feature completion criteria
|
|
52
57
|
expectedDurationMinutes: 5
|
|
53
58
|
foundational:
|
|
54
59
|
- id: tw_mgmt_found_1
|
|
55
60
|
text:
|
|
56
|
-
How do you
|
|
57
|
-
followUps:
|
|
58
|
-
- How do you handle resistance to documentation?
|
|
61
|
+
How do you help team members improve their technical writing skills?
|
|
59
62
|
lookingFor:
|
|
60
|
-
-
|
|
61
|
-
-
|
|
63
|
+
- Reviews documentation and provides specific, actionable feedback on clarity and structure
|
|
64
|
+
- Creates pair-writing or review opportunities to build writing skills through practice
|
|
65
|
+
- Models clear writing in their own specs, emails, and documentation
|
|
62
66
|
expectedDurationMinutes: 5
|
|
63
67
|
working:
|
|
64
68
|
- id: tw_mgmt_work_1
|
|
65
69
|
text:
|
|
66
|
-
How do you
|
|
67
|
-
team?
|
|
70
|
+
How do you establish documentation standards and ensure consistency?
|
|
68
71
|
followUps:
|
|
69
|
-
-
|
|
72
|
+
- How do you balance documentation effort with delivery?
|
|
70
73
|
lookingFor:
|
|
71
|
-
-
|
|
72
|
-
-
|
|
74
|
+
- Creates practical documentation standards that reduce inconsistency without overhead
|
|
75
|
+
- Balances documentation effort against delivery by focusing on high-value documentation
|
|
76
|
+
- Ensures documentation stays current through process integration, not manual enforcement
|
|
73
77
|
expectedDurationMinutes: 8
|
|
74
78
|
practitioner:
|
|
75
79
|
- id: tw_mgmt_pract_1
|
|
76
|
-
text:
|
|
77
|
-
|
|
78
|
-
- How do you keep documentation current?
|
|
80
|
+
text:
|
|
81
|
+
How do you drive documentation culture and spec-driven development in your team?
|
|
79
82
|
lookingFor:
|
|
80
|
-
-
|
|
81
|
-
-
|
|
83
|
+
- Creates team expectation that specs are written before code, not after
|
|
84
|
+
- Makes documentation quality a visible part of team health metrics and retrospectives
|
|
85
|
+
- Builds a culture where engineers view documentation as an investment, not a chore
|
|
82
86
|
expectedDurationMinutes: 8
|
|
83
87
|
expert:
|
|
84
88
|
- id: tw_mgmt_expert_1
|
|
85
89
|
text:
|
|
86
|
-
How do you
|
|
87
|
-
multiple teams?
|
|
90
|
+
How do you shape organizational documentation practices and knowledge management?
|
|
88
91
|
lookingFor:
|
|
89
|
-
-
|
|
90
|
-
-
|
|
92
|
+
- Defines documentation practices and knowledge management systems adopted across the business unit
|
|
93
|
+
- Creates organisational standards that reduce information fragmentation at enterprise scale
|
|
94
|
+
- Influences how the organisation values and invests in documentation infrastructure
|
|
91
95
|
expectedDurationMinutes: 10
|