J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez iStreamPlanet (Seattle, WA) en juil. 2019
Entretien
Started with an initial phone screen with a recruiter. Then an hour technical interview that involved pair programming and some larger questions about my background.
On-site interview was a series of 1 hour sessions:
- whiteboarding - this was a typical algorithm problem with opportunities to reuse code
- cultural chat - this was a friendly but actually pretty grilling session about things such as handling adversity in the workplace
- system design - a typical open ended system design problem
- questions - an open ended session to learn more about the company
J'ai postulé via une agence de recrutement. Le processus a pris 4 semaines. J'ai passé un entretien chez iStreamPlanet (Seattle, WA) en août 2018
Entretien
Had a telephonic round with the Principal Engineer followed by 4 rounds onsite.
Was offered significantly less salary than what I quoted and a lesser role inspite of doing well in interviews. Don't waste your time here if you're looking for a decent salary.
Questions d'entretien [2]
Question 1
White board discussion on designing a url shortner.
J'ai postulé via une agence de recrutement. Le processus a pris 2 semaines. J'ai passé un entretien chez iStreamPlanet (Seattle, WA) en févr. 2016
Entretien
A 1-hour phone screening (live coding) followed by an on-site full loop which includes 5 rounds of technique questions (1 behavior and 4 coding on white board). If you're well prepared, these questions are small piece of cake.
Questions d'entretien [1]
Question 1
Give an API: int read4(char *buf) which reads 4 characters at a time from a file. The return value is the actual number of characters read.
For example, it returns 3 if there is only 3 characters left in the file.
By using the read4 API, implement the function int read(char *buf, int n) that reads n characters from the file.
