Good pay. Great benefits. Yearly events at nice locations = fantastic perk.
The company vision is compelling. A technologist can be happy here if not invested in the things they're building + accept that they serve ever changing needs of researchers.
Many mediocre and even bad people.
Legacy code is embarrassing, demonstrating tolerance for low quality.
Trade off is intentional - some people/locations are cheaper.
Research pulls in all directions, but no one prioritizes because they're afraid to say "no".
This adds to low quality - people get pulled off one thing and onto another before done, which sends message - quality doesn't matter.
Also, the company is ultra-remote - not easy to deal with.
Time zones 12 hours different from your own.
Collaboration very challenging and sometimes large delays in projects.
There's a huge opportunity to build a high-quality, scalable platform for doing research and running alphas, but the platform layer isn't there.
Hire better people and fire mediocre/bad people.
Invest more resources and attention in the platform layer.
Or keep going as you are.
You won't be able to hire the best because it's too frustrating to work there.
Spoke with a few of their team members. Was quizzed on trading market knowledge and technical skills. Overall a positive experience. I think they really want someone with lots of industry experience.
phone interview with an engineer- directly began with questions - asked from many fields:pl, data structures, probability, linux etc.
The interview started with a phone round. It was basic things, like what you are looking for when you review a merge request, where you can put finals, mutable and immutable etc... After that round the next was an in person one. 45 minute with the ma
Spoke with a few of their team members. Was quizzed on trading market knowledge and technical skills. Overall a positive experience. I think they really want someone with lots of industry experience.
phone interview with an engineer- directly began with questions - asked from many fields:pl, data structures, probability, linux etc.
The interview started with a phone round. It was basic things, like what you are looking for when you review a merge request, where you can put finals, mutable and immutable etc... After that round the next was an in person one. 45 minute with the ma