I was lucky to hold an SDE position in the Infrastructure department of Blumberg R&D in the NY office.
Not much to complain about: a lot of smart, experienced people, interesting technologies, and challenging tasks. My management was OK with flexible work hours and working from home once in a while.
Compensation is relatively generous, and the performance review is not very formalized: if your management feels like giving you a raise, they don't have to jump through a lot of hoops to justify it to their management.
Pace is crazy, release schedules are tough.
Long hours are normal and expected; everyone in the company works like this.
Software development processes are not aligned across different teams, so you can get into a situation where you're assigned to a project grown up from a prototype with no infrastructure around it.
One thing you'll run into immediately: a lot of legacy code, sometimes pretty old. A bunch of old proprietary technologies are still in use, and you'll have to deal with it. Though the process of migration to newer technologies is slow but steady.
Compensation is lower than in banks on Manhattan.
If you quit your job not because of family reasons, you'll not be hired back ever. Keep that in mind.
The situation in the R&D Infrastructure group is good. Kudos to Infrastructure management. It would be nice to spread their practices to other R&D groups.
The first conversation was with an internal recruiter. The next one was a coding interview. The coding exercise involved one of the team members. They presented the first exercise, and after it was completed, the second exercise was presented. You h
Good interview process. Interview questions are very relevant to the role. Coding is a very big part of the interview, irrespective of the team. System design questions are more relevant and team-based.
The interview was pretty straightforward, but they demanded more accurate answers. I was contacted by a recruiter and opted for an interview two months later in order to prepare. I bombed the online assessment.
The first conversation was with an internal recruiter. The next one was a coding interview. The coding exercise involved one of the team members. They presented the first exercise, and after it was completed, the second exercise was presented. You h
Good interview process. Interview questions are very relevant to the role. Coding is a very big part of the interview, irrespective of the team. System design questions are more relevant and team-based.
The interview was pretty straightforward, but they demanded more accurate answers. I was contacted by a recruiter and opted for an interview two months later in order to prepare. I bombed the online assessment.