I Found My Own Job Posting Online Before Anyone Told Me
I found my own job online at 11:42 on a Tuesday night.
I was not looking for it.
I was looking for someone else’s.
My friend Nora had sent me a link to a position at my company and asked whether I knew anything about the team.
I opened the careers page.
Scrolled once.
Then stopped.
Senior Operations Specialist.
My title.
My department.
My city.
I clicked.
The first bullet point was a sentence I had written myself two years earlier when my manager asked me to update my job description.
Own cross-functional workflows from intake through final resolution.
I read the posting twice.
Then a third time.
The responsibilities were mine.
The software was mine.
The reporting line was mine.
Even the awkward phrase “operational ambiguity” came from a presentation I had given in March.
There was only one major difference.
The salary range started twelve thousand dollars above what I made.
I took screenshots.
Then I refreshed the page to make sure I had not imagined it.
The posting was still there.
At midnight, I checked my email.
No message from HR.
No meeting invite from my manager.
No announcement.
Just my job, advertised to strangers.
I barely slept.
By eight the next morning, I had developed six explanations.
Maybe someone on another team was using the same title.
Maybe they were adding headcount.
Maybe it was an old posting accidentally republished.
Maybe I was about to be fired.
The last explanation was the only one my nervous system believed.
My manager, Greg, arrived at 8:35.
At 8:37, I asked if he had five minutes.
“Sure.”
We sat in a small conference room.
I put my laptop between us.
“Is this my job?”
Greg read the screen.
His face changed before he answered.
“Where did you find this?”
“Our careers page.”
“Right.”
“Is it my job?”
He exhaled.
“It’s more complicated than that.”
I hate that sentence almost as much as “we should talk.”
“Then explain the complicated version.”
Greg told me the company was redesigning operations.
My role had grown beyond what it was three years earlier.
More systems work.
More data.
Less vendor administration.
Leadership wanted to turn the position into something more technical.
“And nobody thought to tell me?”
“We were still figuring it out.”
“The job is posted.”
“HR moved faster than expected.”
That answer made me angrier.
It treated the posting like a weather event.
Something that happened.
Not something people approved.
“Am I being replaced?” I asked.
Greg paused.
“Not exactly.”
“That is not an answer.”
He looked uncomfortable.
“Leadership wants to see what the market looks like.”
“For my role.”
“For the redesigned role.”
“Am I being considered?”
Another pause.
That was the moment I stopped being afraid and became clear.
“You posted a higher-paid version of my job and you have not decided whether I am qualified for it.”
“That’s not how I’d put it.”
“How would you put it?”
Greg leaned back.
“We need stronger analytics skills.”
“Then why didn’t you tell me that six months ago?”
He did not have a good answer.
That hurt more than the posting.
I could learn analytics.
I could decide I did not want to.
I could apply for the new role.
I could leave.
What I could not do was make any informed choice if the company redesigned my future privately and called it planning.
“You were benchmarking the market against me before anyone told me I was being benchmarked.”
Greg said I was welcome to apply.
That sentence almost broke something in me.
“Apply?”
“Formally, yes.”
“For the job I already have?”
“For the new version.”
I looked at the posting again.
It was eighty percent my current work.
Twenty percent new.
And one hundred percent posted as if I did not exist.
I did apply.
Not because I wanted to prove I deserved my own job.
Because I wanted information.
I updated my résumé.
That was unexpectedly useful.
I had not looked at my work as accomplishments in years.
I had simply been doing it.
I listed the systems I built.
Processes I shortened.
Escalations I reduced.
Projects I rescued quietly enough that nobody called them rescues.
Then I compared the posting to my experience.
The gap was smaller than Greg made it sound.
I lacked one reporting tool.
I had used another.
I lacked a formal analytics certificate.
I had been doing analysis every month.
The interview felt surreal.
Two people I worked with asked me why I wanted the role.
I answered honestly.
“Because most of the role is the work I already do, and I want to understand what you think has changed.”
One interviewer looked embarrassed.
The other took notes.
A week later, HR offered me the redesigned role.
The salary was higher.
Not the top of the posted range.
But meaningfully higher.
Greg seemed relieved.
“I’m glad this worked out.”
I was not ready to call it that.
“Why didn’t you tell me before posting?” I asked again.
This time, he answered more honestly.
“We thought if we told you before we knew the final structure, you’d worry.”
I stared at him.
“I found my own job online.”
He nodded.
“I know.”
“That was less worrying?”
“No.”
At least he did not pretend.
Before accepting, I also spent a weekend looking at similar roles outside the company. That mattered. I did not want relief at being “chosen” internally to become the only reason I stayed. I compared salaries, responsibilities, remote policies, and the kinds of analytics skills other employers expected. The exercise gave me leverage, but more importantly it gave me perspective. I was not applying for permission to remain employed. I was deciding whether the redesigned job still made sense for me.
That distinction changed the offer conversation. I asked directly about the salary range, the training budget, and what success would look like six months later. For the first time since finding the posting, I felt like a participant in the change rather than the object of it.
I accepted the role.
But I also asked for something that was not in the offer letter.
Quarterly role reviews for the team.
Not performance reviews.
Role reviews.
What had changed?
What new skills were becoming important?
What responsibilities were quietly expanding?
What expectations existed that no one had said out loud?
Greg agreed.
HR adopted a version of it for two other teams after another employee raised a similar issue.
Six months later, one of my analysts came to me with a nervous expression.
“Can I ask you something?”
“Of course.”
“I saw a posting that looks like my job.”
My stomach dropped.
Different team.
Different manager.
Same mistake.
This time, I knew what to do.
We opened the posting together.
Then we called her manager into the room.
No private speculation.
No waiting for HR to “finalize” the story.
Just the conversation that should have happened first.
My own role had changed again by then.
That no longer scared me.
Change was not the betrayal.
Silence was.
Read more workplace stories or browse short stories for adults.
This is an original fictional story from Dastan.
Featured photo: Devin Pickell / Unsplash. Inline photos: Vitaly Gariev and Brooke Cagle / Unsplash.
