Add AI usage expectations across all seniority levels#170
Conversation
Each role from Associate to Principal now includes criteria for how engineers are expected to work with AI assistants, covering code review habits, prompting quality, agentic workflows, team enablement, and company-wide adoption at senior levels.
MarkusAbtion
requested review from
KlausEnevoldsen-Abtion,
Copilot,
jeppester and
runephilosof-abtion
|
Merged as per instructed by @hcarreras |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the software engineer progression framework to incorporate expectations and guidelines for using AI assistants across all seniority levels. The feedback is minor and focuses on polishing the document, including correcting a spelling inconsistency to maintain American English, improving grammatical parallelism in a list of activities, and removing trailing whitespace on several empty lines.
|
|
||
| - You review every line before committing it. | ||
|
|
||
| - You use AI beyond code - drafting PR descriptions, summarising tickets, and generating documentation. |
There was a problem hiding this comment.
To maintain spelling consistency with the rest of the document (which uses American English spelling like 'prioritize' on line 167 and 'prioritization' on line 356), 'summarising' should be spelled as 'summarizing'.
| - You use AI beyond code - drafting PR descriptions, summarising tickets, and generating documentation. | |
| - You use AI beyond code - drafting PR descriptions, summarizing tickets, and generating documentation. |
|
|
||
| - You work test-driven. | ||
|
|
||
| - You actively integrate AI assistants into your workflow - for exploration, refactors, and tests - and recognize the cases where they slow you down. |
There was a problem hiding this comment.
For better grammatical parallelism, consider using gerunds ('refactoring' and 'testing') to match 'exploration'.
| - You actively integrate AI assistants into your workflow - for exploration, refactors, and tests - and recognize the cases where they slow you down. | |
| - You actively integrate AI assistants into your workflow - for exploration, refactoring, and testing - and recognize the cases where they slow you down. |
| - You work test-driven. | ||
|
|
||
| - You actively integrate AI assistants into your workflow - for exploration, refactors, and tests - and recognize the cases where they slow you down. | ||
|
|
There was a problem hiding this comment.
This line contains trailing whitespace. It should be kept completely empty.
| - You leave codebases better than how you found them. | ||
|
|
||
| - You model effective AI-assisted workflows that lift the team's output, while holding that code to the same bar in review - catching overengineering, hallucinated APIs, and weak tests regardless of how it was produced. | ||
|
|
There was a problem hiding this comment.
This line contains trailing whitespace. It should be kept completely empty.
| - You build project-level automations using AI - pipelines, scripts, and workflows that reduce manual work for the team. | ||
|
|
||
| - You evaluate emerging AI tooling and propose additions to the team's stack when they deliver clear value. | ||
|
|
There was a problem hiding this comment.
This line contains trailing whitespace. It should be kept completely empty.
There was a problem hiding this comment.
Pull request overview
Updates the Software Engineer progression framework to explicitly define expectations for using AI assistants at each seniority level, covering responsible usage, review rigor, automation, and broader organizational adoption.
Changes:
- Adds role-appropriate AI usage expectations from Associate through Principal (learning, prompting, review habits, and ownership).
- Introduces guidance on agentic workflows, automation opportunities, and team enablement around AI usage.
- Expands senior/lead/principal expectations to include org-wide AI adoption, measurement, and external positioning.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| - You review every line before committing it. | ||
|
|
||
| - You use AI beyond code - drafting PR descriptions, summarising tickets, and generating documentation. |
| - You work test-driven. | ||
|
|
||
| - You actively integrate AI assistants into your workflow - for exploration, refactors, and tests - and recognize the cases where they slow you down. | ||
|
|
|
|
||
| - You draw on your agentic AI experience to continuously raise the project's level of automation. | ||
|
|
||
| - You build project-level automations using AI - pipelines, scripts, and workflows that reduce manual work for the team. | ||
|
|
||
| - You evaluate emerging AI tooling and propose additions to the team's stack when they deliver clear value. | ||
|
|
|
|
||
| - You draw on your agentic AI experience to continuously raise the project's level of automation. | ||
|
|
||
| - You build project-level automations using AI - pipelines, scripts, and workflows that reduce manual work for the team. | ||
|
|
||
| - You evaluate emerging AI tooling and propose additions to the team's stack when they deliver clear value. | ||
|
|
|
👏 |
Each role from Associate to Principal now includes criteria for how engineers are expected to work with AI assistants, covering code review habits, prompting quality, agentic workflows, team enablement, and company-wide adoption at senior levels.