Say each answer aloud and swap the example for something you did. For questions that show up in every process, use the HR interview questions for freshers guide.
Contents
Technical/role knowledge
1. What is a requirement, and how is it different from a solution?
A requirement states who needs what outcome, and why. A solution is one way to meet it, such as a screen or a report. If you start with the screen, ask what would still be true if that screen never existed.
The requirement is that a placement officer can see which students have not submitted a form. A dashboard is one solution. A downloadable list could be another, and I would not lock the solution into the requirement.
2. What belongs in a user story?
Name who it is for, what they can do, and why it matters, then add acceptance criteria someone else can test. The familiar sentence template is optional. A story without a test is a wish.
As a student I can reset a password so I can get into the portal without waiting for an office. Done means the checks in the acceptance criteria pass, not merely that a button exists.
3. When is a process flow more useful than a numbered list?
Use a flow when the path branches, someone hands work to someone else, or a decision sends people back. A list hides those forks. Keep the flow to actors, steps and decisions, and do not draw boxes for their own sake.
A leave request that can be approved, rejected or sent back needs a flow. A straight list would look as if every request ends the same way.
4. What is scope, and what counts as out of scope?
Scope is the set of outcomes you agreed to deliver in this piece of work. Out of scope is a written place for ideas that are real but not in this delivery, so they are not lost and not silently added. Say where an out-of-scope item goes next, even if the answer is a later list.
This release lets students submit the form and lets staff export it. Changing the college branding is out of scope. I would park that request on a list the sponsor can rank later.
5. How do functional and non-functional requirements differ?
Functional requirements say what the system does. Non-functional requirements say qualities such as who can open it, whether actions are audited, or how fast a step needs to feel. If a quality needs a number, say you would agree that number with the people who operate it rather than invent one.
Submitting the form is functional. Restricting the export to placement staff, and keeping a record of who exported it, is non-functional. I would not invent a response-time target in the interview.
Problem solving and scenario
6. A stakeholder asks for something that contradicts an earlier decision. What do you do?
Write both statements down and ask what outcome changed. Do not quietly pick the newer sentence. Record the decision and who made it, so the people building the work are not left with two versions.
Last week the form was optional. Today someone asked to block applications until it is filled. I would show both lines to the sponsor and update the story only after they choose.
7. Two departments define an active student differently. How do you proceed?
Put both definitions on one page and show a count under each. Ask which decision each definition is for, because a fee status and a placement status may both be legitimate. Do not average them into a third meaning nobody uses.
Finance called a student active when fees were clear. Placement called them active when they were eligible to apply. I would label both counts and use the placement definition on the placement report.
8. The brief is only that placements are down. How do you frame the problem?
Define the metric and the comparison before you suggest a cause. Split the drop by a stage or a cohort you can actually see. Say which split you would want if the data is missing, and do not announce a fix in the first minute.
I would ask whether we mean offers, applications or students who sat for drives, and compared with which period. If offers fell and applications did not, I would look at the interview stage rather than at awareness.
9. How would you write acceptance criteria for a password reset?
Write checks a tester can run: request the reset, receive a message that follows the privacy policy, use a link that expires, set a password that meets the agreed rules, and sign in with the new one. Mention what happens to older sessions only if the product does something with them. Do not add security claims you cannot test.
I would include an expired link that fails, a weak password that is rejected, and a successful sign-in with the new password. I would also agree whether the message reveals that the email exists.
10. A developer says the requirement is unclear in the middle of the build. What do you do?
Stop the guessing. Write the ambiguity as a question with two or three options and the consequence of each. Get a decision, update the story, and tell the people who already built against the old reading.
The story did not say whether a blank phone number blocks submit. I would offer block, warn, or allow, note that block will stop some students, and update the criteria the same day.
HR and behavioural
11. Tell me about a time you turned a messy brief into a plan.
Describe the brief in one sentence, the questions you asked, and the one-page version other people used. Keep the focus on what became clearer, not on how busy you were. A college fest, a group assignment or a club works if you did the clarifying.
Our fest brief said to improve footfall. I asked which day and which stall, wrote a one-page plan with owners, and we stopped adding ideas that did not have a person. The useful part was the cut list.
12. Describe a disagreement with a teammate about the work.
State the issue, how you made the options visible, and how you decided. Include what you did to keep the work moving after the decision. Leave out insults and score-settling.
We disagreed on whether to survey people before booking a speaker. I wrote the cost of booking first and the cost of waiting a week. We waited, and I owned the short survey so the delay was not just a veto.
13. Everything is called urgent. How do you choose what to do first?
Name impact, a real deadline, and what slips if this goes first. Ask which urgency is a date and which is a mood. Say the order out loud so the person whose item waits knows why.
I would do the item that blocks a drive happening this week before a report that has no date. I would tell the report’s owner the order and the day I would start theirs.
14. Why business analysis?
Talk about translating between people who want an outcome and people who have to build it. Use one example where a vague request became something testable. Do not claim a certification or a job title you have not held.
I like writing the sentence that both sides can accept. In a group project I turned a request for a better app into three testable stories, and that is the work I want to keep doing.
15. Tell me about a time you had to say not yet.
Say what you declined, the reason, and where the request went so it was not ignored. A refusal with a parking place is easier to defend than a flat no. Show that you told the person directly.
A classmate wanted a new report during the week we were finishing the form. I said not in this pass, wrote it on the later list, and told them who would rank that list. The form shipped, and the report was still written down.