Repeat after me: Its not me, its them. > Long story short, screwed up a step I had done before in the fall without realizing. Then when it was fixed I submitt

Repeat after me: Its not me, its them. > Long story short, screwed up a step I had done before in the fall without realizing. Then when it was fixed I submitted a ticket for a prod systems account rather than a QA one not realizing there would be a difference. (Just so many mistakes all in a row). This is a failure of procedure by your team. if their systems are that badly documented, monitored and controlled, you are doing a great job of QA'ing their shitness. Be sure to document what you've learnt clearly, so that others can avoid your mistakes. > I was sometimes assigned stories no one else on the team had done anything like before Thats another failure of the team/company. > this team isn't a bad one. I can make excuses all I want, but an experienced engineer joined the same time I did and is doing great. They sure as shit sound like one. You know the difference between you and the experienced engineer? _experience_ sure they are doing better than you, but thats because they've made all your mistakes before. > one of the senior engineers even pointed out they shouldn't be helping me with certain processes at this point. That engineer is a shit. if its not documented, then they are being top grade pricks. > when I am actively slowing the team down or causing problems. if that was the case, why are they letting you slow the team down? like if a member of my team was "blocking" something because they were slow, we'd all be free to help. Thus we would help you to get up to speed. If they are letting you stew on stories that are unrelated to what the rest of the team are working on, then I suspect you holding them us is bullshit. > I certainly didn't ask enough questions when I started and I definitely will wait around for people to get back to me sometimes rather then be proactive. I assume you are working with, or are remote? knowing when to ping or VC is one of the things that isn't taught, or even agreed upon. so I have every sympathy with your predicament. However you can afford to ping people more, and ask to setup a 1:1 to make sure you understand (write bullet point summaries and get them to send links) > PIP because of this, I feel like I can't help but see it as a statement on my potential and ability. Ironically a PIP might be actually good. It _should_ give you clear, actionable information along with measurable goals and managerial support to reach them. All of which appear to have been lacking so far. Even if it is a reflection of your potential and ability (its not) it only reflects that team and company. Everyone else: If you see your self in any of the actors in OP's post, you need to fucking change. You're the problem, you shits.