Decent salary, comparing to the market. Lot of written documentation. Not many meetings.
One big technical debt.
People without energy, without initiative.
The most exciting part of the job is the half-year self-assessment.
Hard to force yourself to do something, and if you try, then it's hard to have fun with your work when your code compiles in 10 minutes, then starts in 10 minutes, only to crash. You're never sure if it's your fault or a flaky environment.
Stop forcing people to fill in APEX, and start giving incentives to have fun with coding.
There were 5 interviews: pair programming on data structure and code structure, one system design, one manager interview, and one values interview. Each interview was about an hour long, and each was with only one person. All interviewers were very
I specifically asked the recruiter in the sync-up before my final round if the coding challenge would be a LeetCode-style question. He said no; it would be a "real-world situation." I showed up and was asked a tagged question straight off LeetCode,
I participated in two code interviews, which asked me to find solutions for certain scenarios. There would have been at least another interview about system design, but I failed before that.
There were 5 interviews: pair programming on data structure and code structure, one system design, one manager interview, and one values interview. Each interview was about an hour long, and each was with only one person. All interviewers were very
I specifically asked the recruiter in the sync-up before my final round if the coding challenge would be a LeetCode-style question. He said no; it would be a "real-world situation." I showed up and was asked a tagged question straight off LeetCode,
I participated in two code interviews, which asked me to find solutions for certain scenarios. There would have been at least another interview about system design, but I failed before that.