My Boss Gave the Intern Credit for Two Years of My Work

Posted November 5, 2026

[PART 3]
After lunch, Lorna asked the four of us to meet in a small conference room at Riverton’s offices across the street.

I brought my laptop. Samir brought nothing because, as he said on the walk over, “The project already remembers what happened.”

That was exactly what I needed. I didn’t want a speech about how hard I’d worked. I wanted the ordinary record of the work itself.

Our engineering repository showed every major model revision. Revision 1 had my initials from August 2024. Revision 18 contained the valve sequence Dean had just praised as Theo’s idea. Revision 31 was the approved construction model. Theo’s first company login appeared months later, attached to a folder called CLOSEOUT DASHBOARD.

Lorna didn’t need a forensic investigation. She had attended the client reviews that matched the dates.

She opened her own meeting minutes and found my name beside the same decisions.

Dean tried a different explanation.

“I was speaking broadly,” he said. “Theo represented the new generation coming into the project.”

Lorna looked at him. “You said he helped rethink the operating sequence.”

Dean rubbed the bridge of his nose. “I was trying to recognize a young employee.”

“You can recognize him for what he did,” I said.

Theo sat beside Samir, staring at his hands.

I turned the laptop toward him. “Your dashboard folder is right here. It’s good work. Nobody is deleting it.”

He looked up. “I should’ve corrected the newsletter.”

“Yes.”

“I knew it was exaggerated.”

“Yes.”

Dean cut in. “Janelle, he already apologized.”

“This isn’t punishment. He needs to understand which choice was his.”

Theo nodded before Dean could answer for him again.

He told us that his uncle had started introducing him to executives as “the kid behind Riverton” after a practice presentation. At first Theo thought everyone understood it was shorthand for the dashboard. Then Dean sent him the newsletter draft and told him not to worry about the details because “visibility opens doors.”

Theo didn’t object.

That part mattered.

He hadn’t invented the story, but he’d enjoyed what the story did for him. He’d been invited to sit with senior staff, added to a recruiting panel, and named on the luncheon slide. Each time he stayed silent, correcting it became harder.

“I kept telling myself I’d explain if somebody asked directly,” he said.

Lorna gave a small, tired laugh. “I asked directly.”

“And I almost let him answer for me again.”

Samir finally spoke. “What made you stop him?”

Theo looked at me. “She gave me credit for the dashboard at the same table where he was taking credit from her. That made the whole thing sound as bad as it was.”

I hadn’t done it as a strategy. I had said it because it was true.

Lorna asked what I wanted corrected.

I had thought about that question during the walk over.

“The project record should name the people who did the work,” I said. “The award submission, the case study, and our internal presentation should match. Theo should keep credit for his dashboard. I should be listed as engineering lead. Samir should be listed as project manager.”

“And Dean?” she asked.

“He was division director. That’s accurate too.”

Dean stared at me as if accuracy itself were an insult.

I didn’t ask Riverton to remove Northline from the award. The client team had earned the recognition, and dozens of people had worked on construction, testing, controls, and operations. Turning the correction into a public spectacle would have made everyone else’s work collateral damage.

Lorna agreed. She said Riverton would send a corrected credit list to the association before the online case study went live.

Then she asked Northline for a separate meeting with our managing principal about project attribution.

That was where Dean finally understood the problem wasn’t ending with an awkward lunch.

Back at our office, he called me into his room and closed the door.

“You embarrassed me in front of a client,” he said.

“I asked which revision Theo designed.”

“You knew what that question would do.”

“I knew what the answer was.”

Dean paced once behind his desk. “Do you realize how this looks for Theo?”

“Yes. That’s why he should never have been put in that position.”

He told me I was making a family issue out of a management decision. I told him I hadn’t hired his nephew, written the newsletter, or put the wrong name on the slide.

Then he said something I hadn’t expected.

“Theo asked to be moved off my reporting line.”

I looked at him.

Dean’s jaw tightened. “He says he doesn’t want anyone wondering whether his next assignment came from me.”

That was the first consequence Theo had chosen for himself.

But it wasn’t the last thing he told the company about what had happened.

[PART 4]
The next morning, Theo asked Samir and me to meet before anyone else arrived.

He brought three printed pages. One was the original newsletter draft Dean had sent him. One was the revised version that had gone out. The third was an email Theo had written overnight to our managing principal, Amina Shah.

He handed the pages to me first.

“I want you to see what I’m sending before I send it,” he said.

I read the email. It didn’t make him a hero. That was why I believed it.

Theo wrote that he had not designed the Riverton pressure-control strategy, that he had knowingly allowed inflated descriptions of his role to circulate, and that he had failed to correct them until the client asked him directly. He identified his actual work: dashboard development, chart cleanup, and closeout presentation support.

He also wrote that Dean had encouraged the broader story.

“You don’t need my permission to send this,” I said.

“I know. I wanted to make sure I wasn’t getting your part wrong again.”

“You aren’t.”

He sent it from his laptop while we sat there.

Amina met with each of us that week. The company response wasn’t dramatic. Dean kept his title, but he was removed from approving project-attribution language for the Riverton account and from supervising Theo’s internship. Another director took over Theo’s remaining summer assignments.

The online case study was corrected before publication. Under “Engineering Lead,” it listed my name. Samir was named project manager. Theo was credited for data visualization and closeout support.

That line was smaller than the one Dean had tried to give him.

Theo told me he preferred it.

The harder part was what happened after the correction, because a clean record doesn’t instantly create a clean relationship.

For the first week, Theo barely spoke to me unless a task required it. I didn’t chase him for gratitude. I reviewed his dashboard code the same way I would have reviewed any intern’s work and left comments where the units were unclear.

On Friday he appeared at my desk with a revised chart.

“I fixed the axis labeling,” he said.

“I saw.”

“Is it better?”

“Yes.”

He stood there another second. “Can I ask you something?”

“Go ahead.”

“How do you know what credit to take without sounding like you’re claiming everything?”

I turned my chair toward him.

“Name the decision. Name the work. Name who else touched it. That’s usually enough.”

He nodded and wrote that sentence in his notebook.

Dean and I never became friendly after that. We could work together, but I stopped accepting private verbal changes to staffing or attribution. If he wanted my team to shift ownership, we discussed it with the project manager present and updated the responsibility matrix.

He called that overly formal once.

I told him, “It keeps us from having another luncheon.”

He didn’t argue.

Two months later, Riverton invited our team to present the redesign at a regional operations workshop. Lorna introduced us herself.

“Janelle Ortiz led the engineering,” she said. “Samir Desai managed delivery. Theo Mercer built the closeout visualization you’ll see in the second half.”

Three accurate sentences.

Theo gave his dashboard segment without trying to stretch it into something bigger. He was good. Better, honestly, than he had been during the summer, because he no longer seemed busy proving that he belonged in every part of the project.

Afterward, a utility engineer asked him how he’d developed the valve sequence shown in one chart.

Theo pointed across the room at me.

“I didn’t,” he said. “Janelle did. I can show you how I visualized her test results, though.”

Then he did exactly that.

His internship ended in August. He didn’t ask me for a recommendation, which I respected. A week before he left, I offered one anyway, but I told him what it would say: strong data skills, improving engineering judgment, and a mistake in attribution that he eventually corrected publicly and specifically.

He thought about it before saying yes.

“I’d rather it be true,” he said.

On his last day he returned the old award-luncheon program that I’d left in a project folder. Dean’s original notes were still printed inside it.

Theo had crossed out the line that called him the project’s young designer.

Above it, he had written: “Dashboard and closeout support — Theo Mercer.”

Beside “Engineering Lead,” he wrote my name.

I keep that program inside my worn blue design notebook, the one with two years of valve sketches and field numbers in the margins. When I opened it after Theo left, the corrected page rested exactly where revision 18 began.

Uncategorized