Fui entrevistado pela Outreach (Seattle, WA) em nov. de 2017
Entrevista
Typical recruiter screen then followed by a remote online technical interview.
I was interviewed by a senior engineer on the backend team. Unfortunately, the senior engineer lacked interviewing experience and technical expertise. He would communicate he was not looking for certain things, then down the road ask why it isn't there.
Interviewer didn't have very strong technical expertise. He looked at the solution, and said I don't think it works. When we ran the code and it worked he was really surprised. Interviewer also did not understand runtime. He asked how to optimize an O(n) runtime for a question that cannot optimize to O(log n) / O(1).
Furthermore, interviewer was not prepared to clarify problem. For example, when asked about whether he would like to prioritize the distribution of jobs, he stumbled and was not sure how to answer it.
Overall, I am not sure why this engineer was doing the screen when he lacked the correct experience to do this screen and evaluate the candidate.
11
Outras avaliações de entrevista de vagas de Senior Backend Software Engineer da empresa Outreach
Candidatei-me online. Fui entrevistado pela Outreach (Seattle, WA) em dez. de 2017
Entrevista
Was contacted by Recruiter - Had a nice 30 minutes chat with a recruiter and he scheduled a phone screen.
Phone Screen
20 Minutes Behavioral
40 Minutes Coding based
After few days, I got a rejection email.
Perguntas de entrevista [1]
Pergunta 1
Behavioral
Why outreach
The impact you hope to have from your next role?What is most important factor in your career/job
What do you think about RSpec? How do you compare it with other frameworks
What was the hardest/Challenging technical problem you faced and how did you resolve it
Coding
This problem concerns finding a time when we can do daily recurring maintenance on a server. You are to write a function that is given the following information:
List of times when the server is busy every day
Duration, in minutes, of the desired maintenance window
The function should return the start time of a daily maintenance window when the server is not busy.
In pseudo-code, the function signature would look something like this:
maintWindowStart(busyTimes, durationMins) -> startTime
The "busy times" should be time ranges like the following, and can be represented in whatever data structure you feel is appropriate.
0:05 to 0:30 = [5, 30]
2:00 to 4:01 = [120, 241]
13:10 to 16:55 = [790, 1015]
[[5, 30], [120, 541], [790, 1015]]
// requested duration -> expected start time
// 10 -> 30
// 120 -> 541
// 4 -> 0
// 300 -> 1015
