Company OAsDSA SheetAll ProblemsPlacement DataInterview ExperiencesPremium
OAHelper

Built by students, for students — practice company-specific OAs, DSA sheets, and real interview experiences to land your dream role.

© 2026 OAHelper.in·Terms·Privacy·Refunds·Trust & Safety·Contact·
Ready to crack your next OA?

Practice company-specific questions trusted by thousands of students across India.

Start PracticingGo Premium
OA Practice·DSA·Placements

Disclaimer: OAHelper is an independent educational platform. We (oahelper.in) do not own the images or questions shown. Content is uploaded by users.

E

Eqtechnologic

Software Developer (Implied)

Interview Date

—

Result

Not Specified

Difficulty

Easy (coding problems in online assessment) to Har

Rounds

5 stages (Online Assessment, 3 Technical Interviews, 1 Technical Test)

Drive Type

On-Campus, Full-Time

Topics asked

MCQsCoding (easy to medium)ProjectsHigh-Level Design (HLD)Low-Level Design (LLD)PostgreSQLPrisma ORMSQL (fetching dataJOIN operations)HashMap implementation (OOP)Project ArchitectureFlowchart analysisMicroservicesSDLCJava vs. COOPMemory Management (matrix storage)Internship Experience

Detailed experience

Role: Software Developer (Implied)

College: Not Specified (On-Campus)

Interview Date: Not Specified

Interview Type: On-Campus, Full-Time

Result: Not Specified

Difficulty: Easy (coding problems in online assessment) to Hard (technical rounds, especially HashMap implementation)

Rounds: 5 stages (Online Assessment, 3 Technical Interviews, 1 Technical Test)

Topics Asked: MCQs, Coding (easy to medium), Projects, High-Level Design (HLD), Low-Level Design (LLD), PostgreSQL, Prisma ORM, SQL (fetching data, JOIN operations), HashMap implementation (OOP), Project Architecture, Flowchart analysis, Microservices, SDLC, Java vs. C++ OOP, Memory Management (matrix storage), Internship Experience

Experience:

This on-campus hiring experience from eQ Technologic involved multiple stages.

Online Assessment:

38 students were shortlisted for this round, which started with 15-20 minutes of MCQs where accuracy on the first attempt was crucial as there was no option to go back. This was followed by two coding problems, which were easy for the candidate but medium for some peers. Time efficiency was key.

Round 1: Technical Interview

The interviewer began with introductions and then moved directly to the candidate's projects. The candidate was asked to draw a High-Level Design (HLD) diagram for a resume project and explain the backend approach (PostgreSQL with Prisma ORM). An SQL query for fetching data from the database was also requested. The interviewer then asked for a Low-Level Design (LLD) for the B.Tech project, requiring definition of classes and explanation of workflow. A critical question involved implementing a HashMap using class-based object-oriented programming concepts.

Round 2: Technical Interview

This round also took place on the same day. The interviewer discussed project architecture in detail, provided a flowchart, and asked the candidate to determine relationships between entities, relating them to database schema design. Questions on microservices architecture were also posed. The interviewer then provided two database schemas and asked for SQL queries using JOIN operations. Additionally, a matrix storage problem (efficient memory storage and code implementation) and questions on Software Development Life Cycle (SDLC), latest process models, Java vs. C++ OOP concepts, and adaptability in switching languages were asked.

Technical Test:

The next day, a problem statement was given with a 1.5-hour time limit. The solution had to be submitted as a .txt file via email, and the test was not proctored.

Last Round Interview:

Initially assumed to be an HR round, it turned out to be another Technical Round. Questions included SQL query-related topics, detailed discussions about projects, and past internship experiences.

Major Takeaways: The candidate highlighted that a web-development-oriented (Full-Stack) resume is preferred, as AI/ML skills were of little interest. Strong SQL skills (query writing and schema understanding) and a strong understanding of OOP design principles were deemed essential. DSA was not a major focus, with easy questions if asked.

Submitted anonymously12 NOVEMBER 2025