Systems Engineer

What this interview asks about

How you behave when something is down, and what you change so it does not happen the same way twice.

• A production problem you traced from the machine up
• A fault that was intermittent, and how you pinned it down
• Something you automated that used to be done by hand
• A problem you solved with incomplete information from the user
• Something you wrote down that saved someone later

How it is scored

• Whether the answer actually addresses the question asked
• Whether you give a concrete example rather than a general principle
• Whether the reasoning holds together from start to finish

It does not score your accent, your speed, or how many long words you use.