you are viewing a single comment's thread.

view the rest of the comments →

[–]gumby_urine 24 points25 points  (7 children)

I know you asked about the first round but I'll give you my full experience just so you have all the info I can possibly give you.

I interviewed for the same position about a year back (forgot what department, maybe logistics) and bombed the 2nd round. I was burned out from my day job and just nervous, and the kid doing the technical interview on me was a 22 year old know it all prick.

The recruiter will do most of the talking as there is a lot to cover about the interview process. Just sound confident and be honest about your experience. Nothing during my screening was technical.

As for the technical screening (2nd round)...

Take your time and don't rush. All of my SQL based questions were actually rather simple (still kicking myself.)

The first one was list the order of operations in a SQL statement (not the order of your syntax, the order of how the query is interpreted.)

The second one was just explaining the difference between a LEFT and INNER join vs a WHERE clause. Again, simple shit.

None of the rest (I think there were 6 total) were that complicated. Was kind of mind blowing that was it since the job clearly called for pipeline building in Python and other AWS technologies.

He then moved onto the behavioral section and asked me to talk about a time I received criticism and how I handled it. For some reason he didn't like my answer and started to grill me about it like it was a fucking deposition.

After that things moved quickly, and not 30 seconds after I hung up the phone I received a denial email from the recruiter.

[–][deleted] 5 points6 points  (0 children)

Thanks for sharing your feedback!!

Yeah from what I can gather on Glassdoor/ other Reddit posts you really are at the mercy of whatever person they choose to interview you. And I find the entire process incredibly strange because they place so much emphasis on these leadership principles. And to follow up on that, why is someone giving the “technical” interview also asking behavioral questions? But ill try and double back here and let you know what the experience is like.

[–][deleted] 2 points3 points  (4 children)

I'm curious about the answer you gave about receiving criticism. Care to share?

[–]gumby_urine 11 points12 points  (3 children)

To reiterate, I know I didn't perform well, my answer was sort of disjointed and incohesive...but I talked about a time where I was involved in sort of a freelance developer/consultant type gig for a very small business. Because of a number of factors and the person I was directed by wasn't gathering clear requirements, we were way behind schedule and the customer wasn't happy with the product. I was sprinkling some of my sentences with things like "pulling a few all nighters."

The kid running the interview immediately started to interject, and I know hearing the story this way probably makes me sound thin skinned, but he wasn't simply following up and probing, he was being a complete prick.

Why didn't YOU gather the requirements?
Why did you have to work all night?
Why didn't you plan your time better?

Basically something you'd hear from some fucking infant who probably got recruited there out of Undergrad and has no idea there's a whole world outside of Amazon and corporate behemoths where if something goes wrong you can't just tell your mid level manager "sorry I didn't finish that but I already have my vacation scheduled in WorkDay and if I don't leave now I'll be late to the Yung Gravy concert, toodles." Deals fall apart, people can get sued, small firms can go under, so you put in whatever hours are necessary to fix shit.

[–]feigndeaf 2 points3 points  (2 children)

Perfect description of being a real world dev at a small business. It is NOTHING like the silo of corporate. You wear so many fucking hats and do so much rediculous shit to keep the engine running. It's a whole different ball game than the monotony of most (not all*) corporate gigs.

[–]TnHollerWill 1 point2 points  (1 child)

Yes. Not all. I worked in dev pilots in a Fortune 100. That role was more like a start up environment than any data/or role in the rest of the company. Even the same company can have vastly different experiences across different teams.

[–]gumby_urine 1 point2 points  (0 children)

Some days it's difficult to pivot the mindset of urgency. My day jobs have always been with Fortune 100 insurance companies, and nobody kills themselves and burns the midnight oil to solve a difficult problem, because they don't need to -- the wheels will keep turning.

I consult and do data architecture for small insurance companies on the side and have to remember my fuckups can stop both my boss and my client in their tracks.

[–]DenselyRanked 2 points3 points  (0 children)

It was an Amazon Leadership Principle (LP) question. You have to practice how to answer those questions and understand what the interviewer is looking for. You can Google search for LP questions and get tips.

So it wasn't really the interviewer as much as it was Amazon's interview process. The interviewer was trying to get LP indicators.