Pros
Fully remote work setup
Good Salary.
Cons
1. Design and Product Process Issues
• The environment is engineering-led, leaving little room for design thinking.
• Requirements are often unclear, and change multiple times during execution.
• Design suggestions are frequently overridden without discussion or rationale.
• Visibility is valued over output — people who talk more are assumed to work more.
2. Micromanagement
• Instead of trusting skilled people, work is monitored through time breakdowns, constant updates, and follow-up messages.
• Even tasks labeled as “minor” are expected to be done instantly without context or sane timelines.
3. Developer Pain Points (Consistent and Repeated Across Teams)
• Last-minute changes are extremely common, often during or right before sprint end.
• No proper planning before development starts. Developers are asked to “figure things out as they go.”
• Backend and frontend often work without aligned documentation, leading to rework.
• Teams are pressured to deliver first, and asked to “fix later.”
• Engineers are frequently pulled into unrelated tasks due to lack of role clarity.
• If timelines slip because requirements weren’t clear — the blame shifts to the developer.
• On-call hours extend beyond normal work time without acknowledgement.
4. Culture & Communication
• Internal communication often includes casual disrespect and mocking, which may seem normal to some, but it creates an environment where people hesitate to speak up.
• Jokes are prioritized over professionalism in serious discussions.
• Favoritism exists — a small inner circle gets support, others are sidelined.
5. Employee Exit Process
• Handovers and knowledge transfers are expected to be handled at the last minute.
• Communication about exit responsibilities is vague, but expectations are strict afterward.
• The organization expects employees to be fully cooperative, but does not reciprocate the same respect during the exit.