Company: Arcon

Job Profile: Software Developer

Offer Type: Internship + Placement

Location: Andheri East, Mumbai.

Placement Process:

The entire selection process took place in their office, creating an atmosphere of anticipation and focus. We
were asked to report by 11 AM, and the day’s events concluded by 6 PM. It was a long, eventful day, broken
down into multiple stages, each testing different skills.

1) Aptitude Test:
The first challenge was an aptitude test—24 questions to be solved in just 30 minutes. The difficulty level
ranged from easy to medium, but there were a few tricky ones that kept us on our toes. The questions were a
blend of mathematical concepts, including probability, logical problems, and a few coding-related ones that
touched on data structures. There were also SQL queries to interpret and questions on OOP fundamentals.
While most questions could be managed with a clear head, a couple demanded extra thought and were likely
designed to test deeper problem-solving abilities.

2) Coding Test:
Next came the coding test. We were tasked with solving five questions within 35 minutes. For each, we had to
write pseudo-code, except for one that required a direct answer—an interesting problem about doors and
multiples (100 doors, each opened or closed based on multiples of numbers from 1 to 100, and we had to
figure out how many would remain open). One problem was a variation of the classic LeetCode "Stock Buy
and Sell - 1", while another dealt with finding anagrams from a set of strings. Then, there was a question on
matching parentheses—definitely a logic-based brain teaser. There was one more problem, but I can’t recall
the specifics at the moment. The challenge here was heightened by the fact that everything had to be done on
pen and paper, which meant no quick fixes or auto-corrections—just raw thinking and careful planning.

3) Interview Round 1:
For some, the first interview was in-person; for others, it was conducted online. This round primarily focused
on projects and SQL knowledge—indexes, queries, and the like. The interviewer dove deep into every project
or skill mentioned in my resume, dissecting each one to understand my level of expertise. It wasn’t a nerve-
wracking experience, though. The interviewer was genuinely curious and very patient, creating a friendly
environment that allowed me to explain my work in detail. I could tell they were looking for depth and clarity
rather than just surface-level understanding.

4) Interview Round 2:
The second interview was a bit more technical. It started with logical reasoning and basic data structures and
algorithms. I was asked to insert values into a binary search tree and predict what the final tree would look
like. Another question asked if binary search could work on an unsorted array, which led to a discussion about
sorting and search algorithms. There were also two puzzles thrown in for good measure, designed to test my
problem-solving agility. SQL came up again, with questions about different types of indexes and how they
function. Inorder tree traversal was another key topic, and I had to demonstrate my knowledge in a way that
showed both theoretical understanding and practical application. And at the end, space and time complexity of
various sorting algorithms. When should one prefer a particular sorting algo.
5) Interview Round 3:
The final interview was a brief, informal chat, lasting less than 10 minutes. It was more about assessing my
thought process and less about grilling me on technical concepts. One interesting question that came up was:
"You are organizing a football tournament, how would you create a database schema for efficient
management?". There were also questions about the workings of DFS (Depth First Search) and BFS (Breadth
First Search), but they were presented in a very relaxed manner.

By the end of the day, I had learned a lot, both from the questions posed and the experience itself. One crucial
tip for anyone going through a similar process: always have a few questions prepared for the interviewer.
Whether you ask the same questions in every round doesn’t matter; it shows genuine interest in the role and
the company.

3 students were selected.

Useful Tips and Resources for the Prep:

Maintain a Strong CGPA: Aim for a CGPA above 8. While it might not be explicitly mentioned, many
companies use this as a hidden criterion during shortlisting, even after the HR round.
Tailor Your Resume: Include only projects and experiences that you can explain confidently. Avoid
listing anything that sounds impressive but leaves you struggling when asked to elaborate.
Consistent DSA Practice is Key
Know Your Language Inside Out: If you’ve mentioned Java on your resume, be sure you understand the
architecture and inner workings of the Java collections framework.
Don’t Neglect SQL: SQL is often underestimated, but it's important. The Top 50 SQL problems on
LeetCode should give you solid practice.
Additionally, make sure to review interview questions for any frameworks or tools mentioned on your
resume—Git and GitHub are common topics that could come up.
Non-Tech Roles: If you're preparing for roles outside the technical realm, practicing guesstimates and
puzzles are a must.

Never let early setbacks discourage you if you don’t crack interviews in the first few weeks of the placement
process. It took me about 15 interviews before I finally succeeded in landing this role. Our Training and
Placement Office (TPO) did an incredible job by bringing in a wide range of companies, and I made it a point
to attempt each one. Every interview provided valuable lessons that I carried forward, helping me improve
with each attempt. Eventually, you’ll reach a point where you confidently navigate interviews and online
assessments with ease. Keep trying!