HubSpot Engineering Performance Rubric 7/14/19, 7(59 PM

HubSpot Engineering Performance Rubric

Category 1 2 3 4 5
Effectiveness does not GSD, few meaningful sometimes makes GSD and is often recognized level 4 +=
does not make contributions impactful contributions for large, important no surprises,
meaningful impactful occasionally ships rarely ships bugs/ops contributions nothing is left
contributions contributions bugs or introduces issues ships high quality, high-perf dangling
ships quality ships bugs and operational issues usually focused, and readable code clearly takes
software sloppy code requires frequent sometimes requires accomplishes tasks quickly leadership
focus works on too direction extra direction or keeps manager well informed when dealing
communication many tasks frequent reminders to complete high commits (5+/day) with
timeliness poor surprises/little task frequent deploys (3+/day) operational
commits & communication comm. few communication frequently manages issues and
deploys few commits (0- inconsistent surprises infrastructure and investigates critsits
operations 2/day) commits (2-3/day) consistent commits (3- operational issues seen as a
ability to rare deploys (0- inconsistent 5/day) always resolves alerts and major role
resolve alerts & 1/day) deploys (1/day) consistent deploys (1- JIRAs model/leader
bugs does not operate inconsistently logs 2/day) in the
infrastructure in, creates creates, logs in, and organization
does not resolve infrastructure, or manages infrastructure. others desire
alerts or JIRAs acts on sometimes acts on his/her input or
operational operational information follow his/her
knowledge (logs, monitoring lead in
inconsistently metrics) technical
resolves alerts and resolves most alerts matters
JIRAs and JIRAs

Attitude doesn't put in the inconsistent usually available and always available and above level 4 +=
hours to win availability and working average display of effort champions
effort stays clear from effort owns some projects, proactively takes ownership quality across
ownership owning projects, owns few projects requires some direction proactively improves quality of multiple
attention to avoids taking inconsistently to move them forward projects and responds to PR projects,
quality responsibility addresses quality sometimes improves boldly addresses all alerts and leading
responsiveness does not improve issues quality, and helps with JIRAs, effectively triages refactoring
challenge & the quality of the frequently requires refactoring problems, and keeps efforts and
learning projects they work direction to move usually responds to stakeholders informed in a reviewing all
helping & on projects forward issues in a timely positive manner. proactively pull requests
kindness does not respond inconsistently, fashion and in a neutral investigates warnings and comes up with
team attitude to warnings, unprofessionally, and professional instability new ideas,
alerts, or JIRAs - or slowly responds manner. sometimes freely works with new sees them
frustrated or timid to issues. investigates and technologies and grows skills implemented,
when problems inconsistently follows-up regularly provides feedback encourages
arise follows-up sometimes works with and advice to others adoption and
does not learn infrequently works new technologies, but regardless of team or contributions.
new technology, with new does not proactively technology masters new
does not grow technologies or grow skill set great attitude, takes initiative technology,
their skill set or grows skills usually provides advice to solve problems, is an energy advocates for
embrace new infrequently and feedback to their amplifier new
challenges provides feedback team approaches,
never helps others and advice or has positive attitude, and embraces
not a team player, a negative or welcomes change and all challenges
generally has a unprofessional does the best thing for
negative or self- attitude towards the team, though
directed attitude constructive sometimes requires
rather than putting feedback direction or coaching
the team first inconsistent to take action
attitude, often
reacts negatively
to changes, but
usually comes
around

Leadership never participates as a lead, is as a lead, consistently as a lead, improves the one- level 4 +=
in one-on-ones (as inconsistent with holds one-on-ones on-one processes as a lead,
team a lead) or one-on-ones with reports as a principal, improves the advocates and
development mentoring (as a as a principal, is as a principal, mentoring processes implements
direction & principal) inconsistent with consistently improves the interview and new cross-
alignment never provides mentoring contributes to recruiting processes team direction
speed direction for their infrequently mentoring through improves the on-boarding and in the
team (as a lead) or provides direction code reviews, best- training processes department
never provides to others practice examples, or as a principal,
technology infrequently new tools advocates and
direction for their participates in as a lead, usually implements
team (as a interviews or provides project new
principal) recruiting events direction for team technology
never participates as a principal, usually direction for
in or contributes to provides technology the
interviews or direction for the department
recruiting events department organizes
usually participates in recruiting
interviews events and
sometimes participates materials
in recruiting events

http://github.hubspot.com/engineering-rubric/ Page 1 of 2
HubSpot Engineering Performance Rubric 7/14/19, 7(59 PM

http://github.hubspot.com/engineering-rubric/ Page 2 of 2