Seeking Advice: Advancement from L5 to Staff Role and Leveraging Knowledge for Impact

Different organizations value different things: The main tension here is quality vs. velocity. You should figure out which one is more important within your org by:

• Talking to your manager and tech lead (+ any other senior/staff engineers in your org)
• Observing how carefully and air-tight projects in your org are currently shipped
• Making your own project proposals either very aggressive on quality or velocity and reading the room's response

On top of these, something you should consider is severity of failure. What's the damage if one of your products or services fails? Is it:

1. The user needs to click 2 extra buttons as some API call is flaky
2. The user literally loses their $$$ (very relevant as you work at Intuit)

If it's more like #2, then becoming a quality champion is much more important and has better scope.

When it comes to a Big Tech company like Intuit, I generally prefer internal tooling + infra over product when it comes to Staff scope. Finding Staff scope as a product engineer (especially if you're front-end) is notoriously difficult, and I am speaking from experience here.

That being said, it all depends on your org and overall situation. I think when it comes to framing the conversation with your manager, I would do something like:

1. Come up with a list of projects in the quality/internal tool/product reliability infra space.
2. Come up with a list of projects in the product development space.
3. Share them both with your manager and get their opinion on which list is more impactful.

To help with #1 and #2, I recommend these:

• "How can I come up with big initiatives, especially those at a Staff level?"
• "How do I come up with innovative, impactful ideas and bring them to my team?"

Lastly, how can I show metrics and impact?

This will vary based on org/company (some orgs are more data-driven than others) but generally:

1. Log as much as possible (very important at Intuit's scale)
2. Learn how to run A/B tests
3. Create dashboards that track key metrics, especially over time
4. Get familiar with whatever querying mechanism your org uses - Being reliant on a data scientist to measure your impact makes expanding your scope harder
5. Relate the deltas you produce to the overall team's OKRs/KPIs

Internal tooling + quality improvements can be tougher to measure admittedly - We talk about this in-depth across these discussions:

• "How can I demonstrate the impact of migration projects in a platform team?"
• "What are the heuristics to plan the projects for the better engineering work stream?"
• "How do you convey impact for non-product, technical efforts like adding tests and fixing crashes?"

@Alex, to add to the question
The user literally loses their $$$ (very relevant as you work at Intuit) -> This is the option, I have had several discussions with leadership on this.

This is the option, I have had several discussions with leadership on this.

If this is the case, that makes your life far easier! To measure your impact, just connect everything to revenue:

• If you fix a bug that's losing the company $$$, your work is now effectively making money.
• If you guarantee 100% stability on a product with X revenue, you can say that you "protected" all X of that revenue.
• If you improve the performance of a product (e.g. make it faster) that makes $$$, you can claim the delta from the gains.

I worked on ads back at Instagram, and this was pretty much my life. I gave a case study about it here: [Case Study] Solving A Multi-Million $$ Instagram Bug

This is excellent advice, thank you!

I came across our internal rubrics that outline the expectations at each level. -> We have very clear guidelines on the expectations at each level.

Some other questions:

• How can I tie this in the brag document?
• How can I fetch the $$ amount to stability / users?

This quality project has buy in all the way till the CTO.

How can I tie this in the brag document?

There's nothing special you need to do here - Follow the STAR method. We talk about this here:

• "How can I most effectively talk about my projects?"
• "Any examples to describe the project as a story for promo docs?"

If a project has strong buy-in from the CTO (i.e. they mention it in company meetings and maybe even provide input on its technical direction/timeline), then you can mention that when claiming the credit for it in performance review.

How can I fetch the $$ amount to stability / users?

The basic answer is to run an A/B test of some sort - Meta had a bunch of core metrics (user time spent, ads revenue, etc) that you could easily add to any experiment's dashboard. I imagine Intuit has similar infrastructure.

The real answer is that this will vary a lot based on your organization, its culture, and the existing data tooling you have. You may need to run complex SQL queries to fully understand the impact. If that's the case, talk to your friendly neighborhood Data Scientist. 😊