Skip to content
Lunera Pitch Lunera

6 min read ·

Interview questions and how to answer them—with evidence, not scripts

Prepare for nine common job interview questions with clear answer structures and illustrative examples for startup, technical and early-career roles.

Share X in f
Lunera · 6 min read

Prepare a small set of true examples, not a script for every possible question. A useful answer makes three things clear: what you can do, what evidence supports it, and why it matters for this role.

The questions below cover general job interviews, with examples suited to technical and startup roles. All sample answers are illustrative, not accounts of real candidates. Use their structure, but replace the details with your own experience.

1. “Tell me about yourself”

Answer with your current focus, one relevant piece of experience, and what you want next. Don’t walk through your entire résumé or personal history.

CareerOneStop’s interview guidance recommends a brief, positive summary of your work background and genuine interest in the job.

For example:

“I’m a computer science graduate focused on backend systems. In my final project, I owned the API and deployment workflow for a shared scheduling app. I’m looking for a role where I can develop those skills while working on a product with real users.”

If you’re experienced, substitute a recent responsibility or accomplishment for the student project. Stop when the interviewer has enough context to ask a useful follow-up.

2. “Why do you want to work here?”

Connect something specific about the company to the work you want to do and experience you can contribute. CareerOneStop recommends researching the company so you can explain what you value about it, rather than offering generic enthusiasm.

For example:

“The role description emphasizes making developer onboarding easier. In my internship, I worked on setup documentation and saw how much friction unclear instructions created. I’d like to work on that problem through both the product and its documentation.”

Separate what you know from what you infer. “The job description suggests…” is better than confidently describing an internal culture you haven’t experienced.

3. “What are your strengths?” or “Why should we hire you?”

Choose one or two strengths that match the job, then prove them with an example. A list of adjectives gives the interviewer little to evaluate. CareerOneStop similarly advises matching strengths to the job description and preparing examples of using them.

For example:

“One strength is making unfamiliar systems easier to understand. During an internship, I traced an undocumented import process, wrote a troubleshooting guide, and checked it with another intern who hadn’t used the system.”

Explain your contribution without claiming the team’s entire result. If you have a reliable measure of the outcome, include it. If not, describe what changed without inventing a percentage.

4. “What is your biggest weakness?”

Name a real limitation, its practical effect, and what you’re doing about it. Avoid disguised compliments such as “I care too much.” CareerOneStop advises honesty and explaining the steps you’re taking to improve.

For example:

“I used to spend too long investigating a problem before asking for help. That sometimes delayed decisions. Now I set an investigation checkpoint and share what I’ve tried, what I’ve ruled out, and the specific question I need help with.”

Choose something you can discuss candidly, not an arbitrary flaw selected to sound harmless. Don’t imply the problem is solved unless you have evidence that your behavior has changed.

5. “Tell me about a time you failed or made a mistake”

Use STAR: situation, task, action, result—and explain what you learned. The University of New Mexico’s interviewing guide recommends describing a specific event, focusing on your own actions, and explaining the outcome and learning.

For example:

“I was responsible for migrating a student project’s database. I underestimated the work and missed our internal deadline. I told the team, separated the essential migration from optional cleanup, and helped revise the plan. We completed the essential migration under that revised plan, but the original deadline was still missed. Afterward, I added a small migration rehearsal before committing to estimates.”

Keep the setup short. Spend more time on your decision, recovery, and changed practice. A failure answer doesn’t need to end in a spectacular success; an honest account of a limited outcome is more useful than a forced redemption story.

6. “Tell me about a disagreement with a teammate”

Explain the disagreement, how you tested or discussed it, and how the team reached a decision. Use the same STAR structure, but avoid casting the other person as unreasonable.

For example:

“A teammate wanted to rebuild a component; I preferred a smaller fix because our deadline was close. We listed the requirements and tested whether the fix covered them. It met the immediate need, so we shipped it and documented the remaining limitations.”

The useful detail is how you handled competing priorities—not whether you won. If the team chose the other approach, explain how you supported that decision and what you learned.

7. “How would you solve this technical problem?”

Clarify the requirements, propose an approach, explain trade-offs, and test the result. This is a problem-solving answer, not a STAR story about the past.

Microsoft’s technical interview guidance explicitly asks candidates to clarify ambiguities, make a plan before implementation, and consider testing, boundaries, and error conditions. That is one employer’s guidance, not a universal interview format.

For a hypothetical API-design question, you might begin:

“Before choosing an approach, I’d clarify expected traffic, latency requirements, and whether requests must be processed immediately. Then I’d propose the simplest design that meets those constraints and explain where it could fail.”

If you don’t know something, say so. Explain what you can reason through and what you would verify; don’t bluff familiarity with a tool or system.

8. “Why are you leaving your current role?”

Give a truthful, neutral explanation, then connect it to what you’re seeking. Don’t turn the answer into a complaint about your manager.

For example:

“My current role is primarily maintenance work. I’ve learned a lot from it, but I’m looking for more responsibility for designing and shipping new capabilities. That’s the part of this opening I’d like to understand better.”

If you were laid off or a contract ended, state that plainly. Don’t disguise an involuntary departure as your own decision.

9. “Where do you see yourself in a few years?”

Describe capabilities and responsibilities you want to develop, rather than promising a title. CareerOneStop recommends showing interest in learning and growing within the role, without treating it merely as a stepping stone.

For example:

“I want to become someone who can own a backend service from design through production support, make sound trade-offs, and help newer teammates. I’m looking for a role where I can build toward that responsibility.”

You don’t need a precise career forecast. You do need a credible connection between this job and the work you want to become better at.

Prepare examples you can defend

Before the interview, identify the role’s three most important requirements. Then prepare five true stories: an accomplishment, a mistake, a disagreement, an ambiguous task, and something you learned quickly.

For each, note the context, your responsibility, your actions, the outcome, and what you would do differently. Students can draw on coursework, volunteer work, and team projects; UNM’s guide explicitly includes school and volunteer experience.

Practice aloud from these notes, not a memorized paragraph. Check whether you can answer follow-ups such as “What did you personally do?” and “How do you know it worked?” Keep confidential customer details and proprietary material out of your examples.