New London office is very nice.
Good management: My team lead, manager, manager^2, and manager^3 are all excellent. They're enthusiastic, know the product, and have programming backgrounds. I'm confident about the direction they're leading my team in and the work we're doing, and they're invested in cleaning up the tech debt created by previous management. They also know and care about the team, each of them knowing me, my skills, shortcomings, and desires. My team lead especially has pushed to give me opportunities to advance and have a greater positive impact at Bloomberg.
Good compensation.
Legacy tech stack. We're working on cleaning this up, but in the area I work, there's a considerable amount of C and Fortran code. Most of it is quite nasty. C is converted to C++ when we touch it, and Fortran is 99% just being read to debug a problem and not modified. I have had to change it a few times though in the last 12 months.
Long hours. 8-6 are the contracted hours, but I work more like 8:30-6. My manager is explicitly not fussed about what time you arrive or leave, as long as you get your work done. I'd rather work 9-5, but I'm paid enough to live with it.
Hold course. We're moving in the right direction, and I think things will keep getting better.
It was a very candidate-friendly interview process, with flexible on-site dates. Amazingly quick feedback. Overall, a great experience. * Technical phone screen with an engineer (2 simple/average coding questions) * On-site (technical and beha
I applied online through my school's job portal. A couple months later, I received an email asking for a phone interview. My first interview was cancelled, so I then had to reschedule for a couple of weeks later. The interview was 45 minutes long an
The interview process consisted of 3 rounds. The first round involved talking with 2 people separately. One person asked general questions, while the other asked several programming questions, such as string inversion. In the second round, I spoke
It was a very candidate-friendly interview process, with flexible on-site dates. Amazingly quick feedback. Overall, a great experience. * Technical phone screen with an engineer (2 simple/average coding questions) * On-site (technical and beha
I applied online through my school's job portal. A couple months later, I received an email asking for a phone interview. My first interview was cancelled, so I then had to reschedule for a couple of weeks later. The interview was 45 minutes long an
The interview process consisted of 3 rounds. The first round involved talking with 2 people separately. One person asked general questions, while the other asked several programming questions, such as string inversion. In the second round, I spoke