Q1. What does a typical day look like when managing IT infrastructure? LOW

A. A typical day includes monitoring server and network health dashboards, reviewing overnight alerts, applying scheduled patches, responding to support tickets tied to infrastructure, and checking that backup jobs completed successfully. It also includes documenting any changes made to systems.

Q2. How would you manage and maintain IT infrastructure covering Microsoft 365, Azure, Windows Servers, Active Directory, networking, backups, and disaster recovery? MID

A. Start with a full infrastructure audit to document the current state of servers, directory structure, network topology, cloud resources, and backup and disaster recovery configurations. Implement proactive monitoring and patch management, standardize security baselines, and enforce least-privilege access. Test backups regularly and rehearse disaster recovery runbooks periodically so recovery time and recovery point objectives are verified, not assumed.

Q3. What is your approach to managing firewalls, VPNs, and Wi-Fi? MID

A. Segment networks by function using VLANs, apply scheduled firewall rule reviews, and use centrally managed VPN access with multi-factor authentication. Manage Wi-Fi through enterprise authentication rather than shared passwords, with periodic coverage and capacity audits.

Q4. How do you decide what infrastructure should move to the cloud versus stay on-premises? HIGH

A. This decision should be based on total cost of ownership, compliance requirements, latency sensitivity, and the organization's appetite for operational change. Workloads with variable demand or that benefit from managed services are strong cloud candidates, while systems with strict data residency requirements or heavy legacy dependencies may stay on-premises longer. A phased hybrid approach reduces risk while the organization builds cloud maturity.

Q5. What steps would you take before granting a new employee access to business systems? LOW

A. Confirm the request against an approved access list or manager sign-off, provision accounts using role-based templates rather than copying an existing user, apply least-privilege permissions, and log the change for audit purposes.

Q6. How do you approach oversight of business-critical applications such as CRM, accounting, property management, and document management systems? MID

A. Maintain an application inventory with owners, criticality ratings, and support contacts. Set uptime monitoring and service targets, work with department leads to understand how each system supports their workflow, and review licensing, upgrades, and integration health on a regular cycle.

Q7. What is your experience with property management or similar enterprise systems? MID

A. Relevant experience includes hands-on administration of an enterprise or property management platform — user provisioning, data integrity checks, reporting, and integration with finance or CRM tools — or transferable experience with similarly structured systems and the ability to learn a new platform quickly through documentation and vendor training.

Q8. How would you handle a scenario where two business-critical applications are giving conflicting data to leadership? HIGH

A. Treat this as a data governance issue, not just a technical bug. Identify the system of record for the data in question, trace the discrepancy back through integration points or manual entry steps, and correct the root cause rather than just reconciling numbers once. Communicate transparently with leadership about which figure is authoritative while the fix is implemented, since trust in reporting is as important as the fix itself.

Q9. What automation tools have you used, and for what kind of tasks? LOW

A. Common entry points include automating recurring notifications, approval routing, scheduled reports, and simple data transfers between two systems using built-in connectors or low-code automation platforms.

Q10. How would you lead a systems integration project to reduce duplicate data entry? MID

A. Map data flow between systems to find where duplication occurs, evaluate integration options such as native connectors, middleware, or APIs, prioritize by business impact and effort, pilot one workflow, measure time saved and errors reduced, then scale with documentation and a rollback plan.

Q11. How would you use automation tools to streamline business processes? MID

A. Identify repetitive, rule-based tasks such as approvals, notifications, or data transfers as automation candidates. Build workflows triggered by forms, emails, or system events, add error handling, and confirm sign-off from the process owner before going live.

Q12. How do you build a long-term integration and automation roadmap across an organization with many legacy systems? HIGH

A. Start with a systems and data-flow map, then score each manual or duplicated process by business impact and technical feasibility. Sequence initiatives so early wins fund and justify later, harder integrations. Favor a middleware or integration-platform approach over point-to-point connections so the architecture stays maintainable as more systems are added over time.

Q13. What is multi-factor authentication and why does it matter? LOW

A. Multi-factor authentication requires a second proof of identity beyond a password, such as a code from an app or a hardware key. It matters because it significantly reduces the risk of unauthorized access even if a password is stolen or guessed.

Q14. How would you develop and maintain a cybersecurity strategy? MID

A. Apply a layered defense model that includes endpoint protection and device management across all devices, mandatory multi-factor authentication and conditional access, email security controls against phishing and spoofing, role-based access control with periodic access reviews, a documented incident response plan with clear escalation steps, and ongoing security awareness training with simulated phishing exercises.

Q15. How would you respond to a suspected ransomware incident? MID

A. Isolate affected devices to contain spread, activate the incident response plan and notify relevant stakeholders, preserve logs for review, assess backup integrity, and restore only from backups verified as clean. Follow up with a post-incident review to close the gap and update controls and training.

Q16. What security frameworks or certifications have you worked with, and how do you use them? HIGH

A. Recognized frameworks and certifications help formalize policies, risk assessments, and controls, and provide independent assurance of the organization's security posture to leadership, auditors, and customers. At a strategic level, they're used not just as a checklist but as a structure for continuous improvement and board-level risk reporting.

Q17. What's the difference between a backup and a disaster recovery plan? LOW

A. A backup is a copy of data that can be restored if it's lost or corrupted. A disaster recovery plan is the broader set of procedures for restoring entire systems and operations after a major disruption, including how quickly and to what point data must be recoverable.

Q18. How do you ensure data integrity and governance across enterprise systems? MID

A. Establish clear data ownership, standardized classification conventions, and role-based access controls. Run regular data quality audits and maintain a governance policy covering retention, sharing, and disposal in line with applicable regulations.

Q19. How would you design and test a disaster recovery plan? HIGH

A. Define recovery time and recovery point objectives per system based on criticality, implement backup solutions that meet those targets, and schedule regular tests — from single-file restores to full failover simulations — documenting results and refining the plan. At a strategic level, this also means aligning DR investment with the actual cost of downtime for each business function.

Q20. What makes a dashboard useful versus just decorative? LOW

A. A useful dashboard answers a specific business question at a glance, uses accurate and current data, and is designed around the audience's decisions rather than showing every metric available.

Q21. How would you design dashboards for real-time reporting across departments? MID

A. Meet stakeholders in each area to define relevant KPIs, build a clean and governed data model rather than relying on disconnected spreadsheets, apply row-level security so users see only relevant data, and iterate on design with end users before wide rollout.

Q22. How do you ensure dashboard data stays accurate and trusted at an organizational scale? HIGH

A. Automate refresh schedules, build validation checks that flag anomalies, and document data sources and calculation logic so business users can interpret the figures correctly. At scale, this also requires a governance layer that defines who can create official reports versus ad hoc analysis, so there's a single trusted source of truth.

Q23. How do you manage vendor relationships and service level agreements? MID

A. Maintain a vendor register with contract terms, renewal dates, and SLA metrics. Hold regular service review meetings, track performance against agreed targets, and use that data during renewal or renegotiation discussions.

Q24. How would you approach preparing and managing an annual IT budget? HIGH

A. Build the budget from documented infrastructure needs, licensing, planned projects, and a contingency allowance. Track spend against budget monthly, flag variances early, and support major investments with a cost-benefit business case tied to organizational priorities.

Q25. How do you keep technology projects on scope, budget, and timeline? MID

A. Use a phased project approach — discovery, design, pilot, rollout, and post-launch support. Set clear milestones, track risks and dependencies, and hold regular progress reviews so issues are surfaced early rather than at the end.

Q26. How do you manage user adoption and training when rolling out new technology? MID

A. Involve end users early to gather input, provide role-based training and hands-on sessions, and maintain a feedback channel during rollout so issues are identified and resolved quickly.

Q27. What would you check first if several employees report the same issue at once? LOW

A. Check whether the issue traces back to a shared system, recent change, or outage rather than treating each ticket individually, since a common root cause changes how urgently and broadly it needs to be resolved.

Q28. How would you improve helpdesk response times and user satisfaction? MID

A. Implement a ticketing system with clear priority tiers and response targets, monitor resolution times and recurring issues, and address root causes through documentation or proactive fixes rather than repeated firefighting.

Q29. What is your approach to managing IT assets such as laptops, mobile devices, and meeting room technology? MID

A. Maintain an accurate, centrally managed asset register with purchase date, warranty, assigned user, and lifecycle stage. Set a device refresh cycle, use management tools for remote configuration, and ensure secure decommissioning of retired equipment.

Q30. How would you develop IT governance policies, business continuity procedures, and compliance standards? HIGH

A. Benchmark against recognized frameworks, draft policies covering acceptable use, access control, change management, and incident response, and ensure they are reviewed, approved, communicated, and revisited on a regular schedule.

Q31. What would your first 90 days in this role look like? HIGH

A. In the first 30 days, complete an audit of infrastructure, applications, security posture, and vendor contracts, and meet stakeholders to understand priorities. By day 60, produce a prioritized risk and opportunity list with early quick wins delivered. By day 90, present a draft multi-year IT strategy with a roadmap for reporting, automation, and governance improvements.

Q32. How do you measure the success of the IT function? HIGH

A. Success is measured across several dimensions:

• System uptime and availability
• Helpdesk response and resolution times
• Cybersecurity performance
• Backup and disaster recovery test success
• User satisfaction
• Project delivery against scope, budget, and timeline
• Budget management and cost savings
• Process automation improvements
• Dashboard and reporting adoption
• Data quality and governance
• Vendor performance and SLA compliance

Q33. Describe a time you had to explain a technical problem to someone non-technical. LOW

A. A strong answer focuses on translating the issue into business impact, avoiding jargon, using a relatable analogy, and confirming the listener understood before moving to next steps.

Q34. How do you communicate technical risk to non-technical stakeholders? HIGH

A. Translate technical risk into business terms such as financial exposure, operational disruption, or reputational impact. Use clear visuals rather than jargon, and pair each risk with a recommendation and cost-benefit summary to support fast decision-making.

Q35. How do you prioritize when everything on your plate feels urgent? MID

A. Prioritize based on business impact and risk rather than who asked loudest or most recently. Use a simple framework — such as urgency versus impact — to rank work, communicate the reasoning to stakeholders, and revisit priorities as new information comes in.