People are awesome, pay is good, and benefits are great. The work is very interesting if you're ambitious enough to get into certain teams.
We can have too many meetings at times. I got put into QA when I first joined GM after we talked about data science my entire interview. I had to burn some bridges to get out of QA after six months.
Take the new employee's opinions into account when it comes to team placement.
Easygoing, laid-back process. They asked the typical questions, such as, "When have you been faced with a problem and how did you overcome it?"
Not exactly a standard interview. First, a phone screen with technical questions related to Java (dependency injection, mocking, etc.) and some SQL (inner/outer join), as well as a few design patterns. The on-site was scheduled a few days later and
The process took about three weeks. I got an interview at the career fair for my school and had the interview two days later on campus. It was thirty minutes and all behavioral so as long as you talk and answer their questions, it's fine. I got not
Easygoing, laid-back process. They asked the typical questions, such as, "When have you been faced with a problem and how did you overcome it?"
Not exactly a standard interview. First, a phone screen with technical questions related to Java (dependency injection, mocking, etc.) and some SQL (inner/outer join), as well as a few design patterns. The on-site was scheduled a few days later and
The process took about three weeks. I got an interview at the career fair for my school and had the interview two days later on campus. It was thirty minutes and all behavioral so as long as you talk and answer their questions, it's fine. I got not