Research Scientist Interview Questions
For physicists doing experimental or theoretical research. Interviews focus on measuring the properties of matter and energy, analyzing data and developing theories.
30 questions, ranked by what the job needs most
Also for Research Scientist: Chemists · Biologists · Food Scientists and Technologists · all 15 sets →
Print the top 10:Scoring sheetPractice sheet
Question 1: Walk me through a computer-based calculation you used to analyze physics data.
Example answerThe interviewer wants to see how you use computer-based calculations to analyze physics data and check the results.
Build the answer in order: the problem, the method and tools, the checks, and what the result meant. Be specific about the software or language, but spend most of your time on how you verified the output. Good checks include reproducing a known result, testing limiting cases, comparing two independent methods and looking at how the answer changed with step size or sample size.
Sample answer: "For my thesis I fit a model to temperature-dependent resistance data from a thin film. I wrote the fitting code in Python and used a standard least-squares routine. Before trusting it, I ran it on simulated data with known parameters and got them back within their errors. I also checked that the fit behaved sensibly at the high-temperature limit, where the theory is simple. One fit failed that test, and it turned out I had a unit error in one input file."
Pitfalls to avoid: listing tools without explaining the analysis, skipping the verification step, and claiming precision you can't explain.
Interviewer tipListen for the physical model, numerical method and a suitable check, such as units, a limiting case or an independent calculation. Treating physics output as correct without any check is a red flag.
Candidate tipChoose one physics analysis and explain the physical model, code or software, and your own calculations. Show how you checked units, a known result or a limiting case before interpreting the output.
Question 2: What do you check before trusting a measured signal in a physics experiment?
Interviewer tipA strong answer explains how the candidate checks for background noise or instrument drift and accounts for uncertainty. Calling a single spike a detection without checking the background is a red flag.
Candidate tipStart with the signal you expect to measure. Explain how you check for background noise or instrument drift, then say how measurement uncertainty affects the conclusion you can draw.
Question 3: Tell me about an experiment in which you used lasers, detectors, telescopes or similar instruments to measure a physical property that was hard to pin down.
Example answerThe interviewer wants to know whether you understand your instruments well enough to get a trustworthy measurement out of a difficult experiment.
Use Situation, Task, Action, Result. Name the property and the instrument, then focus on what made it hard: noise, drift, weak signals, alignment or background. Explain the steps you took and how you estimated the uncertainty in the final value.
Sample answer: "In a lab project I measured the lifetime of an excited state using a pulsed laser and a photodetector. The signal was weak and the background from scattered light was close to it in size. I added a filter, shielded the detector and took background runs with the sample removed so I could subtract them. I also repeated the measurement on different days to check for drift. The final value agreed with published results within our uncertainty, and I could explain where most of that uncertainty came from."
Pitfalls to avoid: describing the equipment without the measurement, leaving out how you estimated errors, and taking credit for a team setup you didn't build or run.
Interviewer tipListen for how they set up and calibrated the instrument, found the main sources of error and judged whether the signal was real. Vague talk about equipment with no measurement in it is a red flag.
Candidate tipName the property you measured and the instrument. Explain what made it hard, such as noise, drift or a weak signal, what you changed to deal with it, and how confident you were in the final value.
Question 4: Walk me through how you used an equation in a physics report to express a finding from your observations.
Interviewer tipListen for a clear link between the terms in the equation and what the candidate observed. Presenting a relationship that fits one range of measurements as a general law is a red flag.
Candidate tipPick a report where the math helped you state a finding precisely. Explain what the terms stood for, how the equation related to your observations and where the relationship held.
Question 5: Walk me through how you tested a theoretical model you built or refined from experimental data.
Example answerThe interviewer wants to learn how you use experimental evidence to test a theoretical model rather than just fit observations.
Use Situation, Task, Action, Result to organize one real example. Briefly describe the physical system, the data, and your role in building or refining the model. Focus on your assumptions, the prediction you tested, and the evidence you used to judge it. End with the result and what you learned about the model's limits.
For example: "I refined a model of a damped oscillator using an initial set of measurements. I then predicted its motion under a different starting condition and compared that prediction with new measurements. The model missed part of the decay pattern. I checked the measurement uncertainty and found that our damping assumption needed more work. I revised the model and tested it again. That taught me to distinguish a useful fit from evidence that a model holds beyond the original data."
Avoid calling agreement with the fitting data proof, leaving out measurement uncertainty, or hiding results that challenged your assumptions.
Interviewer tipListen for their own model predictions, checks against experimental data, and lessons from the result. Calling a fit to the original data proof of the model is a red flag.
Candidate tipChoose a real model you built or refined. Explain the data, your test of its predictions, the result, and what you learned about the model's limits.
Question 6: Describe a time you chose which physical effects to leave out of a computer simulation.
Interviewer tipA strong example ties omitted effects to the simulation's purpose, explains their likely size, and gives the outcome and a lesson. Ignoring an effect known to drive the result is a red flag.
Candidate tipName the physical system and the simulation's purpose. Focus on an effect you left out, the evidence behind that choice, and how it affected the result. Include what you learned about the limits of the model.
Question 7: Tell me how you worked with other scientists when a prototype instrument gave inconsistent readings.
Interviewer tipA strong example shows how the candidate used a colleague's input to agree on what to check next. Changing the setup without telling the people comparing the readings is a red flag.
Candidate tipBriefly describe the inconsistent readings and what your colleagues noticed. Focus on your part in deciding together what to check next, and end with what the check showed.
Question 8: Share an example of how you reported a physics experiment's results in a journal paper or a conference presentation.
Interviewer tipListen for a clear main finding backed by evidence the audience could follow. Leaving out a result that weakens the paper or talk's main claim is a red flag.
Candidate tipName the main finding and describe how you chose a figure, table or other evidence to convey it. Include any limit you needed to make clear to readers or listeners.
Question 9: Tell me about a time you narrowed a physics research proposal to make the work feasible with the funding available.
Interviewer tipListen for their own choices about scope, a realistic link between costs and research aims, and the outcome. Keeping aims they knew the budget could not support is a red flag; ask what they learned.
Candidate tipChoose one physics proposal with a funding limit. Explain which aims you kept or cut, the reasons for those choices, and the result. End with what you learned about setting a realistic scope.
Question 10: Tell me about a recent programming project you did for research, such as a simulation or data analysis code.
Example answerThe interviewer wants to know whether you can write research code that is correct, usable and connected to a real physics question.
Start with the goal of the code, then the language and tools you chose and why. Pick one hard problem you solved, explain how you tested the code, and say what results it produced.
Sample answer: "Last year I wrote a Monte Carlo simulation in Python to model how particles scatter in a detector material. The first version was too slow for the number of events we needed, so I rewrote the inner loop using vectorized arrays and moved the slowest part to a compiled library. To test it, I ran cases where we knew the answer analytically and checked the energy loss against published tables. I kept it in version control with a short guide so another student could run it. The group used it to choose the detector thickness for a new prototype."
Pitfalls to avoid: listing languages instead of describing a project, leaving out testing, and overstating your role in shared code.
Interviewer tipLook for clear choices about language, libraries and structure, and some testing or version control. A good answer also says how the code served the physics question. Code nobody else could run is a warning sign.
Candidate tipSay what the code had to do and why. Mention the language and tools, one hard problem you solved, how you tested it, and what results it produced for the project.
Question 11: Share an example of how you chose relevant, reliable results from multiple physics papers or data sets for a research question.
Example answerThe interviewer wants to learn how you judge the relevance and reliability of physics results drawn from different sources.
Use Situation, Task, Action, Result for one research question. Identify the papers or data sets you compared and your role in selecting evidence. Explain your checks of the physical conditions, methods, uncertainty, and limits of each source. End with how your selection affected the work and what you learned.
For example: "I was comparing optical detector measurements to understand a background signal. I gathered papers and data sets, then checked the wavelength ranges, measurement conditions, calibration methods, and reported uncertainties. One paper looked useful at first, but its detector operated outside the range we were studying. I left it out of the direct comparison and noted that limit. Comparing the remaining results helped me narrow the explanations we needed to test. I learned to check whether measurements are comparable before treating disagreement as a physical effect."
Avoid relying on a journal's reputation alone, choosing only results that support your idea, or combining measurements without checking their conditions.
Interviewer tipListen for their own checks of methods, uncertainty, and relevance to the research question, plus the result and lessons learned. Treating a paper's prestige as proof its findings are sound is a red flag.
Candidate tipPick a real research question. Describe the papers or data sets you compared, your checks for relevance and reliability, and how your choices shaped the work. Include what you learned.
Question 12: What would you do if you were asked to review a physics paper that closely overlapped your own unpublished research?
Interviewer tipThe overlap should be disclosed to the journal editor before accepting, with the manuscript kept confidential. Using its ideas or data to advance their own unpublished research is a red flag.
Candidate tipExplain what you would tell the editor about the overlap and how you would decide whether you could review fairly. Address how you would keep the manuscript separate from your own research.
Question 13: Tell me how you helped students or non-specialists understand a difficult physics concept.
Example answerThe interviewer wants to learn how you make a difficult physics concept understandable to students or non-specialists.
Organize a real example using Situation, Task, Action, Result. Name the audience, the concept, and where understanding broke down. Describe your own explanation or demonstration and how you checked its effect. Finish with evidence of learning and what you would carry into another explanation.
For example: "I was explaining energy conservation to introductory students who thought friction made energy disappear. I asked them to describe a block sliding to a stop, then used an energy diagram to show energy moving from motion into thermal energy. I kept the first explanation free of equations so we could focus on that change. Next, I asked them to explain a different sliding example in their own words. Their explanations showed that they could account for the energy after the block stopped. I learned that asking learners to apply an idea tells me more than asking whether it makes sense."
Avoid giving only a hypothetical teaching plan, overwhelming the audience with unexplained terms, or treating quiet attention as evidence of understanding.
Interviewer tipLook for a real example of adapting a physics explanation to the audience and checking their understanding. Assuming silence proves understanding is a red flag; ask what they learned from the attempt.
Candidate tipChoose one real physics explanation. Name the audience and concept, describe what you did to make it clear, and give evidence of their understanding. End with what you learned about teaching it.
Question 14: What would you do if a student proposed a physics lab experiment that could put classmates at risk?
Interviewer tipProtect classmates before any trial, explain the hazard to the student, and guide a safer way to explore the physics. Allowing a risky demonstration just to see whether it works is a red flag.
Candidate tipStart with how you would keep the proposed experiment from putting classmates at risk. Then explain how you would discuss its hazards with the student and help them explore the physics safely.
Question 15: Share an experience in which your attention to detail and thoroughness had an impact on your last company.
Example answerThe interviewer wants proof that you catch errors others miss and that this protects the organization.
Use Situation, Task, Action, Result. Describe what you were checking, what you noticed, and how you found it, such as comparing against a source or double-checking totals. Then explain what would have happened if the error had gone through, and what you did to prevent it next time.
Sample answer: "While preparing an order for a large customer, I compared the quantities against the signed quote, as I always do, and saw that one item had been entered as 1,000 units instead of 100. I flagged it to my supervisor, we corrected it before it shipped, and we avoided a costly return. Afterward I suggested adding a quote-check step to the order form, and the team adopted it."
Pitfalls: Don't just say you're detail-oriented without an example. Avoid exaggerating the dollar impact. Don't describe perfectionism that caused missed deadlines.
Question 16: Share a time when you successfully used scientific rules or methods to solve a problem at work.
Example answerThe interviewer wants to see that you solve problems in a careful, evidence-based way rather than by guessing.
Use Situation, Task, Action, Result. Describe the problem, the idea you formed about its cause, how you tested that idea by changing one thing at a time, and what the results showed.
Sample answer: "Samples from one of our machines kept failing a quality check, but only on some days. I suspected temperature, so I recorded the room temperature and the test results for two weeks. The failures lined up with the warmest afternoons. I then ran test batches at two set temperatures, changing nothing else, and the pattern held. We moved the heat-sensitive runs to the mornings and added better cooling, and the failures stopped."
Pitfalls: Don't jump to a fix without testing the cause. Avoid changing several things at once and claiming one of them worked. Don't use technical terms without a plain explanation.
Question 17: Tell me about an experience in which you analyzed information and evaluated results to choose the best solution to a problem.
Example answerThe interviewer wants to see how you make decisions: what information you gather, how you compare options, and how you check that your choice worked.
Use Situation, Task, Action, Result. Describe the problem, the information you looked at, the options you weighed, and why you picked one. Then show how you measured whether it worked.
Sample answer: "Customer complaints about late deliveries had been rising for two months. I pulled the delivery records and saw most delays came from one shipping route. I compared three options: switching carriers on that route, moving pickup earlier, or adding a second pickup. An earlier pickup cost nothing and fixed the timing gap, so I recommended it. We tracked deliveries for the next month, and late arrivals on that route dropped back to normal."
Pitfalls: Don't jump straight to the solution without explaining how you chose it. Avoid quoting precise figures you can't explain. Don't skip how you checked the result.
Question 18: Name a time when your creativity or alternative thinking solved a problem in your workplace.
Example answerThe interviewer wants to see that you can find a new approach when the usual one isn't working.
Use Situation, Task, Action, Result. Describe the problem and why the normal fix didn't work. Then explain your idea, where it came from, and how you tested it. End with the result and whether the idea was kept.
Sample answer: "Our training sessions for new staff had poor attendance because people couldn't step away from their work for an hour. Instead of rescheduling again, I suggested splitting the material into ten-minute videos people could watch between tasks. I recorded the first three as a test. New staff finished them within their first week, and my manager asked me to turn the rest of the training into the same format."
Pitfalls: Don't describe an idea that was never tried. Avoid claiming sole credit if others helped build it. Don't confuse creativity with ignoring rules or safety steps.
Question 19: How do you plan and prioritize your work when experiments, data analysis, writing and funding deadlines all compete for your time?
Interviewer tipGood answers show a real system, such as fixed deadlines first, protected time for writing and buffers for equipment problems. Saying they just work longer hours is a red flag.
Candidate tipDescribe how you actually plan a week or a month. Give one example of a clash, such as beam time against a paper deadline, and how you decided what came first.
Question 20: Describe how you worked toward a long-range physics research goal you set.
Interviewer tipStrong answers break the goal into milestones, mention funding or equipment needed and show adjustments when results changed the plan. A goal with no concrete steps is a weak sign.
Candidate tipPick one goal, such as building an instrument or settling a research question. Explain the milestones, what slowed you down, how you adjusted, and where it stands now.
Question 21: Describe a time you handled tension with a difficult collaborator or co-author on a research project.
Example answerThe interviewer wants to learn how you handle tension with a research collaborator while keeping the work productive.
Build your answer using Situation, Task, Action, Result. Briefly explain the disagreement and your responsibility on the project. Spend most of the answer on your own actions, including how you understood the collaborator's concern and addressed it. Finish with the effect on the research and a lesson you carried forward.
For example: "A collaborator and I disagreed about whether our analysis was ready to include in a paper. I thought we had checked enough, but they wanted another uncertainty check. I asked them to identify the unresolved concern, then we reviewed the analysis together. I proposed a short list of checks and took responsibility for part of it. We found an assumption that needed a clearer explanation and revised the draft. I learned to discuss specific concerns early instead of treating a request for more checking as a personal criticism."
Avoid attacking the collaborator, describing only what the team did, or claiming the tension disappeared without explaining your part.
Interviewer tipA strong example shows their own steps to address the tension and the effect on the research project. Blaming the collaborator for everything without examining their own actions is a red flag.
Candidate tipSet up the disagreement with your collaborator briefly. Focus on what you did, how it affected the research project, and what you learned about working together.
Question 22: How do you balance cooperation with others and independent thinking? Share an example.
Example answerThe interviewer wants to see that you can work well with a team while still bringing your own judgment, and that you know when to speak up and when to go along.
Start with a short answer about how you balance the two, then give one example. A good example shows you sharing your own view, listening to others, and then supporting the team's decision even if it wasn't yours.
Sample answer: "I try to form my own view first, share it clearly, and then commit to whatever the group decides. On one project, the team wanted to launch a new form right away. I thought we should test it with a few users first and explained why. We agreed on a one-week trial. Testing found a confusing field, we fixed it, and the full launch went smoothly."
Pitfalls: Don't present yourself as someone who always goes along or always insists on your own way. Avoid a story where you ignored the team's decision. Don't skip the example.
Interviewer tipTry to determine if the candidate has a cooperative attitude or is otherwise good-natured.
Candidate tipThe employer wants to know that you have a cooperative attitude or are otherwise good-natured.
Question 23: Tell me about a time your advice to a lab director improved your group's physics research.
Example answerThe interviewer wants to see how your advice to a lab director helped improve the group's physics work.
Use Situation, Task, Action, Result. Describe the decision on the table, what your analysis showed, how you presented it and to whom, and what changed.
Sample answer: "Our group planned to buy a new detector to improve the resolution of a measurement. I ran a quick error budget and found that most of our uncertainty came from temperature drift in the sample stage, not the detector. I put it on one slide that showed each source of error and how much a new detector would actually help. My lab director was skeptical, so I proposed a two-week test with better temperature control first. The test showed less temperature drift, which supported improving the stage before committing to a detector purchase. My lab director used that comparison to revise the equipment plan."
Pitfalls to avoid: taking credit for a group decision, giving advice with no analysis behind it, and leaving out how you handled disagreement.
Interviewer tipListen for advice to a lab director backed by measurements or a comparison of research methods, and a clear result. Taking credit for the group's improvement without explaining their own role is a red flag.
Candidate tipPick a real recommendation about equipment, lab time or a research method. Describe the evidence you showed the lab director, your own role in the discussion, and the improvement that followed.
Question 24: What is the key to success when writing research proposals to receive funding?
Question 25: How would you rate your writing skills?
Example answerThe interviewer wants an honest self-assessment and evidence that your writing is clear enough for the job.
Give a direct rating, then back it up with the kinds of writing you do and one example. Mention how you make sure your writing is clear, such as knowing your reader, keeping it short, and proofreading. If there's an area you're improving, say what you're doing about it.
Sample answer: "I'd rate my writing as strong for everyday work. I write emails, short reports, and how-to guides for my team. Before I send anything important, I ask myself what the reader needs to do with it, put that first, and reread it once out loud. Last year I rewrote our team's onboarding guide, and new staff said it was easier to follow. I'm still working on keeping longer reports concise."
Pitfalls: Don't give a rating with no evidence. Avoid rating yourself as perfect. Don't claim writing experience you couldn't show if asked for a sample.
Interviewer tipAsk for an example that demonstrates great writing skills.
Candidate tipOffer up examples that demonstrate your mastery of English grammar, rules of composition, and adjusting for the audience.
Question 26: Tell me about the last time you monitored or reviewed information and detected a problem. How did you respond?
Example answerThe interviewer wants to see that you keep an eye on your work area or data, notice problems early, and act on them.
Use Situation, Task, Action, Result. Describe what you were checking and how often, what signaled the problem, and the steps you took right away. Include who you told and what you did to stop it happening again.
Sample answer: "I review our inventory report every Monday. One week I saw that one item's stock had dropped far faster than usual. I checked the order records and found a duplicate order that had shipped twice to the same customer. I told my supervisor, contacted the customer to arrange a return, and asked our systems team to block duplicate orders. The return came back the following week, and we haven't seen the problem since."
Pitfalls: Don't pick a problem someone else found and you only fixed. Avoid stopping at the fix without saying how you prevented a repeat. Don't stay vague; name what you were monitoring.
Question 27: Share an experience in which your diligence of inspecting equipment, structures, or materials helped you identify a problem or the cause of a problem.
Example answerThe interviewer wants evidence that you inspect carefully and that your checks catch problems before they grow.
Use Situation, Task, Action, Result. Say what you were inspecting and why, what you noticed, how you traced the cause, and what happened after you reported or fixed it.
Sample answer: "During a routine walk-through, I noticed a small puddle of fluid under one of our machines. It wasn't on the checklist, but I wiped it up and checked again an hour later, and it was back. I followed the line and found a fitting that had worked loose. I tagged the machine, reported it to my supervisor, and maintenance replaced the fitting before the end of the shift. If it had failed during a full run, we would likely have lost most of a day."
Pitfalls: Don't claim you never miss anything. Avoid stories where you found a problem but didn't report it. Don't skip how you confirmed the cause.
Question 28: Share an experience in which you conducted a test of a product, service, or process and successfully improved the quality or performance.
Example answerThe interviewer wants evidence that you test things carefully and use what you find to make them better.
Use Situation, Task, Action, Result. Explain what you tested and why, how you set up the test, what the results showed, and what you changed. End with how you measured the improvement.
Sample answer: "Customers kept saying our online order form was confusing, so I was asked to look into it. I had five coworkers who had never used the form place a test order while I watched and took notes. Four of them got stuck on the same shipping step. I suggested moving that step and rewording two labels, then ran the same test again. All five finished without help, and complaints about the form dropped over the next month."
Pitfalls: Don't describe a change made on a hunch with no test. Avoid skipping how you checked the result. Don't use jargon without explaining it.
Question 29: Share an experience in which you were able to generate a new design or modify a current design to better serve the needs of your customers.
Example answerThe interviewer wants to see that you design with the customer in mind and can turn their needs into a better result.
Use Situation, Task, Action, Result. Explain what customers needed or complained about, how you learned about it, the change you designed, how you tested it, and what happened after.
Sample answer: "Customers told our support team that one of our parts was hard to install because two screw holes were difficult to reach. I read through the support notes, talked with two installers, and redesigned the mounting plate to move the holes to the front. We built a prototype and had an installer try it. Installation went faster, and complaints about that step stopped after the new version shipped."
Pitfalls: Don't describe a design change based only on your own taste. Avoid skipping how you tested the new design. Don't forget the result for customers.
Question 30: Tell me about a time when your ability to analyze needs and product requirements helped you create an effective design or make an informed decision to benefit your company.
Example answerThe interviewer wants to see how you find out what is really needed before you design something or make a decision.
Use Situation, Task, Action, Result. Explain how you gathered the needs or requirements, how you weighed them, the design or decision you reached, and how it helped the company.
Sample answer: "Our team was asked to choose a new tool for tracking customer requests. Instead of starting with product demos, I talked to the people who would use it every day and listed what they needed most: quick search, simple tags, and reports for managers. I scored three options against that list and shared the results. We chose the one that fit the daily work best, even though it had fewer extra features. People were using it within a week, and we didn't need a second round of training."
Pitfalls: Don't jump to the solution without showing how you learned the needs. Avoid a decision made only on cost or personal preference. Don't skip the benefit to the company.