A lot of smart people work here and you can learn a lot from them. Most are nice and approachable. Work life balance is ok.
The engineering problems are less exciting than you find at a tech company and the pay is average at best.
There's constant pressure to "make it work now" and management seems surprised when we end up with problems or move too slowly later. They don't seem interested in investing in good engineering but it's hard enough just keeping everything working let alone supporting new research.
1. Recruiter screening: This stage usually covers high-level questions about your background, past experience, general logistics (such as timeline and location preferences), and your motivation for applying—especially why you’re interested in Voleon.
I spoke to someone in the engineering team, who asked general programming questions (about multithreading basics, etc.) followed by a programming problem in a shared text editor. They decided not to continue to the next stage, without feedback as has
I applied via TripleByte so there's no technical phone interview; just a pitch phone call to know my background, and then there's the onsite. The onsite went just as others reported: 3~4 hour coding session on HackerRank in the morning, lunch time, a
1. Recruiter screening: This stage usually covers high-level questions about your background, past experience, general logistics (such as timeline and location preferences), and your motivation for applying—especially why you’re interested in Voleon.
I spoke to someone in the engineering team, who asked general programming questions (about multithreading basics, etc.) followed by a programming problem in a shared text editor. They decided not to continue to the next stage, without feedback as has
I applied via TripleByte so there's no technical phone interview; just a pitch phone call to know my background, and then there's the onsite. The onsite went just as others reported: 3~4 hour coding session on HackerRank in the morning, lunch time, a