Argil DX Interview Experience | Set 1 (On-Campus)
Question Details
Round 1 Online(30 mins + 30 mins+ 30 mins) a. Technical Aptitude b. Numerical and Reasoning Aptitude c. Coding (Backtracking and St...
Full Details
Round 1 Online(30 mins + 30 mins+ 30 mins) a. Technical Aptitude b. Numerical and Reasoning Aptitude c. Coding (Backtracking and String Permutation)
Round 2 Written Test(40 mins) 4 questions a. Number of direct and indirect reporting employees (N- Ary tree) b. Database design problem( E-R Diagram) c. Puzzle d. Basic Probability(Ant at the corner of equilateral triangle and collision prob)
Round 3 Group Discussion(30 mins) a. Demonetization and its effect on GDP b. There is no right way to do a right thing ( you can interrupt other speaker to make your point . Tip: speak relevant)
Round 4 Technical Interview 1(40 minutes) a. Concepts of OOPs b. Indepth discussion of Hackathon (Technology used, Scenario, Analytics) c. Project Discussion ( Machine Learning and Cloud Tecnology) -> Classifier and clustering difference -> SVM classifier indepth Discussion -> In Depth Discussion of J2EE Framework,MVC Architecture,Use Case -> Natural Language Processing,relevance and Project related details d. Abstraction ( Difference between Abstract and Interface) e. Polymorphism (Both static and Runtime) -
output of the code f. Coupling and the issues g. RMI and Serialisation of the object h. EJB, Servlets and JSP ( Session management, Connectivity and Control) i. Multi threading( coding)
Round 5 Technical Interview 2(2 hours) a. Coding in Java ( N-Ary Tree) and creating functions for the modified queries. b. Static- Discussion c. N- Ary Data Structure and traversals, possibility of inorder traversal id data in subsequent levels are not sorted. d. Data Structures - Binary Trees and Binary Search Trees( In Depth Dis.) e. Spiral Level Order Traversal( Iterative and Recursive) f. Function calling and Stacks(Discussion) g. Database redesign based on the Query modification of the written test h. Joins and Nested Queries comparison i. Data structures use in various cases of the Database Management j. Some Networking Questions ( OSI Layers, Data Transfer Mechanism detailed, Masking, Subnetting, supernetting, Aloha, slotted Aloha) h. Java related output questions ( Polymorphism, Main method overloading) i. Java Pass by Value or Pass by reference?Justify ( Swap method -String, Array, User defined Objects, Primitive types values transfer) in depth discussion j. Wrapper classes k. operating system interaction with java code l. Platform dependence of Java and c++ m. sizeOf function use n. C++ rapid fire o. Pointers in c++ p. Association, Aggregation and composition their difference with Inheritance r. Inheritance in java and c++ difference ( cause and effect) s. Final, Finally, Finalize t. JRE,JVM, JDK
Round 6 HR(10 mins) a. tell me abt yourself b . Strength weakness c. Leadership and asoociations d. Business perspective of a case e. Non technical subjects and basic question(CRM and Economics)
About This Question
This is a reported interview question from a argil dx interview for a eng manager role during the phone screen round reported in 2017.
It covers the following topics: Ml, Trees, Strings, Binary Tree, Binary Search, Sql, Backtracking, Recursion, Os, Probability Stats, Arrays .
Difficulty rating: Easy
About Argil Dx Interview Reports
This question was reported by a candidate who interviewed at Argil Dx. 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 Argil Dx are the higher-signal extractions to take from this report.
For broader preparation context, the Argil Dx 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 Argil Dx reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Argil Dx 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 Argil Dx 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.