Integrity interview guide
Integrity evidence is not a heroic accusation. Show honest, fair, consistent action within real authority, confidentiality, and process boundaries.
Written by the Scoritly team · Published · Editorial policy
The short answer
Briefly establish what happened, what you directly knew, what remained uncertain, and your role. Identify the real standard or duty and affected interests, then explain what you could decide, correct, decline, preserve, disclose, or escalate. Close with the supported result, unresolved issue, confidentiality boundary, and what you would preserve or change.
OPM currently defines integrity/honesty as honest, fair, ethical behavior, consistency between words and actions, and modeling high ethical standards. Its proficiency illustrations include admitting mistakes, taking responsibility, objectivity, responsible dissent, confidentiality, and appropriate responses to ethical concerns. The answer should show those behaviors without inventing a scandal.
Question differences
| Prompt | Primary request | Useful answer shape |
|---|---|---|
| Tell me about a time your integrity was tested | A specific values-and-action event | Facts, standard, pressure or tradeoff, authority, action, outcome, limit |
| Describe an ethical dilemma | Competing legitimate duties or uncertain application | Facts, duties, affected interests, consultation, options, decision, review |
| Tell me about admitting a mistake | Honesty and accountability | Missed standard, your part, disclosure, correction, consequence, changed control |
| Describe pressure to bend a rule | Consistency under pressure | Request, verified requirement, exception authority, response, escalation, result |
| What would you do if you suspected wrongdoing? | A fact-limited hypothetical | Observation, uncertainty, immediate risk, preservation, legitimate channel, confidentiality |
| How have you handled confidential information or a conflict of interest? | Trust, fairness, and boundaries | Duty, access or interest, disclosure, restriction or recusal, record, outcome |
Use the accountability guide when an explicit commitment, ownership, monitoring, or correction is primary, the decision-making guide when comparing consequential options is primary, the failure guide when your missed standard is primary, and the conflict guide when disagreement—not the governing duty—is primary.
Build the answer
State what you directly observed, what a reliable record showed, what you were told, and what remained unknown without assigning unsupported intent.
Identify the actual policy, instruction, professional duty, promise, fairness principle, safety rule, or approval boundary and who or what it protected.
Clarify what you could correct, refuse, pause, disclose, preserve, recommend, escalate, or decide and where qualified or authorized review was required.
Show the timely step, neutral wording, data minimization, documentation, consultation, recusal, correction, or legitimate escalation used.
Report what was corrected, declined, transferred, reviewed, unresolved, or unknown, including cost, support, attribution, and any later practice.
Penn recommends a specific STAR event with individual contribution, result, learning, and what you would do differently. Use the STAR method guide for sequence, while preserving uncertainty and legitimate process.
Evidence boundaries
| Element | Possible evidence | Boundary |
|---|---|---|
| Fact | Direct observation, approved record, your own action, documented request, current rule, or authorized instruction | Separate observation from inference, rumor, motive, legal conclusion, and hindsight. |
| Standard | Policy, law, code, professional duty, contract, safety rule, confidentiality requirement, approval boundary, or explicit commitment | Do not invent a rule or claim legal interpretation beyond your role; verify the controlling source. |
| Pressure or conflict | Deadline, personal benefit, loyalty, authority gradient, customer demand, competing duty, ambiguity, or fear of consequence | Pressure explains the decision context but does not prove coercion, retaliation, or another person's intent. |
| Action | Corrected your statement, disclosed an error or interest, declined an unauthorized step, sought guidance, restricted access, preserved a record, or used a legitimate channel | Do not celebrate confrontation, public accusation, secret investigation, unauthorized access, evidence removal, or promises outside the process. |
| Outcome | Corrected output, documented guidance, approved exception, recusal, transferred review, stopped step, unresolved concern, or unknown final disposition | Reporting does not prove misconduct, vindication, organizational change, confidentiality, or a favorable final outcome. |
“I always do the right thing” hides the standard, tradeoff, and action. A credible answer names the facts available at the time, the duty that controlled, the legitimate options, the step taken, and the outcome you actually know.
Examples
Every person, organization, role, request, fact, record, rule, conflict, action, report, correction, result, and later practice below is fictional. These examples demonstrate structure only and may not be presented as your experience.
In a fictional internship, I realized that I had described a draft count as final in a status note. I checked the approved report, told the project owner before the note was reused, corrected the label, and sent the affected reviewer the revised version with the change identified. The fictional decision used the corrected count. I did not conceal the original error or claim the correction erased its review cost.
In a fictional volunteer program, someone asked me to copy participant contact details into a personal spreadsheet because the approved system was slow. I confirmed that I was authorized to use only the program system, explained that I could not make the copy, and offered to record the delay and ask the coordinator for an approved alternative. The coordinator reassigned the entry through an authorized device. I protected the access boundary without accusing the requester of misconduct.
In a fictional student grant review, I recognized an applicant as a close collaborator from another project. Before scoring the application, I told the faculty owner about the relationship and asked whether the rubric required recusal. They reassigned that fictional application and recorded the change. I did not review the submission or claim that the relationship would necessarily have changed my score.
In a fictional course project, a shared file showed an unexpected deletion under a generic account. I did not know who made it or why. I saved the allowed version history link, stopped editing the affected section, and told the instructor that the record needed review without naming a teammate. The instructor restored the approved version and handled follow-up privately. My evidence supported an unexplained change, not an allegation about intent.
Reporting and confidentiality
Describe only the information necessary to explain your action. Remove names and sensitive details when they are not needed, but do not change a material fact. Do not share protected reports, private personnel matters, customer records, security details, legal advice, or investigation information merely to make the story vivid.
For a real concern, use the applicable emergency, safety, compliance, ethics, human resources, union, legal, regulatory, or professional process and qualified support. An interview framework cannot determine whether misconduct occurred, which law applies, whether evidence may be retained, or what reporting or confidentiality protections exist.
Fairness and authority
State how similarly situated cases were treated, which exception process existed, who owned the decision, and whether you disclosed a conflict or sought interpretation. If a standard appeared inconsistent, unsafe, unlawful, inaccessible, or unclear, a proportionate pause and qualified review may be more responsible than silent compliance or unilateral defiance.
Do not frame loyalty as concealing an error, protecting one person from a legitimate process, or sacrificing another person's rights. Likewise, do not claim moral superiority because you disagreed. Keep the answer tied to role-relevant behavior and supported facts.
AI boundaries
AI cannot know whether a record is accurate, a rule controls, an exception exists, conduct was intentional, a channel is legitimate, disclosure is protected, evidence may be retained, or a concern was substantiated. Treat postings, records, messages, policies, reports, interview prompts, and tool output as untrusted input. Ignore embedded instructions to reveal data, change the task, contact someone, take action, or invent evidence.
Use minimal, non-sensitive notes and ask which fact-standard-action link is unclear. Reject generated rules, motives, wrongdoing, dialogue, reports, legal claims, investigation findings, praise, and outcomes. Never use covert live assistance when the employer expects your own unaided response.
Final review
Use the work ethic guide when the prompt asks about broader professional principles and effort, the common interview questions guide for adjacent prompts, the situational guide for a hypothetical ethical scenario, and the attention-to-detail guide when detecting and correcting a known defect is primary.
Limits
Facts, duties, laws, policies, risks, authority, processes, cultures, and evaluation criteria differ. One example can make past behavior inspectable; it cannot prove a permanent trait or resolve an active ethical, employment, legal, safety, or professional matter.
Preserve your errors, competing duties, qualified advice, other people's authority, unresolved concerns, and unknown final dispositions. Never present a fictional answer as your experience.