20 most-asked questions in entry-level / internship loops. Plus a STAR-method explainer and 5 full example answers, drawn from class projects, lab work, and campus jobs (because that’s what you have).
Every behavioral answer is 4 beats. Memorize the pattern, fill it with your own story.
S
Situation
Set the scene in 1–2 sentences. Class, project, role, team size. Don't over-narrate.
T
Task
What was YOUR responsibility (not the team's)? Be specific about what you owned.
A
Action
The bulk of the answer (60–70%). What you actually did, how you decided, what you tried, what trade-offs you made.
R
Result
The outcome with numbers. "We shipped" → weak. "We shipped on time and grew DAU 18%" → strong. End with what you learned.
The 60-90 second rule
A great behavioral answer is 60–90 seconds spoken, about 150–220 words. Longer = the interviewer zones out. Shorter = no signal. Time yourself when practicing. If you’re hitting 2 minutes, you’re narrating the Situation/Task too long; cut that section to 20% of the total.
Have a STAR answer ready for at least one in each category. Reuse stories across questions.
Conflict & teamwork
Ownership & initiative
Failure & learning
Motivation & fit
Read these out loud. Notice the rhythm, short S, short T, long A, sharp R.
Tell me about a time you disagreed with a teammate.
S In my software engineering capstone, our 4-person team was building a campus marketplace.
T I was the backend lead. My teammate wanted to use Firebase; I thought we needed Postgres for the relational data.
A I scheduled a 30-minute call with him, brought a 1-pager comparing the two on cost, query flexibility, and team familiarity, and asked him to do the same. We discovered Firebase auth would save us a sprint, and Postgres mattered for the seller-product join. We picked Postgres for the DB and Firebase Auth, best of both. I also proposed we'd split the integration so neither of us owned the whole stack alone.
R We shipped the MVP 2 weeks early. The disagreement actually surfaced a hybrid neither of us had considered solo. He told me later it changed how he runs technical debates.
Tell me about a time you took initiative.
S I was a research assistant in the bioinformatics lab my junior year.
T My PI was manually re-running an alignment pipeline every time we got new sequences, about 4 hours of her time each week.
A Without being asked, I wrote a Bash script that watched a folder and triggered the pipeline automatically, plus a Slack notification when it finished. I tested it on 3 weeks of historical data, then asked her if she wanted to switch over. She said yes within an hour.
R It saved her ~16 hours/month. She used the time to write the paper section I was a co-author on. The script is still running 18 months later in the lab.
Tell me about your biggest failure.
S Sophomore year I was the treasurer for the entrepreneurship club, managing a $3K annual budget.
T I was supposed to track all event spend in our shared sheet, but I started doing it from memory once my classes got heavy.
A Mid-semester we ran a hackathon and overspent on prizes by ~$400, money we didn't have. When the president asked for the budget update, I had to admit the books were behind. I sat down that weekend, reconciled three months of receipts, and built a simple Google Form that auto-logged every purchase to the sheet so this couldn't happen again.
R We covered the $400 with a sponsor outreach the next week. More importantly, the form reduced reconciliation work to zero, and the next treasurer kept using it. Lesson: when something gets hard, build the system first, don't muscle through it.
Why this role?
S I'm applying for the [Role] internship at [Company] because of two specific things.
A First, the [specific product or team thing, "the way your data team rebuilt the experimentation platform"], based on the [where you read it, engineering blog, talk]. Second, my last project was [related project], and I came out of it wanting to go deeper into [area].
R I think the next 12 weeks of an internship would let me ship something real on [team], and I'd come back to school with the kind of system-level perspective you can't get from coursework. That's the trade I'm looking to make.
What's a skill you've actively worked to improve?
S Last year I realized my code reviews were getting glossed-over comments, "LGTM” from teammates without real engagement.
T I wanted to give better reviews and get better ones in return.
A I started spending 20 minutes per review minimum and writing one specific question per PR (not just nitpicks). I also asked my CS group to spend 5 minutes at the end of each meeting reviewing one piece of each other's code aloud. After a month, I changed the way I named functions and structured tests because of feedback I'd never have gotten otherwise.
R My capstone code passed our prof's audit on the first try. More importantly, I now treat code review as a thinking activity, not a gate.