☰
Apply for Network Systems Administrator

Please fill out the form below and click Submit to submit your application for consideration. Fields with an asterisk (*) are required.

Summary
Title:Network Systems Administrator
ID:6887
Contact Information
* First Name:
* Last Name:
* City:
* State:
* Zip:
* Phone:
* Email:
Attachments
Resume:
Supported formats: Word, PDF, RTF, Text, and HTML.
  - or Upload from:
 
Cover Letter:
You can type in a Cover Letter or Copy/Paste from an existing document.
Network Admin
Please complete the multiple choice question bank below.
* A core switch failure takes down critical internal systems during peak business hours. As you begin troubleshooting, panicked messages and calls from users and management start flooding in. How do you handle the situation?
A) Focus solely on fixing the issue and ignore all calls/messages until the system is restored.
B) Answer every call as it comes in to reassure users, even if it delays your troubleshooting steps.
C) Briefly notify leadership with a quick status update, establish a regular update interval (e.g., every 20 minutes), and focus on methodical troubleshooting.
D) Pass the issue to a senior colleague or vendor immediately so you don't have to manage user expectations.
* While applying a routine security update to a firewall, you misconfigure a rule that accidentally cuts off remote access for 30 minutes before you catch and fix it. No one has submitted a formal ticket yet. What do you do?
A) Keep quiet about it—the issue is fixed now, so bringing it up only creates unnecessary concern.
B) Inform your team lead/manager promptly, explain what caused the oversight, and update internal documentation or procedures to ensure it doesn't happen again.
C) Mention the outage only if a user or supervisor directly asks what happened.
D) Blame the issue on a bug or unexpected behavior in the vendor's firmware update.
* You spend several hours solving a complex, undocumented network routing issue that has popped up twice in the past month. How do you close out the task?
A) Close the ticket with a brief note like "Resolved" since you already know how to fix it if it happens again.
B) Document the root cause, steps taken, and resolution in the team knowledge base, then share a quick heads-up with team members during the next daily check-in.
C) Send a broadcast email to the entire company explaining the detailed technical solution.
D) Keep the solution in your personal notes so you remain the subject matter expert for that issue.
* While performing a routine diagnostic on a shared network drive to clear space, you accidentally open a folder containing confidential compensation data for your department, including your peers and supervisor. What is your reaction?
A) Immediately close the folder, report the improper folder permissions to your supervisor/security team, and refrain from discussing the contents with anyone.
B) Glance through the file briefly out of curiosity to see where you stand, but promise yourself not to tell anyone.
C) Save a local copy of the file for reference in case you ever need to negotiate a raise.
D) Anonymously alert your coworkers about the leak so they know their data is exposed.
* It’s 4:45 PM on a Friday, and you notice a minor, non-critical backup failure alert. Fixing it isn't strictly required before Monday, but leaving it unaddressed risks missing over-the-weekend snapshot logs. How do you handle it?
A) Ignore the alert and leave immediately—it’s not a critical outage and can wait until Monday morning.
B) Investigate the root cause, resolve the job issue or set an automated retry before leaving, and verify the weekend backup schedule is secure.
C) Mark the alert as resolved without checking it so the dashboard stays green over the weekend.
D) Forward the alert to a junior teammate or contractor on weekend duty without providing context.

Submit
Cancel