Pay was lower than the industry standard (around 2019), but the benefits were great.
Awesome PTO, health benefits, and work-life balance were great.
I ended up switching industries and falling into another line of work, and I miss SAP constantly. Looking back, the benefits generally outweighed the cons.
The code was a mess. Communication between teams was a bit disorganized, but that’s a bit expected with companies so large.
Promotions were based on tenure and not how successful you were at your job.
Diversity wasn’t great. I won’t go into it more, but the dev team could afford to see a bit more variety with who they hire.
Don’t base a developer’s productivity on lines of code.
Offer clear paths to promotion and don’t just base it off of tenure.
Easy/medium LeetCode problems. The interview process was smooth. The focus is more on how you approach the problem rather than a specific language. There were a total of 3 rounds: * Two coding rounds * One managerial round
It was good. I was asked OOP in depth. I had two rounds of technical interviews before rejection. As I was working on a Java-based project, I was asked Java in depth.
Round 1: Online Assignment Round 2: Completely based on React.js, as two of my projects are based on React. Round 3: Questions based on all four projects. Round 4: Hiring Manager round. Asked about the college final project. Round 5: Normal HR ro
Easy/medium LeetCode problems. The interview process was smooth. The focus is more on how you approach the problem rather than a specific language. There were a total of 3 rounds: * Two coding rounds * One managerial round
It was good. I was asked OOP in depth. I had two rounds of technical interviews before rejection. As I was working on a Java-based project, I was asked Java in depth.
Round 1: Online Assignment Round 2: Completely based on React.js, as two of my projects are based on React. Round 3: Questions based on all four projects. Round 4: Hiring Manager round. Asked about the college final project. Round 5: Normal HR ro