Good work-life balance. Good pay.
Highly unpredictable. Very dependent on the housing market to be good.
Usual Software Engineering interview process. First, I had a call with a recruiter to discuss roles. 1 telephonic round. LC question. It was not straightforward; it was not an usual array or tree question. Basic data structure concepts had to be ap
The recruiter contacted me and discussed the available positions. A 1-hour technical phone screen was scheduled. This was followed by a full day of onsite interviews at SF headquarters. There were 4 rounds of interviews plus 1 lunch interview.
The recruiter was very nice and to the point. They set up the phone interview quickly. After asking typical questions about my background, they gave me a question that was rated as hard in LeetCode. (I looked it up after the interview.) There was no
Usual Software Engineering interview process. First, I had a call with a recruiter to discuss roles. 1 telephonic round. LC question. It was not straightforward; it was not an usual array or tree question. Basic data structure concepts had to be ap
The recruiter contacted me and discussed the available positions. A 1-hour technical phone screen was scheduled. This was followed by a full day of onsite interviews at SF headquarters. There were 4 rounds of interviews plus 1 lunch interview.
The recruiter was very nice and to the point. They set up the phone interview quickly. After asking typical questions about my background, they gave me a question that was rated as hard in LeetCode. (I looked it up after the interview.) There was no