Decisions can be made without too much reasoning behind them. Too many useless acronyms are used to describe simple things. Simple things like project names or epics have different names depending on which team you talk to. Compensation is not competitive. Benefits are mediocre, with suboptimal health/dental coverage and low percentage success sharing. All teams are basically forced to stick to Java/Spring when developing new apps.
Phone interview, then you come in for a few hours to see if you're a right fit for the team. If they like you, they'll vouch for you and you're in.
The first step was a phone interview. After a week, I went to have an on-site interview. It was a group interview, which had two parts. The first was about the UML diagram. The second was about scrambled codes.
Was reached out by a recruiter on LinkedIn for an Android Engineer remote position. The recruiter was super, super nice and very responsive. First call was with the recruiter, making sure I met the minimum requirements. Second call was with two of
Phone interview, then you come in for a few hours to see if you're a right fit for the team. If they like you, they'll vouch for you and you're in.
The first step was a phone interview. After a week, I went to have an on-site interview. It was a group interview, which had two parts. The first was about the UML diagram. The second was about scrambled codes.
Was reached out by a recruiter on LinkedIn for an Android Engineer remote position. The recruiter was super, super nice and very responsive. First call was with the recruiter, making sure I met the minimum requirements. Second call was with two of