Responsibilities and Expectations
This explains what is expected of our development team members. Please note that this list of responsibilities is not intended to be exhaustive, and is subject to change.
Orange-Level Developers
Everyday Responsibilities
Actively participate in daily and weekly team meetings
Bring an attitude of ownership to everything you do
Maintain a sense of urgency (SOU) and do everything possible to eliminate or work around roadblocks
Routinely assess your workload and provide updates to your direct supervisor
Communicate with your direct supervisor when tasks cannot be completed by the expected due date (within the assigned sprint)
If you see you will run out of things to do, ask your supervisor what is the next priority
Conduct code reviews with peers (after 2-4 months)
Adhere to internal code standards and development process
Participate in the on-call rotation, and take ownership of any issues that arise when you are on call
Customer Success
Regular, in-person follow-ups with end users after launching a new system
Personal Tasks
Complete all PWI university assignments within the specified time frame
If you cannot complete an assignment within the specified time frame, negotiate a new due date with your direct supervisor
Fill out and submit weekly EntreLeadership reports
Fill out 1:1 meeting agendas in a timely manner
Required reading
Read Deep Work by Cal Newport and complete the assigned survey within 30 days of starting at PWI
Book Recommendations (not required)
The Ideal Team Player, Lencioni
Know What You’re For, Henderson
Getting Things Done, Allen
Radical Candor, Scott
Blue and Green-Level Developers
Responsibilities for blue and green level developers are outlined in this Google doc. Please note that the doc is currently restricted to blue and green software team members only.