> It would have been fun, and productive
How do you know this? The signal of them dumping you with some leetcode should be an indication that it wasn't meant to be?
How do you know this? The signal of them dumping you with some leetcode should be an indication that it wasn't meant to be?
My prior company would have interns do leetcode and system design. Intermediates and up had some paired code writing and a far less formal system design discussion.
Most of the team might have been hired through a network and you only get leetcoded as an external unknown.
The HR person was a complete dolt though, and didnt even understand how to interview me properly...
Sucks - I still respect the company, but their recruiting method was piss-poor..
But a new engineer was assigned to handle interviewing and it was all about a couple of leetcode problems he found on the internet.
The job description was top notch. It was a clear description of what they needed this engineering role to do. Inspire of it being a bit of a niche, I had almost perfect set of experiences from my prior jobs that made it very interesting.
Fun because it would have given me an opportunity to _improve_ upon my already bootstrapped skills. Productive because, I already have a head start than another engineer getting into the groove of things. This is HN, I can be tech specific :-) I have worked a lot on performance from HPC perspective. The job was at a High Frequency Trading platform that needed a sys.engineer who would work on extracting performance with things like pinning a CPU core to a process and several optimisations at the OS and kernel that would shave off a few milliseconds in an already fast application.