• Continuously updating their tech stacks to stay competitive. • Their products are well-maintained and secure. • Their coding standards and best practices are revised regularly. • Great benefits.
• Very easy to burn out here.
• I was approaching burnout, so I brought it up to my manager. I told them I was fried and really needed help, and then… nothing. I brought it up again, and… nothing. Eventually, I was written up for underperforming. I don't quite understand how it worked out that way.
• Communication.
• Management's attention on their team is generally poor. Instead, they focus on keeping their manager(s) happy. Basically, it's backwards.
Listen to your team members and then follow through. Get action items put together specifically for that team member approaching burnout or whatever, and help them get what they need instead of reprimanding them.
Reached out by a recruiter on LinkedIn. It was a standard recruiter call. After that, there was a phone screen. The phone screen consisted of two medium LeetCode questions. I was unprepared as I thought there would only be one. It seems like there
This is the worst company I've ever interviewed with. I cleared the OA with 100% test cases passing for both coding questions. The recruiter said they would be moving forward and scheduling the onsite. After two days, instead of getting the onsite i
The interview process involved a standard tech screen call. This was followed by a LeetCode-style question. After that, there were two technical interviews focusing on designing an efficient algorithm and writing maintainable code. The design inte
Reached out by a recruiter on LinkedIn. It was a standard recruiter call. After that, there was a phone screen. The phone screen consisted of two medium LeetCode questions. I was unprepared as I thought there would only be one. It seems like there
This is the worst company I've ever interviewed with. I cleared the OA with 100% test cases passing for both coding questions. The recruiter said they would be moving forward and scheduling the onsite. After two days, instead of getting the onsite i
The interview process involved a standard tech screen call. This was followed by a LeetCode-style question. After that, there were two technical interviews focusing on designing an efficient algorithm and writing maintainable code. The design inte