Internship Interview Questions

“I'm in my third year studying business, and the part I've enjoyed most is anything with numbers behind a decision, like the pricing module we did last term. Outside class I work part-time at a café, and I run the budget for our university drama society, which means I'm the one chasing receipts and telling people what we can actually afford. Both of those taught me that I like being the person who makes things organised. That's why this finance internship stood out. It's a chance to see how a real team plans and tracks money, and to find out whether I want to build my career in that direction.”

“I looked at a lot of marketing internships, and most of them were mainly about scheduling social posts. What caught my eye here was that interns sit with the research team and actually help run customer interviews. That's the part of marketing I care about most, understanding why people buy, and it's hard to get that experience as a student. I've done a small version of it for a class project where we interviewed twenty shoppers about a new snack idea, and I loved finding patterns in what they said. So this role lets me build on something I've already started, and it'll tell me if research is where I want to go after I graduate.”

“From what I read, you design and build public spaces, mostly parks and school grounds, and you work closely with local councils and communities. The project that stuck with me was the playground redesign on your site where you ran workshops with kids before drawing anything. I also watched a talk one of your senior designers gave about planting for dry summers. As a landscape architecture student, that mix of community input and practical planting is exactly what I want to learn, and it's something my course touches on but can't really give me hands-on. I'd love to hear how interns get involved in those early community sessions.”

“There are three things. First, I want to get properly good at the analysis tools your team uses every day. I've used them in class, but only on clean data sets, and I know real data is messier. Second, I want to see how a real project runs from start to finish, like how priorities get set and how people work with other teams, because that's something you can't learn in a lecture. And third, I'm trying to decide between going into research or working with clients after I graduate, so I'd like to spend time around both sides here if that's possible.”

“Right now I'm leaning towards a career in supply chain, because the operations modules have been my favourite part of my degree. But I've only seen it on paper, so this internship is a real test. If I enjoy working on stock planning and dealing with suppliers here, it'll confirm that's the direction I want and I'd love to apply for your graduate scheme. If I find I prefer the data side, that's useful to know too, and I'll have built skills that carry over either way. I'd rather find out now, while I'm still studying, than after my first full-time job.”

“In my second year of engineering, four of us had to build a small water filter from cheap local materials and test how clean it made muddy water. My part was the testing plan. I set up the same three tests for every design, measured cloudiness before and after, and kept the results in a shared sheet so we could compare fairly. Early on, our best-looking design actually did worst, and the data made that obvious, so we switched to a simpler sand and charcoal layout. We finished with the clearest water in the class. If I did it again, I'd start testing in week one instead of week three, because the numbers changed our minds so much.”

“I'd be upfront in the first couple of minutes. Something like, 'The goal was to cut the time it takes to process a return from three days to one. We got it to two, and here's why.' Then I'd spend most of the time on what we learned, maybe that one approval step caused most of the delay and needs a policy change, which is useful for the team to know. I'd show what's ready to use now and what I'd do next, with enough notes that someone can pick it up after I leave. Senior people usually respect a clear, honest account more than a presentation that hides the result.”

“I think my statistics course will be most useful. It taught me how to judge whether a difference between two groups is likely to be real or could just be random noise. Your job post mentions helping analyse customer survey results, and that's exactly where it matters, because it's easy to see a small change in scores and think something important happened. In class we worked with tidy, complete data, so the bit I'd need to learn is handling messy real responses, with missing answers and people who skipped questions. I'd ask whoever owns the surveys how they usually deal with that before I start drawing conclusions.”

“I'll pick 'Ran a fundraising campaign that doubled the charity society's donations.' The society raised money the same way every year, a bake sale that barely covered costs. I suggested we try an online page tied to a sponsored walk. I set up the page, wrote the posts and got each of the twelve walkers to share it with family. My part was mostly organising and chasing people, which was harder than I expected, because a few walkers never shared at all. We ended up with twice what we raised the year before. If I did it again, I'd start promoting three weeks earlier, because most money came in the last few days.”

“In a history group essay, one teammate kept missing our meetings and hadn't sent his section a week before the deadline. Instead of complaining in the group chat, I messaged him on his own and asked if everything was okay. It turned out he was working extra shifts and was embarrassed to say so. We agreed he'd swap his big research section for the editing and references, which he could do late at night, and I took on part of the research with another teammate. We submitted on time and got a good mark. Since then I set up a simple task list in the first meeting, with names and dates, so problems show up early.”

“At the library where I work part-time, students kept asking the same questions at the desk, like how to book a study room or print in colour. I noticed we were answering the same five things dozens of times a day. I wrote a one-page guide with screenshots and showed it to my supervisor before doing anything with it. She suggested a couple of changes and let me put it up as a poster by the desk and as a link on the booking page. The desk got noticeably quieter at busy times, and they still use an updated version of it. I learned it's worth running an idea past someone first, because her changes made it better.”

“I work best when I know clearly what the goal is and when it's due, and then I'm given room to work out how to get there. A quick check-in once a week or so helps me a lot, because I'd rather adjust early than find out at the end that I misunderstood something. At my part-time job, my best manager did exactly that, and I got more done there than anywhere else. That said, I know every supervisor is different. If someone is very busy and hands-off, I'll just be the one who books the check-ins and comes with specific questions.”

“Last term our group chose to present our research as a short video, and none of us knew how to edit. I volunteered, and we had about ten days. I watched a couple of beginner tutorials to learn the basics, then instead of trying everything, I made a one-minute practice clip with our own footage so I hit the real problems early, like sound levels jumping between clips. When I got stuck on that I asked a friend in media studies, who showed me how to even out the audio in five minutes. The final video was seven minutes long and our lecturer used it as an example for next year's class. My takeaway was to practice on the real thing as soon as possible.”

“In the first few days I'd focus on people and tools. I'd ask for a quick chat with each person on the team to understand what they do and how I might help, and I'd get properly set up on the tools they use. I'd keep a notebook of every term or process I don't know and look them up each evening. By the end of the first week I'd like to have one small, real task done, even something simple, so I understand how work is asked for, checked and handed in. At the end of week two, I'd sit down with my supervisor, agree what I'm aiming for over the rest of the internship and ask how I've done so far.”

“In my first year, I got an essay back with a low mark and a note that said my arguments were buried under too much description. Honestly, I was annoyed at first, because I'd worked hard on it. I went to my tutor's office hour and asked her to show me one paragraph where it happened. She pointed out I spent half a page retelling a case before saying what I thought. For the next essay I wrote my main point as the first sentence of every paragraph, then added evidence after. My mark went up by a full grade, and I still use that habit in reports and even emails.”

“When I was treasurer for our student society, I sent the whole membership an event email with the wrong date on it, a Saturday instead of a Friday. I noticed about an hour later when someone replied asking about it. I told the president straight away, sent a short correction with the right date in the subject line, and updated the event page and posters that afternoon. A couple of people still came on the wrong day, so I apologised to them personally and gave them priority seats at the next event. Now I get one other person to check the date, time and place before anything goes to the full list.”

“In the moment, I'd thank them and ask a couple of questions so I understand what they actually saw, like 'Can you show me where it went wrong?' Often feedback sounds unfair because I'm missing context, maybe the client wanted a different format. I'd take some time before responding, because reacting straight away rarely goes well. If I still thought it was wrong, I'd go back and say something like, 'I had a think about this. I did it this way because of this instruction. Did I misread it?' That keeps it about the work, not about me. And if they still want it changed, I'd change it. As an intern, part of the job is learning how this team likes things done.”

“I'd start by asking my supervisor in the first week what a great internship would look like from their side, maybe two or three things they'd want me to have done by the end. Then I'd ask for a short check-in every week or two, and I'd make my questions specific, like 'Was the level of detail in that report right?' because 'How am I doing?' usually just gets 'fine'. I'd also keep a simple log of what I worked on and any feedback I got. That helps me spot patterns, and it's useful at the end when I'm writing up what I learned or asking for a reference.”

“During exams last spring I was also captain of our football team and working two evening shifts a week at a supermarket. What worked was planning the whole week every Sunday: shifts and training went in first because they were fixed, then I put study blocks in the gaps, even forty-minute ones on the bus. I told my manager two weeks ahead that I needed one exam week off, and he swapped me with someone. I also handed the team's travel planning to our vice-captain for that month. I passed everything and we didn't miss a match. The main lesson was to ask for changes early, not the night before.”

“The key thing is not to let it become a surprise. As soon as I saw the clash, I'd tell my supervisor, ideally weeks before, and bring a suggestion rather than just a problem. For example, I could work extra hours the week before to get my part done early, or hand over a clear piece to someone else with notes. I'd ask what matters most for that deadline, because maybe only one part really needs me. Whatever we agree, I'd stick to it and send a quick update if anything changes. My studies come first in exam week, but that doesn't mean the team should suffer because I didn't plan.”

“I can start on the first of June, right after my last exam, and I'm free until the end of August, when my classes start again. During the summer I can do full-time hours, Monday to Friday. There's one thing to flag now: I have a family wedding in the middle of July and would need two days off that week. If you'd like me to keep going part-time once term starts, I could do about twelve hours a week, on Tuesdays and Thursdays, since those are my lighter days. I'd rather be clear now than surprise you later.”

“Yes, it counts as a work placement module in my degree. My school needs three things. There's an agreement form that you and the university sign before I start, which I'd bring to you. I need to complete a minimum number of hours, which the summer schedule easily covers. And at the end, my supervisor fills in a short one-page evaluation of my work. I'd also write a reflective report myself, but that's my job, not yours. I'll send you the form and deadlines in one email so nothing gets missed, and I'll remind whoever supervises me a couple of weeks before the evaluation is due.”

“First I'd reread the instructions and write down exactly which part I don't understand, so my question is specific. Then I'd look for examples, like a similar report in the shared folder from last year, because that often answers it. If I'm still unsure, I'd ask someone else on the team, maybe the person who sits nearest or another intern who's been there longer. I'd also send my manager a short message they can answer between meetings, something like, 'For the customer summary, do you want every region or just the top three?' Meanwhile I'd start on the parts I'm confident about and keep a note of any assumption I made, so it's easy to adjust later.”

“Before anything else, I'd go back over what I finished, because finishing early sometimes means I've missed something. Then I'd tell my manager it's done and ask what they'd like next, or whether anyone on the team could use a hand. If they're busy and can't answer straight away, I'd pick something useful I can do without supervision, like reading the team's past project documents, learning a tool they use that I'm new to, or tidying my notes from the week. I'd rather be the intern who asks for more work than the one who looks busy doing nothing.”

“I wouldn't try to secretly do both and hand in two rushed pieces. As soon as I realised, I'd let both of them know, something like, 'I've got the slides for you and the data check for Sam, both due at three. I don't think I can do both properly.' If they can agree between themselves, great. If not, I'd ask my supervisor, since they know what matters most to the team. I'd also offer options, maybe I can do a first draft of the slides by three and the full version tomorrow morning. Being honest early is better than disappointing someone at the deadline.”

“First I'd check it quickly, because as an intern I might just be missing context. Say the total in a table doesn't match the numbers above it. If I'm fairly sure, I'd go to the person who wrote it, privately, and put it as a question, like, 'I might be wrong, but should this total be different?' Most people are grateful to catch it before a client does. If it's about to be sent and I can't reach them, I'd tell my supervisor straight away rather than stay quiet. I'd never point it out in a group email or in front of the client. The goal is to protect the work, not to show that I found an error.”

“To me, it's mostly about people being able to rely on you. That means turning up on time, doing what I said I'd do, and if I can't, telling someone early instead of hoping nobody notices. It also means clear communication, like replying to messages the same day and giving short updates on my work without being asked. And it's respecting the workplace, keeping client or company information private, even from friends, and fitting in with how the team does things before suggesting changes. In class, if I'm late with an assignment, I lose marks. At work, other people are waiting on me, so it matters more.”

“Honestly, I expect some of it, and I'm fine with it. Routine tasks still matter, because if the data I enter is wrong, someone's report is wrong. I'd try to do it accurately and quickly, and I'd use it to learn, like noticing what information the team tracks and why. If I see a way to make it faster, maybe a simple template or a checklist, I'd suggest it. Once I've shown I can be trusted with the basics, I'd ask whether I could shadow or help with a bigger project too. In my experience, people give more interesting work to someone who did the boring work well.”

“That's fair, I haven't worked in software yet, and that's partly why I want this internship. What I can show you is how I work. In my final-year project I built a small app for booking lab equipment, and I learned a new framework on my own to do it. I've also worked in a busy restaurant for two years, which taught me to stay calm under pressure and take instructions from different people without dropping things. I'm not coming in with habits from somewhere else, so I'll learn your way of doing things properly. And I've already started going through the tools you listed in the job post.”

“Yes, I have a few. First, what did last year's interns spend most of their time on, and is there a project you're especially proud of that an intern worked on? Second, who would I be working with day to day, and how do you usually give interns feedback during the placement? And third, what separates an intern who does okay from one you'd really want back after they graduate? Finally, could you tell me what the next steps and timeline look like after today?”