Flexible hours. Good perks, more or less.
Culture crash. Politics. Politics. Politics. Very few, if any at all, opportunities to grow technically. A conglomerate of brands with no focus whatsoever.
Get a grip. Figure out what the company is all about. If you need to clean things up, just do it. Don't leave people and teams hanging in the air.
Behavioral questions asked for scenarios on how to handle them, OOP, testing, DB, and some design questions were covered. There was also a lot of focus on behavior, for some reason. Overall, it was a good experience.
I had two phone screens, which were fairly simple. They asked questions such as: * What are the fundamentals of OOP? * What is the difference between OOP and scripting languages like PHP? Then, I went in for the on-site interview, which was all day
Just like other interviews for software positions, I was asked to code on paper to solve some common quizzes in algorithms and information retrieval. Except for that, some open questions were also asked. But none of them were very tough. If your work
Behavioral questions asked for scenarios on how to handle them, OOP, testing, DB, and some design questions were covered. There was also a lot of focus on behavior, for some reason. Overall, it was a good experience.
I had two phone screens, which were fairly simple. They asked questions such as: * What are the fundamentals of OOP? * What is the difference between OOP and scripting languages like PHP? Then, I went in for the on-site interview, which was all day
Just like other interviews for software positions, I was asked to code on paper to solve some common quizzes in algorithms and information retrieval. Except for that, some open questions were also asked. But none of them were very tough. If your work