Behavioral Interview Questions and Answers: 35 STAR Examples
Last updated (2026-11-02)
Behavioral interview questions ask you to describe how you actually handled a real situation in the past, on the idea that past behavior is the best evidence of how you will work on the job. This guide explains how they work, how to answer them with the STAR method, and how to build a small story bank, then gives 35 common questions grouped by theme.
Every question has a short note on what the interviewer is checking and a sample STAR answer written for a software engineer, intern or new grad. The people and projects in the samples are fictional. Use them to see the shape of a strong answer, then tell your own true story in your own words.
What are behavioral interview questions?
A behavioral question asks for a specific past example, not an opinion. It usually starts with "Tell me about a time when...", "Give me an example of..." or "Describe a situation where...". A hypothetical question ("What would you do if...") is different: it tests judgment, while a behavioral question tests evidence.
Software companies use them in a dedicated behavioral round, inside a hiring manager conversation, or as a few minutes at the start or end of a technical interview. Some companies tie them to published values; Amazon, for example, organizes them around its Leadership Principles (see our Amazon behavioral interview questions guide).
- Collaboration: how you work with teammates, reviewers and people outside engineering.
- Ownership and judgment: what you do when something breaks, is unclear, or is not strictly your job.
- Self-awareness: whether you can talk about a mistake or weakness calmly and say what changed.
- Communication: whether you can tell a clear story in about two minutes and answer follow-ups.
How to answer behavioral interview questions with the STAR method
STAR stands for Situation, Task, Action, Result. It keeps your answer in order and makes sure you finish with an outcome instead of trailing off.
| Part | What to say | Rough share of the answer |
|---|---|---|
| Situation | The context in one or two sentences: team, project, what was at stake. | Short |
| Task | Your specific responsibility or goal, not the whole team's. | Short |
| Action | What you did, step by step, and why you chose that approach. | The longest part |
| Result | What happened, ideally something observable, and what you learned. | Short |
- Say "I", not only "we". The interviewer is hiring you, so make your own decisions and actions clear while giving credit to the team.
- Keep it to about two minutes. Skip background the interviewer does not need. They will ask if they want more.
- Use real results. A number helps when you have one ("page load dropped from four seconds to one"), but never invent a metric. An honest, modest outcome is fine.
- End with the learning when the story is about a failure or conflict: what you now do differently.
- Answer the question that was asked. If the question is about conflict, the conflict must be the center of the story, not a footnote.
Some interviewers say CAR (Context, Action, Result) or STARL (STAR plus Learning). They are the same idea: context, what you did, what happened.
Common mistakes
- Describing what you would do in general instead of one specific time.
- Spending most of the answer on the situation and rushing the action.
- Choosing a "weakness" or "failure" that is really a strength, which reads as evasive.
- Blaming a teammate, manager or professor in a conflict story.
- Reusing one story for every question, so the interviewer learns nothing new.
How to prepare a story bank
You do not need a separate story for every possible question. Most candidates can cover a full behavioral round with six to eight well-prepared stories, because one good story can answer several questions from different angles.
- List your raw material. Internships, jobs, class team projects, capstone, hackathons, open source, research, clubs, teaching assistant work, part-time jobs. New grads have more stories than they think.
- Pick six to eight moments with tension. A bug in production, a disagreement, a missed deadline, a time you led, a time you were wrong, a time requirements were unclear.
- Write each one as STAR bullets, not a script. Note the facts you might be asked about: dates, tools, who was involved, what the result was.
- Tag each story with themes (teamwork, conflict, failure, leadership, ownership, deadlines, ambiguity) so you can find one fast under pressure.
- Check coverage. Every theme should have at least two stories, and you need at least one honest failure.
- Practice out loud and time yourself. Reading notes silently is not the same as telling the story.
| Story (example) | Themes it can answer |
|---|---|
| Production outage during internship | Ownership, pressure, failure, communication |
| Capstone team that missed a milestone | Teamwork, deadlines, leadership, failure |
| Disagreement about a database choice | Conflict, persuasion, disagree and commit |
| Feature with a vague spec | Ambiguity, customer focus, initiative |
| Mentoring a new club member | Leadership, helping others, communication |
Common behavioral interview questions about teamwork
Teamwork questions check what you personally contributed and how you make the people around you more effective.
1.Tell me about a time you worked on a team to deliver a project.
What they check: your specific role inside a team, and how you coordinated with others.
Situation: In my senior capstone, four of us built a scheduling app for a campus tutoring center over one semester.
Task: I owned the backend API and the integration with the tutoring center's existing calendar.
Action: I proposed we agree on the API contract in the first week and wrote it down as an OpenAPI file, so the frontend teammates could build against mock data instead of waiting for me. I ran a 15 minute check-in twice a week and kept a shared board of open tasks.
Result: We delivered on time, and the tutoring center used the app for the following semester. I learned that writing the contract early saved more time than any code I wrote.
2.Describe a time you helped a teammate who was struggling.
What they check: empathy and whether you help in a way that builds the other person up rather than taking over.
Situation: A new engineer on my team was stuck on her first ticket for several days and had not asked for help.
Task: I was not her mentor, but I had worked in that part of the codebase and wanted her to get unblocked without feeling embarrassed.
Action: I asked if she wanted to pair for 30 minutes, let her drive, and only asked questions. We found she was missing a local config step that was not documented. Afterward I added that step to the setup README and suggested she open the pull request for it.
Result: She shipped the ticket that day, and the README change helped the next two hires. She later told me the pairing made it easier to ask questions.
3.Tell me about a time you worked with someone outside engineering.
What they check: whether you can translate technical detail for designers, product managers, support or customers.
Situation: During my internship, a support lead reported that customers were confused by an error message on the password reset page.
Task: I was asked to fix the bug behind it, but the real problem was that the message gave no next step.
Action: I sat in on two support calls to hear how customers described the problem, then drafted three versions of the message and reviewed them with the support lead before changing any code.
Result: We shipped the clearer message with the bug fix, and the support lead said tickets about that page dropped noticeably over the next weeks. I learned to talk to the people closest to the user before deciding what to build.
4.Give an example of how you contributed to a team you were new to.
What they check: how quickly you get useful, and whether you learn before you change things.
Situation: I joined a team that owned a payments service written in a language I had not used professionally.
Task: My goal for the first month was to ship real changes without slowing down the senior engineers.
Action: I read the last few months of design docs, picked up small bug fixes first, and asked reviewers to be strict with me. When I noticed the test suite took a long time to run, I measured where the time went and found most of it was one slow integration test.
Result: Fixing that test made everyone's builds faster, which was a useful early contribution, and by the end of the month I was taking normal-sized tickets.
5.Tell me about a time a team project did not go well. What was your part in it?
What they check: honesty about your own role, without blaming others.
Situation: In a databases course, our group of three built a library system, and we demoed it with a broken search feature.
Task: I owned search and had said it would be ready a week before the demo.
Action: I underestimated the full-text search work and did not tell the group I was behind until two days before. Once I did, a teammate helped me cut scope to exact-match search, and we documented the gap in our report.
Result: We still got a passing grade, but lost points on search. Since then I flag risk as soon as I see it, usually halfway to a deadline, instead of hoping to catch up.
Tip: Questions phrased like this are partly failure questions. Own your part first, then the fix.
Behavioral interview questions and answers: conflict
Conflict questions check whether you can disagree respectfully, use evidence, and keep the relationship working.
6.Tell me about a time you disagreed with a teammate.
What they check: whether you argue with data and stay respectful, and what you do once a decision is made.
Situation: A senior teammate wanted to add a caching layer to fix a slow page, and I thought the slowness came from a missing database index.
Task: I needed to make my case without blocking a fix customers were waiting for.
Action: I asked for a day to test my idea, ran the slow query with and without the index on a copy of production data, and shared the query plans in our team channel. I was clear that if the index did not help, caching was the right next step.
Result: The index fixed most of the delay, so we shipped that first and kept caching as a follow-up. My teammate and I kept working well together, partly because I had framed it as testing both ideas rather than proving him wrong.
7.Describe a conflict with a manager or someone more senior.
What they check: whether you can push back on authority respectfully and commit once a decision is made.
Situation: My manager asked me to ship a feature by Friday by skipping the load test.
Task: I owned the feature and was worried it could slow down a shared database during peak hours.
Action: I asked for 15 minutes, explained the specific risk, and offered a middle option: release behind a feature flag to a small share of users on Friday and run the load test over the weekend before a full rollout.
Result: She agreed. The load test found one slow query, which I fixed before the full release. I learned to bring an option along with the objection.
8.Tell me about a time you received critical feedback.
What they check: whether you can hear criticism without getting defensive, and whether you act on it.
Situation: In my internship midpoint review, my mentor said my pull requests were too large and hard to review.
Task: I wanted to fix it before the end of the internship, since review time was slowing my whole project down.
Action: I asked him for an example of a well-sized PR, then started splitting my work into small steps: one PR for the data model, one for the API, one for the UI. I also wrote a short description at the top of each PR explaining what to look at first.
Result: My review turnaround went from days to hours, and my final review mentioned the change specifically.
9.Give an example of a time you had to work with a difficult person.
What they check: maturity: describing the behavior, not attacking the person, and what you did to make the work go well.
Situation: In a hackathon, one teammate kept rewriting other people's code late at night without telling anyone.
Task: We had 36 hours, and the rewrites were breaking the demo build.
Action: I talked to him privately, assumed good intent, and asked what he was trying to fix. He was worried the code was messy. We agreed he would open small pull requests and I would review them quickly so he did not feel blocked.
Result: The build stayed stable for the rest of the event and we demoed on time. I learned that a lot of difficult behavior comes from a worry nobody has asked about.
10.Tell me about a time you had to persuade someone to change their mind.
What they check: influence without authority, using evidence and listening.
Situation: Our team wrote end-to-end tests by hand for each release, and the tech lead was skeptical about automating them.
Task: I believed automation would catch regressions earlier, but I was the most junior engineer on the team.
Action: Instead of arguing in a meeting, I automated the five tests that broke most often in a weekend spike, ran them in our pipeline on a branch for two weeks, and shared which real regressions they caught. I also listed the maintenance cost honestly.
Result: The tech lead agreed to adopt them, and we expanded the suite over the next quarter. Showing a small working version did more than any argument I could have made.
Behavioral questions about failure and mistakes
Failure questions check self-awareness. Pick a real mistake with real consequences, then spend most of the answer on what you did and learned.
11.Tell me about a time you failed.
What they check: whether you take responsibility and what you changed afterward.
Situation: During my internship I ran a database migration on the staging environment that locked a shared table for most of an afternoon.
Task: I owned the migration and had tested it only on a small local dataset.
Action: As soon as other teams reported staging was down, I told my mentor, stopped the migration, and posted what happened in the team channel. Then I rewrote it to run in small batches and tested it on a staging-sized copy of the data first.
Result: The second run finished without locking anything. Since then I test migrations against realistic data sizes, and I added that step to the team's migration checklist.
12.Describe a mistake you made at work or school and how you handled it.
What they check: speed and honesty when something goes wrong, and whether you fix the cause, not just the symptom.
Situation: I deployed a change that sent duplicate notification emails to a few hundred users.
Task: It was my code, so it was my job to stop the damage and explain what happened.
Action: I rolled back within minutes, confirmed the duplicates had stopped, and wrote a short incident note the same day. The cause was a retry that was not idempotent, so I added an idempotency key and a test that sends the same event twice.
Result: No more duplicates went out, and the support team used my note to reply to the users who asked. I now check retry behavior in every change that sends messages.
13.Tell me about a time you missed a goal.
What they check: whether you can analyze why without excuses.
Situation: I set a goal to contribute a feature to an open source testing library during my final semester.
Task: I had picked an issue that looked small and planned to finish it in a month.
Action: Two weeks in, I realized the change touched the core plugin system and would need a design discussion with maintainers. I posted my findings on the issue, asked for guidance, and contributed two smaller fixes while the discussion continued.
Result: The feature did not land before I graduated, but my two fixes were merged and my notes on the issue were used by the contributor who finished it. I learned to scope work by reading the code first, not by guessing from the issue title.
14.What is a piece of work you are not proud of?
What they check: honest reflection, and that your standards have grown.
Situation: Early in my first job I built an internal admin page quickly and skipped tests to hit a demo date.
Task: The page was meant to be temporary, so I told myself tests were not needed.
Action: It stayed in use for a year. When it broke after a library upgrade, I was the one who fixed it, and it took much longer because nothing was tested. I used that fix as a chance to add tests for the main flows.
Result: It works reliably now. I learned that temporary code often becomes permanent, so I write at least basic tests even for quick tools.
15.Tell me about a time you took a risk that did not pay off.
What they check: whether you take reasonable risks and limit the downside.
Situation: For a class project I chose a new web framework none of my group had used, because I wanted to learn it.
Task: I convinced the group, so I felt responsible for making it work.
Action: After a week we were moving slowly because of missing documentation. I set a checkpoint: if we could not finish the login and main page by the next weekend, we would switch to a framework we knew. We missed it, so I led the switch and ported what we had.
Result: We lost about a week but finished on time. The checkpoint idea is what I kept: decide in advance when you will stop a risky bet.
Behavioral questions about leadership
You do not need a manager title. Leading a project, a study group, a code review standard or an incident all count.
16.Tell me about a time you showed leadership.
What they check: whether you take the initiative to organize people toward a goal.
Situation: Our university coding club's weekly practice sessions had shrunk to a handful of students.
Task: As a new officer, I took on getting attendance back up.
Action: I surveyed members and learned the problems were too hard for beginners. I split each session into a beginner and an advanced track, recruited two seniors to lead the advanced one, and posted the problems a day early.
Result: Attendance grew steadily over the semester, and the two-track format continued after I graduated.
17.Describe a time you led without formal authority.
What they check: influence through clarity and trust rather than a title.
Situation: Three teams depended on a shared logging library that nobody owned, and it had a bug that hid some errors.
Task: I was not anyone's manager, but my team was hit hardest by the bug.
Action: I wrote a one-page proposal for the fix, asked one engineer from each team to review it, and offered to do most of the work if each team tested the change in their service. I set up a short weekly sync until it shipped.
Result: The fix rolled out to all three services within a month, and the teams agreed on a rotating owner for the library afterward.
18.Tell me about a time you mentored or taught someone.
What they check: patience, clarity, and whether you measure success by the other person's growth.
Situation: As a teaching assistant for an intro programming course, I noticed several students failing the recursion assignment.
Task: My job was to run lab sections, and I wanted those students to pass the next assignment on their own.
Action: Instead of re-explaining the lecture, I had students trace small recursive functions on paper and predict the output before running them. I also held an extra office hour focused only on recursion.
Result: Most of the students who came did noticeably better on the next assignment, and the professor asked me to share the tracing exercises with the other TAs.
19.Give an example of a decision you made that was unpopular.
What they check: judgment and backbone, and how you explain a decision to people who disagree.
Situation: As release owner for a sprint, I found a bug in a feature two days before the planned launch.
Task: I had to decide whether to ship on schedule or delay a feature the sales team had promised to a customer.
Action: The bug could show one customer's data to another in a rare case, which I judged too serious to ship. I delayed the launch by three days, explained the exact risk to the product manager and sales lead, and gave them a fixed new date.
Result: The fix shipped on the new date. Sales was unhappy at first but agreed the risk was real once they saw the example. Being specific about the risk is what made the decision acceptable.
20.Tell me about a time you set a standard others followed.
What they check: whether you raise the bar for the team, not only for your own work.
Situation: Our team's pull requests often had no description, so reviewers had to read the whole diff to understand the change.
Task: I wanted reviews to be faster without adding a heavy process.
Action: I wrote a short pull request template with three questions (what changed, why, how it was tested), used it on all of my own PRs for two weeks, then proposed it at retro with examples of reviews that went faster.
Result: The team adopted it, and reviewers said they could start reviewing without asking basic questions first.
Behavioral questions about ownership and initiative
Ownership questions check whether you act when something needs doing, even when it is not strictly your job.
21.Tell me about a time you went beyond what was asked.
What they check: initiative that served a real need, not extra work for its own sake.
Situation: My internship project was to add an export button to a reporting page.
Task: While testing it, I noticed the report itself took a long time to load for larger accounts.
Action: I shipped the export first, since that was my commitment. Then I profiled the page in my own time during the project, found an N+1 query, and asked my mentor whether fixing it was in scope before opening a pull request.
Result: He agreed, and the fix made the report load much faster for the largest accounts. I made sure the extra work never delayed what I had promised.
22.Describe a time you fixed a problem nobody had asked you to fix.
What they check: whether you notice problems and take responsibility for them.
Situation: Our test suite had a handful of flaky tests that everyone re-ran until they passed.
Task: Nobody owned them, and they were wasting time on every merge.
Action: I tracked which tests failed most often over two weeks, fixed the three worst (two had timing assumptions, one depended on test order), and posted a short note on the patterns so others could spot them.
Result: Re-runs dropped sharply, and two teammates fixed similar tests using the same patterns.
23.Tell me about a time you were on call or responsible when something broke.
What they check: calm under pressure, clear communication, and follow-up after the fire is out.
Situation: I was on call when our checkout API started returning errors late on a weekday evening.
Task: My job was to restore service and keep stakeholders informed.
Action: I checked recent deploys first, saw a configuration change from that afternoon, and rolled it back after confirming the error timing matched. I posted updates in the incident channel every 15 minutes. The next day I wrote the incident review and added validation so that config value could not be empty.
Result: Service recovered shortly after the rollback, and the validation has blocked the same mistake since.
24.Give an example of a time you improved a process.
What they check: whether you find and fix waste in how the team works.
Situation: In a research lab during my senior year, students ran experiments by copying and editing scripts by hand.
Task: I was a research assistant, and results were hard to reproduce because nobody knew which settings produced which result.
Action: I wrote a small command-line tool that read experiment settings from a config file and saved the config next to every result. I documented it and helped two other students switch over.
Result: The lab adopted it for new experiments, and the professor could finally trace each figure back to its exact settings.
25.Tell me about a time you made a decision with incomplete data.
What they check: judgment and bias for action when waiting is costly.
Situation: A third-party API we used for address validation started timing out, and their status page said nothing.
Task: I had to decide whether to wait or change our checkout flow during a busy week.
Action: I could not know how long the outage would last, so I chose the reversible option: put the validation behind a flag, turned it off, and let orders through with a warning for manual review. I set a reminder to check the vendor every hour.
Result: Orders kept flowing, and when the vendor recovered I turned the check back on. Choosing the easily reversible option let me act without full information.
Behavioral questions about deadlines and pressure
Deadline questions check how you prioritize, communicate early, and protect quality when time is short.
26.Tell me about a time you worked under a tight deadline.
What they check: prioritization and calm execution.
Situation: Two weeks before my internship ended, my team asked me to add a feature for a customer demo that was moved earlier.
Task: I had to finish it and still hand over my main project properly.
Action: I listed what the demo truly needed and agreed with my mentor to cut two nice-to-have screens. I built the core flow first, demoed it to him every two days, and wrote the handover notes for my main project in the evenings.
Result: The demo went ahead with the feature, and my handover notes let the team keep my main project moving after I left.
27.Describe a time you had to juggle several priorities at once.
What they check: how you decide what comes first and how you communicate trade-offs.
Situation: In my final semester I had a capstone milestone, a part-time job at the campus IT help desk, and job interviews in the same week.
Task: I needed to meet the capstone deadline without letting my team or my job down.
Action: I listed every commitment with its deadline and the cost of missing it, swapped one help desk shift with a coworker a week in advance, and told my capstone team which evenings I would be offline so they could plan around it.
Result: We hit the milestone, I kept every shift I had committed to, and I learned that telling people early is most of managing priorities.
28.Tell me about a time you realized you would miss a deadline.
What they check: whether you raise the flag early and come with options.
Situation: Halfway through a two-week task to migrate a service to a new queue system, I found the old system had undocumented retry behavior.
Task: I owned the migration and had committed to a date the team was planning around.
Action: I told my lead the same day, explained the new work, and offered two options: keep the date with a simpler retry design, or take four more days to match the old behavior exactly. I recommended the second because other services relied on it.
Result: We moved the date, and the migration shipped with no lost messages. Raising it early meant nobody downstream was surprised.
29.Give an example of a time you had to cut scope.
What they check: whether you can separate essential from nice to have and get agreement on it.
Situation: At a hackathon, our team planned an app with voice input, a map and user accounts.
Task: With 12 hours left, I realized we could not finish everything, and I was presenting.
Action: I asked what the judges actually needed to see: the core idea working end to end. We dropped accounts, faked the map with a static image clearly labeled as a mockup, and spent the remaining time making voice input reliable.
Result: The demo worked on the first try, which mattered more than features we would have shown half-broken.
30.Tell me about a time you stayed calm in a stressful situation.
What they check: composure and clear thinking under pressure.
Situation: My laptop died an hour before my end-of-internship presentation to the engineering team.
Task: I still had to present my project and live demo.
Action: I borrowed a teammate's laptop, pulled my slides from the shared drive, and ran the demo against the staging environment instead of my local setup. I told the audience at the start that I was on a borrowed machine in case anything looked different.
Result: The presentation went fine, and I now keep a backup of any demo running somewhere other than my own laptop.
Behavioral questions about ambiguity and learning
Ambiguity questions check how you make progress when requirements are unclear or the technology is new to you.
31.Tell me about a time you worked with unclear requirements.
What they check: whether you clarify before building and make sensible assumptions explicit.
Situation: A product manager asked me to add "better search" to an internal tool, with no further detail.
Task: I owned the feature and needed to turn the request into something buildable.
Action: I interviewed three heavy users, found that their real problem was searching by partial order numbers, and wrote a one-paragraph spec with my assumptions. I got the product manager to confirm it before writing code.
Result: I shipped partial-match search in a week instead of building a full search engine, and the users said it solved their problem.
32.Describe a time you had to learn something new quickly.
What they check: how you learn, and how fast you become useful.
Situation: On the first day of my internship I was assigned to a team using a mobile framework I had never used.
Task: My first task was due in two weeks.
Action: I did the framework's official tutorial in the first two days, read our app's code for the screens I would touch, and asked a teammate for a 30 minute walkthrough of how the app was organized. I kept a list of questions and asked them in batches.
Result: I shipped the task on time, and my notes became the start of the team's onboarding doc for that app.
33.Tell me about a time you had to make a decision without clear guidance.
What they check: judgment, and whether you document and communicate the decision.
Situation: Our capstone sponsor left for two weeks without answering whether the app needed to work offline.
Task: I was the team lead and we could not stop work for two weeks.
Action: I chose the approach that kept both options open: we stored data locally and synced it, which worked online and could be extended for offline use. I wrote the decision and reasoning in our project log and emailed the sponsor a short summary.
Result: When the sponsor returned, offline support turned out to be needed, and we added it in days instead of rebuilding.
34.Give an example of a time you had to change course midway.
What they check: adaptability, and whether you change direction based on evidence.
Situation: I was building a feature to recommend related articles using a machine learning model.
Task: Partway through, testing showed the model's suggestions were no better than simply showing articles with the same tags.
Action: I shared the comparison with my team, recommended we ship the simple tag-based version first, and proposed revisiting the model once we had more user data.
Result: We shipped weeks earlier, and the simple version did well enough that the team prioritized other work. Letting the test results decide saved us from maintaining a model we did not need.
35.Tell me about a time you were curious about something and it led to an improvement.
What they check: curiosity that turns into useful action.
Situation: While using my university's course registration site, I wondered why it became so slow during registration week.
Task: I was not responsible for the site, but I was studying web performance and wanted to understand it.
Action: I measured the page in my browser's developer tools, saw it loaded a very large uncompressed script, and wrote a polite email to the IT department with what I found and how compression could help.
Result: They enabled compression the next term and thanked me. It also became my favorite answer when interviewers asked what I learn outside class.
Put this guide to work
Build a one-page resume, check it against a real job description, then practice your answers out loud.
Practice next
- Amazon behavioral interview questionsTypical questions for each of Amazon's 16 Leadership Principles, with STAR samples.
- AI mock interviewPractice behavioral answers out loud and get feedback.
- Self introduction for interviewStructure and samples for the tell me about yourself answer.
- HR interview questions for freshersThe HR round, from salary questions to relocation, with sample answers.
- Interview process guidesHow the software engineer interview works at major tech companies, with sources.
- Resume builderMake sure every story you tell matches your resume.
- New grad software engineer jobsUS roles with a new grad, university or early career title, refreshed every 6 hours.
- Entry-level tech jobsBrowse jobs in India, the US, the UK, Canada, Europe, Australia and remote.
Frequently asked questions
What are the most common behavioral interview questions?
The ones that come up most for software roles are: tell me about a time you worked on a team, disagreed with someone, failed or made a mistake, showed leadership, handled a tight deadline, worked with unclear requirements, and received critical feedback. Prepare at least two stories for each theme.
What are the top behavioral interview questions for software engineers?
Expect questions about a technical disagreement, a bug or outage you handled, a project you are proud of, code review feedback you received, working with product or design, and learning a new technology quickly. They are the same STAR questions as other roles, with engineering situations.
How long should a behavioral interview answer be?
About two minutes for the first telling. Keep the situation and task short, spend most of the time on your actions, and end with the result. The interviewer will ask follow-up questions if they want more detail.
Can new grads answer behavioral questions without work experience?
Yes. Class team projects, capstone, internships, hackathons, open source, research, clubs, teaching assistant roles and part-time jobs all count. Interviewers care about how you behaved, not where it happened.
Should I memorize behavioral interview questions and answers?
Memorize your stories as bullet points and key facts, not word-for-word scripts. Scripted answers sound flat and fall apart under follow-up questions, while a well-practiced true story adapts to whatever is asked.