Tell me about a time you didn’t know how to solve a challenging problem.
Infrastructure Engineer Interview Questions
Infrastructure Engineer Interview Questions
Infrastructure engineers are responsible for building and maintaining digital networks. In your interview for an infrastructure engineer position, be prepared to answer technical questions about IT systems and software. Interviewers may also ask non-technical questions to assess your communication and time management skills.
Top Infrastructure Engineer Interview Questions & How to Answer
Question 1
Question #1: How do you communicate complex issues to non-engineer colleagues or clients?
How to answer
How to answer: Interviewers use this question to assess your ability to communicate IT information to co-workers and clients from non-IT backgrounds. List and describe the verbal and written communication strategies you have used in the past to break down difficult concepts into understandable pieces.
Question 2
Question #2: What are the positive and negative aspects of working within an Agile construct?
How to answer
How to answer: Agile is one of the most popular project management and software development approaches used by IT teams. This question allows interviewers to assess your understanding of the Agile environment as well as your approach to teamwork and interpersonal communication. If possible, use previous work experience to elaborate on the benefits and issues you have experienced working within an Agile environment.
Question 3
Question #3: How do you produce quality work when you have several projects to complete?
How to answer
How to answer: Infrastructure engineers must juggle all of their projects while simultaneously dealing with infrastructure issues requiring immediate attention. Interviewers use this question to assess your time-management skills and your ability to work well under pressure. List and discuss planning tools you use on the job and how you handle emergency issues.
3,735 infrastructure engineer interview questions shared by candidates
Tell me about a time you had to work through a technical issue or troubleshoot a technical problem.
Tell me about a time when you made a bad decision.
Describe a time when you refused to compromise your standards around quality/customer service, etc.
Tell me about a time when your team’s goals were out of alignment with another team you relied on in order to meet your goal.
Tell me about a time you didn’t meet a deadline? What did you do and why?
What is my learning process?
Not Remeber well for a long time.
(Email Screening Question) A monitoring script, written in Ruby (MRI 2.1.7) and running in a server with Ubuntu 12.04 64bit, with kernel 3.2, periodically checks for the disk I/O of running processes using this snippet of code: def disk_stats(pid) proc_io =File.read("/proc/#{pid}/io") io =YAML.load(proc_io) [ io["read_bytes"], io["write_bytes"] - io["cancelled_write_bytes"] ] end The following exception, however, is sporadically raised from inside the method when trying to acquire the stats: Psych::SyntaxError: (<unknown>): could not find expected ':' while scanning a simple key at line 8 column 1 What do you think is going on here? Is the bug in our disk_stats function, in the YAML parser or in the kernel?
(Email Screening Question) The following areas map to technologies we use on a regular basis at GitHub. Experience in all of these areas is not a prerequisite for working here. We'd like to know how many of these overlap with your skill set so that we can tailor our interview questions if we move forward in the process. Please assess your experience in the following areas on a 1-5 scale, where (1) is "no knowledge or experience" and (5) is "extensive professional experience". If you're not sure, feel free to leave it blank. Just place the number next to the corresponding areas listed here: • coding o comp-sci fundamentals (data structures, big-O notation) o C or C++ programming o Go programming o git usage o git internals o shell scripting o ruby programming • troubleshooting o debuggers (gdb, lldb) o profilers (perf, oprofile, perftools, strace) o network flow (tcpdump, pcap) • large system design o unix processes and threads o sockets o signals o mysql o redis o distributed systems • operational experience o reading and debugging code you’ve never seen before o helping other engineers understand and navigate production systems o handling large scale production incidents (external communications, internal coordination)
Viewing 2761 - 2770 interview questions