Pros
Opportunity to work in Robotics and solve complex problems. Huge chunk of work to be done and be proud. A small company that could have been fast-paced.
Cons
I worked for Eiratech Robotics for two months, and it was horrible. Instead of trapping myself "just for CV," I decided to leave them as soon as possible and forget as a nightmare. Here, I write only about their RMS software team and the management above. I apologize to very few hard-working individuals for writing this review. But I have to reveal the truth to cause changes or help applicants to make a choice. RMS team is stagnant, and the management doesn't welcome anything to improve the situation. The software is of poor quality. The implemented algorithms are elementary. Unfortunately, it is simply too slow and unreliable. Frequent incidents at customer sites and no work is done to systemize and prevent them from happening again. The infrastructure has zero automatization. The building system is fragile and module dependencies are not managed. There are persistent problems with reproducing problems and having conflicting versions in production builds. I tried to approach the problems above with working solutions, but the management didn't want to listen, answering profanity and giving no technical feedback. Right, you come with an idea and/or a solution for a problem to discuss; you get irrelevant feedback and personal attacks. The CTO turned out to be a good talker. But talk is cheap. I didn't notice iterations towards an improved environment where the product could become more reliable and actually smart, and the development process more qualitative and predictable. Moreover, I found him surprisingly disconnected from the software engineering world. Instead, he was consistently telling me about titles emphasizing the hierarchy. I thought leaders don't need titles. Once, nit-peeking on my conversations was so ludicrous and surreal I had an epileptic seizure triggered during a meeting. My last drop became when a critical problem in the network layer leading to a messages loss didn't get attention, and my fix wasn't accepted: there was no technical feedback on it. It is hard to believe, but I was told to wait for the problem to encounter in production. Any qualified software engineer knows how difficult it can be to debug such issues. You can guess already deadlines are failing in such conditions. Sprints are very sporadic and slow. Some management tends to go on long unannounced 'holydays.' Micromanagement is so ridiculously high that you are not trusted to make any decisions.
