Most architecture or technology decisions are political, with no technical justification.
The general level of knowledge tends to be low, with little experience or desire to learn new things.
The culture can be quite toxic, depending on the team.
We have to go to the office 3 days a week, they want to go back to 5 days eventually.
Human resources decisions are made based on the labor market and attrition rates, employee feedback is not taken into account.
It started with two 45-minute technical rounds. The first one was a pair programming session, and the second one was a technical discussion on systems design. Afterwards, I was forwarded to a 30-minute behavioral round. After all that and a few follo
Don't waste your time. I had a call with the recruiter, a call with the VP of technology, and they sent me a challenge. Then I had a group interview with a team (without warning that it would be with so many people). I applied knowing they were askin
It was nice and straightforward. I only had two stages. The first one was an explanation about the team and my job inside the company, and later the second interview was a technical test with questions and a little coding test.
It started with two 45-minute technical rounds. The first one was a pair programming session, and the second one was a technical discussion on systems design. Afterwards, I was forwarded to a 30-minute behavioral round. After all that and a few follo
Don't waste your time. I had a call with the recruiter, a call with the VP of technology, and they sent me a challenge. Then I had a group interview with a team (without warning that it would be with so many people). I applied knowing they were askin
It was nice and straightforward. I only had two stages. The first one was an explanation about the team and my job inside the company, and later the second interview was a technical test with questions and a little coding test.