Clinical Research Associate Interview Questions

"I did a life sciences degree and then took a job as a study coordinator at a hospital research unit. I worked on three trials there, mostly in cardiology, so I handled consent, visit scheduling, data entry and a lot of queries. The part I found most interesting was when our CRA came in. She'd spot things we'd missed, like a lab value that made a patient ineligible, and explain why it mattered for the whole trial. That made me see the job as protecting patients and the data across many sites, not just one. I've got the site side of it in my hands now, and I want to take that into monitoring, where I can help sites get it right from the start."

"I looked at your public trial listings, and most of your current work is in oncology, with a few early phase studies and a couple of large late phase ones. That fits me well, because two of the trials I supported as a coordinator were oncology studies, so I'm used to complex eligibility rules, lots of imaging and a heavy safety reporting load. I also noticed you run many of your trials with a smaller number of experienced sites, which tells me the relationship with each site matters. That's the part of monitoring I enjoy most. I want to grow in oncology specifically, and this looks like a place where I could go deep instead of jumping between areas."

"Over the last three years I've monitored four studies. Two were phase three trials in diabetes, where I had six sites each and did qualification, initiation, routine and close-out visits on my own. One was a phase two respiratory study with three sites, and the last was a small phase one study where I co-monitored with a senior CRA. I've worked in two different EDC systems, raised and closed queries, filed documents to an electronic TMF and logged visit reports in a trial management system. I've also handled drug accountability and one site through a sponsor audit. So I'm comfortable running sites independently, and I'm still building experience in early phase work."

"I plan my month around visit dates first, then block time straight after each visit to write the report while it's fresh, because reports are the thing that slips when you're travelling. Before every visit I prepare from a checklist: open actions from last time, queries, new documents, expiring items, and what central monitoring has flagged. I keep one tracker across all my sites so nothing lives only in my head. Working alone doesn't mean working without support, so I keep in regular touch with my study manager and other CRAs on the study. And if I can see I'm heading toward too many sites or late reports, I say so early. It's much easier to fix a workload problem before a deadline than to explain a missed one after it."

"Phase one is about safety. A small group, often healthy volunteers but sometimes patients, as in cancer studies, gets the drug so we can learn how it's tolerated, how the body handles it and what dose range is safe. Phase two moves into patients with the condition to see if there's a real signal that it works and to narrow down the best dose, while still watching side effects closely. Phase three is the big confirmatory stage, usually randomised and often across many sites and countries, comparing against placebo or the current standard treatment. That's the data the approval decision rests on. Phase four happens after approval and looks at long-term safety and use in the wider population. As a monitor, early phases mean close safety oversight, and late phases mean consistency across many sites."

"The coordinator works at the site, for the principal investigator. They schedule visits, help with consent, collect data, enter it into the case report forms and keep the site file in order. The CRA works for the sponsor or a CRO acting for the sponsor. My job is to check that the site is running the trial as the protocol and GCP require, that participants are protected, and that what's in the database matches the medical records. So we meet all the time: the coordinator is usually my main contact, and I help them understand the protocol and fix problems. But the line matters. I can train, explain and point out issues, but I don't enter site data or sign site documents, because then I'd be checking my own work."

"Good Clinical Practice is the international ethical and scientific quality standard for how trials are designed, run, recorded and reported. The ICH E6 guideline is the one most sponsors work to, and local laws sit on top of it. It has two big aims. First, the rights, safety and well-being of participants come before the interests of science or the sponsor. Second, the data has to be credible and accurate. As a monitor, the principles I lean on most are that every participant gives informed consent freely before anything happens, that the study only runs with ethics approval and follows the approved protocol, that staff are qualified for the tasks they're given, and that records are accurate and can be traced back to source. Every check I do on a visit links to one of those."

"An ethics committee, or IRB in some places, is an independent group with scientific and non-scientific members whose job is to protect participants. Before a trial starts it reviews the protocol, the consent form and participant information, any recruitment adverts, what participants are paid, the investigator brochure and whether the investigator is suitable. During the trial it reviews amendments, new consent versions, important safety information and progress reports, and it re-reviews the study at regular intervals. A site can't enrol anyone before approval, can't start using an amended protocol or a new consent version before it's approved, and can't put up a new recruitment advert without approval either. The main exception is a change needed right away to remove an immediate hazard to participants, which can be made first and reported promptly after. Purely admin changes, like a new phone number, don't need approval either."

"The investigator can delegate tasks, but not responsibility, so this is a serious GCP concern. First I'd check the facts: is the junior doctor on the delegation log for those tasks and trained, and is there any evidence the investigator reviews eligibility, lab results or adverse events? Then I'd ask for a meeting with the investigator directly, not through the coordinator. I'd explain calmly what I've found and that inspectors look for evidence of oversight, such as reviewing eligibility before enrolment and signing off causality on events. We'd agree practical steps, like a regular review meeting that gets documented. I'd put it all in my visit report and follow-up letter with dates. If nothing changes by the next visit, I'd escalate to my study manager, because the sponsor may need to act, up to pausing enrolment at the site."

"I'd stay calm and not accuse anyone, because there could be an innocent reason, like a copying error or a broken device. First I'd gather facts quietly: compare the values with other sources, such as the machine printouts, the hospital's own records, appointment logs and whether the participant was actually in the building that day. I might ask the coordinator an open question about how vitals are taken, without suggesting anything. I'd write down exactly what I saw, objectively. Then I'd escalate quickly to my study manager and quality team, following the company's process for suspected misconduct. That's not something a CRA should investigate or confront alone, and a for-cause audit may follow. Meanwhile I'd keep it confidential and keep monitoring normally, so I don't tip anyone off or damage evidence."

"I'd say no, kindly but clearly. I'd explain that the data has to come from the site, and if I enter it, I'm then verifying my own work, which breaks the whole point of monitoring and would look very bad in an audit. But I don't want to just leave her stuck. I'd sit down with her and help her prioritise: which visits are overdue, which data drives upcoming deadlines, and whether there are quick fixes like a form she's struggling with that I can explain. If the real problem is workload, I'd raise it with the principal investigator, because the site agreed to have enough resources for the study, and I'd note it in my visit report. If it stays a problem, the sponsor may need to talk about recruitment pace or support."

"I wouldn't sign off data I'm not confident in just to hit a date, but I also wouldn't just say it's not ready and stop there. I'd go to the study manager and data manager early with specifics: which participants, which fields, and why I'm not confident. Maybe some endpoint assessments are missing source, or queries were answered in a way that doesn't match the notes. Then I'd propose options, like an extra remote session with the site this week to resolve the critical items, and a clear list of what's minor and can be documented as is. The final call on timing belongs to the study team, but they need to make it with the full picture. In my experience, being clear early helps the team trust you when you say something really matters."

"I check every consent form for every participant, because it's the first thing that protects them. On the form itself, I look at whether it's the version the ethics committee approved for that date, whether the participant and the person who took consent both signed and dated it personally, and whether any optional sections are completed. Then I check timing against the source: the consent date has to come before any study-specific procedure, even a screening blood test. I also look for a note describing the consent discussion, that the person taking consent is on the delegation log and trained, and that the participant got a copy. If someone needed a legal representative or an impartial witness, I check that was done properly. And when a new version comes out, I check each active participant was re-consented."

"The participants' rights come first, so I'd ask the site to re-consent both of them on the current version at the earliest chance, ideally at their next visit or sooner if the new version had important safety information. The new form gets signed and dated on the day it's actually signed, never backdated, and the coordinator writes a clear note in the source explaining what happened. It gets reported as a protocol deviation, and the site tells the ethics committee if their rules require it. Then I'd look at why it happened. Usually the old forms are still printed in a drawer or saved as a template. We'd remove every old copy, and I'd check every participant consented since the approval date to make sure there aren't others. And if the new version added a procedure, like an extra blood sample, I'd make sure it wasn't done before they agreed to it."

"Source data verification is checking that the data in the case report form matches the original record, the source. So if the CRF says the blood pressure was 128 over 80 at visit three, I find that value in the clinic notes or the vital signs sheet and confirm it's the same. Source data review is broader. I read the source itself to judge the quality of what happened: were procedures done in the right window, is there anything in the notes that looks like an adverse event nobody recorded, does the patient really meet eligibility, is the investigator overseeing the care. The difference matters because a site can transcribe perfectly and still have a big problem. Many studies now do targeted SDV on critical data, but review of source stays essential."

"It starts with a qualification or selection visit, where I check the investigator's interest and time, the patient population, staff and facilities to see if the site can run the study. If it's chosen, there's an initiation visit once approvals are in place. I train the team on the protocol, consent, safety reporting, the systems and their delegated tasks, and I check the site file is ready. Then come routine monitoring visits, on site or remote, where I review consent, verify and review source, look at safety events, drug accountability and the site file, and follow up earlier actions. At the end there's a close-out visit, where I make sure all data queries are resolved, drug is returned or destroyed properly, and the site knows how long to keep records. Every visit ends with a report and a follow-up letter to the site."

"A protocol deviation is any time the site doesn't do what the approved protocol says, whether it's a visit a day out of window or enrolling someone who didn't meet the criteria. I judge importance by the effect. If it could harm a participant's safety, rights or well-being, or damage the reliability of key data, like the primary endpoint, it's important. Enrolling an ineligible patient, starting procedures before consent, a dosing error or a missed primary endpoint assessment would all be important. A visit slightly outside the window with no effect on the data is usually minor. Most studies have a deviation plan that lists examples, so I follow that. Then I make sure it's documented, reported to the sponsor and to the ethics committee if their rules require, and I work with the site on why it happened."

"The idea is that not every data point matters equally, so monitoring effort should go where the risk is. At the start, the study team identifies the critical data and processes, things like consent, eligibility, the primary endpoint and safety reporting, and builds a monitoring plan around them. Then central monitoring looks at data across all sites to spot patterns: a site with far fewer adverse events than others, unusually perfect vital signs, slow data entry or lots of queries. Those key risk indicators drive what I do. So instead of verifying every field at every site, I might do full review of consent and eligibility, targeted verification of the endpoint data, and spend extra time on whatever signal flagged that site. It's more work to think through, but it finds real problems faster."

"In one diabetes study, a site had over a hundred open queries, some more than two months old, and we had an interim data cut coming. I pulled the list and sorted it by type. Around half came from the same two issues: missing units on lab values, and a concomitant medication form they were filling in wrongly. So I booked a half-day working session with the coordinator, went through the med form with her, and we cleared the simple ones together while I watched rather than entering anything myself. I also went back to the data management team, because some of our queries were confusingly worded, and we rewrote a couple. The site was down to a handful within three weeks, and new queries from those two causes mostly stopped."

"Early on as a CRA, I didn't notice that a site's lab certification had expired. It sat in the site file looking fine, and I only checked it was there, not its dates. It came up a couple of months later when the study manager ran a document expiry report. I told my manager straight away, contacted the site, and they got the current certificate, which showed the lab had stayed accredited the whole time, so the data was fine. We filed the new certificate and a note to file explaining the gap. What I changed was my visit routine. I now keep a simple tracker of every document that expires, like lab certificates, normal ranges and CVs, and check it before each visit, so I'm asking for renewals before they lapse instead of finding out after."

"ALCOA stands for attributable, legible, contemporaneous, original and accurate. The plus adds complete, consistent, enduring and available. I use it as a quick test on any record. Can I tell who wrote this and when? Can I read it? Was it written at the time, or much later? Is this the original, or a certified copy? Does it match other records? For example, if I see a correction, it should be a single line through the old entry so it's still readable, with the new value, initials, date and a reason if it isn't obvious. No correction fluid, no overwriting. If a note was written days later, that's allowed, but it should be clearly marked as a late entry with the actual date it was written. Those small things are what an inspector looks at first."

"Essential documents are the ones that, together, show how a trial was run and whether it met GCP and the rules. An inspector should be able to pick them up and rebuild the story. The sponsor keeps the trial master file, and each site keeps its investigator site file, which is really the site's share of the whole TMF. Many documents sit in both, like the protocol and amendments, ethics approvals, the approved consent form versions, the investigator brochure, signed agreements, staff CVs and training, the delegation log, lab certificates and normal ranges. Some stay only at the site, like signed consent forms and the list that links participant numbers to real names. On visits I check the site file is complete and current, and I make sure what I collect gets filed to the TMF on time."

"An adverse event is any unfavourable medical occurrence in a participant during the study, whether or not anyone thinks the drug caused it. The protocol says when collection starts, often from consent. A serious adverse event is one that meets specific outcome criteria: it results in death, is life-threatening, needs hospital admission or makes a stay longer, causes lasting or significant disability, causes a birth defect, or is another important medical event in the investigator's judgement. Severe is about intensity, like mild, moderate or severe. So a severe headache that keeps someone in bed at home is severe but not serious. A mild event that gets someone admitted overnight is serious. The difference matters because serious events have to be reported to the sponsor very quickly, and mixing the two words up is how reports get missed."

"First I'd confirm the facts: when the admission was and why. A hospital stay planned before the participant joined, for a condition that hasn't got worse, usually isn't an SAE, and the protocol says how to handle that. If it does meet serious criteria, I'd raise it with the coordinator and investigator the same day, not at the end of the visit. The investigator assesses it and reports it to the sponsor immediately, which most protocols define as within 24 hours of the site becoming aware. It's in their own notes, so it's already late and goes today. I'd tell my study manager and the safety team too. Then I'd document it as a late report, which is a deviation, and work out why it was missed. Maybe the site isn't getting discharge letters. Finally I'd check other participants' notes for the same gap before I leave."

"At my last company I had a site that had enrolled two patients in four months against a target of eight. Instead of just asking them to try harder, I went through their pre-screening and screening logs with the coordinator. Two things stood out. Most screen failures were on one lab criterion, and they were only finding patients through the investigator's own clinic. For the lab issue, I found out they were screening patients too soon after a medication change, so we agreed to time screening better. For referrals, the investigator agreed to talk to two colleagues in a nearby department, and we got an approved referral letter through the ethics committee. Over the next three months they enrolled five more. I also kept the study manager informed throughout, so there was a clear point to decide about adding a backup site."

"I did a qualification visit at a hospital site where the investigator was very enthusiastic and said he saw dozens of eligible patients a month. When I went through their records with the coordinator, the real number who'd meet our criteria looked closer to a handful. They also had three competing studies in the same population and only one part-time coordinator. The pharmacy and freezer storage were fine, and their ethics approval timelines were reasonable. I wrote the report honestly: good facilities and a keen investigator, but real risk on recruitment and staffing. I recommended selecting them only if they could confirm extra coordinator time, and flagged a lower enrolment estimate. They did add coordinator hours, and they ended up enrolling close to the number I'd estimated, not the one he'd promised."

"A principal investigator wanted to enrol a patient whose kidney function result was just outside the inclusion range. He felt strongly the patient would benefit and asked me to get the sponsor to approve an exception. I said I understood why he wanted it, but explained that eligibility exceptions aren't allowed, because the criteria are there partly for the patient's safety and partly so the results mean something. I suggested an option: if the protocol allowed a repeat test within the screening window, and it did, he could retest, and if the patient qualified then, fine. I also checked with the medical monitor so he heard it from them too. The retest was still out of range, so the patient wasn't enrolled. He wasn't happy that day, but later he told me he appreciated that I didn't just say no and walk away."

"At one oncology site, a routine visit turned up a lot at once: three participants with tumour scans outside the protocol window, missing investigator sign-off on two eligibility checklists, and a site file nobody had updated in months. The coordinator was new and clearly stretched. I didn't want her reading it cold in a letter, so I asked the investigator to join the exit meeting and went through it in person, starting with the scans because they fed the primary endpoint. I kept to facts and dates, not blame, and asked what was getting in the way. It turned out nobody had shown her how to book scans against the visit windows. We agreed actions with owners and dates, I put exactly the same points in the follow-up letter, and I set up a short call two weeks later. By the next visit the scans were on time and the file was current."

"The first thing is to stop the affected stock being used. I'd ask the pharmacist to quarantine it, labelled clearly, and not destroy it. Then the site reports the excursion to the sponsor through the study's process, with the temperature log showing how high or low it went and for how long. The sponsor, usually with the manufacturer's stability data, decides whether the drug can still be used. Meanwhile I'd check whether any participant was dosed from that stock since the excursion, because if so the investigator needs to know and it may need a deviation and safety follow-up. Finally, why wasn't it noticed? Maybe nobody reviews the log daily or the alarm didn't work. I'd agree a fix with the site, record it all in my visit report and check it next time."

"A sponsor auditor visited one of my sites and found that two staff members had been doing study assessments before they were added to the delegation log and trained. It was a major finding. When I looked into it, the root cause was simple: the site onboarded people quickly when their coordinator left, and nobody treated the log as something to update before work started. I'd also missed it, because I was checking the log was signed, not comparing it against who actually signed source documents. The correction was to document their training, add both staff to the log with the real dates and a note explaining the gap, and have the sponsor judge whether the assessments they'd already done could be used. For prevention, the site added a step to their onboarding checklist, and I changed my own visits to compare signatures in source against the log every time. The follow-up audit found no repeat."

"I'd tell my study manager and quality team straight away, and book a visit within days. At that visit I'd focus on what inspectors usually look at: consent for every participant, eligibility for a sample of patients, whether serious adverse events were reported on time, drug accountability, and whether the delegation log matches who actually did the work and their training. I'd make sure the site file is complete and in order. Where there are known issues, like past deviations, the site should have a clear, honest explanation and the corrective actions ready, not hide them. Gaps can be fixed with properly dated notes to file, but nothing gets backdated or recreated. I'd also help with logistics, like a quiet room, access to electronic records and who will answer which questions, and remind staff to answer honestly, stick to what's asked and fetch the record rather than guess."