What are the most common interview questions for freshers?

What are the most common interview questions for freshers?

The most common fresher interview questions in an Indian software drive are not a mystery list of riddles. They are a small set of HR questions, plus a project walk-through, plus whatever technical page matches the role. “Tell me about yourself,” “why this role,” “walk me through your project,” “what is your strength and your weakness,” and “what are your salary expectations” appear constantly. The technical half depends on the job: Python, Java, SQL, JavaScript, React, Power BI, or a short DSA round. This page answers the questions that show up in almost every process. The specialist pages answer the coding.

A good answer is short, specific, and tied to something you did. A bad answer is a paragraph about passion with no example. Practise out loud. The notes below are a preparation guide for students and freshers, including Asmorix learners in Pondicherry. They are not a script a company is required to follow.

How do you answer “tell me about yourself”?

Use four beats and about a minute. Your degree and city. The role you are aiming at. One project, with the user and the tool. What you want to learn in the first year. Stop. “I am a hardworking person since childhood” spends the minute without giving the interviewer a hook. “I finished a B.Sc. in Villianur, I built a small order tracker in Python and SQL, and I want a junior developer role where I can work on that stack” gives them a hook. They can ask about the tracker. That is the point.

Do not recite the entire resume. Do not start with school marks unless they ask. Do not apologise for the college name. The project and the role are the content. If you have a gap or a non-IT degree, put one calm sentence in this answer so it is not a surprise later. “I finished B.Com and then trained in Java because I wanted a software role” is clearer than hoping they will not notice.

How do you answer “why this role” and “why this company”?

Why this role means why this work, not why any salary. A tester who likes breaking flows, a Java fresher who wants APIs, an analyst who likes reconciling a number: pick the true reason and attach it to the project. Why this company means you looked at something real: a product you used, a service line that matches your project, or a graduate program whose stack you can name. “It is a dream company and a great brand” fits every firm and therefore fits none. If you do not know the firm, say what you read on the drive announcement and one question you hope to ask them. Curiosity is allowed. Flattery is thin.

Pondicherry students interviewing for Chennai or Bengaluru roles should be ready for “are you willing to relocate?” Answer with a real constraint. If you can move, say so. If you can move after a date, say the date. A vague “anywhere in India” that you will reverse after the offer wastes both sides.

How do you walk through a project when the question is not technical yet?

Five sentences. Who the user was. What they could not do. What you built, in tools you can open. What went wrong. What you would change. Then wait. The technical panel will pull a thread. The HR panel will listen for whether you did the work. “We built an app in a team” is weaker than “I owned the login form and the SQL that listed unpaid orders.” Claim the part you owned. Do not claim the part a teammate owned. A follow-up on their part will show the gap.

Bring the project in a state you can run. A repository you cannot clone, a Power BI file that does not open, or a Spring app that does not start will undo a fluent story. The night before, run it once. The specialist pages show how to go deeper once they ask: Python, Java, SQL, JavaScript, React JS, Spring Boot, Power BI, and DSA.

How do you answer strength and weakness?

A strength needs evidence. “I am a quick learner” is a claim. “I learned SQL joins in two weeks and used a left join to find students with no scores in my project” is evidence. Pick a strength the role uses. A weakness needs a real habit and a current fix. “I am a perfectionist” is a costume. “I used to start coding before I wrote the query result I expected, and I now write one example row first” is a weakness that shows a method. Do not offer a weakness that is a requirement of the job, such as “I hate talking to people” for a support role, or “I do not like coding” for a developer role.

One strength and one weakness are enough. A list of five strengths sounds rehearsed and leaves no time for the example. The example is the answer. The adjective is the label.

How do you answer salary expectations?

Separate CTC from in-hand before you say a number. CTC is the company’s yearly cost. In-hand is the monthly credit after employer costs and your deductions. If you do not know the difference, read the CTC full form guide before the interview, not during it. For a fresher, a calm answer is: “I have seen public fresher bands for this kind of role, and I am more concerned with the role and the fixed pay. I am happy to look at your band.” If they insist on a number, give a range you can explain, and say it is CTC, not in-hand. Do not invent a precise monthly figure you computed by dividing a headline by twelve.

Company-specific planning ranges, when you need them after the interview, are on the salary guides for TCS, Accenture, and the other fresher pages linked from the blog. Those ranges are not your demand in the interview. They are context so a later offer letter does not surprise you. In the room, curiosity about the band is safer than a speech about what a cousin earns.

How do you explain a gap, a backlog, or a career switch?

Say what the gap was, in one sentence, without a long apology. Then say what you did during it that is relevant: a course, a project, a family responsibility you handled, or work that paid the rent. Then stop and return to the skill you have now. A backlog is similar. “I had two backlogs in the second year, I cleared them, and my recent project is the work I want judged” is adult. A ten-minute defence of the subject you failed is not. For a switch from commerce or arts into software, name the training and the project, and do not pretend the degree was computer science. The interviewer can read the form. They are checking whether you can learn the work.

If the gap includes a job you left quickly, say what you learned about the kind of work you want. Blaming a manager at length makes the next manager imagine being blamed. Keep it factual and short.

How do you answer a conflict or a failure question?

“Tell me about a time you disagreed” and “tell me about a mistake” are the same shape. Situation, what you did, what changed. Pick a small true story from a project or a team assignment. “We disagreed on the database key, I showed a duplicate row, we switched to a surrogate id” is excellent. “I have never failed” is not believable. “I failed an internal test because I had not practised joins, I spent a week on left joins, and I cleared the retest” is believable and useful. Do not pick a story whose lesson is that you refuse feedback.

Keep names out if the story criticises a classmate. Describe the decision, not the person’s character. Panels are hiring a colleague. Colleagues who narrate other people as villains are a risk.

What should you ask the interviewer?

Ask one question that helps you do the job. What does the first ninety days look like? Which team or technology do freshers join after training? How is the training period paid, if there is one? What would a strong fresher be able to do alone after three months? Skip “how many leaves” as the first question, and skip a question whose answer was on the slide they just presented. If the round is ending and you are confused about the role, ask whether the work is development, support, or testing. That question prevents a bad join. It is allowed.

Write the answer down after you leave. Memory edits the package and the role by the evening. The note is what you compare with the offer letter.

How do the HR round and the technical round differ?

The technical round asks you to do the skill: a query, a function, a model, a dry run. The HR round asks whether the story is consistent, whether you will join, and whether you can work with people. Candidates who tell HR a project they cannot open in the technical round create a contradiction. Use the same project in both. In HR, stay at five sentences. In the technical round, open the file. If you do not know a technical answer, say so. Do not invent a function and hope. HR is not fooled by a confident wrong stack either, because the technical panel writes it down.

Group discussions and aptitude tests sit beside these rounds in many drives. For a group discussion, make one clear point, let others speak, and disagree with the point rather than the person. For aptitude, timed practice beats a last-night formula sheet. This page cannot replace that practice. It can stop you spending the last night only on aptitude and then freezing on “tell me about yourself.”

What do you do the day before and the morning of the interview?

The day before, run the project, revise the one-minute introduction, and revise the specialist list for the role you were actually called for. Sleep. A new topic opened at midnight rarely becomes an answer you can code. The morning, arrive early enough that you are not apologising as you sit down. Keep a notebook. When they explain the role, write the team and the stack. When they explain pay, write CTC and ask what is fixed. You can smile and still write.

Clothes and camera position matter less than the project, and they are not nothing. For an online round, test the link, the microphone, and a second way to share the screen. For a campus room, carry a pen. These details do not get you the offer. Forgetting them can distract a round you were ready for.

How do you prepare this week if the drive is soon?

Day one is the one-minute introduction and the five-sentence project, recorded on your phone. Listen once. Cut any sentence that does not contain a fact. Day two is the strength, the weakness, the gap if you have one, and the relocate answer. Day three is salary language: CTC versus in-hand, and a range you can say calmly. Day four and five are the technical page for the role, coded from a blank file. Day six is a mock with a friend who is allowed to interrupt. Day seven is a light review and an early night. If you are training at Asmorix, use placement preparation to rehearse the interruption, not to collect another list of questions.

The common questions are common because they reveal whether the technical skill belongs to a person who can join a team. Answer them with the same specificity you use for a join or a hook. Specific, short, and true will beat a long answer you memorised from a page you do not believe.

How do you handle an online interview specifically?

Join five minutes early. Keep water off to the side, not beside the laptop where a reach can cut the call. Look at the camera when you introduce yourself, and look at the screen when you read a snippet. Tell the interviewer if you are about to share a window, and close anything you would not want on camera before you share the whole desktop. A noisy room is a real problem. Headphones help. If the connection drops, rejoin and continue the same answer. Do not restart your life story. A one-line “I will continue from the project bug” is enough.

For a coding screen, practise in the same style of editor: a plain box, no autocomplete if the company disables it. Font size large enough that a watcher can read it. Talk while you type. Silence looks like a freeze on video even when you are thinking. Say “I am checking the empty case” so the pause has a label.

How do you talk about notice period, joining date, and other offers?

If you are a fresher with no job, your joining date is the date you can travel and start, not a fictional notice period. If you are on an internship or a bond, say the date you are free and whether a buyout exists. Do not invent a notice period because it sounded professional. If you are holding another offer, you can say you are in process elsewhere without turning the conversation into an auction. Share numbers only if you are comfortable and they are true. A bluff that collapses at the offer stage damages trust. Ask them for their timeline too. “When should I expect a decision?” is a fair question.

Read the written offer later with a calm head. Verbal CTC in the interview is not the annexure. Compare fixed pay, city, and the work, using the project you already described. A higher headline for a role you cannot explain in six months is a weaker offer than a clear role you can grow in. Decide with the letter, not with the relief you feel in the lobby.

What if the interview is in English and you usually think in another language?

Short sentences are an advantage, not a limitation. Prepare the introduction, the project, and the strength in the language of the interview, out loud, until the words are yours. You do not need decorative vocabulary. You need accurate verbs: built, queried, fixed, tested. If you miss a word, describe it. “The function that runs when the button is clicked” is fine if the word handler slips. Ask for the question again if you did not hear it. Guessing the question and answering a different one is the expensive mistake. Panels in India hear many accents. Clarity beats accent. Pause, then answer.

Write down hard questions after the round in the language you revise in, and practise the answer once in the interview language the same day. That loop improves the next drive faster than another hour of silent reading.

Put the answers on one card

Write six lines on paper the night before. Introduction in one sentence you can expand. Project user and tool. Strength with evidence. Weakness with the fix. Joining or relocate constraint. One question you will ask them. That card is the whole common-question set. If a new HR question appears, it usually hangs off one of these lines. “Where do you see yourself in five years?” hangs off the role line: you want to be trusted with a larger piece of the same work, not a fantasy title. “Why should we hire you?” hangs off the project line: you can show the work this week, and you know what you are still learning.

Keep the card factual. Remove any line you would be embarrassed to demonstrate. Then sleep. In the room, answer the question they asked, then stop. The extra minute people add after a good answer is where invented details appear. A stopped answer can be followed by their next question. A rambling answer uses up the time you needed for the project. Specific, short, and true is the standard for every prompt on this page.

Put the answers on one card

Write six lines on paper the night before. Introduction in one sentence you can expand. Project user and tool. Strength with evidence. Weakness with the fix. Joining or relocate constraint. One question you will ask them. That card is the whole common-question set. If a new HR question appears, it usually hangs off one of these lines. “Where do you see yourself in five years?” hangs off the role line: you want to be trusted with a larger piece of the same work, not a fantasy title. “Why should we hire you?” hangs off the project line: you can show the work this week, and you know what you are still learning.

Keep the card factual. Remove any line you would be embarrassed to demonstrate. Then sleep. In the room, answer the question they asked, then stop. The extra minute people add after a good answer is where invented details appear. A stopped answer can be followed by their next question. A rambling answer uses up the time you needed for the project. Specific, short, and true is the standard for every prompt on this page.

If a panel member is silent, do not fill the silence with a new claim. Ask whether they want the project in more detail or a different example. Silence is often them writing. Candidates who fear silence invent a second project and then cannot open it. One true project, offered again in more depth, is the safer use of that pause. Leave with the date they gave you for a decision, and compare the later letter with the notes you took, not with the mood you left in.

Related reading: Python interview questions, Java interview questions, SQL interview questions, CTC full form.

These answers are a preparation guide for students and freshers, including learners at Asmorix in Pondicherry. A company may ask a different follow-up. This page is not a leaked paper and it is not a promise of a result. Say the short answer, show one example, and revise the same day any question you could not code or click.