First job interviews are nerve-wracking — partly because of the stakes, but mostly because you don't know what to expect. The good news? Entry-level interviewers ask a very predictable set of questions. Once you've prepared solid answers for the ten below, you're ready for 80% of what you'll face.
The Framework: STAR
Before diving into the questions, learn the STAR format. It's the most reliable way to answer behavioural interview questions:
- Situation — briefly describe the context
- Task — explain what you were responsible for
- Action — describe specifically what you did
- Result — share the outcome, ideally with numbers
Keep each answer to 90-120 seconds when speaking. Practice out loud — not just in your head.
The 10 Questions
1. "Tell me about yourself."
This is the opener. Most people ramble. Don't.
Formula: Current status → relevant background → why you're here.
Example: I just graduated from the University of Edinburgh with a degree in Computer Science, where I specialised in machine learning. During my final year I built a sentiment analysis tool for social media data that got picked up by one of my professors for further research. Before that I did two internships — one at a startup in Edinburgh and one remote stint with a US-based SaaS company. I'm now looking for a full-time junior engineering role where I can go deeper on production systems. That's what drew me to this position.
2. "Why do you want to work here?"
Interviewers use this to filter out people who are applying everywhere indiscriminately.
What they want: Evidence you researched the company and have a specific reason.
Example: I've been following your work on sustainable logistics technology since you launched the carbon tracking feature last September. The engineering blog post your CTO wrote about how you approached the database sharding problem was genuinely interesting to me — that's the kind of technical challenge I want to be working on. Plus, the company's product is something I actually believe in.
3. "What are your strengths?"
Don't say "I'm a hard worker and a team player." Everyone says that.
Pick one strong, specific quality and back it with evidence.
Example: My strongest skill is breaking down complex problems into small, testable steps. During my dissertation, I was working on a dataset that kept throwing up inconsistencies and I couldn't figure out why. Instead of trying to solve everything at once, I built a systematic audit process that identified a data labelling error about three weeks in — which would have invalidated months of work if we'd missed it. That kind of methodical approach under pressure is something I've consistently leaned on.
4. "What is your greatest weakness?"
Don't say "I work too hard" or "I'm a perfectionist." Interviewers hate this.
Pick a real weakness, explain what you've done about it, and show progress.
Example: I used to struggle with asking for help — I'd spend too long trying to solve problems independently when I should have reached out earlier. I noticed during a group project that it was holding the team back, so I started setting a personal rule: if I'm stuck on something for more than two hours without meaningful progress, I ask. That's made me significantly more effective and it's something I've carried into every role since.
5. "Tell me about a time you worked in a team."
Use STAR. Focus on your specific contribution, not what the team did collectively.
Example: During my third year, I worked in a five-person team building a web application for a local charity as part of a module. Halfway through the project we hit a conflict — two team members wanted to completely redesign the backend two weeks before the deadline. I took on the role of mediator, suggested we document both approaches and score them against our timeline constraints, and we ended up with a hybrid approach that satisfied both sides without blowing the deadline. We delivered on time and got a distinction.
6. "Where do you see yourself in five years?"
They're checking two things: ambition, and whether your trajectory makes sense with this role.
Example: In five years I want to be a solid mid-level engineer who's contributed meaningfully to a product people use every day. I'm not in a rush to manage people — I want to first become genuinely excellent at the technical craft. I think this role gives me the right foundation for that, especially given the complexity of the problems your team works on.
7. "Tell me about a time you failed."
They want honesty and self-awareness — not perfection.
Pick a real failure. Take ownership. Explain what you learned.
Example: In my second internship I was asked to write a report summarising competitor pricing. I misunderstood the brief and spent a week building a detailed spreadsheet model when they just needed a two-page summary to share in a board meeting. I had to redo it in 24 hours and it was stressful. After that I made it a habit to clarify the required output format and audience upfront before starting any piece of work. It sounds obvious now, but that experience drilled it in.
8. "Why did you choose your degree / why are you applying to this field?"
Show that your choice was intentional, not accidental.
Example: I studied economics because I was genuinely curious about how incentive structures drive behaviour — why people and companies make the decisions they do. Halfway through my degree I found I was spending more time on econometrics and data work than anything else, and that's what led me toward data analytics as a career. It feels like a natural extension of what I was already doing.
9. "How do you handle pressure or tight deadlines?"
Give a specific example, not a general claim.
Example: My last internship had one particularly rough week — three deliverables due at the same time, one of which had just changed scope on the Monday. My approach was to block my calendar, rebuild a priority list from scratch, and communicate early with the relevant stakeholders that one of the three would need a deadline extension. Being upfront about it early meant we had time to adjust rather than scrambling at the last minute. Everything got delivered within the week.
10. "Do you have any questions for us?"
Always have questions. This is not optional. Candidates who say "no, I think you've covered everything" look disengaged.
Good questions to ask:
- What does the first 90 days look like for someone in this role?
- What are the biggest challenges the team is currently working through?
- How does feedback typically work here — how would I know if I'm doing well?
- What does career progression look like from this position?
Avoid: questions about salary or holidays in a first interview, and questions you could have answered by reading the company website.
One Final Thing: Practise Out Loud
Reading these answers is useful. Saying them out loud in front of a mirror — or better, recording yourself — is ten times more valuable. The goal is to feel the answer in your body so you're not reciting it in the room.
If you want structured practice with instant feedback, Arcenly's AI Interview Coach asks you questions based on the job you're applying for and gives you detailed feedback on your answers. Good way to prep before the real thing.