Associate Engineer Interview Questions

35,490 associate engineer interview questions shared by candidates

1) describe Raid, 2) High Volume Data Movement, 3) describe UDP vsTCP, 4) describe data center system architecture, 5) what do you do to setup webserver, 6) fw vs Sw, 7) reqs/laws/etc for web consumer vs govt, 8) describe IDS config, 9) describe hash, 10) describe FW config, 11) describe most common network architecture without honeypot, 12) access mgmt basics, 13) describe DMZ, 14) describe how you would recommend creating a new system for new business.
avatar

Systems Engineer Associate

Interviewed at Amazon

3.5
Aug 18, 2015

1) describe Raid, 2) High Volume Data Movement, 3) describe UDP vsTCP, 4) describe data center system architecture, 5) what do you do to setup webserver, 6) fw vs Sw, 7) reqs/laws/etc for web consumer vs govt, 8) describe IDS config, 9) describe hash, 10) describe FW config, 11) describe most common network architecture without honeypot, 12) access mgmt basics, 13) describe DMZ, 14) describe how you would recommend creating a new system for new business.

Think about Google's autofill functionality. Currently, the way we've implemented it is that after every letter a request is sent to the server to find all valid possibilities of what the word could be. So, for example, if we're trying to search "hello", after we type the letter "h", then a request is sent. Then we type "e" and another request is sent. The number of valid possibilities becomes smaller and smaller as we type more and more of the word out. The current model of sending a request to a server after each keystroke is pretty expensive so what sort of algorithm would you use to limit the number of server requests sent while still maintaining the autofill functionality (meaning that it appears rapid to the user and doesn't stall).
avatar

Associate Software Engineer

Interviewed at Workday

3.5
Nov 20, 2015

Think about Google's autofill functionality. Currently, the way we've implemented it is that after every letter a request is sent to the server to find all valid possibilities of what the word could be. So, for example, if we're trying to search "hello", after we type the letter "h", then a request is sent. Then we type "e" and another request is sent. The number of valid possibilities becomes smaller and smaller as we type more and more of the word out. The current model of sending a request to a server after each keystroke is pretty expensive so what sort of algorithm would you use to limit the number of server requests sent while still maintaining the autofill functionality (meaning that it appears rapid to the user and doesn't stall).

Viewing 1001 - 1010 interview questions

Glassdoor has 35,490 interview questions and reports from Associate engineer interviews. Prepare for your interview. Get hired. Love your job.