Very talented people. Interesting projects with a significant research component. Products have an impact. Good perks and a pleasant work environment (most people have offices, not cubes).
Limited opportunity for advancement.
Best teams don't necessarily get needed resources.
"Not invented here" syndrome, tendency to reinvent the wheel.
Offer a clearer path for career development. Increase developer interaction with the larger community in their fields. Prune priorities to achieve better focus and results for the real priorities.
Phone interview with HR. No technical questions were asked. I was asked to describe one of my projects, followed by some behavioral questions. It was not a difficult interview, lasting around 15 minutes in total.
Got a call from MathWorks. They told me about the position and asked what I knew about the company from the career fair. They were happy with my response and asked if I had any questions. They then scheduled a technical phone interview. Overall, it w
The first phase was a general screening, which took about 10-15 minutes. The second phase was a basic programming level test, lasting approximately 90 minutes. As long as you possess fundamental programming knowledge, you will be fine. The third ph
Phone interview with HR. No technical questions were asked. I was asked to describe one of my projects, followed by some behavioral questions. It was not a difficult interview, lasting around 15 minutes in total.
Got a call from MathWorks. They told me about the position and asked what I knew about the company from the career fair. They were happy with my response and asked if I had any questions. They then scheduled a technical phone interview. Overall, it w
The first phase was a general screening, which took about 10-15 minutes. The second phase was a basic programming level test, lasting approximately 90 minutes. As long as you possess fundamental programming knowledge, you will be fine. The third ph