Think Twice Before Joining – This Could Set Your Career Back by Years - Associate Software Engineer RoboMQ Employee Review

I am writing this review because I wish someone had warned me before I joined. What I experienced was not just disappointing — it was genuinely damaging to my career, my confidence, and my mental health. If you are reading this while considering an offer, please read every word carefully. The Positive Reviews Are Misleading Do not let the high ratings fool you. Before joining, I made the mistake of trusting the glowing reviews without digging deeper. Speak to former employees. Speak to people who have actually spent significant time inside the organization. The reality is drastically different from what is presented on the surface. Many positive reviews come from people who either had a very short stint or had not yet seen the full picture. You Will Not Learn. You Will Survive. If you are joining as a fresher hoping to build real skills, develop engineering discipline, or learn industry best practices — stop. That is not what happens here. What actually happens is that you are thrown into a system so poorly maintained, so poorly documented, and so structurally broken that most of your time is spent simply trying to understand what already exists — not building anything meaningful. The codebase is a nightmare. Functions stretching thousands of lines. Zero meaningful documentation. Layers of technical debt that nobody fully understands. Even experienced engineers visibly struggle. For a fresher, this is not a learning environment — it is a trap. You will leave knowing less about good engineering than when you arrived, because everything you absorb here teaches you the wrong way to build software. You Can Be Let Go Without Warning — Even After Being Told You're Doing Well This is the part that should genuinely frighten you. Imagine completing your internship. Receiving positive feedback in every review cycle. Being extended a full-time offer. Feeling secure. Working hard for months more — and then suddenly being asked to leave. No clear reason. No warning signs. Nothing that aligns with the feedback you had been receiving. This happened. And it raises a deeply disturbing question: what does success even mean here? If clearing interviews, completing milestones, receiving positive evaluations, and being offered a full-time role still does not protect you — then there are no rules. You are never safe. You are always disposable. For fresh graduates, this is not just an inconvenience. This is a crisis. By the time you are let go, your college placement window has closed. The campus support system is gone. The off-campus market is brutal. You are left — after months of hard work and sacrifice — starting from zero, with uncertainty eating into your confidence every single day. There Is No Work-Life Balance. There Is Only Work. Let me be direct: there is no work-life balance here. None. Official working hours exist on paper. In practice, they are meaningless. Staying late is not occasional — it is the norm. It is expected. It is silently demanded. Leaving on time is noticed. Boundaries are not respected. Your evenings, your weekends, your personal time — all of it quietly becomes the company's time. There is zero flexibility. deadlines themselves are the problem. Teams are regularly pushed to deliver within timelines that completely ignore the complexity of the system, the state of the codebase, and the sheer volume of unknowns involved. The pressure is relentless. Stress becomes your baseline. Burnout is not a risk — it is a destination. Management Does Not Listen Raise a technical concern? Suggest a better approach? Propose something that might improve quality or reduce long-term pain? Do not expect it to be taken seriously. Delivery speed matters. Everything else is noise. Long-term thinking is not rewarded here. Quick outputs are — regardless of whether they are built on a foundation that will collapse in six months. Requirements are frequently unclear, and nobody owns them. Developers spend an absurd amount of time chasing multiple teams just to understand what they are supposed to build — let alone why. The resulting confusion, delays, and rework are then somehow treated as developer failure. Accountability Only Flows Downward When something goes well, credit quietly disappears upward. When something goes wrong, blame lands squarely on the individual contributor. In an environment with poor documentation, shifting requirements, and an unstable codebase, this is not just unfair — it is demoralizing. People stop taking initiative. People stop caring. And then they leave — or are asked to leave before they can. For Experienced Engineers If you value clean architecture, thoughtful design, mentorship, documentation, or collaborative decision-making — this is not your place. You will spend your time fighting fires in a system that was never built to last, under management that does not prioritize the things that make engineering sustainable. My Final Advice To candidates: a higher salary package can look exciting. But ask yourself what you are actually buying with that salary. If the answer is stress, instability, zero flexibility, no work-life balance, and a genuine risk of losing your job despite doing everything right — is it worth it? Talk to people who have left. Ask the hard questions about retention, about real working hours, about how evaluations actually work. Do not sign an offer based on surface-level impressions. To management: the way people are treated here — especially fresh graduates at the start of their careers — has consequences that extend far beyond a resignation or a termination. You are not just losing employees. You are leaving lasting damage on people who trusted you with the beginning of their professional lives