https://qconsf.com/presentation/oct2022/secret-finding-impactful-projects-land-staff-plus-engineer-role
So, you want to be a Staff-Plus Engineer at your organization. Are you one of a hundred engineers vying for that big new shiny project to get you there?
Let me tell you a little secret: Listen to what your peers and managers are complaining about. Are they drowned in production issues on an old unreliable system that no one wants to touch? Are they stuck waiting for approvals from design committees? Are they struggling to make large-scale interactive applications work across data centers? Or is the business losing money on over-provisioned hardware in the cloud?
These tedious unattractive problems could be your biggest opportunities to solve hard technical issues while having a massive impact on your entire organization.
In this talk, we will use some real-world examples to unpack how to recognize such problems, broaden your scope, and embrace the soft skills needed to tackle them at scale to land a Staff-Plus Engineer role.
22. 2. Business case for solving the
problem
- Motivation (Why?)
- Problem Statement (What?)
- Technical solution (How?)
- LoE (Level of effort)
- RoI (Return on Investment)
22
23. 3a. What soft skills do I need?
- Connect to business impact
- Written communication
- Executive presentations
- Convince non-eng leaders
23
24. 3b. What technical skills do I
need?
- Understand the codebase
- Redefine models & interfaces
- Modularization
- Microservices
- Migrate clients to new API
24
25. 4. Should I pursue a solution?
- Does it energize me?
- Am I ready to see it through
roadblocks?
25
26. 5. Am I willing to learn?
- Embrace technical & non-
technical skills
- Outside my comfort zone
26
28. 6. Recognize patterns & build generic
solutions
- Build for leverage
- Solve for the organization
- Evangelize your solution
28
29. Six steps to a Staff-plus role
1. Seek & recognize impactful problems
2. Build a business case
3. Determine tech & soft skills needed
4. Ask yourself: Am I excited to pursue the
solution?
5. Embrace skills outside comfort zone
6. Recognize patterns & build generic
solutions
29
37. Recognize impactful problems
- Hard to change team review process
- No one is satisfied
- Impacts all of engineering
- Slows development -> slows business
37
57. Recognize impactful problems
- Hard technical problem
- Many teams complaining, no obvious strategy
- Wasteful to solve for each product
independently
- Direct impact to interactive products
57
59. Determine soft skills needed
- Gathering requirements
- Estimating business impact across
product lines
- LoE and RoI tradeoffs
- Alignment with storage infra leads
- Written technical communication
59
60. Recognize patterns & build generic
solutions
- Common remote-DC write APIs
- Common libs to route traffic to
entities pinned to a DC
60
73. 73
1. Encourage constructive criticism
2. Create forums for engineers to
express non-technical challenges
3. Coach your engineers to sell their
ideas and proposals.
76. 76
Why is it better than
REST APIs “for us”?
It’s so much better
than REST APIs
77. 77
What is the advantage “for us”
Migration strategy?
Level of effort?
Return on investment?
78. 78
Let’s write a proposal
and drive consensus
Hmmm, let me get
back to you
79. 79
1. Encourage constructive criticism
2. Create forums for engineers to
express non-technical challenges
3. Coach your engineers to sell their
ideas and proposals.
4. Training programs
80. 80
Design doc workshop
5 things you didn’t know about documentation
Persuasive speaking
How do we make money as a business?
Presenting to executives
84. Important Staff-plus skills
- Write great proposals: why? what? how?
- Influence peers & gain consensus
- Understand the business & RoI
- Present to executives & cross-functional
leaders
84