Interview Questions by Subject: Java, Python, SQL, DSA, Cloud, AI

Last updated: 13 October 2026 · By the Asuraa Team

Quick answer: Fresher technical interviews in India draw on one programming language, OOPs, DSA, DBMS and SQL, operating systems and computer networks, plus the tools of your target role, such as React and Node for web, Excel, Power BI and statistics for data, or AWS for cloud. Prepare the core subjects first, then your role's subjects, then HR and managerial rounds.

Key takeaways

• Most fresher technical rounds in India draw on one programming language, OOPs, DSA, DBMS and SQL, operating systems and computer networks.
• Prepare the core computer science subjects first, then add only the subjects your target role uses, such as React for web or Power BI for data analysis.
• Answer technical questions with a one-line definition, the reason the concept matters and a short example or piece of code.
• Practise answers aloud in your own words, because interviewers follow up with why and what-if questions that expose memorised answers.
• Prepare HR and managerial rounds as seriously as technical ones, since many candidates lose offers there after clearing the technical round.

Where should you start?

Technical interviews for freshers in India test a predictable set of subjects: a programming language, OOPs, DSA, DBMS and SQL, operating systems and computer networks, plus the tools of your target role. Role-level interviews then go deeper into one area. Prepare the core first, then your role.

1. Understand how technical rounds work: how to prepare for technical interview questions.
2. Master one language: Java or Python.
3. Cover the CS core: OOPs, DSA and DBMS.
4. If you are taking a mass-recruiter test, practise pseudo-code questions.
5. Add the subject sets for your target role from the sections below.
6. Finish with HR interview questions and managerial round questions.

Which core computer science subjects are asked in fresher interviews?

Most fresher technical rounds draw on OOPs, DSA, DBMS, operating systems and computer networks, whatever the role. Interviewers expect a clear definition, the reason the concept matters and a short example.

Which programming language questions should you prepare?

Prepare deeply for one language you will code in, and know the basics of any language named in the job description. Expect output-prediction snippets as well as concept questions.

Which questions come up for web development and testing roles?

Web roles test the framework you will use and how the browser and server handle requests; testing roles test manual testing concepts and automation tools.

Which questions come up for data and analytics roles?

Data analyst interviews test SQL, a spreadsheet or BI tool and basic statistics, then ask you to reason through a business problem. Data scientist and ML interviews add modelling and evaluation.

Which questions come up for AI and machine learning roles?

AI and ML interviews test fundamentals of models and evaluation, then the specific stack of the role: LLMs and retrieval, NLP, vision or deployment.

Which questions come up for cloud, DevOps and security roles?

Cloud and DevOps interviews test core services, networking, access control and automation; security interviews test threats, controls and incident thinking.

Which questions come up for software, product and support roles?

These sets cover the role-level and non-technical rounds that sit alongside subject questions.

Which subjects should you prepare for your target role?

How should you practise with these question sets?

Do not just read answers. Close the page, answer each question aloud in your own words, then compare. For coding and SQL questions, write the solution yourself before checking, and run it if you can. Keep a short notes file of questions you got wrong and revisit it every few days.

Practise the answer structure interviewers like: a one-line definition, the reason it matters, and a concrete example or small piece of code. If a question has a common trap, such as output order in asynchronous JavaScript or the meaning of a p-value, say the trap out loud; it shows depth.

Connect subjects to your own work. When you explain normalization, mention how you designed tables in your project; when you explain REST, mention the API your app called. The projects and portfolio guide helps you build projects worth talking about.

Finally, learn how your target company runs its rounds. Mass recruiters and product companies test differently, and the company hiring process guides and the broader interview preparation guide cover the round structure.

What do most people get wrong about preparing interview questions?

The biggest mistake is memorising answers word for word. Interviewers almost always follow up with "why?" or "what happens if?", and a memorised answer collapses at the first follow-up. Learn the concept well enough to explain it with a different example than the one you read.

The second mistake is spreading preparation too thin. Freshers try to cover every subject, every framework and every role set, and end up shallow everywhere. Master one programming language and the CS core, then add only the subjects your target role uses. Being solid in a few areas beats being vague in many.

The third is skipping the non-technical rounds. Many candidates clear the technical round and then lose the offer in the HR or managerial round because they did not prepare simple answers about themselves, their projects and their choices. Give these rounds the same practice time you give DSA.

Related guides

• Fresher Jobs and Internships in India: How to Get Hired (2026)
• Interview Preparation Guide for India: HR, Technical and Role Rounds
• Tech Career Roadmaps in India: Every Role Explained (2026)

FAQ

Which subjects are asked in technical interviews for freshers?

Most fresher technical interviews in India cover one programming language such as Java or Python, OOPs, data structures and algorithms, DBMS and SQL, operating systems and computer networks. On top of that, interviewers test the tools of the role, for example React and Node for web developers, Excel and Power BI for data analysts, or AWS for cloud roles.

Should I prepare Java or Python for placement interviews?

Prepare the language you are most comfortable coding in, and know it deeply. Interviewers care more about clear logic, correct code and understanding of core concepts than about which language you choose. If a job description names a specific language, add its basics. Many IT services roles and Android jobs lean towards Java, while data and AI roles lean towards Python.

How should I answer conceptual technical questions?

Use a simple structure: give a one-line definition, explain why the concept matters, then show a short example or code snippet. If there is a common trap, mention it. Then connect it to something you built, such as a table design in your project. This shows understanding rather than memorisation and prepares you for follow-up questions.

What are pseudo-code questions in placement tests?

Pseudo-code questions show a short, language-neutral program and ask for its output, the number of loop iterations or the bug. They appear in the technical sections of many IT services assessments. Solve them by tracing every variable line by line on paper, and confirm assumptions about division, loop bounds and array indexing before you start.

How much DSA do freshers need for interviews?

It depends on the company. IT services interviews usually test basic arrays, strings and simple logic, while product companies go deeper into linked lists, trees, graphs and dynamic programming. A small set of patterns, such as hashing, two pointers, sliding window, binary search and BFS or DFS, covers most fresher questions. Learn the patterns rather than memorising individual problems.

Are HR and managerial rounds really important?

Yes. Many candidates clear the technical round and then lose the offer in the HR or managerial round. Prepare clear answers about yourself, your projects, your strengths and weaknesses, relocation and shifts, and why you want the role. Practise them aloud just as you would technical questions, and keep answers honest, specific and short.

Final thoughts

Strong interview preparation is layered: the CS core and one language first, then your role's subjects, then the HR and managerial rounds. Practise aloud and connect every answer to something you built. If you want feedback from someone who has interviewed candidates, book a 1:1 session with Asuraa mentors.