Ivanti Staff Software Engineer Interview Experience
Interview Experience
Hello, I recently had an interview at
Ivanti for Staff Software Engineer on .Net, went through three rounds of interview, and here are the interview questions in case it helps others. Even after c
Full Details
Hello, I recently had an interview at
Ivanti for Staff Software Engineer on .Net, went through three rounds of interview, and here are the interview questions in case it helps others. Even after clearing all rounds I was told they decided to go with someone else.
Round 1 Basic .Net questions, then asked to review the following block of code on order processing:
public class OrderProcessor { private readonly IOrderRepository _orderRepository; private readonly IPaymentGateway _paymentGateway; private readonly IInventoryService _inventoryService; private readonly IEmailService _emailService; public OrderProcessor(IOrderRepository orderRepository, IPaymentGateway paymentGateway, IInventoryService inventoryService, IEmailService emailService) { _orderRepository = orderRepository; _paymentGateway = paymentGateway; _inventoryService = inventoryService; _emailService = emailService; } public async Task<bool> ProcessOrderAsync(Order order) { if (await _inventoryService.CheckAvailabilityAsync(order.Items)) { var paymentResult = await _paymentGateway.ProcessPaymentAsync(order.TotalAmount, order.PaymentDetails); if (paymentResult.IsSuccessful) { _orderRepository.SaveOrderAsync(order); _inventoryService.UpdateInventoryAsync(order.Items); _emailService.SendOrderConfirmationAsync(order);
**return** true; } }
**return** false; } }
Then asked to explain how I would write a program for the following:
/* Given a string s which represents an expression, evaluate this expression and return its value. The integer division should truncate toward zero. You may assume that the given expression is always valid. All intermediate results will be in the range of [-2^31, 2^31 - 1].
**Note**: You are not allowed to use any built-in function which evaluates strings as mathematical expressions, such as eval().
**Example 1**:
**Input**: s = "6/3+2*2"
**Output**: 7 Example 2:
**Input**: s = " 3/2 "
**Output**: 1 Example 3:
**Input**: s = " 3+5 / 2 "
**Output**: 5 Constraints: - s consists of integers and operators ('+', '-', '*', '/') separated by some number of spaces. - s represents a valid expression. - All the integers in the expression are non-negative integers in the range [0, 2^31 - 1]. - The answer and any intermediate results are guaranteed to fit in a 32-bit integer. */
Round 2 Entirely coding round, asked to write the program for the following question and then run it with given samples. Create a least recently used(LRU) cache and then test it against the following:
private static void TestCache() { LRUCache lRUCache = new LRUCache(4); lRUCache.put(1, 1); // cache is {1=1} lRUCache.Display(); lRUCache.put(2, 2); // cache is {1=1, 2=2} lRUCache.Display(); lRUCache.put(3, 3); // LRU key was 2, evicts key 2, cache is {1=1, 3=3} lRUCache.Display(); lRUCache.put(4, 4); // LRU key was 1, evicts key 1, cache is {4=4, 3=3} lRUCache.Display(); Console.WriteLine("Getting 2:" + lRUCache.get(2)); //
**return** 1 Console.WriteLine("Getting 3: " + lRUCache.get(3)); //
**returns** -1 (not found) Console.WriteLine("Getting 4: " + lRUCache.get(4)); //
**return** -1 (not found) Console.WriteLine("Getting 1: " + lRUCache.get(1)); //
**return** 3 lRUCache.put(5, 5); lRUCache.Display(); }
Round 3 Asked to review a block of code on .Net Core API call and System Design for below: Functional Requirements: > Million of endpoints (laptops and devices) Every 4 hrs Vulnerability data is pushed (JSON) - scan report > View it on a dashboard Top 10 vulnerabilities Want to see how many are patched. Non-Functional : > Scalability (<1MB) 1Mil x 4hrs = 0.25M/hr reliability durability Cost effective Security
About This Question
This is a candidate experience report from a ivanti interview for a swe role (staff level) during the coding round reported in 2026.
It covers the following topics: Strings, System Design .
Difficulty rating: Easy
Topics
About Ivanti Interview Reports
This question was reported by a candidate who interviewed at Ivanti. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Ivanti are the higher-signal extractions to take from this report.
For broader preparation context, the Ivanti interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Ivanti reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Ivanti Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Ivanti reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.