Skip to content

Mainframe Systems Programmer Interview Questions

For mainframe systems and transaction-processing programmers. Interviews focus on shared system resources, software maintenance and reliable transaction processing.

30 questions, ranked by what the job needs most

Print the top 10:Scoring sheetPractice sheet

  1. Question 1: Walk me through a time you improved mainframe batch throughput without slowing online transactions.

  2. Question 2: Describe a time you revised a systems software effort estimate after uncovering a hidden dependency.

  3. Question 3: What would you do if a proposed systems software release had no tests for recovery after a crash?

  4. Question 4: Walk me through a time you adapted existing systems code to a new processor or device while keeping support for the old one.

  5. Question 5: What belongs in an interface agreement between a driver developer and a hardware engineer before implementation starts?

  6. Question 6: Share an example of a time you turned a vague speed requirement for systems software into a measurable performance target.

  7. Question 7: How would you model the queue capacity a systems service needs when requests arrive in short bursts faster than it can process them?

  8. Question 8: Give an example of a recommendation you made after checking a requested feature against the system's memory, timing or schedule limits.

  9. Question 9: Share an example of how you coordinated a mainframe system software update around batch schedules and online service windows.

  10. Question 10: Describe a time you tested whether an interrupted mainframe transaction left shared records consistent.

  11. Question 11: How did you predict and then check the effect of a design choice in systems software you helped build?

  12. Question 12: Looking back at a test procedure you wrote for a compiler or other systems software, what would you change?

  13. Question 13: Share an experience in which consulting with engineering staff helped you in your work.

  14. Question 14: Tell me how you sorted out which requirements mattered for a systems component using input from hardware engineers, developers and users.

  15. Question 15: Walk me through your response when testing or monitoring showed a system was missing its performance or reliability specs.

  16. Question 16: How do you effectively ensure that systems operate in conformance with specifications?

  17. Question 17: Give an example of how you caught misleading workload data before using it to size a systems component.

  18. Question 18: Share an experience in which your retrieval or manipulation of data helped you analyze system capabilities or requirements.

  19. Question 19: What would you do if a shared system library needed an update on servers whose services could not all be stopped at once?

  20. Question 20: What factors do you consider when determining if a new system or modification to an existing system is necessary?

  21. Question 21: Describe the methods you used to ensure that software systems are properly maintained.

  22. Question 22: How have you helped a customer choose between a temporary workaround and waiting for a systems software fix?

  23. Question 23: Share an experience in which you successfully explained a project's status or technical issue to a customer.

  24. Question 24: Talk about a time you changed a systems software design after a project manager explained a hardware limit.

  25. Question 25: Provide a time when conferring with others helped you to obtain information on data processing projects. How did it benefit you in your work?

  26. Question 26: What do you check before putting a systems software benchmark result in a project status report?

  27. Question 27: Tell me about a report you prepared concerning project specifications or status which you were happy with. How about one you were unhappy with?

  28. Question 28: Share an experience in which you directed software programming and/or development of documentation. What methods led to your success?

  29. Question 29: Walk me through a recent systems-level project you worked on, such as a driver, compiler, operating system component or network service.

  30. Question 30: Tell me about a time you used logs, traces or crash dumps to find the root cause of a hard-to-reproduce system failure.