Published on (UTC)
This post was submitted by a user and reflects their personal experience or opinion. The publication date is not an employment or interview date.
None
Be careful: while you are writing code, the PM may change the project process and the designer may change the designs without discussing or informing you.
After you report this to your manager and receive no response, you raise it again at the technical meeting. Once the project ends, you are directly put on a one-month improvement plan (what exactly are you supposed to improve? They say they will look at the quality of your code afterward?).
Then a senior engineer brings your manager into a meeting to criticize you, saying, “Their process and design changes didn’t prevent you from writing code, so what were you raising at the meeting?”
Then, when the project is rushed and there is only one day between acceptance and going live, the senior engineer throws over a piece of code and says, “Just solve it this way—it’s very simple. Do you even know how?” But when you run it, it does not meet the project’s requirements at all, and you also waste time explaining this to the senior engineer.