This page is for anyone interviewing as a safety officer or HSE officer on a construction site, plant or facility. Most panels check three things: that you know the fundamentals cold, that you can hold a line when production pushes back, and that workers will actually listen to you. Expect a few questions on your path, stories from real sites, what-would-you-do scenarios, and checks on risk assessment, permits, high-risk work and investigations. Each question shows what the panel is listening for, a shape for your answer and a sample you can say out loud. Swap in your own sites and stories.
Search all questions by round, difficulty and level, or save the ones you want to practise.
Path: the short version, one or two steps that brought you here.
Moment: a specific experience that made the work feel real.
Why it lasts: what you get out of the job day to day.
"I trained as a mechanical technician and spent my first two years on a maintenance crew. During that time a colleague on another shift crushed his hand in a conveyor that hadn't been isolated properly. He recovered, but it stuck with me, because everyone knew the isolation step and still skipped it when they were rushed. I started volunteering for the site safety committee, then did a general occupational safety certificate and moved into a safety assistant role. What keeps me here is that the job is really about people and habits, not paperwork. When a crew starts stopping a job on their own because something looks wrong, that's the best part of my week."
Saying you wanted an office job on site, or giving a path with no moment that shows you care about the people.
Their work: what the site does, in one line.
Top hazards: the two or three things most likely to kill or seriously injure someone there.
Your fit: where your experience matches those hazards.
"From what I read, this is a warehouse and distribution site with a lot of forklift traffic, racking, and loading docks running around the clock. So the hazards I'd worry about most are people and vehicles mixing, falls from loading docks or when someone climbs racking, and fatigue on night shifts. Slips and manual handling matter too, but those first ones are where a bad day becomes a fatality. My last two years were on a logistics site, where I worked on separating pedestrian routes and tightening the rules on who drives what. I want this role because it's a bigger operation, and I'd like to bring what worked there and learn from a team that's further along."
Listing hazards that could apply to any building, with nothing about what this site actually does.
What you hold: the certificate and level, stated plainly.
What it changed: one thing you now do differently because of it.
What's next: the next step you're working toward and why.
"I hold a recognised general certificate in occupational health and safety, plus separate training in first aid and confined space supervision. The general certificate mattered most, because it gave me a structure. Before it, my risk assessments were really a list of hazards. Now I think through who is exposed, how likely and how bad the harm is, and which controls sit higher up the hierarchy before I reach for PPE. I also learned to read the actual regulations for the country I'm working in instead of relying on what someone told me. Next, I'm working toward a diploma-level qualification, because I want to move into leading a site's whole safety system, not just inspections."
Reciting certificate names as if they prove competence, with no example of using what you learned.
Hazard: anything with the potential to cause harm.
Risk: the chance that harm happens combined with how bad it would be.
Example: one hazard whose risk goes up or down with the situation.
"A hazard is anything that could cause harm, like electricity, a chemical, or an unprotected edge. Risk is the combination of how likely it is that someone actually gets hurt and how bad that harm would be. So the hazard can stay exactly the same while the risk changes a lot. Take a roof edge. On a day when nobody goes up there, the risk is low. Put a crew up there fixing solar panels without guardrails, and the risk is high, even though the edge hasn't changed. Add proper edge protection and the risk drops again. That's why a safety officer's job is mostly managing risk: we can't always remove a hazard, but we can change exposure and controls."
Using the two words as if they mean the same thing, or defining risk without mentioning both likelihood and severity.
Identify: walk the task with the crew and list the hazards.
Who and how: who could be harmed, including visitors and nearby workers.
Evaluate and control: rate the risk, pick controls using the hierarchy, record it.
Communicate and review: brief the crew, then review after changes or incidents.
"I start by going to where the task actually happens and watching it or talking it through with the people who do it, because they know the shortcuts. I break the task into steps and list the hazards in each. Then I think about who could be harmed, not just the crew but people passing by, cleaners, contractors. For each hazard I look at how likely harm is and how bad it could be, check what controls already exist, and decide what extra controls are needed, starting high up the hierarchy rather than jumping to PPE. I record it clearly, brief the crew so they understand it, and set a review point. I also review it any time the task, the equipment or the people change, or after an incident or near miss."
Describing a desk exercise with no site visit and no input from the people doing the work.
How it works: score likelihood and severity, combine them into a rating that sets priority.
Weak spots: scores are subjective and rare fatal events can land in a low band.
How you compensate: treat high severity as special, use more than one scorer, look at controls not just numbers.
"A matrix scores likelihood on one axis and severity on the other, often on a scale of one to five, and the combination gives a rating that tells you how urgent the controls are. It's useful for ranking and for explaining priorities to managers. But it misleads in a few ways. The scores are subjective, so two people can rate the same task very differently. It also flattens things: a very unlikely event that could kill several people can end up in the same band as a common minor cut, which makes it look acceptable. And people sometimes lower the likelihood score to get a green result. So I always treat anything with a fatal or permanent outcome seriously whatever the score, I score as a group, and I focus on whether the controls are real and working."
Treating the matrix score as the answer, and accepting a low score on a task that could kill someone.
What happened: the mistake, plainly stated.
How you found out: and what you did straight away.
What changed: the lasting change to how you work.
"Early on I did a risk assessment for painting a stairwell. I covered ladders, fumes and slips, and I was quite pleased with it. What I didn't think about was that the stairwell was also the fire escape route for two floors, and the crew had stacked paint tins and dust sheets on the landings. A fire warden spotted it during a drill, not me. I went straight to the crew, we cleared the landings, and I rewrote the assessment. Since then, whenever I assess a task, I look beyond the task itself at what the area is used for, who else passes through, and what it does in an emergency. I also ask someone else to read my higher-risk assessments before they're signed."
Claiming you've never made a mistake, or picking a trivial example with no lesson.
Order: elimination, substitution, engineering controls, administrative controls, PPE.
Examples: one practical example per level.
Why the order: higher levels don't depend on human behaviour.
"The hierarchy is the order you should try controls in, from most effective to least. First, elimination: remove the hazard completely, like assembling a steel frame at ground level so nobody works at height. Second, substitution: swap in something less dangerous, like a water-based paint instead of a solvent one. Third, engineering controls: physically separate people from the hazard, like guarding on a machine, local exhaust ventilation, or guardrails. Fourth, administrative controls: procedures, permits, signage, training, rotation. And last, PPE, like gloves, respirators and harnesses. The order matters because the top levels work whether or not someone is tired or rushed. PPE only works if it's the right type, fits, is worn correctly, and is worn every single time. In practice you usually combine several levels."
Getting the order wrong, or treating PPE as the main control rather than the last one.
Why last: it only protects the wearer and fails silently if misused.
Selection and fit: right type for the hazard, fitted to the person.
Training and care: how to wear, check, store and replace it.
Follow-through: supervision, comfort and feedback from wearers.
"It's the last line because it doesn't remove the hazard, it only protects the one person wearing it, and it fails without warning. A respirator that doesn't seal looks exactly like one that does. So for a programme to work, first you pick PPE matched to the actual hazard, not just what's in the store. Then fit matters: tight-fitting respirators need fit testing, gloves and harnesses come in sizes, and one size rarely fits everyone. People need training on how to put it on, check it and when to replace it. Storage and inspection need to be someone's job. And I ask the wearers what's uncomfortable, because PPE that's hot or clumsy gets taken off the moment I walk away. Comfort is a safety issue."
Saying the fix for a hazard is simply to issue more PPE and discipline anyone who doesn't wear it.
Pause: no start on a high-risk job without an approved plan.
Quick path: help them produce it on the spot or contact their office.
Check it's real: edge protection, access, competence and rescue fit this roof.
Fix the gap: why did the site's process let them arrive without it?
"They don't start. Roof work is high risk, and without a plan I don't know how they'll stop someone falling. But I don't want to just send them away either. I'd ask them to call their office for the method statement, and if they don't have one, I'd sit with their supervisor and help them write one for this roof, covering access, edge protection, fragile surfaces, weather limits and how they'd rescue someone. Then I'd check it against what I can actually see on the roof and their training records. Only once it's approved and they've had the site induction would the job start. Afterwards, I'd find out how they were booked without the documents being checked, because that's the real gap in our contractor process."
Letting them start and promising to catch up on paperwork later.
What it is: written authorisation for specific high-risk work, at a set place and time.
Contents: scope, hazards, isolations, tests, precautions, signatures of issuer and receiver.
Live control: displayed at the job, handed over at shift change, suspended when conditions change.
Closure: site left safe, isolations removed only after sign-off.
"A permit to work is a formal written system that authorises specific high-risk work, like hot work, confined space entry, or work on isolated equipment, at a set location and for a set time. It spells out the scope, the hazards, the isolations, any gas tests, and the precautions, and it's signed by the person issuing it and the person receiving it. For it to protect anyone, the issuer has to actually visit the job and check the isolations, not sign at a desk. The permit sits at the worksite. It gets handed over properly at shift change, and it's suspended if conditions change, like a gas alarm. Conflicting permits in one area need to be cross-checked. And at the end, the area is checked and handed back before isolations are removed and the permit is closed."
Describing a permit as paperwork that gets signed in the office, with no site check and no handback.
Avoid: can the job be done from outside?
Prepare: permit, isolate energy and lines, drain, clean and ventilate.
Test: calibrated meter, oxygen first, then flammables, then toxic gases, and keep monitoring.
People and rescue: trained entrants, an attendant outside, a rescue plan and equipment ready.
"First I'd ask whether anyone needs to go in at all, because sometimes the cleaning can be done from outside with remote equipment. If entry is needed, it goes under a confined space permit. The tank has to be isolated: every line blanked or disconnected, agitators and pumps locked out, then drained, cleaned and ventilated. Before entry, a trained person tests the atmosphere with a checked and calibrated meter, oxygen first, then flammable gas, then any toxic gases we'd expect, testing at different levels in the tank. Monitoring continues while people are inside. There's a trained attendant outside the whole time who never goes in, and a rescue plan with equipment set up before entry starts. A lot of confined space deaths are would-be rescuers, so that part isn't optional."
Letting anyone enter before testing the atmosphere, or leaving rescue to a phone call to emergency services.
Avoid: do the work from the ground where possible.
Prevent: guardrails, scaffolds, working platforms and mobile elevating platforms.
Mitigate: fall arrest, nets or airbags when a fall can't be prevented.
Rescue: a quick plan to reach anyone suspended in a harness.
"I follow an order. First, can we avoid height altogether, like pre-assembling on the ground or using long-reach tools. If not, I prevent falls with collective protection: guardrails, a proper scaffold, or a mobile elevating platform, because those protect everyone without them having to do anything. Only if that's not possible do I move to things that reduce the harm of a fall, like nets or personal fall arrest. A harness is the wrong answer when there isn't a rated anchor point, when there isn't enough clearance below for the lanyard to stop the fall before the person hits something, or when there's no plan to rescue someone hanging in it. Being suspended in a harness is dangerous in itself, so rescue has to be fast. The height where formal rules kick in depends on local law, so I check that too."
Going straight to 'give them a harness' with no thought about anchor points, clearance or rescue.
Hold the line: no test, no permit, said calmly.
Why: conditions change overnight and yesterday's result proves nothing today.
Help: get a tester there fast, prepare everything else in parallel.
Escalate: if pressure continues, involve the manager and record it.
"I'd say no, calmly and clearly. A gas test is the control that tells you whether the air can ignite right now, and yesterday's result doesn't tell you anything about today. Things change overnight: a valve leaks, a line gets drained nearby, residue heats up. I'd explain that in one or two sentences, then switch to helping. I'd find the nearest qualified tester and a calibrated meter, and get the rest of the permit ready in parallel, the fire watch, extinguishers, covering drains and clearing combustibles, so the moment the test passes the job starts. If the supervisor kept pushing, I'd bring in the shutdown manager and make sure the conversation was recorded. Being late is recoverable. A fire during a shutdown often isn't."
Issuing the permit 'just this once', or refusing and walking away without helping the job move.
Facts first: scene, photos, statements, records, before opinions.
Keep asking why: use a method like five whys or a cause diagram.
System causes: equipment, procedures, training, supervision, time pressure.
Actions that fit: fix the causes, not just retrain the person.
"Human error is usually where the investigation should start, not where it ends. I gather facts first: the scene, photos, what the equipment showed, and statements taken separately and quickly while memories are fresh. Then I keep asking why. Say someone cut their hand on a machine with the guard off. Why was the guard off? Because it had to come off to clear jams. Why were there so many jams? Because the feed material changed and nobody reviewed the setup. Why was the guard easy to remove without isolating? Because it wasn't interlocked. Now I've got actions that matter: fix the jamming, interlock the guard, and make clearing jams a proper procedure. Retraining the worker alone would have changed almost nothing."
Ending the investigation at 'worker error, retrained' with no look at why the error was easy to make.
Response: care for the injured person, make the area safe, secure the scene.
Evidence: photos, statements, records, equipment checks.
Analysis: root causes, not just the immediate cause.
Close-out: actions with owners and dates, checked for effectiveness and shared.
"A worker's foot was run over by a pallet truck in the dispatch area. When I got the call, first aid was already being given, so my focus was making the area safe and stopping it being tidied up. I took photos and measurements, pulled the camera footage, and took separate statements from the driver, the injured worker and two witnesses that same day. The immediate cause was the worker stepping into the aisle between racks. But the footage showed people did that all the time, because the only route to the printer crossed the aisle. The root causes were layout and planning. Actions were moving the printer, marking a walkway and adding a barrier. Each had an owner and a date, and I went back a month later to check people were actually using the new route."
An investigation that ends in a finding against one worker and no check that the actions worked.
Casualty and safety: make the area safe, first aid, call emergency services.
Control the site: stop related work, keep people away, secure the scene.
Notify: management, family through the right person, and the regulator if the law requires it.
Preserve evidence: photos, witnesses, equipment kept as found.
"The injured person comes first. I'd make sure the area is safe so nobody else gets hurt reaching them, get a first aider there, and make sure emergency services have been called and someone is at the gate to guide them in. I'd stop similar work nearby until we know what happened. Once the casualty is in good hands, I'd secure the scene, taping it off and keeping equipment exactly as it was, apart from anything that has to move for the rescue. I'd tell site management straight away and make sure the right person contacts the family. Many places require serious injuries to be reported to the authorities within a set time, so I'd check that duty. Then I'd take photos and names of witnesses while it's fresh, and look after the people who saw it."
Starting with the paperwork or questioning the injured worker before the scene and casualty are dealt with.
Lagging: measures of harm after it happens, like lost-time injury frequency.
How a rate works: injuries times a fixed base of hours, divided by hours worked, so sites of different sizes can be compared.
Leading: measures of activity that prevents harm, like near-miss reports and actions closed.
Balance: report both and explain the story behind them.
"Lagging indicators measure harm that's already happened: lost-time injuries, recordable injuries, days lost. They're usually shown as a frequency rate: the number of injuries times a fixed base, often one million hours or 200,000 hours depending on the system, divided by total hours worked. So two lost-time injuries in 500,000 hours is four per million hours, or 0.8 on the 200,000 base. The trouble is they only tell you about the past, and on a small site one injury makes the rate jump. So I pair them with leading indicators, like near-miss reports, inspections completed, corrective actions closed on time, and safety conversations held. I'd give management a short dashboard with both, plus a sentence on what's changed and why, because a number without context doesn't help anyone decide anything."
Reporting only injury counts, or not knowing how a frequency rate is worked out.
Inspection: a frequent check of physical conditions and practices.
Audit: a planned, systematic check of the safety system against a standard.
Frequency: inspections often and routine, audits planned and less often, based on risk.
"An inspection is a hands-on look at the workplace: guards in place, walkways clear, fire exits open, scaffold tags current. It's frequent, sometimes daily for high-risk areas, and it finds conditions that need fixing now. An audit is bigger and more systematic. It checks whether the safety management system actually works as written, so I'd sample permits, training records, risk assessments and incident actions, and interview people to see if what's on paper matches what happens. Audits are planned, often yearly or on a cycle set by risk, and ideally someone independent does at least some of them. An inspection might find a missing guard. An audit asks why our system let that guard stay missing for a week."
Using the two words interchangeably, or describing an audit as just a longer walk around the site.
Finding: what it was and why it mattered.
Resistance: the manager's reason, heard fairly.
Approach: evidence, options, cost of doing nothing, escalation if needed.
Outcome: what got fixed and what you learned.
"During an inspection I found that the emergency lighting in a basement plant room had failed its test and had been logged as failed for months. The facilities manager said it was low priority because hardly anyone went down there. I listened, and he had a point about budget. But I showed him the maintenance crew's schedule, which had people in that room every week, often alone, and I asked him to walk it with me with the main lights off. That changed the conversation. We agreed on temporary battery lights that week and the repair in the next budget round, and I tracked it on the action log that went to the site leadership meeting. It was fixed within two months. I learned that showing someone the risk beats arguing about it."
Saying you simply raised it and it was out of your hands after that.
Celebrate carefully: recognise effort, not just a number.
Check reporting: near misses, first aid logs and light duty for signs of hiding.
Check serious risks: are the high-risk controls actually working?
Reframe: reward reporting and good practice, not just zero.
"I'd be happy to recognise the crew, but I'd want to check a few things first. Are near-miss reports steady or did they drop? A falling number next to zero injuries can mean people have stopped reporting. I'd look at first aid logs and light or restricted duty, because sometimes an injury gets kept off the books by moving someone to a desk. I'd ask a few workers quietly whether they'd feel comfortable reporting an injury. And I'd review our serious risks, like work at height and vehicles, because a year of no injuries can also be luck. If it all checks out, great. Either way, I'd suggest celebrating the behaviours, like reporting and stopping unsafe jobs, rather than the zero, so there's no pressure to hide the next one."
Treating zero injuries as proof the site is safe, or rewarding the number in a way that encourages hiding incidents.
Triangle: heat, fuel and oxygen; take one away and the fire goes out.
How extinguishers work: cool it, smother it, or break the chemical reaction.
Matching: ordinary solids, flammable liquids, electrical equipment, cooking oil, metals.
Local labels: class letters differ by country, so read the label and the local standard.
"A fire needs three things: heat, fuel and oxygen. Take any one away and it goes out. Some people add a fourth side, the chemical chain reaction, which is how dry powder works. Water works by cooling, so it's good for wood, paper and cloth. CO2 pushes the oxygen away, so it's the usual choice for electrical equipment and it leaves no mess. Foam smothers burning liquids like fuel. Cooking oil fires need a wet chemical extinguisher, because water on hot oil can throw burning oil across the room. Metal fires need a special powder. The two mistakes that hurt people are water on live electrics and water on burning oil. The class letters on extinguishers aren't the same in every country, so on a new site I check the labels and the local standard, and I make sure the right type sits next to the right hazard."
Saying any extinguisher will do, or suggesting water on an electrical or cooking oil fire.
What happened: the drill or event and what went wrong.
Why: the cause you found when you looked into it.
Fix: what changed and how you tested it again.
"We ran an unannounced evacuation drill on a night shift, and the roll call at the assembly point didn't match the sign-in sheet. It took a long time to work out that three contractors had signed in but left early without signing out, while one visitor had never signed in at all. In a real fire, we might have sent someone back in looking for people who weren't there, or missed someone who was. So we moved to a card-based sign-in at the gate that could print a live roll call for the fire wardens, made signing out part of the gate procedure, and gave night supervisors the warden role for their area. We ran another night drill six weeks later and the count matched within a few minutes."
Describing drills as a box to tick, or a problem that was noted but never fixed.
Need: can the part be moved away, or joined without heat?
Remove fuel: relocate the flammables, or shield what can't move.
Permit and checks: hot work permit, gas test if vapours are possible, drains and gaps covered.
Fire watch: someone trained with extinguishers during and for a period after.
"First I'd ask whether the welding has to happen there at all. Sometimes the part can be taken to the workshop, or a bolted or cold-cut method works instead. If it has to happen in place, the flammables get moved away, not just covered. Anything that genuinely can't move gets shielded with fire-resistant blankets or screens. I'd look for gaps in floors and walls where sparks could travel, and cover drains. If vapours could be present, there's a gas test before work and during it. It goes on a hot work permit. There's a trained fire watch with suitable extinguishers who does nothing else, and they stay on after the welding stops, because smouldering fires often start after everyone has left. Exact distances and watch times depend on your local rules."
Letting the job start with only a fire extinguisher nearby and nobody watching afterwards.
Situation: how low reporting was and why.
Actions: what you changed to make reporting easy and safe.
Feedback loop: how people saw something happen after they reported.
Result: the change in reports and in behaviour.
"At my last site we were getting maybe one near-miss report a month from over two hundred people, which told me nobody trusted the system. When I asked around, the answers were the same: the form was long, and the last person who reported a near miss got questioned like he'd caused it. So I cut the form down to a few lines and added a quick option at the canteen. I agreed with the site manager that near misses would never lead to discipline on their own. And every week in the toolbox talk I read out a couple of reports and what we'd fixed because of them, naming the fix, not the person. Within a few months reports were coming in weekly, and a couple of them led to real changes in the loading bay."
Saying you made reporting mandatory and penalised people who didn't report, with no thought about trust.
Topic: why you picked it, ideally from a real event on site.
How you ran it: short, on the job, with questions to the crew.
Change: what people did differently afterwards.
"We'd had two near misses in one week where people walked behind reversing forklifts. Instead of a talk in the canteen, I did it right at the loading bay, about ten minutes at the start of shift. I asked one of the drivers to sit in the forklift and had everyone take turns standing where the pedestrians had been, so they could see from the seat how little the driver can see behind. Then I asked the crew what would stop it happening, and they came up with painting a keep-out zone and a rule that drivers stop if someone's inside it. We put both in place that week. The next month, nobody was caught walking in that zone during inspections."
Describing a talk that was a lecture read from a printout, with no involvement and no follow-up.
Situation: the job, the hazard and the pressure.
The stop: how you stopped it and what you said.
Pushback: how you handled it without a shouting match.
Outcome: how the job restarted safely and what changed.
"We had a crane lift planned for a steel beam, and when I got there the ground under one outrigger was soft after overnight rain and no mats were in place. I stopped the lift. The site supervisor was angry because the client was visiting that afternoon and the lift was meant to be the highlight. I didn't argue about who was in charge. I showed him the ground, reminded him that a crane tipping over with the client watching was the worst possible outcome, and offered a fix: get timber mats from the other side of site and recheck the ground. It took about ninety minutes. The lift went ahead safely before the client arrived. Afterwards we added a ground check to the lift plan sign-off so it wasn't down to me noticing."
A story where you either backed down to keep the peace or won by pulling rank with no solution offered.
Now: make it safe first, calmly.
Talk: respect his experience, explain the risk, ask why he unclipped.
Fix the cause: anchor points, lanyard length, task design.
Follow-up: follow the site's process fairly, and share the lesson.
"First I'd get him safe, calmly, without shouting across the site: ask him to clip on or come down. Once he's safe, I'd talk to him privately. I'd respect that twenty years is real experience, and I'd also say that falls happen to experienced people precisely because the job feels routine. Then I'd ask why he unclipped. Often there's a real reason, like the anchor points are in the wrong place and he couldn't reach the work while clipped on. If so, that's our problem to fix, not just his. If there's no reason and it's a pattern, the site's disciplinary process applies, and I'd let his supervisor know. I'd also ask him to help me talk to the younger workers, because he's someone they listen to."
Either ignoring it out of respect for his experience or humiliating him in front of the crew.
Presence: be on the floor, not behind a desk.
Listen and fix: act on what workers raise and tell them what happened.
Tone: ask before you tell, praise good practice, correct in private.
"Mostly by being out on site and fixing things people ask me to fix. If a worker tells me the ladder at bay four is damaged and I get it replaced that week, I've earned more trust than any poster could. I try to ask questions before I give instructions, like 'what's the hardest part of this job?', because the answers show me where the real risk is. I notice good practice out loud, not just the bad. When I do have to correct someone, I do it privately and explain why. And I'm honest when I don't know something. Over time people start coming to me first, and that's when I hear about the problems before they turn into incidents."
Describing your role mainly as catching people breaking rules and writing them up.
Behaviours: people stop unsafe work, report freely, and leaders act on it.
Leaders: managers visible on site and consistent under pressure.
How to tell: watch, listen, and compare what's written with what's done.
"To me, a good safety culture is one where people do the safe thing when nobody is watching and when the job is late. You see it in behaviour: workers stop a job and nobody punishes them for it, near misses get reported and something visibly changes, and supervisors don't quietly signal that the rules are for audits only. Leaders walk the site and ask real questions. To tell whether a site has it, I'd spend time on the floor and at shift change, ask a few workers what happens when they raise a concern, and compare a couple of permits and risk assessments with what I see at the actual job. I'd also look at how the last serious incident was handled. Whether it ended in blame or learning tells you a lot."
Pointing to posters, slogans or the injury rate as proof of a good culture.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your resume and notes are never stored on our servers. It stays out of screen share on every plan; only you can see it.