0

I have a new project on Health, Monitoring and Guardrails and I need help driving this.

Profile picture
Entry-Level Software Engineer [E3] at Meta2 days ago

Hi everyone, I have to drive this E4 level project. The project is focused on Health and monitoring. I have to create an Eng plan focused on how we’ll add loggings, build dashboard, alerts, and add tests.

I have a TL to guide me. I’m totally new to this and I need help and wisdom on how to go about this. I want this to be a successful project. Or if you can provide any resources that will be helpful too.

Thank you for your prompt response.

31
2

Discussion

(2 comments)
  • 1
    Profile picture
    I just work here @ Robinhood
    a day ago

    For larger efforts, the main expectation is that you are able to disambiguate what needs to be done.

    Right now, we can see from your question you're leaning towards thinking about it as one big thing. You've broken it down to a few sub items, which is a good step forward.

    The next steps would be: how should the work be sequenced? Let's start with the first step: there's always a first step in the project. Out of the different things you need to do, what should be done first and why should it be done first? And are you able to break it down into an even smaller action?

    That's a lot of questions, so let me start with one to help you move forward: what's stopping you from doing everything right now without needing someone else to carry you? Answer this question and see if you can narrow down on something from that answer that you can immediately do independently.

    For general junior => mid level advice, I'd recommend:

  • 0
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    15 hours ago

    I need to make a new, higher-quality version of this, but this should help: [Course] System Design Masterclass: Shipping Real Features To Production

    You'll get a ton of points as an E3 for making a doc like this and sharing it. Keep in mind that it doesn't need to be perfect and since you're an E3, nobody is expecting it to be. Just start it and take your best guess on what goes into each section and what technical decisions to make. After that, share it with your TL and other relevant technical stakeholders and get feedback.

    In general, this process is more about being ultra-comfortable being wrong. Just write down and then organize as much of your thought process as you can and expose it aggressively to your team. From there, suck in feedback to sharpen your approach and make things better.

    The code quality course should help as well, particularly with the pieces around decomposition. I recommend starting from this lesson and going forward: https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/sweat-the-details-call-out-edge-cases/