SWE 0 - Software Engineer Co-op & Intern

I grow my knowledge through learning from my team and mentor.

Scope

You seek to learn how to execute pieces of projects by practicing your stack and gaining a foundation of knowledge. You contribute to the project at hand with guidance from your mentor. You grow your knowledge, drawing from your team and the guilds.

Craft

Your focus is dedicated to learning how to work within a team and to grow your knowledge project over project. You learn how to collaborate with your mentor and team on projects. You are receptive to coaching on code reviews and you aim to grow with each contribution. You ask clarifying questions aimed at formulating a deeper understanding of your stack.

Responsibility	Behaviors
Technical	I iterate on feedback in code reviews and read code surrounding my own. I develop healthy code practices.
Scoping & Estimation	I collaborate with my teammates to provide estimates to complete my work. I build an understanding of my own speed and apply that to estimations in project planning.
Quality	I transform constructive feedback into valuable opportunities for personal development and integrate learning into my contributions I learn how to develop tests within my stack.

Communication and Collaboration

You participate in team meetings and ask clarifying questions. You work closely with your mentor, communicating early and often, asking for help when needed, and keeping your mentor informed of project status. You invest in learning about your team and the people around you to foster close collaboration.

Responsibility	Behaviors
Autonomy	I ask for help early and often when I am stuck.
Accountability	I keep my team informed as to my project status.
Data Driven	I learn from the data my team analyzes to make decisions, and I look to derive insights from data on projects I work on.
Clarity	I ask questions when I do not have clarity in pursuit of a strong understanding.

Moving to the SWE 1 level (or other full-time position)

• You start to deliver your own estimations on work broken down by the team.
• You begin to learn and understand operational excellence through observability, monitors, and alerts.
• You start to understand the architecture and where your code lives in the broader ecosystem.