Amazon Lab126

  www.lab126.com
Work in HR? Unlock Free Profile

Amazon Lab126 Interview Questions & Reviews in Cupertino, CA

Updated May 12, 2014
All Interviews Received Offers

Getting an Interview  

42%
24%
18%

Interview Experience  

50%
33%
16%

Interview Difficulty  

Average Difficulty
38 candidate interviews Back to all interview questions
Relevance Date Difficulty

No Offer

Positive Experience

Average Interview

Software Development Engineer In Test Interview

Software Development Engineer In Test
Cupertino, CA

I applied online and the process took 2 weeks - interviewed at Amazon Lab126 in May 2014.

Interview Details – Questions about your previous job experience. Questions to know your disagreement with the Management on certain design or solution. How did you resolved the disagreement?

Log analysis program. Write a java program to find number of occurrences of a keyword in logs. Categorize count of ERROR/INFO, files etc differently.

Interview Question – Log analysis program. Write a java program to find number of occurrences of a keyword in logs. Categorize count of ERROR/INFO, files etc differently.   View Answer


Accepted Offer

Neutral Experience

Very Difficult Interview

Senior Software Development Engineer Interview

Senior Software Development Engineer
Cupertino, CA

I applied through other source and the process took 3 weeks - interviewed at Amazon Lab126 in July 2010.

Interview Details – At least 1 phone interview about past experience and some coding interview questions.
One or two site interviews with about 4 engineers for technical questions and one bar raiser.
The bar raiser is an experienced one but sometime they are not from the same field that you are applying for. Questions can be anything. There are some interview guidelines, but most of the time engineers do not learn the guidelines.
The second onsite interview most of the time is to see the managers and directors level, but sometime also has some technical questions.

Interview Question – In my field, ask more about bit field, linked list and hardware debugging skill, like i2c spec, but the most difficult one is to find all errors in a function.   Answer Question

Negotiation Details – I was looking badly for the job, so there is no negotiation


Declined Offer

Positive Experience

Average Interview

Senior Software Development Engineer Interview

Senior Software Development Engineer
Cupertino, CA

I interviewed at Amazon Lab126 in April 2014.

Interview Details – Initial communication was great, all in all a very good experience. Technical phone-screens were all as expected. The interview questions were much more heavily design-focused than algorithms focused, probably due to the nature of the position I was applying to. Most of the soft skill questions were reasonable, but some of them sounded like the interviewers were driving at particular answers they were expecting, and it was difficult to gauge what they looking for. The interview would have been rough back when I was younger, but was quite reasonable for a senior level position. All in all, though, it was as good an experience as one could ask for.

Interview Question – One of the interviewers asked me a design question that was very far afield of my expertise, and I winged it as best I could -- after doing my best with that question, I bowed out of further consideration for that, and he gave me a much more general design question that was a bit of a softball, and I asked him some pointed questions regarding Amazon's distributed design ethos. The fact that the initial question was so far afield of my resume makes one question if that is the point, or if   Answer Question

Reason for Declining – I had more than one offer to consider, and gave notice while debating between the two: my current employer immediately made me a counter-offer I couldn't refuse (significant promotion & raise).


Accepted Offer

Positive Experience

Difficult Interview

Product Development Engineer Intern Interview

Product Development Engineer Intern
Cupertino, CA

I applied through other source and the process took 2 months - interviewed at Amazon Lab126 in January 2013.

Interview Details – Two onsite interviews. Each interview was comprised of 4 different interviewers.

Interview Question – How would you redesign the case to the kindle fire so that the button no longer gets stuck?   Answer Question

Negotiation Details – No negotiation, it was an Internship and the pay was extremely good.


1 person found this helpful

Accepted Offer

Neutral Experience

Very Easy Interview

Hardware Engineer Interview

Hardware Engineer
Cupertino, CA

I applied online and the process took 1 week - interviewed at Amazon Lab126 in January 2010.

Interview Details – Had to smile and brown nose to get the job

Interview Question – Just act non threatening and you will get the job   Answer Question

Negotiation Details – There was no negotiation


No Offer

Neutral Experience

Average Interview

Senior Software Engineer Interview

Senior Software Engineer
Cupertino, CA

I applied through a recruiter and the process took 2+ weeks - interviewed at Amazon Lab126 in December 2013.

Interview Details – First, a 30-minute interview on the phone with a developer from the team. Went well.

Second, an on-site interview with the developers and managers from two teams working on the same project. All goes well, some algorithm questions, some design questions... I think I hit it off nicely with both managers.

And then, there's the "culture guy".

How well you did during the previous five hours is irrelevant. The culture guy will ask you a "culture question" and then will keep repeating "what if that doesn't work" all the while giving you the unflinching death stare.

What are you supposed to do? Heck if I know. I can merely suggest to not crack a joke during that time. I did. I wasn't seriously thinking what I said. I thought it was bleedingly obvious that I wasn't serious but I think that joke destroy my chance right then and there. Oops!

Oh, but for extra brownie points, think of something Amazon could do better. Something real.

Interview Question – The unflinching death stare.   View Answer


Declined Offer

Neutral Experience

Average Interview

Engineer Interview

Engineer
Cupertino, CA

I applied online and the process took 1+ week - interviewed at Amazon Lab126 in March 2013.

Interview Details – good and quick. every thing went smoothly

Reason for Declining – commute


No Offer

Positive Experience

Average Interview

EPM for Hardware Interview

EPM for Hardware
Cupertino, CA

I applied online and the process took 5 months - interviewed at Amazon Lab126 in October 2013.

Interview Details – Interviewed back in Oct 2013. Phone interview by hiring manager, recruiter got back couple of days after to setup onsite interviews. Following week was the onsite for 6 hours. Very nice folks, interesting questions. Recruiter got back after a couple of days saying the results were positive but they decided to go with an internal candidate. I was told they would get back to me early 2014 with a new req. I didn't quite understand at the time what that meant - You interview hoping for positive results, but then you wait longer for another req? I didn't mind, thought it was worth the wait. But never heard from the recruiter again. Mails, calls ignored. Their process is not too obvious. Hope they understand how stressful interviews are in the first place to give such dangling responses. #humankindness folks!

Interview Question – None. Read the job requirements 10 times. If you think you are a good fit, you will ace the interviews!   Answer Question


1 person found this helpful

Accepted Offer

Positive Experience

Average Interview

Software Development Engineer II Interview

Software Development Engineer II
Cupertino, CA

I applied online and the process took 4 weeks - interviewed at Amazon Lab126 in November 2013.

Interview Details – Submitted my resume online. Recruiter contacted me a day or two later for a phone interview the next week on a Tuesday. After the first phone interview, scheduled a second one for Thursday. Then scheduled an onsite for the following Wednesday (actually after an intervening holiday week). I knew by Friday that they planned to make an offer and received it on Monday. The whole process was lightning fast.

The interview was your standard 5 hour process, with lunch, except that lunch was served in the interview meeting room and half of the time slot was used for eating and half for conducting another interview so either you don't finish your lunch, or you feel like you need to scarf down the food. I'd prefer an actual break for lunch. There were six interviewers, four "regular" interviewers, plus one slot with the second-tier manager and one with a principal engineer. I didn't find the interview questions to be extraordinarily difficult. Went into some detail about threading, locking, deadlock avoidance, priority inversion with one interviewer, and tree traversal and optimization with another. Seemed pretty standard, but maybe that's because these are particular interests of mine. Other interviewers focused more on design.

Takeaway: Didn't like how lunch was conducted. Very much liked meeting with the principal engineer and getting a chance to speak with someone who would act as a mentor. This second point made a big difference for me.

Also, the recruiter was scheduled for a short slot which I thought was odd. He asked about my current salary and benefits. It took me by surprise and I answered his questions, but in hindsight, I did not appreciate this. This sort of thing should be done _after_ the interviews and after they have signaled their intent to make an offer, not before.

Negotiation Details – Recruiter initially gave me only 3 days to consider offer. The standard is 2 weeks. I planned to accept the offer without negotiation and so agreed to the 3 day time period. My current employer made a counter offer for a different position within the company. I asked for additional time to consider both offers and it was granted with no problem. Lab matched (roughly) the offer the next day. I suggested a salary/bonus/stock offer that I would be able to accept immediately. They met some of my requests fully, and others partially, still it increased their offer and allowed me to accept it.

My advice: balk at a 3-day offer expiration. The standard is 2 weeks. If you don't need 2 weeks, you can always accept sooner. This will give you a few days to solicit additional offers if possible. I was lucky and got an unexpected offer from my current employer within the 3-day window. Salary, bonus, and stock were all negotiable to some extent.


Accepted Offer

Positive Experience

Average Interview

Hardware Engineer Interview

Hardware Engineer
Cupertino, CA

I applied through a recruiter and the process took 2 weeks - interviewed at Amazon Lab126.

Interview Details – Excellent hiring staff, excellent communication, effective and pleasant. Interviews were typical 6-7 people with a bar raiser.

Interview Question – Standard technical questions.   Answer Question

Negotiation Details – Solid offer, no negotiation was req'd

Worked for Amazon Lab126? Contribute to the Community!

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.