Need help on how to navigate PIP

I highly recommend going through the course I developed about PIPs here: https://www.jointaro.com/course/the-ultimate-performance-improvement-plan-pip-guide/, in particular the lesson about whether you should work through a PIP.

The quick summary: you should evaluate from (1) reading the PIP document, (2) your manager's attitude, and (3) your coworkers if you have a chance of surviving the PIP.

• Unfortunately, the answer is often no, and the PIP is a way to push you out.
  • In this case, you should view the PIP period as time to do interview prep and network.
• If the PIP is doable (I'd say this happens < 20% of the time), then you should put your best effort and view it as a learning opportunity.

It looks to me like the core point of your PIP is the bugginess of your code. This makes sense as a staple of a solidly performing junior engineer (and any engineer really) is that I trust them to push high-quality code independently and don't have to worry. The good news is that this can be fixed.

First, I recommend following the steps here to show that you have the right mentality when working with mistakes - You need to earn back trust: "How to turn a string of silly mistakes into a mature positive outcome?"

After that, I highly recommend going through my code quality course: [Course] Level Up Your Code Quality As A Software Engineer

If you truly master all the concepts in that course, I guarantee you that you will absolutely crush the expectations of the PIP and earn back the respect of your peers (assuming the PIP is in good faith, which is a trickier issue). All of the tactics in the course will make you write higher-quality code that breaks less.

The PIP being 60 days is good news - A classic sign of a PIP that's designed to make you fail is that it's only 30 days long. Now you should test if your manager was telling the truth about providing support. My course covers proactive measures like creating plans for your commits and soliciting feedback. After your code goes into review, it should be reviewed quickly and thoroughly. If your teammates aren't doing that, this is a sign the team doesn't actually want you to survive the PIP.

In terms of what to say to your director about the PIP, I really don't know. They obviously know that you're on a PIP (they almost certainly approved it), so the general skip 1 on 1 tactics of asking about higher-level org vision don't really apply here. The PIP is the elephant in the room.

My recommendation is to own up to the PIP and show that you're going to take the feedback in stride and get better as an engineer. You can even use Taro to show that - Not only are you pushing hard within work, you are going through external resources outside of work crafted by top engineers as well to further augment your skills.

At the end of the day though, actions speak louder than words. Speak with your actions by following the advice from the code quality course and implementing the tactics ASAP. It should be an immediate difference in the quality of your code, and teammates should see it (and hopefully the good word will spread to your director).