98 lines
3.7 KiB
Markdown
98 lines
3.7 KiB
Markdown
# IC1 Reliability Engineer – Dropbox Engineering Career Framework
|
||
|
||
- **期号**: SRE Weekly Issue #280（2021-07-25）
|
||
- **作者**: Dropbox
|
||
- **链接**: https://dropbox.github.io/dbx-career-framework/ic1_reliability_engineer.html
|
||
|
||
## 简介
|
||
|
||
Check it out, Dropbox publicly released their SRE career ladder.
|
||
|
||
## 正文
|
||
|
||
☰
|
||
|
||
×
|
||
|
||
Dropbox Engineering Career Framework
|
||
|
||
*I take direction from my team to automate and understand the systems*
|
||
|
||
**Scope**
|
||
*Area of ownership and level of autonomy / ambiguity*
|
||
|
||
- I execute on defined tasks and contribute to solving problems with defined solutions.
|
||
|
||
**Collaborative Reach**
|
||
*Organizational reach and extent of influence*
|
||
|
||
- I work within the scope of my team with specific guidance from my manager/TL
|
||
|
||
**Impact Levers**
|
||
*Technical levers typically exercised to achieve business impact*
|
||
|
||
- Craft - I primarily focus on improving my craft as an engineer
|
||
|
||
**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
|
||
|
||
**Agility / Innovation**
|
||
|
||
- I share new ideas and can adapt my work when circumstances change
|
||
|
||
**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
|
||
|
||
**Talent Development**
|
||
|
||
- 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
|
||
|
||
**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).
|
||
|
||
As a entry level Reliability Engineer, my primary craft focus is on learning the fundamentals of sustainably operating services and systems with a focus on reliability, efficiency, automation, and debugging coupled with gaining familiarity with the technologies in my area of work, and learning to work against plans and schedules.
|
||
|
||
**Systems Fluency**
|
||
|
||
- I understand the basics of OS or networks, or hardware and can quickly debug basic system issues.
|
||
- I am learning to understand a typical full stack application (client/load-balancer/frontend/backend/DB) and use the right tools to troubleshoot system issues.
|
||
- I automate simple tasks to reduce the toil in operating systems efficiently.
|
||
- I identify and suggest improvements to system utilization.
|
||
|
||
**Code Fluency**
|
||
|
||
- I translate ideas into clear code, written to be read as well as executed.
|
||
- My code is free of glaring errors - bugs are in edge cases or design, not mainline paths - and is well documented and well tested with appropriate use of manual vs automated tests.
|
||
- I’m capable of reading and navigating functions and classes/modules that I didn’t write.
|