Solicité el puesto a través de un captador. El proceso duró 6 semanas. Acudí a una entrevista en Box (Redwood City, CA) en sept 2016
Entrevista
Recruiter contacted me on LinkedIn.
Process took around 6 weeks.
Be well prepared with algorithms and overall coding in your favorite language. Basic data structures and algorithms which are most useful (at least for this interview) were stack and hash table.
Secondly make sure that you understand the role they are hiring for. Talk about how that interests you and what value can you add.
Overall interviewers were very good. Make sure that you keep talking (loud thinking). Take appropriate hints from interviewers.
Preguntas de entrevista [1]
Pregunta 1
1) Phone screen - basic intro and a coding exercise.
2) Onsite day 1 -
a) 1hr Design interview
b) 1hr Technical discussion
c) Lunch with manager
c) 2 hour coding exercise on my laptop
d) 1 hr technical discussion on past projects
2) Onsite day 2 -
a) 1 hr behavioral etc. with VP
b) 1 hr behavioral etc. with manager
One of worst interviews I had. They neglected me only based on coding interview. No discussion, no Q&A, no system design interview, no "soft" questions, just plain coding interview which is far from accurate and fair evaluation of candidate.
Preguntas de entrevista [1]
Pregunta 1
The coding task is about reading numbers from a CSV file, computing a rolling window statistics (average and maximum) over those numbers, and printing current statistics at every time step. It should be done in O(nlogn) time. To do it data structures like (in Java) TreeMap or PriorityQueue come handy. Unfortunately there's little time to do it (slightly more than an hour). Although I had idea how to do it, I stressed out and I failed to meet the O(nlogn) time in all cases, and only based on it I was rejected.
Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Box (Redwood City, CA) en may 2022
Entrevista
1 Hour Technical Screening followed by an on-site interview consisting of multiple interviews over the course of an afternoon. These interviews were a mixture of technical coding tests, architecture, and behavioral interviews.
Preguntas de entrevista [1]
Pregunta 1
I can't discuss details but they were pretty standard leetcode/hackerrank style questions, a long coding challenge, and coding questions that were specific to the job.
Solicité el puesto en persona. Acudí a una entrevista en Box (Redwood City, CA) en feb 2020
Entrevista
Recruiter reached out based on my online profile and setup a technical phone screen. They obviously know what my background is and the skillset I bring to the table.
Phone screen setup relatively quickly and the interviewers seemed friendly and nice to talk to. 3 coding interview Qs of increasing difficulty level. Wrote code on coderpad for all 3 in the alloted time, walked through testcases and interviewers agreed on the solution and correctness.
2 days later get a cold rejection e-mail indicating my background does not fit the requirement.
Duh !! What a waste of time and effort...
Preguntas de entrevista [1]
Pregunta 1
Bit manipulation, pagehit counter and some Qs to return topK integers in files in a directory.
