Software Engineering
Delivers a maintainable change with clear interfaces, tests and an explanation of trade-offs.
Suggested target: 3 (independent). Confirm it together.
Free to use. No signup.
Rate people against the skills the work needs. See gaps instantly.
An engineering skills matrix maps delivery capabilities against the work your team owns. Rate evidence from changes, incident reviews and design decisions, rather than treating years of experience as a proficiency score.
Click a cell to step through the levels, or type 0 to 4. Backspace clears. Leave unknown skills unrated. A coral dot marks a rating below its target.
| Team member | Software Engineering target | TypeScript Development target | SQL Database Management target | CI/CD Pipeline Implementation target | Security & Authentication Protocols target | Technical Explanation target |
|---|---|---|---|---|---|---|
Your entries stay on this page unless you choose an export. Refreshing clears them.
At targetBelow targetUnrated
For TypeScript Development: pick one real task to practise with support, agree what good looks like and set a review date.
For Technical Explanation: pick one real task to practise with support, agree what good looks like and set a review date.
Leave your work email if you would like to discuss using these results with your team. Your results stay in this browser. No report will be emailed. Privacy policy.
Pick a completed change and review the design, tests and operational follow-through with the engineer. Match expectations to your stack and responsibilities. A blank cell means you need evidence, not that the person lacks the skill.
Look for work that relies on one person. Arrange pairing and documentation before buying broad training. Do not use a small matrix as a promotion algorithm or a ranking of people.
Pair on one small change from design through release review. Ask the learner to explain the trade-offs, add a failure-case test and improve the handover note. Review independence after the second change.
These skills come from Omie’s taxonomy. Targets are suggested levels of independence. Adapt the evidence and expectations to your team’s responsibilities, tools and context.
Delivers a maintainable change with clear interfaces, tests and an explanation of trade-offs.
Suggested target: 3 (independent). Confirm it together.
Models a real data boundary and handles invalid input without hiding type errors.
Suggested target: 3 (independent). Confirm it together.
Explains a query plan and a safe data change with review from a database owner.
Suggested target: 2 (with help). Confirm it together.
Changes a build or test step and demonstrates both its passing and failing behaviour.
Suggested target: 2 (with help). Confirm it together.
Explains an authentication boundary and tests access denial with a reviewer.
Suggested target: 2 (with help). Confirm it together.
Writes a decision note that makes risks and alternatives understandable to another team.
Suggested target: 3 (independent). Confirm it together.
Agree which work samples count before scoring. A person may be independent in one workflow and need help in a different context. Keep those limits in your notes and revisit them when the work changes.
Ratings are your judgement, not verified assessment results. Targets are editable suggestions, not occupational standards.
Omie gives each person one short practice a day on the skill you picked.
Start your free 90-day pilotStart with the six selected skills and the work examples below. Remove irrelevant skills, add a custom skill and agree targets with the people doing the work. The selection is an editable starting point.
Use 0 for not yet, 1 for awareness, 2 for with help, 3 for independent and 4 for can coach. Leave unknown ratings blank. Review a recent work sample and discuss the context before deciding on a rating.
Yes. Download the current matrix as a PDF, or as a CSV for Excel or Google Sheets. These ratings are your judgement, not verified assessment results or promotion criteria.