Employee Found Her Entire Proposal Word-for-Word on a Coworker’s LinkedIn as a ‘Personal Project’

Mara was half-listening to a Monday morning stand-up while scrolling LinkedIn the way everyone does when they’re trying to look busy on camera. She’d promised herself she’d stop doom-scrolling career updates, but her thumb kept moving anyway—past the promotions, the humblebrags, the motivational posts that sounded like they were written by the same robot.

Then she saw it: a familiar headline, a clean little carousel graphic, and a caption about a “learning journey” and a “self-driven initiative.” The author was Jonah, the new-ish analyst on her cross-functional team. And the project he was showing off wasn’t just similar to Mara’s proposal. It was Mara’s proposal, line for line, down to the weird phrasing she used when she was trying to sound confident and not tired.

At first she thought she was imagining it. It was early, she’d slept poorly, and she’d been living on reheated coffee. But she clicked through, and there it was again: her framework, her timeline, her exact three-phase rollout. Even a sentence she’d written in a rush and never bothered to smooth out, because only internal stakeholders were supposed to see it.

The problem started before the big blowup

Mara had spent six weeks on the proposal, which was supposed to be her “big swing” for the quarter. She wasn’t trying to be dramatic about it, but she needed this win. Her partner had just gone back to school, money was tight, and her manager had casually mentioned she’d be “ready for the next level” if she could lead something end-to-end.

The project was a process overhaul that would cut down on duplicated work between teams. It wasn’t glamorous, but it would save hours, and it would be the kind of thing leadership loved because it sounded efficient and measurable.

Jonah had been added late to the team, mostly as support. He was friendly, eager, always the first to volunteer to “capture notes,” and always the first to message Mara after meetings asking for “anything you can share so I can get up to speed.” She didn’t think twice about it. Sharing drafts was normal. Collaboration was normal.

She’d sent him a PDF two weeks earlier after he asked if he could “study how you structure proposals.” She even felt a little flattered. She remembered typing, “Of course, happy to help,” like an idiot.

The moment she realized it wasn’t a coincidence

By lunchtime, Mara had compared Jonah’s LinkedIn post to her original document like she was cross-checking a suspicious essay in college. The content wasn’t “inspired by” hers. It was copied. The same headings, same order, same examples. He’d swapped out one internal product name for a generic phrase, but he hadn’t even bothered to change the transitions.

And he’d presented it as something he built on nights and weekends. He’d even tagged a few people in leadership, including the director who was set to attend Mara’s proposal review later that week.

Mara felt her face get hot, like embarrassment and anger had teamed up to fight for space. Part of her wanted to slam her laptop shut and pretend she never saw it. Another part of her wanted to comment publicly and light the whole thing on fire.

Instead, she screenshotted everything. The post. The slides. The timestamps. The comments praising Jonah for being “such a self-starter.” She forwarded the screenshots to herself, then pulled up her sent email with the PDF attached. Date and time, right there. She didn’t want drama. She wanted proof.

She tried the quiet route first—and it backfired

Mara messaged Jonah privately, keeping it short and painfully polite. She told him she’d seen his post and noticed it matched her proposal. She asked him to take it down and clarify where it came from.

Jonah replied quickly, and the tone was all wrong. He didn’t apologize. He acted confused, then defensive, then oddly offended. He wrote that it was “based on team discussions,” that he’d “reframed it into a personal project,” and that it was “a common approach in the industry.” He finished by saying he thought she’d be “excited to see the work getting visibility.”

Mara stared at the message and felt something drop in her stomach. He wasn’t going to back down. In his mind, he’d done nothing wrong, and if she pushed, she’d look like the difficult one.

That afternoon, in a meeting with a few teammates, Jonah referenced his LinkedIn post out loud like it was a fun little update. He said he’d gotten “such great feedback” and that it was “cool to see engagement.” Mara didn’t say anything in the moment, but her manager’s eyes flicked to her, then away, like she’d noticed something but didn’t want to touch it.

HR got involved, and suddenly everyone had an opinion

Mara looped in her manager after work, asking for a quick call. She didn’t lead with emotion. She laid out the facts: her proposal, the draft history, the email where she sent it, and Jonah’s post. She also pointed out that the document contained internal information, even if Jonah had scrubbed a few specifics.

Her manager went quiet in that way that says, “This is bigger than I want it to be.” Then she asked Mara to forward everything and said she’d bring in HR and their department lead.

By the next morning, Jonah’s post was still up, and the comments were still rolling in. Meanwhile, Mara was pulled into a meeting with HR where the questions were maddeningly calm. Did she give Jonah permission to share the content? Did the proposal have any confidentiality labels? Had she asked him to remove it? Did she have the original files?

It felt like being asked to prove she hadn’t left her wallet on the sidewalk and invited someone to take it.

Word traveled fast anyway. Coworkers pinged her in that vague, careful way people do when they don’t want to be pulled into anything. A couple of teammates were supportive and said they’d noticed Jonah had a habit of presenting ideas from group chats as if they were his own. One person warned her, quietly, that Jonah was well-liked by a senior manager because he was “always putting himself out there.”

And then there were the other reactions: the ones that made Mara want to scream. A colleague told her, gently, that LinkedIn was “just marketing” and she shouldn’t take it personally. Another said she should consider it a compliment, because it meant her work was “good enough to imitate.”

Mara didn’t need compliments. She needed her work back.

The cleanup was messy, and the damage wasn’t just online

Two days later, Jonah’s LinkedIn post disappeared without any explanation. No correction. No acknowledgement. Just gone, like it had never existed.

Internally, though, the situation didn’t vanish. Jonah was removed from the project, and his access to certain folders was restricted. Mara found out when she tried to share an updated draft with the team and noticed his name wasn’t on the list anymore.

What she didn’t get was a satisfying resolution. HR told her they “addressed it” and reminded everyone of their intellectual property policy. Her manager told her she handled it professionally and encouraged her to focus on her upcoming presentation.

Jonah avoided her in the hallway. When they did end up on the same call, he was stiff and overly formal, like she’d accused him of something ridiculous instead of showing receipts.

Then came the part Mara hadn’t expected: a weird social chill. A few people stopped chatting with her as much. Someone she used to grab coffee with suddenly became “so busy.” Another teammate, who prided herself on being neutral, said she hoped Mara and Jonah could “move forward” because “we’re all under pressure.”

Mara kept thinking, I’m under pressure too. That’s why I didn’t steal anyone’s work.

Her proposal moved forward, but it didn’t feel like a win

On the day of Mara’s review, she walked leadership through her plan with her hands steady and her heart doing something frantic under her ribs. She didn’t mention Jonah. She didn’t reference LinkedIn. She presented the proposal as what it was: her work, built from weeks of research and hard choices, shaped by team input but owned by her.

The director asked good questions, the kind that meant they were taking it seriously. Her manager backed her up. By the end, Mara got the green light to pilot the first phase.

After the meeting, she sat at her desk and stared at her screen, waiting for the rush of relief she’d been picturing for months. It didn’t come. What she felt instead was a dull kind of exhaustion and a new wariness she didn’t want to carry into every project.

She started locking down drafts. She stopped sending documents without a clear purpose. When someone asked for “anything you can share,” she asked what they needed and why. She hated that she had to think that way now, but she also hated the idea of learning the lesson twice.

Jonah eventually transferred teams. No announcement, no goodbye message, just a quiet shift in the org chart. The people who’d acted like the whole thing was no big deal moved on to the next office topic. Mara didn’t get an apology, and she didn’t get her sense of trust back quickly.

But she did get something else: a pilot project with her name on it, a manager who’d seen what happened, and a private understanding that being “helpful” doesn’t have to mean being wide open. She could still be generous. She was just going to be careful about who got to hold the draft.