Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto un giorno. Ho sostenuto un colloquio presso Amazon nel mese di feb 2011
Colloquio
She was very calm and cool. Asked me about my favorite subject. Any project i did on that. A brief intro reqd on that. Then she went to technical part. Asked about Hashtable. Asked to explain how would you implement one. Data structure and how and what hash function will do. Cross questioned a lot with logic proposed. Gave clues where implementation or way i think is wrong, gave a chance to re-think and correct myself (many times during whole interview on different questions). Problems with hashtables, how would i solve such a problem (gave me an example scenario,collision). Asked me to design and code an algorithm (actual code NOT pseudo code). Asked to optimize, calculate Big O and how and what each steps takes (again gave a clue when she thought i was wrong, in optimization. i corrected it quickly). Asked about some design patterns and in the end gave me a chance to ask some questions i had.
She was very calm and very supportive and gave me clues where-ever my approach or code was wrong/or could be better, was patient enough to give me time to identify my mistake myself and correct it. Overall a fantastic person with a lot of stress on fundamentals, nothing too hi fi and would still test your skills of problem solving and depth of fundamentals.
I'm still waiting for my result but i'm 50/50 on my selection, as i did solved all the questions she asked and to some extent efficiently, but i did stumbled on leaving out edge cases(big mistake) and could have focused myself on efficiency of solution i proposed until she made me think of better solution(which i did in the end and she seemed ok with answers, but little practice of considering edge cases and habit of double checking code for optimization would have done more good for my chances). Keeping my fingers crossed and rate the interviewer 10/10 and way she took interview was pleasing as much as it was a great learning experience on what to take care of when interviewer asks a question.
Q2) Certain Customers buy kindle on day one and certain customers buy kindle on day two. Design an algorithm(optimum) to find customers who bought on both days. Each customer has a unique ID (Integer). (I forgot to consider case of duplicates,until she reminded), You need to write complete code(NOT just pseudo code within given time and read it out)
It started with an OA, and then after a few weeks, I got invited to four rounds of interviews: technical and behavioral at 3 of the 4, and behavioral only at one.
Ho sostenuto un colloquio presso Amazon (San Paolo del Brasile, )
Colloquio
Um teste de código online, se aprovado, vai para o loop. O loop é 4 entrevistas seguidas, duas em inglês e duas em português. 3 entrevistas técnicas de código, todas as 4 têm pergunta de liderança.
Domande di colloquio [1]
Domanda 1
Pergunta historicas baseada nos principios de lideranca da amazon.
The whole process stretched over nearly a month, longer than I anticipated. After an initial phone screen, I faced a technical round that included a Min Stack implementation question. We discussed design considerations and thread safety, which threw me for a bit. Fortunately, I remembered a specific mock interview I practiced on PracHub that mirrored this scenario closely, making me feel more at ease. Ultimately, I received an offer, but I chose to decline due to the company culture not feeling like the right fit.
Le migliori aziende per "stipendio e benefit" vicino a te