Candidatei-me online. O processo levou mais de 1 semana. Fiz uma entrevista na empresa MapR Technologies (San Jose, CA).
Entrevista
I applied via LinkedIn. I got a call within a week. I had 1 technical phone screen which want that difficult. After the phone screen I got an onsite call. Onsite interview was for 4 hrs with 4 different 1v1 interviews. In the first interview the discussion was on my previous work experience. The Second Interview was more technical. I was asked to write a recursive algorithm( return true if there is a path from root to a leaf with total sum == sum), LRU Cache, there are numbers from 1..n in a list of numbers with size (n+k) with k duplicates. Print k duplicates. Third Interview was with the hiring manager he told me why I should consider MapR and he asked me to write a program which should read form a huge file and write into a huge file and how will I scale it. Final Interview was another programming interview. He asked me to write a breath first search. Once I completed he wanted me to insert line breaks after every level. Then clock angle question.
The interview process was fun. But its a really long technical interview which was a bit tiring experience.
Perguntas de entrevista [1]
Pergunta 1
1. Read from a huge file say 1tb and write it into a huge file and scale it
2. Write a code piece from your previous project(unexpected!)
3. LRU cache
4. BFS with line breaks (not necessarily balanced)
Candidatei-me por meio de recrutador(a). O processo levou 2 dias. Fui entrevistado pela MapR Technologies (Hyderābād) em jul. de 2016
Entrevista
Telephonic followed by multiple F2F. Unless you answer exactly what panel expects, donot expect a positive response.
Initially MapR struggled to get people now few people are showing true colors after getting in.
Perguntas de entrevista [1]
Pergunta 1
1st round:
How do you find free memory in linux?
How do you list open files
Few more cmdlet based
2nd round:
As a developer how do you develop an support system to run at client in case of an failure. ~40 minutes on this to cover all aspects.
Then as a QA engg how do u test it.