The 15 Most Common First Job Interview Questions (And How to Answer Them)

The first job interview is a milestone that almost every professional remembers vividly — the preparation, the anxiety, the moment you walk into the room or join the video call and realise that this is real. For many graduates, it is the first time they have ever had to sell themselves professionally to a stranger, and the combination of unfamiliarity and high stakes makes it one of the most nerve-racking experiences of early adult life.

Here is what changes the experience completely: knowing that interviews are not unpredictable. The questions that come up in first job interviews are remarkably consistent. Hiring managers use the same frameworks, the same behavioural questions, and the same evaluation criteria across industries, companies, and roles. Once you understand the logic behind each question — what the interviewer is actually trying to find out — and you have practised answering them clearly and specifically, the interview stops feeling like an ambush and starts feeling like a conversation you have prepared for.

This guide covers the 15 most common first job interview questions in full detail. For each question, we explain why interviewers ask it, what a weak answer looks like, and what a strong answer looks like — with real examples you can adapt. At the end, we cover the questions you should be asking the interviewer, because how you ask questions matters almost as much as how you answer them.

Before We Get Into the Questions: The Mindset That Changes Everything

Most candidates approach a first interview as though they are being examined — as though the interviewer holds all the power and their job is to avoid making mistakes. This mindset produces defensive, vague, over-rehearsed answers that feel robotic and tell the interviewer very little about who you actually are.

The mindset that produces strong interviews is different: you are in a mutual evaluation. Yes, the company is assessing whether you are right for the role. Simultaneously, you are assessing whether the role and the company are right for you. Coming into the conversation with this frame — curious, confident, genuinely interested rather than just anxious — changes the quality of your answers and the impression you make.

It also changes your preparation. When you are preparing to have a genuine conversation rather than to survive an examination, you prepare differently. You think about your actual experiences and what you genuinely believe about them, rather than trying to reverse-engineer what the interviewer wants to hear. This produces more authentic, more specific, and more memorable answers.

With that said, let us get into the questions.

The 15 Most Common First Job Interview Questions

Question 1: "Tell me about yourself."

Why they ask it: This is almost always the opening question, and it is an invitation to frame the conversation on your terms. Interviewers use it to get an overview of your background, assess your communication style, and — importantly — to see whether you understand what is relevant to mention. A candidate who talks for four minutes about their childhood is telling the interviewer something just as significant as the content itself: they do not understand what professional context requires.

What a weak answer looks like: A chronological recitation starting from secondary school that runs too long and ends with "...so that's basically me." Or a short, anxious answer that undersells significantly: "Um, I just graduated from university and I'm looking for my first job in marketing."

What a strong answer looks like: Follow the Present → Past → Future structure. Start with who you are now professionally (your degree, your most relevant skills, and any standout experience). Then briefly mention the past experience that is most relevant to the role. End with why you are excited about this specific opportunity.

Keep it to between 90 seconds and two and a half minutes. Longer than that and you are rambling. Shorter than 90 seconds and you have undersold yourself.

Example: "I recently graduated from Covenant University with a degree in Computer Science, where I focused on web development and software engineering. During my studies, I built three full-stack projects — including a job matching platform for my final year project — and I have been maintaining a GitHub portfolio ever since. I also completed a three-month internship at a Lagos-based software agency where I worked on the frontend of a client's e-commerce platform, which was my first experience delivering production code on a real deadline. I am now looking to join a team where I can continue building those skills in a more structured environment — and the junior developer role here felt like a natural fit based on your stack and the kind of products you are building."

Notice what this answer does: it is specific (named the project, named the internship), it is relevant (directly connects past experience to the role), and it ends by demonstrating that the candidate has done their research.

Question 2: "Why do you want to work here?"

Why they ask it: They are separating candidates who actually want this job from candidates who are applying to every company that posted an opening. The difference matters enormously — candidates who are genuinely interested in the company are more likely to be motivated employees, more likely to stay, and more likely to contribute ideas and energy beyond their minimum requirements.

What a weak answer looks like: "I've always admired your company and I think the culture would be a great fit for me." This answer could have been written about literally any company in the world. It is generic and the interviewer knows it.

What a strong answer looks like: Reference something specific — a product, a campaign, a news story, a mission statement, a customer experience, something that a person who had genuinely researched the company would know.

Example: "I have been following Flutterwave's work on cross-border payment infrastructure for about a year, and the way your platform has lowered the barrier for small businesses to transact across African markets is genuinely impressive to me — I worked with my uncle on his export business for a summer and saw firsthand how much friction there was in international payments. When I saw you were hiring for this operations role, it felt like a direct application of the problem I care about. Beyond the product, the fact that your engineering team publishes detailed technical posts and actively contributes to open source — I've read three of those posts — tells me something specific about the kind of learning environment this is."

This answer references specific work, connects it to personal experience, and then demonstrates independent research (having read technical blog posts). It is almost impossible to fake convincingly, which is exactly why it works.

Question 3: "What are your greatest strengths?"

Why they ask it: They want to know whether you have genuine self-awareness, whether your strengths are relevant to the role, and whether you can back them up with evidence. Saying you are "a hard worker" is the single most useless answer to this question because it is unverifiable, universally claimed, and completely uninformative.

What a weak answer looks like: "I'm very hardworking, passionate, and a fast learner." These three things are claimed in approximately 80% of all entry-level interviews. They mean nothing without evidence.

What a strong answer looks like: Choose two or three strengths that are genuinely relevant to the role and back each one with a specific example. The format is: name the strength, give the evidence, connect it to the role.

Example: "Two things stand out for me. The first is my ability to synthesise and communicate complex information clearly — I developed this doing academic research where I regularly had to turn dense academic papers into actionable summaries for non-specialist audiences. My dissertation on consumer psychology in digital markets was selected for publication in our faculty journal, which I take as evidence that I do this reasonably well. The second is that I am genuinely good at working across different types of people — in group projects I was often the person who translated between the 'just get it done' people and the 'let's do it properly' people, and most of our best outcomes came from finding the middle ground. Both of those feel directly relevant to a marketing analyst role where you are working with both creatives and data teams."

Question 4: "What is your greatest weakness?"

Why they ask it: Self-awareness is a quality that is extremely hard to teach and extremely valuable in employees. An interviewer asking about weaknesses is not trying to catch you out — they are evaluating whether you are honest about yourself, whether you understand the areas where you need to grow, and whether you are actively working on them.

What a weak answer looks like: "My greatest weakness is that I work too hard and care too much." This non-answer is so universally recognised as a cop-out that it actively damages your credibility. "I have no weaknesses" is worse. "I'm a perfectionist" has become almost as clichéd unless you back it up with something real.

What a strong answer looks like: Give a real weakness — one that you are genuinely working on, one that is not a critical disqualifier for the role you are applying for. Describe what the weakness is, where it comes from, and specifically what you are doing to address it.

Example: "I have historically found it difficult to delegate — I prefer to be confident that something is done correctly, and that has sometimes led me to take on more than I should rather than trusting teammates to handle their parts. I noticed this clearly during a group project last year when I ended up rewriting sections that others had contributed, which created tension and was not a good use of anyone's time. Since then, I have been deliberately practising giving clearer briefs upfront and then stepping back — and the last two collaborative projects have gone significantly better because of it. It is an ongoing thing for me, but I am paying attention to it."

This answer works because it is specific, honest, shows self-awareness, demonstrates growth, and frames the weakness as an active work-in-progress rather than a fixed character flaw.

Question 5: "Where do you see yourself in five years?"

Why they ask it: They want to understand your ambition, your commitment to the field, and whether your trajectory makes sense within the context of this role. They are also, partly, checking whether you are thinking of this as a stopover or as a genuine starting point for a career.

What a weak answer looks like: "In five years I see myself in a senior leadership position with lots of responsibility." This is generic and tells them nothing about your understanding of how careers actually develop. "Honestly, I'm not sure" is honest but suggests a lack of intentionality.

What a strong answer looks like: Show that you have thought seriously about the career path in this field, that your ambitions are grounded in a realistic understanding of how development works, and that you see this role as a genuine foundation — not a stepping stone to somewhere completely different.

Example: "In five years, I want to have developed deep expertise in data analysis — specifically in the intersection of financial data and product analytics, which is where my interest genuinely lies. I hope to be working at a level where I am contributing to strategic decisions rather than just reporting on them, and ideally in a role that has given me some experience managing a small team or at least mentoring more junior analysts. I am not committed to a specific title at this point — I am committed to the substance of the work. What drew me to this role is that it looks like an environment where that kind of deep development is possible."

Question 6: "Tell me about a challenge you faced and how you handled it."

Why they ask it: This is a classic behavioural question designed to evaluate problem-solving, resilience, and decision-making under pressure. Interviewers use it because past behaviour in challenging situations is the best available predictor of future behaviour in similar situations.

What a weak answer looks like: A vague, unverifiable answer: "I once had a really difficult group project and I just worked harder to make it succeed." No specifics, no transferable learning, no evidence of self-reflection.

What a strong answer looks like: Use the STAR method — Situation, Task, Action, Result. Set the scene briefly. Explain what your specific responsibility was. Walk through the specific actions you took. Describe the result, including what you learned.

Example: "In my third year, I was leading a team of five for our major project when one team member had a family emergency and had to withdraw two weeks before the deadline, taking a full section of the project with her. [Situation] My responsibility was to get the project to a high standard on time without any additional resources or deadline extension. [Task] I called an emergency team meeting that evening, mapped out exactly what was complete and what was missing, and redistributed the remaining work based on each person's strengths rather than dividing it equally. I took the most technically complex section myself, worked through two nights, and briefed the team daily so everyone knew the overall status. [Action] We submitted on time and received a first-class grade. More than the result, what I took away from it was a clearer understanding of how to prioritise under pressure and the importance of maintaining team morale when things get difficult — people perform better when they feel informed and trusted, not just directed. [Result and learning]"

Question 7: "Why are you leaving your current/last position?"

Why they ask it: Even for recent graduates who have not held a professional role, this question might come up in reference to an internship, part-time job, or student role. The interviewer is looking for professionalism and honesty — and specifically checking whether you speak negatively about previous employers, which is a red flag regardless of how justified the criticism might be.

What a weak answer looks like: "My last manager was terrible and the team was completely disorganised." Even if this is entirely true, saying it tells the interviewer something about how you will talk about them one day.

What a strong answer looks like: Focus entirely on what you are moving toward, not what you are moving away from. Be honest about the fact that it was a fixed-term arrangement if that is true. Express genuine gratitude for what you learned.

Example: "My internship was a fixed-term role and was never going to be a long-term position — that was clear from the start. I am grateful for what I learned there about working in a professional environment and managing client expectations, and I left on excellent terms. I am now looking for a full-time role where I can invest properly, build something over a longer horizon, and continue developing the skills I started building during that placement."

Question 8: "How do you handle working under pressure or tight deadlines?"

Why they ask it: Work involves pressure and deadlines. They want to know whether you have a reliable system for managing them, whether you stay functional under stress, and whether you have enough self-awareness to know what helps you perform.

What a weak answer looks like: "I'm very good under pressure." This is a claim without evidence and every candidate says it.

What a strong answer looks like: Describe your actual system, back it with a specific example, and be honest about what you have learned from situations where you handled it imperfectly.

Example: "My approach when a deadline is coming up or priorities are competing is to immediately make a list and sort by actual impact — not urgency as I feel it emotionally, but actual consequence if something is late. Then I communicate proactively with anyone who is waiting on me so they can plan accordingly. During exam season last year, I was simultaneously managing a large group project, preparing for three exams, and leading a campus event. I used a simple task board in Notion, blocked my time explicitly, and sent a quick update to the event committee when I realised the exam week would reduce my availability. Everything landed. What I have also learned is that asking for help earlier than feels comfortable is usually the right call — most people are more flexible than you assume if you give them enough notice."

Question 9: "Do you prefer working independently or in a team?"

Why they ask it: They want to understand your working style and check whether it matches how the team actually operates. If the role requires heavy collaboration and you say you strongly prefer working alone, that is a potential fit problem.

What a weak answer looks like: Saying one extreme without nuance: "I definitely prefer working independently." Or saying whatever you think they want to hear.

What a strong answer looks like: Give an honest, contextual answer. Most professional work requires both, and showing that you understand this — and that you can shift between them — is more impressive than either extreme.

Example: "Genuinely, I enjoy both and think the best work usually comes from doing them at the right times. For deep analytical or creative work — writing, research, coding — I need blocks of uninterrupted individual focus. But I find that the ideas I develop in that individual space become significantly better through collaborative review and challenge. Some of my best work has come from a teammate pointing out something I had completely missed because I had been too close to it. If I had to identify a stronger preference, I would say I slightly favour environments where individual ownership is clear and respected, but where the team is genuinely collaborative in the problem-definition and review phases."

Question 10: "How do you prioritise when you have multiple tasks or projects?"

Why they ask it: Most jobs involve competing demands and limited time. They want to see that you have a system, that you understand the difference between urgent and important, and that you can communicate proactively when priorities conflict.

Example: "My starting point is always to get the full picture of everything that is outstanding, estimate the time each task genuinely requires, and then rank by impact and deadline — not just the deadline that feels most pressing. I try to identify the one or two things that, if completed, would unblock other people or have the highest downstream consequence. For recurring work, I maintain a simple task list with weekly reviews so nothing quietly slips. When I have genuinely too much to complete well in the available time, I try to flag that early rather than silently delivering late — a quick message saying 'I can have X by end of day Wednesday or a preliminary version by Monday, which is more useful to you?' gives the other person agency and usually leads to a better outcome than silence followed by a late delivery."

Question 11: "Tell me about a time you worked in a team."

Why they ask it: Almost all professional work involves collaboration. They want evidence that you can contribute constructively to a group, manage different personalities, and deliver results through other people as well as through your own effort.

Example: "The most memorable team experience I have was our final year case study competition. We were a team of four with very different working styles — two of us were detail-oriented and process-driven, one was highly creative but resistant to structure, and one was results-focused to the point of cutting corners. Early in the project there was friction, particularly between the creative and the detail-oriented members. I took on an informal coordination role — not because I was assigned it, but because it was clearly needed. I had a direct conversation with each person about how they worked best and what they needed from the others, and then proposed a structure where the creative person owned the ideation phase fully, the detail people owned the execution phase, and the results-focused person managed our timeline. We reached a first-class mark and genuinely respected each other by the end. What I took from it was that teams work better when people understand each other's working styles explicitly rather than assuming everyone operates the same way."

Question 12: "What do you know about our company / this industry?"

Why they ask it: They are checking whether you did any research. Candidates who cannot answer this question beyond the company's tagline have clearly not invested time in understanding the role they are applying for, which is a poor sign for how much care and attention they will bring to the job itself.

What a strong answer looks like: Demonstrate knowledge at three levels — what the company does broadly, what differentiates them specifically, and what is currently relevant or interesting about their position in the market. You should be able to name at least one specific product, initiative, or development that is not on the homepage.

Example: "You are a fintech company focused on providing payment infrastructure for SMEs operating across West Africa. The core product is a cross-border payment API that allows businesses to send and receive payments in multiple African currencies without needing a separate banking relationship in each market. What I found interesting in my research is your recent partnership with three major telecom operators to extend mobile money integration — that suggests you are moving beyond the traditional banked SME market toward a much larger underserved segment. The broader industry context is one where the regulatory environment is tightening across most African markets, which I imagine creates both compliance challenges and potential competitive advantages for established players who have invested in compliance infrastructure early."

Question 13: "Are you comfortable with [specific tool / technology / approach]?"

Why they ask it: They want to understand your existing skill level with tools or methods the role requires, and assess whether any gaps are manageable through training.

What a weak answer looks like: Claiming proficiency you do not have. This will become apparent quickly once you are in the role and it damages trust that is very hard to rebuild.

What a strong answer looks like: Be honest about your current level, describe your experience specifically, and if there is a gap, address it directly and explain how you plan to close it.

Example: "I have used Excel extensively for data analysis during my degree, including pivot tables, VLOOKUP, and basic charting. I have not used Tableau professionally, but I completed the Tableau Desktop Specialist learning path online and built three practice dashboards during my job search — I can share those if it would be helpful. I am confident I can reach a functional working level in any additional tools quickly; my approach to learning new software is to set up a real project rather than just following tutorials."

Question 14: "What motivates you?"

Why they ask it: They want to understand what drives you because it tells them whether this particular role and environment is likely to keep you engaged and performing well — or whether you will be searching for your next job in six months.

What a weak answer looks like: Generic answers: "I'm motivated by success and achieving my goals." Or answers that focus on compensation: "Honestly, salary motivates me a lot." Neither of these tells the interviewer anything useful.

What a strong answer looks like: Be genuine and specific, and connect it to the role.

Example: "I am genuinely motivated by seeing the practical result of analytical work — the moment when a pattern in the data leads to a change in how something is done and you can see the effect of that. During my degree I ran a research project on social media engagement patterns for local businesses, and when the results clearly showed that the conventional advice about posting times was wrong for this particular market, I found that genuinely exciting — not because I had been clever, but because the finding was real and actionable. That feeling of a concrete result from careful analysis is what I want more of professionally."

Question 15: "Do you have any questions for us?"

Why they ask it: This question is your opportunity to demonstrate genuine curiosity, show that you have thought seriously about the role, and assess whether this company is actually a place where you want to work. Answering "no, I think you have covered everything" is a mistake that signals either a lack of preparation or a lack of genuine interest.

Prepare at least five questions in advance so that if some are answered during the interview, you still have others. These are the most effective categories of questions to ask:

About the role specifically:

• "What does success look like in this role after six months?"
• "What are the biggest challenges the person in this role typically faces in the first 90 days?"
• "What does a typical week look like for someone in this position?"

About the team:

• "How would you describe the team's working culture and communication style?"
• "What are the characteristics that the people who have done this role well tended to have in common?"

About growth and development:

• "How does the company typically support professional development at the entry level?"
• "What does the career path from this role usually look like?"

About the company genuinely:

• "What is the biggest challenge the business is currently navigating?"
• "What do you enjoy most about working here?"

That last question — what do you enjoy most about working here — is one of the most powerful questions you can ask. It invites the interviewer to speak personally and authentically, and the answers tell you far more about what the organisation is actually like than any official culture statement does.

Practical Preparation: How to Actually Prepare for an Interview

Reading this guide is step one. Actually preparing is what makes the difference. Here is the preparation process that produces consistently strong interviews.

Step 1: Write out your STAR stories

Before any interview, write out at least eight specific stories from your academic, volunteer, or work experience. Each story should follow the STAR structure: Situation, Task, Action, Result. The stories should collectively cover: a challenge you overcame, a time you worked in a team, a time you led something, a time you failed or made a mistake and what you learned, a time you dealt with a difficult person or situation, and a significant achievement.

Having these stories written out and rehearsed means you will not struggle to think of examples under pressure. Most behavioural questions can be answered with one of eight to ten core stories — you just adjust the framing slightly depending on what the question emphasises.

Step 2: Research the company properly

Spend thirty to forty-five minutes on genuine research before any interview. Read the About page, the recent news, the LinkedIn company page, and any blog posts or case studies they have published. Search for the company name in Google News to see what has been reported about them recently. If you know who is interviewing you, look at their LinkedIn profile — understanding their background gives you context for who you are talking to.

Step 3: Practise out loud

This is the step most candidates skip, and it is the most important one. Answers that sound clear and confident in your head often come out disorganised and hesitant when you actually say them out loud. Record yourself on your phone answering the fifteen questions in this guide. Then watch the recording. It is uncomfortable, but it is also the fastest way to identify where you need to improve.

Step 4: Prepare your logistics

For in-person interviews: know exactly where you are going, how long the journey takes, and add fifteen minutes of buffer. Have two copies of your CV. Dress one level above what you think the office dress code is. Bring water.

For video interviews: test your technology the day before. Check your camera, microphone, and internet connection. Choose a clean, quiet background. Position your camera at eye level — looking up into a laptop camera is unflattering and suggests you have not prepared. Look at the camera lens, not at the screen image of the other person, when you are speaking.

Step 5: Prepare your opening and closing

Know exactly how you will answer "tell me about yourself" before you walk in. Write it out. Time it. Make sure it is under two minutes. Also know how you will close: "Thank you so much for your time — I am genuinely excited about this role and I look forward to hearing from you" is simple, warm, and leaves a good final impression.

After the Interview: What Most Candidates Do Not Do

Within twenty-four hours of an interview, send a brief thank-you email to the interviewer or the HR contact who arranged it. Keep it short — three to four sentences. Express genuine gratitude, reference one specific thing from the conversation that stood out to you, and reaffirm your interest in the role.

Most candidates do not do this. It takes five minutes and it consistently makes a positive impression.

If you have not heard back within the timeline they indicated, follow up once — politely and briefly. Something like: "I wanted to follow up on my application for the [role] position and check on the timeline for next steps. I remain very interested in the opportunity." Do not follow up more than twice.

If you receive a rejection, it is worth asking for feedback — not to challenge the decision, but to learn. Some recruiters will not respond or will give generic answers. But occasionally you will receive genuinely useful information about how to improve. Every piece of that information is valuable.

The Interview Is a Conversation — Approach It That Way

Preparation matters. Rehearsed answers matter. Research matters. But the single thing that makes the biggest difference in a first interview is whether you show up as a real, curious, engaged person rather than as a candidate trying to perform the role of "good interview candidate."

Hiring managers interview dozens of people. They remember the ones who seemed genuinely interested, who pushed back thoughtfully on something they said, who asked a question that made them think, who brought specific knowledge about the company that went beyond the homepage. They forget the ones who gave technically adequate but entirely forgettable answers to every question.

Be prepared. Be specific. Be genuine. The rest will follow.

When you are ready to start applying, browse all available entry-level and graduate roles on Job Foundry Hub — every listing is verified for candidates with 0 to 2 years of experience.