Preparing for an interview? Check out Cracking the Coding Interview
Published on

Systems Development Engineer - Amazon/AWS - Online Assessment

Author
  • Shared Anonymously

I've had a few interview cycles with Amazon's SysDE, but recently they've started performing these Online Assessments. I just wanted to offer a few strategic tips that I wish I'd known going into it, without just revealing the actual problems they gave. I'm more of a Linux/Systems person, and even tho I regularly provide scripted solutions, DSA is not my forte.

  1. The OA is performed using HackerRank, so it would help to be familiar with this interface going into it. This will save you time, as you can bypass the [easy] sample problem which is designed to get you familiar with the interface.

  2. There were two coding problems.. the first was the more challenging. This is exactly the opposite of what I thought it would be (I thought they would be in increasing difficulty). Because I thought a majority of the "points" would be on the second problem, I had to leave off on the first one, just so I had "something." Turns out it would've been better if I'd focused on getting a "running" solution on the first one first, even if it took me extra time and I never got to the second one.

  3. Even if you have what you think is a "brilliant" solution, it's likely that nobody will read it unless it's running. Even then, they may not even look at them at all. They probably have so many applications, that it's impossible for a real person to check all the OA's that come through.

  4. Make sure you have common library and method names memorized. Apparently there's a mechanism which checks application focus, but if you try to look up a few things from the docs (even if you're not looking up solutions online) they have no way to distinguish this from cheating. In the beginning there's a small blurb that says you can use documentation, but there is no practical way to make that work. In my case I would've had both of my solutions "running" if I had been able to remember a few method names.

Anyhow, I hope this helps. For some people, the OA will be super easy, but for those of us who came up through a more systems engineering background, but who can still script, it may be more challenging.

ReportMark as Helpful