I relatively worked for 20 years at Mathworks due to frustrating and tortuous work environment I had experienced in architecture and tooling team ( as per theory of relativity just like planet near Gargantua black hole in Interstellar ) even though I stayed for 2+ years there.
1. Exhausting interview process with several rounds on one day as if you will be building rocket next day..:)
2. Internal architectures tools used are mostly legacy tools sans some basic principles of Software Engineering. Also welcome to http era.
This makes learning curve and skills set very limited.
4. Reinventing the wheel practice followed often.
e.g Open source tools already available with developed features but not utilized there.
5. Be prepared for manual tasks in this era.
6. Bizarre decision of build failure investigation being done by RE which is normally the job responsibility of a developer ideally.
7. Extreme sycophancy and open favoritism - it's an open secret in the team with better synonyms.
8. Join the team only if you have gained superpower of premonition so that you can know when you are going to fall sick. Even if you have enough sick leaves but you are not supposed to avail those.
9. Once you have decided to switch, make sure to publish in newspapers whether you have offers or not. Be prepared for ridiculous questions like - Why did u take sick leave and internal training if you were planning to resign.
10. Unprofessional language used during mentoring and initial days of training.
Ultra micro-management throughout the year. You would receive a WhatsApp call -> call on phone -> followed by WhatsApp ping even if you have gone for tea/ snacks break in the evening irrespective of work to be done or not.
"Enemy of knowledge is not ignorance but illusion of knowledge" - Stephen Hawking.
If you are looking for a thrilling and chilling experience, then I would recommend to work in this tools team.
