Infoblox Software Engineer candidates report a recruiter call, an aptitude or cognitive test, coding, and technical rounds covering DSA, networking, and DBMS. Formats vary a lot between reports, and some describe slow communication.
$123K
Avg. Base Comp
$150K
Avg. Total Comp
3-6 rounds
Typical Rounds
3-16 weeks
Process Length
Infoblox Software Engineer candidates describe different loops, so prepare for breadth across algorithms, networking, and databases rather than one specialty. Most reports start with a recruiter conversation. Several then mention a timed or cognitive assessment before the technical interviews.
On coding, one candidate was rejected in the first coding round after failing to solve Find Minimum in Rotated Sorted Array, which requires an O(log n) approach. Another called the coding round significantly harder than the aptitude test and said it required solid DSA fundamentals. A third described standard LeetCode-style work such as validating an IPv4 address.
Technical conversations lean on fundamentals. Candidates report being asked to explain OSI model layers, sorting algorithms with time and space complexity, and UDP versus TCP. One candidate with a five-interview loop also saw API design, a calendar-app system design question, and a discussion of their current project. Another candidate, interviewing for an India-based Software Engineer I role, saw DBMS, SQL, string reversal, file operations, and regular expressions.
Communication and timing varied. Two Software Engineer candidates reported offers. Three reported no offer: one after the first coding round, one after weeks of silence following an onsite, and one after roughly four months when the role was closed. Plan to ask recruiters about next steps and timelines. The evidence is limited, so treat the reports as examples of what you might see, not a fixed format.
Synthesized from 6 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Infoblox process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Infoblox
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Weighted Keys | |
| Longest Increasing Subsequence | |
| Flatten N-Dimensional Array to 1D Array | |
| Skyscanner Partner ETL | |
| Complete Addresses | |
| Hurdles In Data Projects | |
| Centralized Event Ingestion | |
| Target Indices | |
| Portfolio Platform Architecture | |
| Common Prefix | |
| Count Transactions | |
| Seller Type Modeling | |
| Second Longest Flight | |
| Three Indexes Adding Zero | |
| Stranded Capacity | |
| Blob Indexing | |
| Text Editor With OOP | |
| Variate Anomalies | |
| Smart Fitness Tracker Launch | |
| Client Solution Pushback | |
| LRU Cache 1 | |
| Decreasing Payments | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter telephone conversation or screening call. One described it as a freeflow chat about problem-solving approach and past experience. Be ready to explain what you have built and why, and ask about the number of rounds and expected timeline early.
Several candidates mention an assessment. One described a 40-question aptitude test with a 20-minute limit, where the questions were easy but time pressure filtered people. Another was sent a cognitive test and personality assessment, and one mentioned a final UCAT aptitude test. Placement in the process differs between reports, so confirm with your recruiter.
Reported coding questions include Find Minimum in Rotated Sorted Array with an O(log n) requirement, and IPv4 address validation. One candidate called this round significantly harder than the aptitude test. Another was rejected here after not solving the problem. Practice binary search variants and string handling, and talk through your reasoning aloud.
Candidates report conceptual technical rounds on OSI layers, sorting algorithm complexity, UDP versus TCP, DBMS and SQL, API design, and a calendar-app system design prompt. One five-interview loop had a different interviewer and topic in each 45-minute slot. Another candidate said some questions lacked clear requirements, so asking clarifying questions may help.
Reports mention hiring manager, VP, or HR conversations near the end. Outcomes varied: two Software Engineer offers and three no-offer results. One of those came after three weeks of silence, and another came after about four months when the role was closed. An MTS candidate reported about three weeks from recruiter call to signed offer. Follow up politely and ask for decision timelines.
