Quantexa

I joined Quantexa during the academy scheme. This was one of the first implementations of the scheme, so hiccups were to be expected. - The People are generally nice and helpful - There is a mentorship scheme, which is great - The office is nice and has free coffee - The CEO (Vish) is incredible: transparent, friendly, and of course extremely skillful. I believe in his plans for the company. - Great pension scheme and medical care (Originally, pre-existing medical conditions were not covered, but you can apply to have them covered). - WFH is allowed with no penalisation (project requirements affect this but you will not be asked in the office more than 3 times a week)

• Open plan office - on busy days, it's hard to get a seat. Can also be loud. - A lot of socials are drinks-based/ there is a drinking culture and if you're not extroverted you are often left out. General introvertedness/shyness is also penalised during performance reviews as it is often used to suggest lack of confidence. - Progression can be very hard and biased when you are low/mid level - senior people who have never met you have more say than your manager/client feedback! - Very poor communication from people team/PMO. You never know when your next project is or who it will be until the last second, even if it was 'confirmed' a couple of weeks beforehand. Emails end up ignored if you are junior and ask them any questions, and they only give info to your manager who then relays it to you. - For some this may be a pro, but for me it is a con: you may be shifting project/teams every 4 months which means you become a jack of all trades but a master of none. This is fine when you are junior, but in performance reviews they often require you to have experience with the full stack before promotion (despite current senior developers not having all of this experience either). - Opportunities to be part of a stable team are very rare.

• Please streamline communication from PMO/project allocators to the engineers!- Opportunities for engineers to stay on one project longer/deep dive into a specific technology (provided they have covered all base knowledge) would be great.
• Recognise that being introverted does not imply a lack of confidence or skill, particularly for employees from underrepresented groups who may face additional barriers.