🪜Engineering Levels

Base expectations for all engineers at any level

• You exhibit our Values.

• Stay on top of errors occurring in your areas. To do this you need to make sure your alerts and notifications are properly configured so you immediately know when critical errors happen. If a customer is notifying us of an issue before this has happened this is a serious issue.

• Maintain a list of improvements, refactors and fixes needed in your area and bring these to sprint planning and work with the Head of Product to ensure these are slotted in when appropriate.

You are active in Notion & Slack with your teammates. We work in async across different time zones. We fully expect team members to manage their time; block deep work and mark it as such in Slack. We expect you to be responsive in hours outside of deep work contribute to discussions and follow up with insights where needed.

You consistently post your weekly stand-up in Notion on Mondays. We intentionally avoid daily stand-ups to reduce the number of meetings. However, everyone needs to be aware of each other's work. This way, tasks can be properly prioritized and planned. Failing to post your weekly stand-up undermines the team's ability to work efficiently in an asynchronous manner.

You write code that is tested. You should not be introducing code that isn't backed by some level of automated tests. It's risky and prevents us from building stable systems. If you need assistance getting new code under tests, reach out to more senior engineers for help

The 5 verticals 🏛️

Engineers are evaluated against 5 verticals:

1. Leadership

   • Leading by example.

   • Instigating change.

   • Understanding what drives people.

   • Developing processes.

   • Showing initiative.

   • Helps other team members via mentorship.

2. Technical Skills

   • Breadth of experience (applications, services, domains, technologies, stacks).

   • Knowledge of best practices.

   • Testing.

   • Refactoring and codebase improvements.

   • Tooling and awareness of progress in the industry.

3. Communication

   • Written and oral communication.

   • Explaining work to peers and non-technical stakeholders.

   • Proactive communication.

   • Developing and improving communication channels.

   • Show empathy and avoid blaming.

4. Delivery

   • Size and scope of the deliverables.

   • Understanding when to get support.

   • Showing initiative

5. Business Knowledge

   • What we do at Junction.

   • The difference between Lab Tests and Wearables.

   • How a piece of work connects to the business.