Growing network load. Growing staff. Amazingly effed up technologies that you'll never guess could work. Easy to make 10x difference to random processes. Extreme troubleshooting culture, good for true full-stack troubleshooters. Very good people to work with. Great work-life balance (lots of kids on site during spring vacation; no eyebrows raised; working remotely post-school hours is common).
High management is non-technical and doesn't stay too long, so lots of money/human lives are poured into "projects" that never could succeed, while the essential work of paying off technical debt and scaling the system for each year's new internet customers is done in the shadows by grumpy people that get poor reviews.
Realize that despite the organic growth from the transition to a fully digital economy, our particular organization is cost-dominated by legacy code. Finishing projects to delete components/code, fixing bugs, and making code and systems more readable and transparent will have an ROI that grows exponentially year over year.
Also, try to listen a bit more to the people that say "no" than to the eager beavers that only say yes and then completely screw up working systems in the pursuit of some shiny new technology, which they will abandon after it becomes legacy whilst only taking 5% of traffic.
System Design Round with HLD and further discussions. The interviewer was a senior architect and had high expectations for the internals of the components. If I can assess the round, it was not a HLD but rather went too deep into traffic management
It is not very complex. Have good knowledge in datastructures and algorithms, and it will work. Have good knowledge in: * Time-intervals * Trees * Sort functions * Architecture Learn PayPal principles.
The recruiter reached out to me and told me they use Karat for the screening, and honestly, I have never liked Karat. But I went through the interview. The first 20 minutes consisted of five system design questions where you just had to speak. The l
System Design Round with HLD and further discussions. The interviewer was a senior architect and had high expectations for the internals of the components. If I can assess the round, it was not a HLD but rather went too deep into traffic management
It is not very complex. Have good knowledge in datastructures and algorithms, and it will work. Have good knowledge in: * Time-intervals * Trees * Sort functions * Architecture Learn PayPal principles.
The recruiter reached out to me and told me they use Karat for the screening, and honestly, I have never liked Karat. But I went through the interview. The first 20 minutes consisted of five system design questions where you just had to speak. The l