IC1 Quality Assurance Engineer
I plan and execute testing of features and report on quality risks to cross-functional stakeholders
Scope Area of ownership and level of autonomy / ambiguity | Collaborative Reach Organizational reach and extent of influence | Impact Levers Technical levers typically exercised to achieve business impact |
- I execute on defined tasks and contribute to solving problems with defined solutions.
| - I work within the scope of my team with specific guidance from my manager/TL
| - Craft - I primarily focus on improving my craft as an engineer
|
Results
Responsibility | Key Behaviors |
Impact | - I work with my manager to prioritize tasks that add the most value and deliver high-quality results for my customer
- I understand and effectively participate in the core processes of my team (planning, on-call rotations, bug triage, metrics review, etc)
|
Ownership | - I follow through on my commitments, take responsibility for my work, and deliver my work on time
- I ask questions to clarify expectations
- I own my failures and learn from them
|
Decision Making | - I escalate to my manager when I get stuck and reflect on ways that I can improve from my mistakes
|
Direction
Responsibility | Key behaviors |
Agility / Innovation | - I share new ideas and can adapt my work when circumstances change
|
Talent
Responsibility | Key Behaviors |
Personal growth | - I'm open to and act upon feedback from my manager and peers
- I'm gaining self-awareness about my strengths and areas for development
- I have a high standard of excellence for my work
|
Hiring | - I am learning to interview and assess candidates to help us build a diverse and talented team. I consistently provide timely, detailed, and evidence-based interview feedback.
- I am able to represent my team’s initiatives and goals to candidates in a compelling way
|
Culture
Responsibility | Key Behaviors |
Collaboration | - I can effectively collaborate to get work done
- I work with my manager to manage conflict with empathy in mind
|
Organizational health | - I listen to different perspectives and I remove biases from my words and actions
- I practice the Dropbox Diversity Commitments on a regular basis
|
Communication | - I write and speak clearly
- I listen to understand others and ask clarifying questions
- I share relevant information on my project including difficult task-level trade-offs that impact the product to my manager and team (including product/business partners).
|
Craft
At the entry-level for QA Engineers at Dropbox, I am focused on learning the fundamentals of testing fluency, testing strategy, and quality assessment.
Responsibility | Key Behaviors |
Testing Fluency | - I write test cases for a feature that is well-defined (but may not have a formal written spec) and utilizes knowledge of our customers
- primarily execute manual “black box” UI testing
- I identify bugs that are obvious/clearly present
- My test cases effectively cover positive and negative test cases and include most basic edge cases
- My bug reports provide sufficient detail so that a developer can investigate further.
|
Testing Strategy | - I plan and execute testing on small to medium sized features of simple to moderate complexity.
|
Quality Assessment | - I report status to cross-functional partners including a basic understanding of quality risks.
|
Quality Advocacy | - I understand who the customers are for the features I work on and the intended impact of the feature on them
|
IC1 Quality Assurance Engineer