They did a mob-programming session whilst I was there.
1:1 was also solid - this might be because I had a relatively good manager.
There were a couple of good senior engineers that will be fun to work with.
Some engineers will want to nitpick your PR to oblivion to show they know what they are doing, up to the point where they'd have to come back to apologize a couple of times for not reading what your actual PR does.
This turned into an exhausting cycle.
Not much advice, but if there was a way to handle PR vampires like the above, the teamwork would not feel like hell.
There were two engineers. It was a LeetCode problem, followed by a questions and answer session on scalability and security. LeetCode-style coding problem (live coding, algorithm/data structures). Q&A discussion focused on scalability and security
Interview based on many technical terms, however, the interviewer conducted it very well.
The interview process involves several stages: * HR interview * Take-home (8-hour) coding assignment * Leadership skills-focused interview * Pairing with two developers * Technical interview * Team interview * Manager interview * Dep
There were two engineers. It was a LeetCode problem, followed by a questions and answer session on scalability and security. LeetCode-style coding problem (live coding, algorithm/data structures). Q&A discussion focused on scalability and security
Interview based on many technical terms, however, the interviewer conducted it very well.
The interview process involves several stages: * HR interview * Take-home (8-hour) coding assignment * Leadership skills-focused interview * Pairing with two developers * Technical interview * Team interview * Manager interview * Dep