@forwardimpact/schema 0.9.2 → 0.10.1
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/README.md +15 -7
- package/examples/capabilities/delivery.yaml +12 -4
- package/examples/questions/capabilities/business.yaml +17 -14
- package/examples/questions/capabilities/delivery.yaml +7 -6
- package/examples/questions/capabilities/people.yaml +17 -12
- package/examples/questions/capabilities/reliability.yaml +16 -11
- package/examples/questions/capabilities/scale.yaml +8 -6
- package/examples/questions/skills/architecture_design.yaml +2 -1
- package/examples/questions/skills/cloud_platforms.yaml +6 -6
- package/examples/questions/skills/code_quality.yaml +54 -31
- package/examples/questions/skills/data_modeling.yaml +19 -11
- package/examples/questions/skills/devops.yaml +28 -17
- package/examples/questions/skills/full_stack_development.yaml +39 -21
- package/examples/questions/skills/sre_practices.yaml +38 -22
- package/examples/questions/skills/stakeholder_management.yaml +41 -25
- package/examples/questions/skills/team_collaboration.yaml +37 -26
- package/examples/questions/skills/technical_writing.yaml +41 -26
- package/examples/stages.yaml +13 -7
- package/package.json +2 -2
- package/src/modifiers.js +1 -1
package/README.md
CHANGED
|
@@ -1,19 +1,27 @@
|
|
|
1
1
|
# @forwardimpact/schema
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
A public site describing the data model for consumption by AI agents and
|
|
4
|
+
engineers.
|
|
4
5
|
|
|
5
6
|
## Role in the Vision
|
|
6
7
|
|
|
7
|
-
The schema
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
8
|
+
The schema app is the fundamental underpinning of all Forward Impact apps. It
|
|
9
|
+
defines how engineering competencies, career progression, and agent capabilities
|
|
10
|
+
are structured—and publishes that structure in machine-readable formats so AI
|
|
11
|
+
agents can reliably interpret and work with career framework data.
|
|
12
|
+
|
|
13
|
+
Making the schema well understood is a first-class goal. By publishing JSON
|
|
14
|
+
Schema and RDF/SHACL definitions alongside canonical example data, we ensure
|
|
15
|
+
that every consumer—human or AI—shares a consistent understanding of the data
|
|
16
|
+
model.
|
|
11
17
|
|
|
12
18
|
## What It Does
|
|
13
19
|
|
|
14
|
-
- **
|
|
15
|
-
disciplines, tracks, and grades
|
|
20
|
+
- **Public data model** — JSON Schema and RDF/SHACL definitions for skills,
|
|
21
|
+
behaviours, disciplines, tracks, and grades
|
|
16
22
|
- **Data loading** — Parse and validate YAML data files
|
|
23
|
+
- **Validation** — Enforce referential integrity, required fields, and schema
|
|
24
|
+
compliance
|
|
17
25
|
- **Index generation** — Generate browser-compatible file indexes
|
|
18
26
|
- **Example data** — Canonical examples for testing and reference
|
|
19
27
|
|
|
@@ -361,6 +361,8 @@ skills:
|
|
|
361
361
|
- All dependencies installed and versions locked
|
|
362
362
|
- Environment variables configured for local development
|
|
363
363
|
- Database running locally with schema applied
|
|
364
|
+
- All credentials stored in .env — NEVER hardcoded in code,
|
|
365
|
+
including seed scripts and utility scripts
|
|
364
366
|
- Linter and formatter pass on existing code
|
|
365
367
|
- Development server starts and responds to requests
|
|
366
368
|
- CI pipeline configuration is valid
|
|
@@ -379,6 +381,7 @@ skills:
|
|
|
379
381
|
- Database schema supports the feature
|
|
380
382
|
- Error handling spans all layers
|
|
381
383
|
- Feature works end-to-end
|
|
384
|
+
- At least one test exists for each API route and passes when run
|
|
382
385
|
- Deployment is automated
|
|
383
386
|
review:
|
|
384
387
|
focus: |
|
|
@@ -613,10 +616,12 @@ skills:
|
|
|
613
616
|
Surface ambiguities and unknowns before attempting solutions.
|
|
614
617
|
readChecklist:
|
|
615
618
|
- Document the initial problem statement as understood
|
|
616
|
-
-
|
|
617
|
-
|
|
618
|
-
-
|
|
619
|
-
-
|
|
619
|
+
- ASK the user who the stakeholders are and what their perspectives
|
|
620
|
+
are
|
|
621
|
+
- ASK the user what is known vs unknown about the problem
|
|
622
|
+
- ASK the user to confirm or reject your assumptions
|
|
623
|
+
- Mark all ambiguities with [NEEDS CLARIFICATION] and ASK the user
|
|
624
|
+
to clarify them
|
|
620
625
|
confirmChecklist:
|
|
621
626
|
- Initial problem statement is documented
|
|
622
627
|
- Stakeholders are identified
|
|
@@ -858,6 +863,9 @@ skills:
|
|
|
858
863
|
confirmChecklist:
|
|
859
864
|
- Core concept is demonstrable
|
|
860
865
|
- Happy path works end-to-end
|
|
866
|
+
- At least one smoke test verifying the happy path exists
|
|
867
|
+
- SSR pages that fetch from API routes use environment-aware base
|
|
868
|
+
URLs (not hardcoded localhost)
|
|
861
869
|
- Known limitations are documented
|
|
862
870
|
- Stakeholders can interact with it
|
|
863
871
|
review:
|
|
@@ -7,8 +7,8 @@ professionalQuestions:
|
|
|
7
7
|
The product team wants to add a feature that will increase revenue but
|
|
8
8
|
requires significant technical investment. How would you evaluate this?
|
|
9
9
|
context:
|
|
10
|
-
The feature is an AI-powered recommendation engine. Product estimates
|
|
11
|
-
revenue increase. Your team estimates 4 months of work and ongoing
|
|
10
|
+
The feature is an AI-powered recommendation engine. Product estimates
|
|
11
|
+
15% revenue increase. Your team estimates 4 months of work and ongoing
|
|
12
12
|
maintenance costs.
|
|
13
13
|
decompositionPrompts:
|
|
14
14
|
- What questions would you ask the product team?
|
|
@@ -22,16 +22,17 @@ professionalQuestions:
|
|
|
22
22
|
- Thinks about alternatives and build vs buy decisions
|
|
23
23
|
expectedDurationMinutes: 15
|
|
24
24
|
followUps:
|
|
25
|
-
- What if the CEO strongly favors this feature but your analysis
|
|
26
|
-
otherwise?
|
|
25
|
+
- What if the CEO strongly favors this feature but your analysis
|
|
26
|
+
suggests otherwise?
|
|
27
27
|
- How would you handle if the revenue estimate turned out to be
|
|
28
28
|
optimistic?
|
|
29
29
|
|
|
30
30
|
practitioner:
|
|
31
31
|
- id: biz_pro_pract_decomp_1
|
|
32
32
|
text:
|
|
33
|
-
Your company is considering entering a new market that requires
|
|
34
|
-
compliance requirements. How would you approach the technical
|
|
33
|
+
Your company is considering entering a new market that requires
|
|
34
|
+
different compliance requirements. How would you approach the technical
|
|
35
|
+
evaluation?
|
|
35
36
|
context:
|
|
36
37
|
The new market is healthcare (HIPAA compliance). Current systems handle
|
|
37
38
|
financial data but were not designed for healthcare. Leadership wants a
|
|
@@ -60,9 +61,9 @@ managementQuestions:
|
|
|
60
61
|
Your engineering organization needs to reduce costs by 20% while
|
|
61
62
|
maintaining delivery commitments. How would you approach this?
|
|
62
63
|
context:
|
|
63
|
-
Budget constraints require significant cost reduction. You manage 3
|
|
64
|
-
with 18 engineers total. Current commitments include two major
|
|
65
|
-
launches in the next quarter.
|
|
64
|
+
Budget constraints require significant cost reduction. You manage 3
|
|
65
|
+
teams with 18 engineers total. Current commitments include two major
|
|
66
|
+
product launches in the next quarter.
|
|
66
67
|
decompositionPrompts:
|
|
67
68
|
- How would you identify cost reduction opportunities?
|
|
68
69
|
- How would you prioritize cuts while protecting critical work?
|
|
@@ -75,7 +76,8 @@ managementQuestions:
|
|
|
75
76
|
- Renegotiates scope or timelines where necessary
|
|
76
77
|
expectedDurationMinutes: 15
|
|
77
78
|
followUps:
|
|
78
|
-
- What if leadership insists on no headcount changes but still needs 20%
|
|
79
|
+
- What if leadership insists on no headcount changes but still needs 20%
|
|
80
|
+
savings?
|
|
79
81
|
- How would you handle if key team members leave due to uncertainty?
|
|
80
82
|
|
|
81
83
|
practitioner:
|
|
@@ -85,9 +87,9 @@ managementQuestions:
|
|
|
85
87
|
engineering organization. How would you evaluate the technical due
|
|
86
88
|
diligence and integration plan?
|
|
87
89
|
context:
|
|
88
|
-
The target company has 100 engineers, different tech stack, and
|
|
89
|
-
product lines. You have 6 weeks for due diligence and need
|
|
90
|
-
integration risks and synergies to the board.
|
|
90
|
+
The target company has 100 engineers, different tech stack, and
|
|
91
|
+
overlapping product lines. You have 6 weeks for due diligence and need
|
|
92
|
+
to present integration risks and synergies to the board.
|
|
91
93
|
decompositionPrompts:
|
|
92
94
|
- What technical areas would you prioritize in due diligence?
|
|
93
95
|
- How would you assess organizational and cultural compatibility?
|
|
@@ -101,4 +103,5 @@ managementQuestions:
|
|
|
101
103
|
expectedDurationMinutes: 15
|
|
102
104
|
followUps:
|
|
103
105
|
- What if the acquisition goes through despite your concerns?
|
|
104
|
-
- How would you handle if the target's best engineers leave
|
|
106
|
+
- How would you handle if the target's best engineers leave
|
|
107
|
+
post-acquisition?
|
|
@@ -23,7 +23,8 @@ professionalQuestions:
|
|
|
23
23
|
- Thinks about scalability and performance constraints
|
|
24
24
|
expectedDurationMinutes: 15
|
|
25
25
|
followUps:
|
|
26
|
-
- What would you do differently if their data was in 5 different
|
|
26
|
+
- What would you do differently if their data was in 5 different
|
|
27
|
+
systems?
|
|
27
28
|
- How would you handle if a key team member left mid-project?
|
|
28
29
|
|
|
29
30
|
practitioner:
|
|
@@ -78,12 +79,12 @@ managementQuestions:
|
|
|
78
79
|
practitioner:
|
|
79
80
|
- id: del_mgmt_pract_decomp_1
|
|
80
81
|
text:
|
|
81
|
-
You're responsible for coordinating a major platform initiative across
|
|
82
|
-
|
|
82
|
+
You're responsible for coordinating a major platform initiative across 4
|
|
83
|
+
engineering teams. How would you structure the delivery?
|
|
83
84
|
context:
|
|
84
|
-
The initiative is a 12-month platform modernization affecting all
|
|
85
|
-
Teams have different managers, priorities, and technical
|
|
86
|
-
Executive sponsorship is strong but teams are skeptical.
|
|
85
|
+
The initiative is a 12-month platform modernization affecting all
|
|
86
|
+
products. Teams have different managers, priorities, and technical
|
|
87
|
+
preferences. Executive sponsorship is strong but teams are skeptical.
|
|
87
88
|
decompositionPrompts:
|
|
88
89
|
- How would you establish alignment across teams?
|
|
89
90
|
- What governance and coordination mechanisms would you put in place?
|
|
@@ -29,9 +29,9 @@ professionalQuestions:
|
|
|
29
29
|
practitioner:
|
|
30
30
|
- id: ppl_pro_pract_decomp_1
|
|
31
31
|
text:
|
|
32
|
-
Two senior engineers on your team have conflicting views on the
|
|
33
|
-
direction. This is affecting team morale and velocity. How do
|
|
34
|
-
it?
|
|
32
|
+
Two senior engineers on your team have conflicting views on the
|
|
33
|
+
technical direction. This is affecting team morale and velocity. How do
|
|
34
|
+
you address it?
|
|
35
35
|
context:
|
|
36
36
|
One wants to adopt a new framework for better developer experience. The
|
|
37
37
|
other wants to stick with the current stack for stability. Both are high
|
|
@@ -39,7 +39,8 @@ professionalQuestions:
|
|
|
39
39
|
decompositionPrompts:
|
|
40
40
|
- How would you understand the root cause of the conflict?
|
|
41
41
|
- What process would you use to reach a decision?
|
|
42
|
-
- How would you maintain both engineers' engagement regardless of
|
|
42
|
+
- How would you maintain both engineers' engagement regardless of
|
|
43
|
+
outcome?
|
|
43
44
|
- What would you do if the conflict persists after a decision?
|
|
44
45
|
lookingFor:
|
|
45
46
|
- Separates technical disagreement from interpersonal conflict
|
|
@@ -48,19 +49,22 @@ professionalQuestions:
|
|
|
48
49
|
- Plans for ongoing relationship management
|
|
49
50
|
expectedDurationMinutes: 15
|
|
50
51
|
followUps:
|
|
51
|
-
- What if one engineer threatens to leave if their approach isn't
|
|
52
|
-
|
|
52
|
+
- What if one engineer threatens to leave if their approach isn't
|
|
53
|
+
chosen?
|
|
54
|
+
- How would you handle if this pattern repeats with the same
|
|
55
|
+
individuals?
|
|
53
56
|
|
|
54
57
|
managementQuestions:
|
|
55
58
|
working:
|
|
56
59
|
- id: ppl_mgmt_work_decomp_1
|
|
57
60
|
text:
|
|
58
|
-
One of your team members is consistently underperforming despite
|
|
59
|
-
feedback conversations. How would you handle this situation?
|
|
61
|
+
One of your team members is consistently underperforming despite
|
|
62
|
+
multiple feedback conversations. How would you handle this situation?
|
|
60
63
|
context:
|
|
61
64
|
The engineer has been on the team for 8 months. They meet basic
|
|
62
65
|
expectations but are not growing. Peers are frustrated with carrying
|
|
63
|
-
extra load. You've had 3 feedback conversations with limited
|
|
66
|
+
extra load. You've had 3 feedback conversations with limited
|
|
67
|
+
improvement.
|
|
64
68
|
decompositionPrompts:
|
|
65
69
|
- How would you assess whether this is a skill, will, or fit issue?
|
|
66
70
|
- What performance improvement approach would you take?
|
|
@@ -82,8 +86,8 @@ managementQuestions:
|
|
|
82
86
|
You need to grow your engineering organization from 25 to 50 engineers
|
|
83
87
|
over the next year. How would you approach this scaling challenge?
|
|
84
88
|
context:
|
|
85
|
-
The company has secured Series B funding. Current team is strong but
|
|
86
|
-
|
|
89
|
+
The company has secured Series B funding. Current team is strong but has
|
|
90
|
+
no formal career ladders or management structure. You're the only
|
|
87
91
|
engineering manager reporting to the CTO.
|
|
88
92
|
decompositionPrompts:
|
|
89
93
|
- How would you structure the hiring plan and timeline?
|
|
@@ -98,4 +102,5 @@ managementQuestions:
|
|
|
98
102
|
expectedDurationMinutes: 15
|
|
99
103
|
followUps:
|
|
100
104
|
- What if you can't find enough quality candidates?
|
|
101
|
-
- How would you handle if existing senior ICs don't want to become
|
|
105
|
+
- How would you handle if existing senior ICs don't want to become
|
|
106
|
+
managers?
|
|
@@ -30,10 +30,12 @@ professionalQuestions:
|
|
|
30
30
|
- id: rel_pro_pract_decomp_1
|
|
31
31
|
text:
|
|
32
32
|
You're designing the disaster recovery strategy for a system that
|
|
33
|
-
processes customer financial transactions. Walk me through your
|
|
33
|
+
processes customer financial transactions. Walk me through your
|
|
34
|
+
approach.
|
|
34
35
|
context:
|
|
35
|
-
The system handles $10M in daily transactions, uses AWS in us-east-1,
|
|
36
|
-
currently has no cross-region capability. Budget for DR is $50K
|
|
36
|
+
The system handles $10M in daily transactions, uses AWS in us-east-1,
|
|
37
|
+
and currently has no cross-region capability. Budget for DR is $50K
|
|
38
|
+
annual.
|
|
37
39
|
decompositionPrompts:
|
|
38
40
|
- What are the key requirements you need to establish first?
|
|
39
41
|
- How would you structure the technical options analysis?
|
|
@@ -46,7 +48,8 @@ professionalQuestions:
|
|
|
46
48
|
- Plans for regular testing and runbook maintenance
|
|
47
49
|
expectedDurationMinutes: 15
|
|
48
50
|
followUps:
|
|
49
|
-
- What would you do if a regional outage happened before DR was
|
|
51
|
+
- What would you do if a regional outage happened before DR was
|
|
52
|
+
complete?
|
|
50
53
|
- How would you handle if the $50K budget was cut in half?
|
|
51
54
|
|
|
52
55
|
managementQuestions:
|
|
@@ -71,19 +74,20 @@ managementQuestions:
|
|
|
71
74
|
- Creates sustainable practices rather than short-term fixes
|
|
72
75
|
expectedDurationMinutes: 15
|
|
73
76
|
followUps:
|
|
74
|
-
- What if leadership says there's no budget for additional on-call
|
|
77
|
+
- What if leadership says there's no budget for additional on-call
|
|
78
|
+
support?
|
|
75
79
|
- How would you handle if the most experienced engineers refuse on-call?
|
|
76
80
|
|
|
77
81
|
practitioner:
|
|
78
82
|
- id: rel_mgmt_pract_decomp_1
|
|
79
83
|
text:
|
|
80
|
-
Your organization has grown to 20 services owned by different teams
|
|
81
|
-
|
|
84
|
+
Your organization has grown to 20 services owned by different teams but
|
|
85
|
+
has no consistent approach to reliability. How would you establish
|
|
82
86
|
reliability practices at scale?
|
|
83
87
|
context:
|
|
84
|
-
Some teams have mature SLOs and incident response, others don't.
|
|
85
|
-
|
|
86
|
-
|
|
88
|
+
Some teams have mature SLOs and incident response, others don't. Recent
|
|
89
|
+
cross-team incidents took too long to resolve due to unclear ownership.
|
|
90
|
+
Leadership wants to improve reliability organization-wide.
|
|
87
91
|
decompositionPrompts:
|
|
88
92
|
- How would you assess current reliability maturity across teams?
|
|
89
93
|
- What standards and practices would you establish?
|
|
@@ -97,4 +101,5 @@ managementQuestions:
|
|
|
97
101
|
expectedDurationMinutes: 15
|
|
98
102
|
followUps:
|
|
99
103
|
- What if teams resist reliability requirements as overhead?
|
|
100
|
-
- How would you handle if different teams have conflicting SLO
|
|
104
|
+
- How would you handle if different teams have conflicting SLO
|
|
105
|
+
definitions?
|
|
@@ -8,8 +8,8 @@ professionalQuestions:
|
|
|
8
8
|
1000 RPS in 6 months due to a new partnership. How would you approach
|
|
9
9
|
this?
|
|
10
10
|
context:
|
|
11
|
-
The API is a monolithic Node.js application backed by PostgreSQL.
|
|
12
|
-
time P99 is currently 200ms and must stay under 500ms.
|
|
11
|
+
The API is a monolithic Node.js application backed by PostgreSQL.
|
|
12
|
+
Response time P99 is currently 200ms and must stay under 500ms.
|
|
13
13
|
decompositionPrompts:
|
|
14
14
|
- What would you need to measure and understand first?
|
|
15
15
|
- How would you identify the scaling bottlenecks?
|
|
@@ -23,7 +23,8 @@ professionalQuestions:
|
|
|
23
23
|
expectedDurationMinutes: 15
|
|
24
24
|
followUps:
|
|
25
25
|
- What if the partnership deal accelerated and you had only 3 months?
|
|
26
|
-
- How would you handle if the new load had very different access
|
|
26
|
+
- How would you handle if the new load had very different access
|
|
27
|
+
patterns?
|
|
27
28
|
|
|
28
29
|
practitioner:
|
|
29
30
|
- id: scl_pro_pract_decomp_1
|
|
@@ -58,8 +59,8 @@ managementQuestions:
|
|
|
58
59
|
but you don't have dedicated infrastructure expertise. How would you
|
|
59
60
|
build this capability?
|
|
60
61
|
context:
|
|
61
|
-
The system needs to 10x in capacity over the next year. Your team of
|
|
62
|
-
|
|
62
|
+
The system needs to 10x in capacity over the next year. Your team of 6
|
|
63
|
+
engineers has strong application development skills but limited
|
|
63
64
|
infrastructure and performance engineering experience.
|
|
64
65
|
decompositionPrompts:
|
|
65
66
|
- How would you assess your team's current capabilities and gaps?
|
|
@@ -99,4 +100,5 @@ managementQuestions:
|
|
|
99
100
|
expectedDurationMinutes: 15
|
|
100
101
|
followUps:
|
|
101
102
|
- What if teams push back on cost accountability?
|
|
102
|
-
- How would you handle if major cost savings require significant
|
|
103
|
+
- How would you handle if major cost savings require significant
|
|
104
|
+
refactoring?
|
|
@@ -3,7 +3,8 @@
|
|
|
3
3
|
professionalQuestions:
|
|
4
4
|
awareness:
|
|
5
5
|
- id: arch_pro_aware_1
|
|
6
|
-
text:
|
|
6
|
+
text:
|
|
7
|
+
How do you decide where to draw boundaries when structuring new code?
|
|
7
8
|
lookingFor:
|
|
8
9
|
- Thinks about grouping related functionality together
|
|
9
10
|
- Considers how changes in one area might affect others
|
|
@@ -57,7 +57,8 @@ managementQuestions:
|
|
|
57
57
|
awareness:
|
|
58
58
|
- id: cp_mgmt_aware_1
|
|
59
59
|
text:
|
|
60
|
-
How do you stay informed about cloud capabilities that could benefit
|
|
60
|
+
How do you stay informed about cloud capabilities that could benefit
|
|
61
|
+
your team?
|
|
61
62
|
lookingFor:
|
|
62
63
|
- Actively explores cloud capabilities relevant to team work
|
|
63
64
|
- Evaluates new services for practical team benefit
|
|
@@ -65,8 +66,7 @@ managementQuestions:
|
|
|
65
66
|
expectedDurationMinutes: 5
|
|
66
67
|
foundational:
|
|
67
68
|
- id: cp_mgmt_found_1
|
|
68
|
-
text:
|
|
69
|
-
How do you support team members in developing cloud platform skills?
|
|
69
|
+
text: How do you support team members in developing cloud platform skills?
|
|
70
70
|
lookingFor:
|
|
71
71
|
- Creates structured learning paths for cloud skills
|
|
72
72
|
- Pairs team members on cloud tasks for knowledge transfer
|
|
@@ -75,7 +75,8 @@ managementQuestions:
|
|
|
75
75
|
working:
|
|
76
76
|
- id: cp_mgmt_work_1
|
|
77
77
|
text:
|
|
78
|
-
How do you balance cloud costs with team productivity and delivery
|
|
78
|
+
How do you balance cloud costs with team productivity and delivery
|
|
79
|
+
needs?
|
|
79
80
|
followUps:
|
|
80
81
|
- How do you communicate cloud spending to stakeholders?
|
|
81
82
|
lookingFor:
|
|
@@ -96,8 +97,7 @@ managementQuestions:
|
|
|
96
97
|
expectedDurationMinutes: 10
|
|
97
98
|
expert:
|
|
98
99
|
- id: cp_mgmt_expert_1
|
|
99
|
-
text:
|
|
100
|
-
How do you shape organizational cloud strategy and governance?
|
|
100
|
+
text: How do you shape organizational cloud strategy and governance?
|
|
101
101
|
lookingFor:
|
|
102
102
|
- Defines cloud governance that enables innovation within guardrails
|
|
103
103
|
- Influences cloud direction across organizational boundaries
|
|
@@ -3,7 +3,8 @@
|
|
|
3
3
|
professionalQuestions:
|
|
4
4
|
awareness:
|
|
5
5
|
- id: cq_pro_aware_1
|
|
6
|
-
text:
|
|
6
|
+
text:
|
|
7
|
+
How do you ensure the next person who reads your code understands it?
|
|
7
8
|
lookingFor:
|
|
8
9
|
- Thinks about readability from another developer's perspective
|
|
9
10
|
- Uses naming and structure to communicate intent
|
|
@@ -16,7 +17,8 @@ professionalQuestions:
|
|
|
16
17
|
- What naming conventions do you follow?
|
|
17
18
|
- How do you decide when to add comments?
|
|
18
19
|
lookingFor:
|
|
19
|
-
- Uses consistent naming and structure that communicates intent to
|
|
20
|
+
- Uses consistent naming and structure that communicates intent to
|
|
21
|
+
readers
|
|
20
22
|
- Formats code for scanability and groups related logic together
|
|
21
23
|
- Writes comments that explain why, not what
|
|
22
24
|
expectedDurationMinutes: 5
|
|
@@ -30,13 +32,13 @@ professionalQuestions:
|
|
|
30
32
|
- id: cq_pro_work_1
|
|
31
33
|
text: How do you approach code review? What do you look for?
|
|
32
34
|
lookingFor:
|
|
33
|
-
- Follows a systematic approach covering correctness, clarity, and
|
|
35
|
+
- Follows a systematic approach covering correctness, clarity, and
|
|
36
|
+
design
|
|
34
37
|
- Balances thoroughness with keeping reviews timely
|
|
35
38
|
- Gives constructive feedback that helps the author improve
|
|
36
39
|
expectedDurationMinutes: 8
|
|
37
40
|
- id: cq_pro_work_2
|
|
38
|
-
text:
|
|
39
|
-
How do you decide what to test and what level of testing to apply?
|
|
41
|
+
text: How do you decide what to test and what level of testing to apply?
|
|
40
42
|
followUps:
|
|
41
43
|
- How does AI-generated code change your testing approach?
|
|
42
44
|
lookingFor:
|
|
@@ -48,7 +50,8 @@ professionalQuestions:
|
|
|
48
50
|
- id: cq_pro_pract_1
|
|
49
51
|
text: How have you improved code quality practices in your team?
|
|
50
52
|
lookingFor:
|
|
51
|
-
- Identifies specific quality gaps and addresses them with measurable
|
|
53
|
+
- Identifies specific quality gaps and addresses them with measurable
|
|
54
|
+
actions
|
|
52
55
|
- Influences team norms around quality through mentoring and example
|
|
53
56
|
- Balances quality investment with delivery commitments
|
|
54
57
|
expectedDurationMinutes: 8
|
|
@@ -66,42 +69,51 @@ professionalQuestions:
|
|
|
66
69
|
expert:
|
|
67
70
|
- id: cq_pro_expert_1
|
|
68
71
|
text:
|
|
69
|
-
How have you established code quality standards across an organization
|
|
70
|
-
multiple teams?
|
|
72
|
+
How have you established code quality standards across an organization
|
|
73
|
+
or multiple teams?
|
|
71
74
|
followUps:
|
|
72
75
|
- How did you gain adoption?
|
|
73
76
|
- How do you measure success?
|
|
74
77
|
lookingFor:
|
|
75
|
-
- Creates standards that teams adopt willingly because they solve real
|
|
76
|
-
|
|
77
|
-
-
|
|
78
|
+
- Creates standards that teams adopt willingly because they solve real
|
|
79
|
+
problems
|
|
80
|
+
- Measures quality through defect rates and change failure, not just
|
|
81
|
+
lint scores
|
|
82
|
+
- Evolves standards as practices change, especially around AI-generated
|
|
83
|
+
code
|
|
78
84
|
expectedDurationMinutes: 10
|
|
79
85
|
- id: cq_pro_expert_2
|
|
80
86
|
text:
|
|
81
87
|
How do you approach reviewing AI-generated code at scale? What practices
|
|
82
88
|
ensure quality?
|
|
83
89
|
lookingFor:
|
|
84
|
-
- Designs review processes that catch AI-specific failure modes like
|
|
85
|
-
|
|
86
|
-
-
|
|
90
|
+
- Designs review processes that catch AI-specific failure modes like
|
|
91
|
+
plausible but wrong logic
|
|
92
|
+
- Creates verification depth guidelines calibrated to risk, not just
|
|
93
|
+
code origin
|
|
94
|
+
- Establishes organisational patterns for when AI-generated code needs
|
|
95
|
+
deeper scrutiny
|
|
87
96
|
expectedDurationMinutes: 10
|
|
88
97
|
|
|
89
98
|
managementQuestions:
|
|
90
99
|
awareness:
|
|
91
100
|
- id: cq_mgmt_aware_1
|
|
92
|
-
text:
|
|
93
|
-
How do you communicate the importance of code quality to your team?
|
|
101
|
+
text: How do you communicate the importance of code quality to your team?
|
|
94
102
|
lookingFor:
|
|
95
|
-
- Connects quality to outcomes the team cares about like fewer bugs and
|
|
96
|
-
|
|
103
|
+
- Connects quality to outcomes the team cares about like fewer bugs and
|
|
104
|
+
faster changes
|
|
105
|
+
- Uses concrete examples of quality impact rather than abstract
|
|
106
|
+
principles
|
|
97
107
|
expectedDurationMinutes: 5
|
|
98
108
|
foundational:
|
|
99
109
|
- id: cq_mgmt_found_1
|
|
100
110
|
text:
|
|
101
111
|
How do you help team members improve their coding and testing practices?
|
|
102
112
|
lookingFor:
|
|
103
|
-
- Provides specific, actionable feedback in code reviews rather than
|
|
104
|
-
|
|
113
|
+
- Provides specific, actionable feedback in code reviews rather than
|
|
114
|
+
vague suggestions
|
|
115
|
+
- Creates pairing opportunities that build quality skills through real
|
|
116
|
+
work
|
|
105
117
|
- Identifies individual skill gaps and tailors development approaches
|
|
106
118
|
expectedDurationMinutes: 5
|
|
107
119
|
working:
|
|
@@ -111,29 +123,40 @@ managementQuestions:
|
|
|
111
123
|
followUps:
|
|
112
124
|
- How do you handle disagreements about code quality?
|
|
113
125
|
lookingFor:
|
|
114
|
-
- Establishes review norms that balance thoroughness with turnaround
|
|
115
|
-
|
|
116
|
-
-
|
|
126
|
+
- Establishes review norms that balance thoroughness with turnaround
|
|
127
|
+
time
|
|
128
|
+
- Facilitates quality disagreements toward shared standards rather than
|
|
129
|
+
personal preference
|
|
130
|
+
- Creates review practices that work for AI-generated code, not just
|
|
131
|
+
human-written
|
|
117
132
|
expectedDurationMinutes: 8
|
|
118
133
|
practitioner:
|
|
119
134
|
- id: cq_mgmt_pract_1
|
|
120
135
|
text:
|
|
121
|
-
How do you balance code quality standards with delivery pressure from
|
|
136
|
+
How do you balance code quality standards with delivery pressure from
|
|
137
|
+
stakeholders?
|
|
122
138
|
followUps:
|
|
123
139
|
- How do you communicate quality trade-offs?
|
|
124
140
|
lookingFor:
|
|
125
|
-
- Translates quality trade-offs into business terms stakeholders can act
|
|
126
|
-
|
|
127
|
-
-
|
|
141
|
+
- Translates quality trade-offs into business terms stakeholders can act
|
|
142
|
+
on
|
|
143
|
+
- Pushes back on shortcuts that create future cost while accepting
|
|
144
|
+
pragmatic trade-offs
|
|
145
|
+
- Creates visibility into quality metrics so trade-offs are informed,
|
|
146
|
+
not guesses
|
|
128
147
|
expectedDurationMinutes: 8
|
|
129
148
|
expert:
|
|
130
149
|
- id: cq_mgmt_expert_1
|
|
131
150
|
text:
|
|
132
|
-
How do you drive code quality culture and standards across multiple
|
|
151
|
+
How do you drive code quality culture and standards across multiple
|
|
152
|
+
teams?
|
|
133
153
|
followUps:
|
|
134
154
|
- How do you measure quality improvement?
|
|
135
155
|
lookingFor:
|
|
136
|
-
- Creates cross-team quality standards that teams adopt without heavy
|
|
137
|
-
|
|
138
|
-
-
|
|
156
|
+
- Creates cross-team quality standards that teams adopt without heavy
|
|
157
|
+
governance
|
|
158
|
+
- Uses metrics like defect escape rate and change lead time to track
|
|
159
|
+
quality trends
|
|
160
|
+
- Shapes engineering culture so quality is a shared value, not a
|
|
161
|
+
compliance exercise
|
|
139
162
|
expectedDurationMinutes: 10
|
|
@@ -54,15 +54,15 @@ managementQuestions:
|
|
|
54
54
|
awareness:
|
|
55
55
|
- id: dm_mgmt_aware_1
|
|
56
56
|
text:
|
|
57
|
-
How do you ensure your team considers data modeling implications in
|
|
57
|
+
How do you ensure your team considers data modeling implications in
|
|
58
|
+
their work?
|
|
58
59
|
lookingFor:
|
|
59
60
|
- Ensures modeling decisions are considered during feature planning
|
|
60
61
|
- Communicates how data model quality affects system behaviour
|
|
61
62
|
expectedDurationMinutes: 5
|
|
62
63
|
foundational:
|
|
63
64
|
- id: dm_mgmt_found_1
|
|
64
|
-
text:
|
|
65
|
-
How do you help team members develop data modeling skills?
|
|
65
|
+
text: How do you help team members develop data modeling skills?
|
|
66
66
|
lookingFor:
|
|
67
67
|
- Creates learning opportunities through real project work
|
|
68
68
|
- Pairs less experienced engineers with modeling-skilled colleagues
|
|
@@ -75,16 +75,21 @@ managementQuestions:
|
|
|
75
75
|
followUps:
|
|
76
76
|
- How do you handle disagreements about modeling approaches?
|
|
77
77
|
lookingFor:
|
|
78
|
-
- Creates review processes that catch modeling issues before they reach
|
|
79
|
-
|
|
80
|
-
-
|
|
78
|
+
- Creates review processes that catch modeling issues before they reach
|
|
79
|
+
production
|
|
80
|
+
- Facilitates productive disagreements about modeling by focusing on
|
|
81
|
+
trade-offs and evidence
|
|
82
|
+
- Ensures the team aligns on modeling conventions to reduce
|
|
83
|
+
inconsistency
|
|
81
84
|
expectedDurationMinutes: 10
|
|
82
85
|
practitioner:
|
|
83
86
|
- id: dm_mgmt_pract_1
|
|
84
87
|
text:
|
|
85
|
-
How do you coordinate data modeling decisions across teams to ensure
|
|
88
|
+
How do you coordinate data modeling decisions across teams to ensure
|
|
89
|
+
consistency?
|
|
86
90
|
lookingFor:
|
|
87
|
-
- Creates cross-team alignment on shared data models and naming
|
|
91
|
+
- Creates cross-team alignment on shared data models and naming
|
|
92
|
+
conventions
|
|
88
93
|
- Facilitates discussions between teams when models need to interoperate
|
|
89
94
|
- Establishes modeling standards that reduce friction at team boundaries
|
|
90
95
|
expectedDurationMinutes: 10
|
|
@@ -93,7 +98,10 @@ managementQuestions:
|
|
|
93
98
|
text:
|
|
94
99
|
How do you shape organizational data modeling standards and governance?
|
|
95
100
|
lookingFor:
|
|
96
|
-
- Defines data modeling practices and governance adopted across the
|
|
97
|
-
|
|
98
|
-
-
|
|
101
|
+
- Defines data modeling practices and governance adopted across the
|
|
102
|
+
business unit
|
|
103
|
+
- Creates organisational standards that improve data interoperability at
|
|
104
|
+
scale
|
|
105
|
+
- Influences how the organisation values and invests in data
|
|
106
|
+
architecture quality
|
|
99
107
|
expectedDurationMinutes: 10
|