There is a lot of unclarity with respect to goals in the team. No one seems to know anything about the project and I find myself stumbling in the dark many times. There is not a lot of coding, but my team leads(are new) seem to over-engineer and find unnecessary problems in my code reviews, code that I see exist in other parts of the app too. I don't get much feedback from my manager in 1 on 1 except I need to complete certain X tasks a sprint, but I see not much appreciation. I have been told that any promotion will be based on my team mates feedback. I work reasonably hard, document aggressively but tend to get blocked often on external communications or knowledge or pending and late-coming code reviews. I like a more dynamic environment where there is emphasis on getting work done rather than over-engineering everything. Am I a likely contender to being PIPed? when would I know, after performance reviews? I have not met the people my promotion depends on, I don't think they like me much. I am wondering if I should start preparing for a job change/team change. Quite low on inspiration. New ICT3 at Apple(a few months in)
Ok Sorry, then I read you were just few months in. Ahh this is normal for starting new especially now as we all are less face to face. Give at least 6-8 months, you have insecurity and seems you do not like the job. Talk to your manager and colleagues, give them a hint. Ask them how you can help more. If still have issues abandon ship. I recommend talk ASAP as I have seen someone in same situation getting PIPed at Amazon just in 3 months 🤧
At Apple folks are encouraged to take ownership of their stuff eg. If you are blocked on external dependency talk to the person directly, if no response ask your team lead or EPM to push the person. Nobody will do it for you if you never ask. If code review is taking too much time just message the folks asking to prioritize it. Also always listen to what your team lead has to say, he is the team lead for a reason. Discuss specific scenarios if you think his approach is not optimal. Attention to detail is what makes Apple “Apple”. Just because similar or same code is already present in the codebase, does not mean its correct or optimal. As you spend more time in the team your coding will be close to what the team or reviewers expect and so you will actually start spending time on building more stuff. Give it some time, right now learn and keep an open mind.
Start Preparing ASAP. PIP coming on the way. Have exit plan. Be Careful.
Is there anything I can do to save my situation? When do they inform about PIP?
Dude, you are safe... that’s how it is in most of Apple. They only PIP if you are a hindrance to people or have some other major red flags. That fortinet guy is taking out of his a**.