DEV Community: Vrajkumar Patel

GrowExx Jr.Software Engineer Interview Experience | Ahmedabad FRESHER 7.2 LPA

Vrajkumar Patel — Sun, 28 Dec 2025 16:52:05 +0000

Overview of the Company

Company Name: GrowExx

Role Offered: Jr. Software Engineer
There were three tracks: MERN, AI/ML, and LAMP
Interview Type: On-Campus (In-Office)
Offer Details: ₹7.2 LPA (FTE), ₹10K stipend (Internship)
Location: Ahmedabad
Total Rounds: 4
Recruitment Process: Online Assessment → Task Assignment → Technical Round 1 → Technical Round 2 + HR

Interview Rounds

Round 1: Online Assessment (OA)

Duration: 2.5 hours

The OA included MCQs from multiple domains. It started with Aptitude, covering logical reasoning, verbal reasoning, quantitative aptitude, etc.
Then it moved to CS Fundamentals like Data Structures, OS, and DBMS. There were separate MCQ sections for different tech stacks such as Python, React, Node/Express, PHP, and even a section for the Machine Learning track.
The time was sufficient to attempt all questions.

Tips for this round:

Practice popular interview MCQs from online platforms.
Track/role allocation in the next round depended on performance in each individual section.

The next day, the shortlisted candidates were announced, and I was selected.

Round 2: Task Assignment

Format: On-site
Duration: 2–3 hours

We were assigned roles based on OA performance, and I got MERN, which was also the role I had applied for.

Task:
We were given a server logs text file, and we had to generate the output in JSON format, including:

Number of successful requests
Number of error requests
Payload size
A few more properties (I don’t remember all of them)

I was able to build around 80% of the logic. We were allowed to use Google/documentation, but AI tools were not allowed.

After waiting for about 5–10 minutes, I received confirmation that I had cleared the round.

Tips for this round:

Have a strong command over your chosen programming language (Python/JavaScript).
Be comfortable with parsing, logic building, and data formatting (JSON, aggregations, etc.).

Round 3: Technical Round 1

Format: On-site
Duration: 30 minutes

There were two interviewers. I started with my introduction, and then they went through my resume. They asked about my projects and followed up with questions like:

How I deployed my web app using AWS
What AWS Lambda is
One SQL query involving multiple joins + GROUP BY

I explained the SQL query thoroughly. After discussing my research project briefly, they concluded the interview and asked if I had any questions.

I asked about the kind of opportunities the company provides, and they explained the work culture and growth opportunities, which cleared my doubts.

Tips for this round:

Know your resume projects deeply and be ready for follow-up questions.
Prepare a few good questions to ask the interviewer beforehand.

Later, I got to know that I was the first one to clear all the rounds so far only one round was remaining.

Round 4: Technical Round 2 + HR

Duration: 20 minutes

This was a rapid-fire round. The Senior Manager and HR Head were both present.

They asked me to introduce myself again, and then the Senior Manager started asking questions one by one based on my resume. I answered quickly and clearly, and he seemed satisfied.

The HR round included questions on:

Family background
Motivation for learning
Strengths and weaknesses

I had already prepared behavioral answers, so I responded confidently.

Tips for this round:

Improve communication skills and learn to present yourself clearly.
Build confidence by giving mock interviews.
In my case, I had already given 4–5 interviews earlier, which helped a lot.

Outcome

✅ Result: Selected!

After two days, I received the selection email. It felt great because I had been preparing consistently for the past 3–4 months, and in the end, all the hard work paid off.

Special Mention

The founder, interviewers, and HR team were very supportive throughout the process. Since it was an on-site drive, the entire process was managed smoothly and professionally.

Follow for more updates!

https://x.com/ilovecompiler

Oro Money | Oncampus Interview Experience | 10LPA - GIFT CITY GANDHINAGAR

Vrajkumar Patel — Sat, 27 Dec 2025 14:53:58 +0000

Overview of the Company

Company Name: Oro Money

Roles: Frontend Engineering Intern, Backend Engineering Intern
Interview Type: On-Campus (In-Office)
Offer Details: 8–10 LPA for FTE, ₹25K stipend for interns
Location: GIFT City, Gandhinagar
Interview Duration: 3 rounds
Recruitment Process: Resume Screening → Technical Round 1 → Technical Round 2 + HR

Interview Rounds

Round 1: Resume Screening

I applied for the Backend Engineering role. Only 47 students were selected, and I was one of them.

Tips for this round:

Use an ATS-friendly resume template (or your institute template), but keep it concise - 1 page only.
Add projects aligned with the role you’re applying for.
Mention key technical skills clearly.

Round 2: Technical Round 1

Format: On-site (GIFT City)

Duration: 1 hour

Key Topics Covered:
First, I was asked to introduce myself. Then the interviewer went through my resume and asked about my background and some basic questions from the projects section. He asked about my previous internship—my responsibilities, role, and what I worked on.

He asked about Node.js eventloop its architecture and How it works. Some basic questions related to React states, hooks and components.

Then he moved to DSA. He asked a LeetCode medium question based on HashMap and told me to code it in my VS Code. I read the problem and within 5 minutes, I came up with a brute-force approach and implemented it. Then he asked me to optimize it to linear time complexity. I took around 15–20 minutes and submitted the optimized solution.

He was satisfied with my approach and moved forward. Then he asked fundamental questions on databases, mainly around SQL, transactions, and normalization. After that, he moved to OOP design and asked me to design an Instagram-like system using OOP principles.

Finally, he asked some puzzles and scenario-based tricky questions.

Tips for this round:

Go through puzzles from GFG.
Revise OOP design questions like Instagram system design and basic DB design + normalization.
Practice Easy–Medium LeetCode problems.
Revisit your projects and CS fundamentals.

After waiting for 5–10 minutes, I got a message that I was moving forward to the next round.

Round 3: Technical Round 2 + HR

Duration: 1 hour

The Tech Lead was in this final round. First, he asked me to introduce myself and then moved to my resume.

Key Topics Covered:
He first asked about my research project mentioned in my resume, so I explained it in detail. It was based on database query optimization.

Then he pointed at a water bottle and asked me to write a class for a bottle. (I didn’t expect this, but I managed to write 4–5 properties and 3–4 methods.)

Then he moved to system design:

Database locking mechanisms
Mutual exclusion and semaphore-related questions
A scenario-based BookMyShow system design problem

I took some time and shared my thoughts and approach. That was it.

Outcome

Result: Rejected

After two days, I got an email saying only 4 people were selected, and I was 5th on the priority list. Sad, but that’s reality. I contacted the interviewers and a senior for feedback, and they told me that I wasn’t a cultural fit for the role.

Key Takeaways

Even though I wasn’t selected, the experience boosted my confidence since I reached the final round. It also helped me improve my communication and resume-building skills. The process took the whole day, and I was exhausted, but overall it was a good experience.

Intuitive.ai (Intuitive.Cloud)-Oncampus Interview Experience | 10LPA

Vrajkumar Patel — Sat, 27 Dec 2025 13:27:42 +0000

Overview of the Company:

Company Name: Intuitive.Cloud

Roles: Cloud & DevOps, Modernization/Migration (SDE), Data Engineer and AI/ML, Network Security/Cyber Security
Interview Type: On-Campus
Offer Details: 10 LPA for FTE, 20K stipend for interns
Timings/Location: Night shift (Ahmedabad)
Interview Duration: 4 rounds
Recruitment Process:
Online assessment, Group Discussion, Technical Round 1, HR + Technical Round 2

We had some prior knowledge about the company as the placement committee had conducted a session with the CEO & CTO before the placement drive.

Interview Rounds:

Round 1: [Online Assessment]

Duration: 90 Minutes
Types of Questions:

Section A: CS Fundamentals MCQs
Section B: Aptitude & Logical Reasoning
Section C: DSA Coding Question (Easy to Medium)
Section D: Scenario-Based Coding Question

Tips for this round:
Focus on Aptitude and Speed Math questions.
Solve Java/OOPS principles MCQs from GeeksforGeeks (GFG).

I was selected for the next round.

Round 2: [Group Discussion]

Format: On-Site

There were groups of 5 students. We introduced ourselves first, then began a discussion on "Can Art & Pop Culture benefit our society?"

I spoke 2 to 3 valid points, and after 15 minutes, a list of selected students was announced. I was informed that only two people were selected for the Cloud/DevOps role, and I was one of them.

Round 3: [Technical Round 1]

Format: On-Site
Duration: 30 Minutes
Key Topics Covered:

The interview was entirely focused on Cloud/DevOps, as I had applied for that role.

I started by introducing myself, and the interviewer then moved on to my projects. I had worked on a database research project and completed some projects using AWS.

Example Question(s):

She asked me basic to intermediate questions about AWS, such as how I deployed my backend app on AWS EC2, what AWS Lambda is, how it differs from EC2, and to explain serverless architecture. She also asked questions about S3 buckets, among others.

Tips for this round:

Explain your projects thoroughly, as they may ask follow-up questions based on your answers. Prepare in advance and revise questions asked in interview experiences relevant to the domain you're applying for.

After three hours of waiting, I received a message from the placement team informing me that I am not moving forward.

Outcome:

Result: Rejected

I wasn't surprised by the rejection because I had sensed it during the interview itself. The company selected 3 students for the SDE role and 1 for the Cloud role. Later, the Cloud student was moved to the SDE profile, which was the company's decision.

Key Takeaways:

Even though I wasn't selected, the experience boosted my confidence as I cleared multiple rounds for the first time. It also helped me improve my communication and resume-building skills. I learned the areas in which I need to improve.

Final Thoughts:

Overall, it was a good experience. The interviewers were professional and punctual, which was the most important factor for me.

Advice for Future Candidates:

If you are applying for roles in Cloud/DevOps, AI/ML, or Data Migration, prepare thoroughly. Go deep into the projects you're working on, as it's essential to be over-prepared rather than making mistakes during the interview.