eBay

You can learn a lot from working in the company.

No culture, there is no onboarding on anything, and you need to figure things out by yourself. If you don't perform as a robot, they will fire you without even giving a reason. Horrible experience, I was hoping to learn a lot from the team. I delivered on time (before sprints ended), and even today, I don't know the reason why they fired me. I'm assuming it was because I needed context into a ticket because no onboarding was done correctly for the vast codebase.

If you ask too many questions inside your team for clarification, it's a red flag. From my perspective, it's considered a bad thing that you ask questions to give the best results. Always do it by yourself and cross your fingers you are thinking the same as they are.

Let people ask questions; that's why teams exist. If someone is asking you for advice, it's not that the candidate is not performing well. It needs a correct onboarding session, code practices, and all the tools needed to solve subsequent problems without asking anything.

Finding excellence is not always the best path. You should seek people who are really curious and want to learn even more. That's how success is achieved.

I believe there is a massive breach in how the manager sees a programmer and how a programmer sees their day-to-day job. If the manager does not know anything about code, a simple "He is asking me this question" will trigger an alarm to the manager, leading to bad decisions earlier.

If no questions are asked for new people joining the team, there is no guarantee of the quality of the delivered results.

I believe that it is better to ask and do the job right the first time rather than doing something that is not on track with the standards.