Part III: What Makes an Answer Strong · Chapter 9
The big idea: The fastest way to learn a strong Casper answer is to see a weak one and a strong one for the same prompt, with the difference named.
Carry it into the test as: When you draft, ask what would turn your answer from the weak version into the strong one. It is usually the same few moves.
Read each prompt, draft your own answer in your head, then compare the two versions and the breakdown. Every weak answer here is a realistic version of what rushed applicants actually write. Every strong answer runs the DECIDE method. All scenarios are original.
Scenario. You and a close friend work the same part-time job and report to the same manager. Your friend wants to skip a shift to go to a concert and asks you to tell the manager they are home sick, and to back up the story if asked.
Question: What would you do, and why?
Weak answer. I would tell them no. Lying to your boss is wrong and they could get in trouble, and so could I. They should just be honest and ask for the day off like everyone else. It is not my job to cover for them.
Strong answer. The conflict here is between loyalty to a good friend and being honest with a manager who relies on accurate information, and it affects my friend, me, our manager, and whoever has to cover the gap if the shift goes unfilled. I understand the pull, my friend really wants to go, and they are asking me because they trust me. But I would not tell the manager they are sick, because that is a lie I would be actively telling on someone else’s behalf, it could backfire on both of us, and it leaves the team short. I would say that to my friend directly but kindly, then offer the honest paths that actually solve their problem: ask the manager for the night off, try to swap the shift with someone, or find their own cover. If they were stuck and I genuinely could, I might offer to swap shifts myself. That way I am still being a good friend, just not by lying.
Why the strong answer wins. The weak answer gets the decision right but little else: it sees one side (the rule), never grants the friend’s perspective, justifies thinly, moralizes (“they should just be honest”), and ends on a cold note (“not my job”) that signals low empathy. The strong answer makes the same decision but names the real dilemma, holds both the friendship and the honesty, justifies on a clear principle, and redirects to honest alternatives that still help the friend, judgment paired with humanity. Same choice, far more judgment on the page.
Scenario. In a group project, one member, Alex, talks over everyone, dismisses others’ ideas, and has started making decisions for the group without asking. Two quieter members have stopped contributing.
Question: How would you handle this?
Weak answer. I would tell Alex to stop being so controlling and let other people talk. It is really rude, and the quiet members deserve a chance. A good team is equal, so Alex needs to back off and listen for once.
Strong answer. The real issue is that the group’s process has broken down: one person is dominating, two have disengaged, and the project will suffer if that continues, so this affects Alex, the quiet members, me, and the quality of what we submit. Alex may not realize the effect they are having; some people who are anxious about a deadline take over without meaning to shut others out. I would not embarrass Alex in front of the group, because that usually makes people defensive. I would talk to them privately first, acknowledge that they are clearly invested and contributing a lot, then name what I am seeing, that a couple of members have gone quiet, and suggest we make room for everyone, for example by going around for input on big decisions. I would also draw the quieter members back in during meetings by asking for their views directly. If the pattern continued after a respectful heads-up, I would raise it with the group as a process problem rather than as Alex’s fault, or involve the instructor if it threatened the work. The goal is a functioning team, not winning a point against Alex.
Why the strong answer wins. The weak answer is one-sided and a little hostile: it casts Alex as the villain, prescribes “back off,” and never considers why Alex acts this way or how to repair the team. The strong answer reframes it as a process problem, extends good faith to Alex, chooses a concrete and proportionate action (private conversation first, escalate only if needed), protects the quiet members actively, and keeps the shared goal in view. It demonstrates collaboration rather than just demanding it.
Scenario. You are volunteering at a clinic. While helping an elderly patient to the exit, they confide that they have stopped taking one of their prescribed medications because they cannot afford it, and they ask you not to mention it to anyone because they are embarrassed.
Question: What would you do?
Weak answer. I would respect their wishes and keep it private, because they trusted me and confidentiality is important. It is their choice whether to take their medication, so I would not get involved.
Strong answer. This is a real tension between respecting the patient’s privacy and dignity and protecting their health, because stopping a prescribed medication can be dangerous, and it affects the patient most of all, plus the care team who can only help with information they have. I would take the patient’s embarrassment seriously and not make them feel judged, so I would respond warmly and reassure them that this is far more common than they think and nothing to be ashamed of. But I would not simply keep it to myself, because a care decision driven by cost is exactly the kind of thing a care team can often solve, through cheaper alternatives, samples, or assistance programs, and they cannot help if they do not know. I would gently explain that and encourage the patient to let me connect them with a nurse or someone who can look at lower-cost options, framing it as getting them help rather than reporting them. I would stay within my role as a volunteer: I would not give medical advice, but I would make sure the concern reaches someone qualified, with the patient’s understanding. If they were adamant, I would still quietly flag the safety concern to a staff member, because the risk to their health outweighs keeping a secret that was never really mine to keep.
Why the strong answer wins. The weak answer mistakes a real safety issue for a simple confidentiality request and hides behind “their choice” to avoid acting, low judgment dressed as respect. The strong answer holds both values, leads with empathy for the embarrassment, recognizes that this secret has a health risk attached, stays in role (connect, do not advise), and reframes “telling someone” as getting help rather than betraying a confidence. It protects the person, not just their privacy.
Scenario. A question asks for your view directly.
Question: Is it ever acceptable to break a promise?
Weak answer. No. A promise is a promise. If you break promises, people cannot trust you, and trust is everything. You should always keep your word no matter what. That is what integrity means.
Strong answer. Usually you should keep a promise, because promises are how people build trust and rely on one another, and breaking one carelessly does real damage. But “never” is too strong, because circumstances can change in ways that pit the promise against something more important. If I promised to keep a friend’s secret and then learned they were planning to seriously harm themselves or someone else, keeping that promise would protect my word at the cost of their safety, and safety has to win. So my position is that promises should be kept by default and broken only rarely, when keeping them would cause clear and serious harm, and even then you should be honest about it: tell the person, explain why, and try to limit the damage to their trust. The test is not whether breaking it is convenient, but whether keeping it would violate a more important obligation.
Why the strong answer wins. The opinion question is a trap for one-sided answers, and the weak version walks right in: it takes an absolute position, never considers a competing case, and substitutes a slogan for reasoning. The strong answer acknowledges the real value behind keeping promises, tests it against a hard case, lands on a clear and qualified position, and gives a usable principle for when the exception applies. Balanced does not mean wishy-washy. It commits, but to a defensible, reasoned view.
Scenario. A question asks about your own experience.
Question: Describe a time you received difficult feedback. How did you respond?
Weak answer. I always take feedback really well because I believe in growth. Once a supervisor gave me some criticism and I listened carefully, thanked them, and improved right away. I think being open to feedback is one of my biggest strengths.
Strong answer. During a part-time job, a supervisor told me that my shift summaries were too vague to be useful to the next person on duty. My first reaction, honestly, was defensive, because I had been proud of being fast, and I felt the criticism overlooked that. I did not say anything in the moment beyond thanking her, but afterward I sat with it and realized she was right: fast was not the same as useful, and the next person was the one paying for my shortcuts. So I asked her for an example of a summary she considered good, used it as a model, and started writing summaries that took a little longer but were actually complete. Within a couple of weeks she mentioned the handoffs had gotten much smoother. What I took from it is that my instinct to defend my work can get in the way of hearing accurate feedback, so now I try to sit with criticism before reacting to it.
Why the strong answer wins. The personal question rewards a specific, honest story with real reflection, and the weak version gives the opposite: a vague, self-congratulatory claim (“I always take feedback well”) with no concrete situation and no genuine self-awareness. The strong answer is specific, admits a real flaw (the defensive first reaction), shows what the person actually did about it, and ends on a genuine lesson. Admitting the imperfect first reaction makes it more credible, not less, and it demonstrates self-awareness instead of claiming it.
Look back and the same upgrades turned every weak answer into a strong one:
That is the DECIDE method, applied. When you draft an answer, run this same comparison in your head: what is the weak version, and what one or two moves would make it the strong one?
