Good pay, talented & fun coworkers, flexible hours, work from home, and a wide selection of food trucks at lunchtime.
This was a developer position, and I barely got the opportunity to program. When I did, it was mind-numbingly trivial.
I worked in Retail Systems, and they are mostly bogged down in trouble tickets and constant feature requests from the business side, leaving little time to actually develop software. Furthermore, the paranoia about losing money leads to an aversion toward software change, which means the codebase is a monstrous pile of incremental changes accumulated over the years.
Almost no documentation, and I frequently would hear sentiments that documentation or comments would be a hindrance—since that would mean having to maintain the documentation or comments in parallel with the code (this might have just been a cultural aspect of my team).
There seems to be a revolving door for young developers, as well as people jumping around from team to team, so teams' know-how deteriorates to the point where there are large portions of code that no one is familiar with. And yet, you have to support that code when you are on-call.
If you aren't familiar with on-call, it means getting paged at any time of day when there are problems with the software. You might be thrown into a scenario where you are responsible for Amazon ordering being down, and the problem lies in your team's software, but you aren't familiar with that part of the code.
You will probably just have to relay this to your team members—which is fine—but needless to say, it is stressful.
I was promised to eventually get the chance to do some real software development, but perhaps not for a year or more. If you are in it for the long haul, maybe it could be okay. I didn't care about the money, and it didn't make it worth letting my career stagnate for 2-3 years, waiting until I was senior enough to do, maybe, have the chance to do some real work.
Slow down feature requests and realize that technical debt and software cruft are a serious detriment to the company's future. They drive away talent who would prefer to design and innovate in a way that would secure a better future for the company. Treat your employees better—the "customer obsession" and "frugality" mantras alienate employees to the point where they feel like customers come before them.
Round 1: OA. Cleared in November 2024. No word until February 2025 when I was told I was scheduled for interviews. A week later, they wrote back stating that email was sent "by mistake" and should not be considered. Another recruiter reached out in
Before being considered for an interview, you will need to pass an OA. The interview process will consist of three interviews. * The first interview had two coding questions. * The second interview included two behavioral questions and a LLD qu
The interview process is too lengthy. It includes an online assessment that lasts for 4 hours, followed by a panel round consisting of three back-to-back interviews: one for LeetCode, one for system design, and one behavioral interview. My interview
Round 1: OA. Cleared in November 2024. No word until February 2025 when I was told I was scheduled for interviews. A week later, they wrote back stating that email was sent "by mistake" and should not be considered. Another recruiter reached out in
Before being considered for an interview, you will need to pass an OA. The interview process will consist of three interviews. * The first interview had two coding questions. * The second interview included two behavioral questions and a LLD qu
The interview process is too lengthy. It includes an online assessment that lasts for 4 hours, followed by a panel round consisting of three back-to-back interviews: one for LeetCode, one for system design, and one behavioral interview. My interview