Did Amazon OA today. First problem all test cases passed and gave most optimal solution. Second problem, I was on right track but while the code had some runtime exception. The system made debugging very difficult as print statements and stack trace couldn’t be printed in case of runtime exceptions. Finally, I had to manually trace the recursion tree and found the problem. Before I could provide the fix, time ran out and code was left in un-compilable state. What should I expect? Can I ask recruiter for one more attempt? I have passed similar assessments from Amazon twice in the past but had a bad day today. Feeling disappointed as don’t want to wait for another 6 months.
Sorry to read this. It is unlikely you’ll get a call. Sounds like problem 1 was easy and problem 2 hard. Is it ?
Both were LC medium. The second one was dfs. Debugging it became difficult with system not showing any prints and not telling what kind of exception is happening.
Did you try it on your local IDE ?
Sorry to hear this. I went through something similar and didn’t get a call.
Do you know about cool off period?
I think it’s 6 months , but Amazon guys can tell you better. Hasn’t been 6 months for me yet. Still smarting...
Better luck next time buddy, sorry to hear.
What is OA?
Online Assessment
So, I do manual OA reviews (my org does them and I went through the requisite training, which frankly wasn't all that thorough). You have a chance, but it depends upon the system and your reviewer. Most OA submissions do not go through a manual review (you get an automatic "rating" based on test cases, compile results, and runtime performance--if both solutions fail to compile, for example, it's an automatic reject). It's the borderline ones that get the human touch. Most submissions I see are horrible (the candidate only "solves" the easy one in naive fashion with sloppy code style, and makes a really weak attempt or no attempt at all on the harder one), so by having mostly working code and a decent approach on the second problem, you're already ahead of the curve. My personal attitude is that this is a very early screen, and passing you on to a phone screen isn't a particularly risky or expensive proposition, so I'm mostly just looking for evidence of competence and care, not perfection (i.e. perfectly bug-free or running a supposedly optimal runtime...I also hate that the OA reports will show a prominent runtime analysis but nothing for memory use, which discourages thinking about trade-offs and reinforces the "optimize for time complexity" code monkey theme). I'm not going to debug your code (especially since OAs can be done in a slew of different languages and I'm not going to be an expert in all of them), but if your code is clean (you use descriptive variable names and make good use of subroutines or control structures), you solve one of the problems with all cases passing and your approach on the other appears to make sense and seems mostly correct, I'll usually recommend a screen with a note for the screener to drill down on areas of concern.
Does amazon review each one of OA?
Update?
Today I Learned
Yesterday
1740
White male privilege is real
Tech Industry
Yesterday
2501
Do people underestimate E6 role at meta?
2024 Presidential Election
Yesterday
252
Canceling debt isn’t inflationary or costing tax payers
Personal Finance
Yesterday
688
Biden wants to raise capital gains tax to 40%
World Conflicts
10h
924
Why do Indians support Israel so much( on blind surprisingly) when Israel really thinks 💩of them ?
Unlikely you ll get a call. People who look at your OA don’t have time to analyze where you got stuck.
Cool off period in that case?
I'll usually recommend phone screens in these cases if the code is clean and the approach makes sense.