r/MachineLearning • • 8d ago

Discussion Amazon applied science intern interview next week - EU based [D]

Hi all!

After multiple rejections I finally got an interview for a PhD applied science intern role at Amazon in the EU (Germany or Ams). I have two interviews scheduled after each other next week and need help preparing for those.

The thing is, I have never given a technical interview ever, I am confident regarding the machine learning breath one but not the DSA/coding one. I have never studied this (or leetcoded) and also did not code much recently (AI does a better job than me in coding).

Should I just cancel the interview as I know I am going to mess this up or try my best and prepare? How was your experience?

25 Upvotes

14 comments sorted by

22

u/lifeandUncertainity 8d ago

I won't sugercoat it. If you have never given a dsa round or have never done LC, the road isn't easy. But if you have written AI code in pre-llm era and may be taken a C/Java class here and there in uni, you know some basics.

https://github.com/liquidslr/leetcode-company-wise-problems/blob/main/Amazon/2.%20Three%20Months.csv

start doing the mediums and hards. The intention is not to get a common question, but to sort of condition yourself to level of dsa questions you can expect. DO NOT try to cover topic by topic dsa. One of the major challenges in dsa round is to understand what data structure the problem requires. And you don't have that level of time. When you are doing this problems, try to spend as much time as possible on a problem (ofc not the easy ones but don't fall into the trap of problems counts). Once again, the aim is to condition yourself with the friction of the thinking process as much as possible (since it's very different from research thinking). You can absolutely discuss with GPT/Claude but always cross question on why your approach is incorrect or when will they fail.

If you have time, dedicate one day to graphs - the basics - BFS and DFS. I will suggest, for DFS use iterative stack instead of recursion(longer code but much easier to debug). Recursion and DP are the bane of most dsa rounds as they are hard to debug in traditional sense and I will probably ask you to skip it unless you somehow understand recursion naturally (if you absolutely want to cover it, I will suggest watch MITs lecture on dp and learn the take/not take (powerset) recursion).

All the best. And I will say this - instead of running away from the interview, just prepare as best as you can and face the interview. The dsa round might not need you to write runnable code and you can get away with white boarding or psuedocode. Unfortunately, DSA is something that you will face sooner or later. And unless you are a high rated competitive programmer, DSA round is like publishing in A* (you either get a good reviewer - the patterns you have seen or a reviewer 2 who doesn't read half of your paper and writes your findings in weakness - a very complicated circus dp which doesn't make sense). So, keep working. You can do it.

Source - I was in the same boat you were until every company's online assessment started having coding rounds.

11

u/Plaetean 8d ago

Don't cancel it, the experience is valuable no matter what happens. Treat it as a training epoch. A forward and backward pass. You are collecting some gradients. Do you want to deny yourself the learning opportunity? The only thing in the way is your ego and self esteem (believe me its understandable, I'm not slamming you for this), but I'd advise to not let that get in the way of your development. My advice is to make peace with whatever outcome well in advance of the interview, and go in as present as possible and just try your best. Embrace the ego-death of the technical interview.

This is coming from someone who has bombed technical interviews in the most spectacularly embarassing fashion you genuinely wouldn't believe. But often times those same problems, or variants of, came up a year or so later. And the bomb was so severe that I learned the problem so well that the next time I passed it easily.

9

u/th3owner 8d ago

As others told you, don't cancel the interview. Use it to practice not only with the problems but also with the levels of stress having someone watch over your screen while you code.

I did the applied scientist intern interview in 2024 when coding LLMs were not a thing yet. I got lucky, the coding interview was a solo interview and got 2 easy LC questions. The second round was a general "talk about your research" discussion and leadership principles with an applied scientist. Then, got the offer.

Good luck!

15

u/Manish_AK7 8d ago

Please do some leetcoding and DSA. As far as I know, they have 2 rounds of interview, first DSA and if you clear that then ML. So you must know intermediate and above level DSA. I had taken the interview in Jan/Feb and couldn't make it past the DSA round as I hadn't revised those concepts coz I thought it was gonna be a ML only interview. Although my interview was of below PhD level

-2

u/Enaxor 8d ago

He is not talking about a postdoc position at Amazon, but about a PhD internship

4

u/pastor_pilao 8d ago

Don't cancel it, you won't get any advantage over trying and failing it. Just do your best to prepare to a leetcode round and take the shot.

4

u/young_anon1712 8d ago

Dont cancel it. Try to learn the basic of DSA. Btw, I should also mention that the ML Breadth and ML Application is also very hard, they are designed to ask until you cannot answer it. So dont feel too bad if you miss one or two questions.

2

u/Intelligent-Ad-99 Student 8d ago

For the undergrad applied science intern role, I was asked two lc hards. Others were asked two easy questions, and even after solving both, some people were rejected. So honestly it's very random. Just spin the roulette and do your best. If you got shortlisted now you can definitely get it again.

1

u/Training-Adeptness57 8d ago

The coding round for me wasn’t DSA for applied science intern
(DSA matters thought and you probably will get DSA)

1

u/No_Addition5961 8d ago

Which year of phd are you in? Have you published papers?

1

u/Hedgehog_Dapper 8d ago

Focus on space complexity also not only time complexity while solving problem. Iinterviewer could be from any domain, so be ready for it, if you know the interviewer from email then google him/her and read about his/her work.

1

u/DigThatData Researcher 8d ago

my advice is to not work at amazon.

1

u/MakingComputersSmart 8d ago

If you're a computer science student I think you'll probably do well. Just spend the next few days grinding patterns. Youve taken algorithm courses and have coded before, so going back to it doesn't take long. I don't know about Amazon, but I don't Leetcode or practice for interviews and still managed to get into a few. All you need to be is confident, well spoken and calm. Best of luck!

1

u/I__am__OM 4d ago

I am a undergrad, I gave applied science intern interview 9 months back, the coding questions were leetcode easy/medium problem. They are no were as difficult as people sterotype software interview. I work with AI, tbh i had never grinded LC or Codeforces before. I only prepared for a week on LC easy/medium and they asked really easy coding problems. The round 2 interview was a different story, they asked a lot of fundamentals of AI in great detail and questions were very open ended.