Great people to work with and a lot of collaboration amongst teams.
Too big to be agile.
Differing ideas of direction moving forward.
Remove some levels - too many Chiefs
Was invited to on-site interview by a recruiter. Got a paper exam on-site. I received an exam with no coding questions, only ordinary object-oriented definition questions. Was asked about common data structures and design patterns. Included also theo
Telling about myself, my past, and asking some technical questions. I started talking about my previous company experience, what languages I used, and what environments and protocols I employed in my work at each place I was employed.
The interview was based completely on the resume. Each and everything on the resume is important. If you are confident enough with your answers, there is a great chance that they'll hire you.
Was invited to on-site interview by a recruiter. Got a paper exam on-site. I received an exam with no coding questions, only ordinary object-oriented definition questions. Was asked about common data structures and design patterns. Included also theo
Telling about myself, my past, and asking some technical questions. I started talking about my previous company experience, what languages I used, and what environments and protocols I employed in my work at each place I was employed.
The interview was based completely on the resume. Each and everything on the resume is important. If you are confident enough with your answers, there is a great chance that they'll hire you.