The scent of dust and stale air filled Mark's living room as he sat on the couch, staring at the box of personal items from his desk. His daughter's drawing sat on top—a picture of him at his desk, with the words "My Daddy works with computers" written in crayon. He had told his wife what happened. She had been supportive, angry on his behalf. But he could see the worry in her eyes. How will we pay the mortgage? How will we pay for health insurance? What will we do now? He didn't have answers. --- Around 3 PM, his phone buzzed. An email from David. Subject: Company Statement Mark, I wanted to share this with you before it goes public. The company will be releasing a statement tomorrow. Best, David Below was a draft of the statement. NexTrade Technologies Statement on Trading System Incident On March 15th, our trading system experienced a technical issue that resulted in significant financial losses. We have conducted a thorough investigation and have taken appropriate action to address the situation. The investigation found that the incident was caused by a failure in our code review process. We have terminated the employment of the individual responsible for this failure. We are committed to learning from this incident and have implemented the following improvements: - Enhanced code review protocols - Additional testing requirements - Increased oversight of AI-generated code We take full responsibility for this incident and are committed to ensuring it does not happen again. Mark stared at the statement. We have terminated the employment of the individual responsible. He was the individual. He was the answer. We take full responsibility. But they didn't. He did. --- He read the statement again. There was no mention of the concerns he had raised. No mention of the warnings he had given. No mention of the process that management had approved. It was as if he had acted alone. As if the failure was entirely his. He thought about responding. About defending himself. About telling his side of the story. But he knew it wouldn't matter. The company had made its decision. The narrative was set. He was the individual responsible. --- That night, Mark couldn't sleep. He lay in bed, staring at the ceiling, replaying the past two weeks in his mind. The meeting with David. The questions. The paper trail. The meeting with Jennifer. The termination. The escort out of the building. He had been a good employee. He had raised concerns. He had followed the process. But none of that mattered. When something went wrong, someone had to pay. And the person who paid was always the one with the least protection. He thought about David. About Jennifer. About Michael from Legal. They were all still employed. They would all continue their careers. They would all move on. But Mark would carry this. The termination. The stigma. The question that would follow him to every job interview: Why did you leave your last position? He closed his eyes. Someone has to pay. That's how it works. --- The next morning, Mark woke up early. He made coffee. He sat at his kitchen table. He stared at his phone. The company statement had been released. He saw it in his news feed. NexTrade Technologies Terminates Employee After $87 Million Trading Loss He clicked on the article. It quoted the company statement. It mentioned "failures in the code review process." It mentioned "appropriate action." It didn't mention him by name. But in the industry, people would know. People would talk. He closed the article and put down his phone. --- Around 10 AM, he received a text from Sarah Kim. Mark, I saw the news. I'm so sorry. I never wanted this to happen. Mark stared at the text. He wasn't sure how to feel about Sarah. She had warned him. But she had also documented everything. She had also cooperated with the investigation. He typed a response. Sarah, I appreciate your concern. I don't blame you for what happened. I should have listened to your warnings. He hit send before he could second-guess himself. A few minutes later, Sarah responded. Mark, I tried to help. I really did. But the process was bigger than both of us. The process was bigger than both of us. Mark stared at the words. They felt true. The process—the system of documentation, of approval, of accountability—had been designed to protect the company. And when something went wrong, the process found someone to blame. I know, Mark typed back. Take care of yourself. You too, Sarah responded. --- That afternoon, Mark received a call from a recruiter. "Mark, I saw the news. I'm sorry about what happened. But I wanted to reach out. I have a client who might be interested in your skills." Mark felt a flicker of hope. Maybe there was life after NexTrade. "Thank you," Mark said. "I'd like to hear more." They talked for twenty minutes. The recruiter asked about his experience. His skills. His availability. Then came the question Mark had been dreading. "Can I ask about the circumstances of your departure from NexTrade?" Mark's stomach tightened. He had prepared for this question. But it still hurt to answer. "There was an incident with the trading system," Mark said. "I was the code reviewer. The company determined that I was responsible for the failure." "I see." The recruiter's voice was neutral. "And do you agree with that assessment?" Mark hesitated. He could defend himself. He could explain the context. He could talk about the concerns he had raised. But he knew that wouldn't help. "I take responsibility for my role in the incident," Mark said. "I should have been more thorough in my review." "I understand." The recruiter's voice was professional. "I'll be in touch if my client wants to move forward." If, Mark thought. If they want to move forward. He knew what that meant. The termination would follow him. The question would come up in every interview. The stigma would never fully disappear. --- That night, Mark sat with his wife on the couch. Their daughter was asleep upstairs. The house was quiet. "How are you feeling?" his wife asked. Mark thought about the question. How was he feeling? Angry. Frustrated. Scared. But also something else. "I feel like I was the answer," he said. "Not the solution. The answer. Someone had to pay. It was me." His wife took his hand. "It's not fair." "No," Mark said. "It's not. But it's how the system works." They sat in silence for a while. "What will you do now?" his wife asked. Mark thought about the recruiter. About the interviews that would come. About the questions he would have to answer. "I'll find another job," he said. "Eventually. But I'll carry this with me." His wife squeezed his hand. "We'll get through this together." Mark nodded. He knew she was right. But he also knew that some things couldn't be undone. He had been the answer. Someone had to pay. And now he was paying.
Three months later, Mark started a new job. It wasn't as prestigious as NexTrade. The pay was lower. The benefits were worse. But it was a job. He had been through seven interviews before he got an offer. Each time, the question came up. Can you tell me about your departure from NexTrade? Each time, he gave the same answer. There was an incident with the trading system. I was the code reviewer. I take responsibility for my role. Each time, he saw the same reaction—a pause, a nod, a careful "I see." He knew what they were thinking. This guy caused an $87 million loss. Do we really want to hire him? But eventually, someone gave him a chance. A small company that needed his skills. A manager who had been through something similar himself. "I know how these things work," the manager had said during the interview. "Sometimes you're just the person in the wrong place at the wrong time." Mark had almost cried. --- One afternoon, Mark received an email from a former colleague at NexTrade. Subject: Update Mark, I thought you'd want to know. David left the company last month. He got a VP position at a bigger firm. Best, Tom Mark stared at the email. David had left. David had gotten a promotion. He thought about David's notebook. The careful documentation. The "for the record" questions. The friendly conversations that were actually evidence collection. David had played the game well. And he had been rewarded. Mark typed a response. Tom, Thanks for the update. I'm not surprised. David always knew how to protect himself. Best, Mark He hit send and closed his laptop. --- A few days later, he saw a news article about NexTrade. Trading System Company Implements New AI Oversight Protocols He clicked on it. NexTrade Technologies has announced new protocols for AI-generated code review. The changes come three months after an $87 million trading loss that resulted in the termination of a senior employee. The new protocols include: - Mandatory line-by-line code review for all AI-generated code - Additional testing requirements for edge cases - Independent oversight of the review process "We've learned from this incident," said CEO Robert Martinez. "We're committed to ensuring it never happens again." Mark stared at the article. Mandatory line-by-line code review. That was what he had asked for. That was what he had been told wasn't necessary. Additional testing requirements for edge cases. That was what Sarah had warned about. That was what he had failed to follow up on. Independent oversight of the review process. That was what the process had lacked. That was what had allowed him to become the answer. They had learned. They had changed. But it was too late for him. --- That night, Mark sat with his wife on the couch. Their daughter was doing homework at the kitchen table. The house was warm and full of life. "I saw an article about NexTrade today," Mark said. "They've changed their review process." His wife looked at him. "How do you feel about that?" Mark thought about the question. How did he feel? "Vindicated, I guess," he said. "They're doing what I suggested. What I was told wasn't necessary." "That must be frustrating." "It is." Mark paused. "But it also proves something." "What?" "That I was right. The process was flawed. I tried to warn them. But I was the one who paid for it." His wife nodded. "Do you regret anything?" Mark thought about the question. Did he regret anything? He regretted not following up on Sarah's warning. He regretted not documenting his concerns more thoroughly. He regretted trusting that the process would protect him. But he also knew that he had done his best. He had raised concerns. He had followed the process that was approved. He had never intended for the incident to happen. "I regret that I was the answer," he said. "But I don't regret trying to do my job." --- A few weeks later, Mark received a message on LinkedIn. It was from Sarah Kim. Mark, I hope you're doing well. I wanted to reach out because I've been thinking about what happened. I've been offered a promotion at NexTrade. They want me to lead the new code review team. I wanted to ask your advice. Should I take it? Best, Sarah Mark stared at the message. Sarah was being offered his job. Or rather, an expanded version of his job. He thought about what to say. He could be bitter. He could warn her. He could tell her to run. But he also knew that Sarah was talented. That she had tried to help. That she had been caught in the same system that had caught him. He typed a response. Sarah, Congratulations on the offer. You deserve it. My advice: document everything. Every concern. Every warning. Every conversation. Protect yourself. The system will use you until it doesn't need you anymore. Make sure you have a paper trail. Best, Mark He hit send before he could second-guess himself. A few minutes later, Sarah responded. Mark, Thank you. I'll take your advice to heart. I'm sorry about what happened to you. It wasn't fair. Best, Sarah Mark closed LinkedIn and sat back in his chair. It wasn't fair. No, it wasn't. But it was how the system worked. --- A year later, Mark was still at his new job. It wasn't glamorous. It wasn't prestigious. But it was honest work. He had stopped following news about NexTrade. He had stopped thinking about David, about Jennifer, about the process that had consumed him. But sometimes, late at night, he would think about the question that had haunted him since the beginning. Who was responsible? The answer, he knew, was complicated. He was responsible—for not following up on warnings, for not documenting concerns, for not being more thorough. But so was David—for dismissing concerns, for documenting every conversation, for protecting himself at Mark's expense. So was the company—for approving a flawed process, for relying too heavily on AI, for finding a scapegoat instead of fixing the system. So was the system itself—for being designed to protect the organization at the expense of the individual. Someone has to pay. That's how it works. Mark had been the answer. But he wasn't the only one responsible. He was just the one who paid. --- One evening, Mark sat with his daughter as she drew a picture. "What are you drawing?" he asked. "A picture of you at your new job," she said. She held up the paper. There was a stick figure at a desk, with a computer and a coffee cup. Above it, she had written: "My Daddy helps computers work." Mark felt a lump in his throat. "That's beautiful," he said. "Thank you." His daughter smiled and went back to drawing. Mark looked at the picture. It was simple. It was honest. It was real. He had lost his job. He had been the answer. He had paid the price. But he was still here. Still working. Still a father. The system had taken his job. But it hadn't taken his life. And maybe that was enough. --- The Blame Game continues. At companies across the world, people are being held responsible for failures that are not entirely their own. They are being documented, investigated, and terminated. The system protects itself. The individual pays the price. And the game goes on. Who will be the next answer?