Coworker Kept Asking Why She Didn’t Have Kids — Then She Asked HR What the Policy Was on Personal Questions

By the time the third “so when are you finally having a baby?” landed in her inbox, the 29-year-old analyst had stopped pretending it was small talk. It was a Tuesday morning check-in, the kind that should have been about deadlines and deliverables, and instead it turned into another round of her coworker circling back to her personal life.

She worked at a mid-sized company with a hybrid schedule, and the team had gotten closer over months of recurring meetings and shared projects. But one colleague on her immediate team had latched onto a single topic and wouldn’t let it go. At first it was framed as curiosity. Then it became commentary, and eventually it felt like pressure.

The questions started as “friendly,” then became a routine

It began after a casual conversation about weekend plans. She mentioned meeting her sister’s newborn, and her coworker reacted with a knowing smile and a follow-up: why didn’t she have kids yet? She laughed it off, gave a vague answer about being busy, and tried to steer back to work.

After that, the questions popped up everywhere. In the break room on office days, in team chats, and sometimes right before meetings, like an icebreaker. The coworker would ask if she and her spouse were “trying,” whether she “even wanted” children, and what her “reason” was.

She tried different approaches: changing the subject, answering with humor, and eventually offering a firm “I don’t discuss that at work.” Nothing stuck. The coworker treated the boundary like a negotiation and kept coming back with variations that were just different enough to seem casual, but consistent enough to feel targeted.

Boundaries didn’t work, and the tone got sharper

The turning point came during a group lunch after an in-office training. Someone mentioned childcare costs, and the coworker pivoted straight to her again, asking if she was avoiding kids because she was selfish or because she “couldn’t.” The table went quiet in a way that made it clear everyone heard the implication.

She didn’t want to cause a scene, so she waited until they were back at their desks and sent a short message: she was uncomfortable with personal questions about family planning and wanted it to stop. The coworker replied with a shrugging tone, saying it was only conversation and that she was being overly sensitive.

After that, the questions didn’t stop—they just moved. Instead of asking directly in front of others, the coworker started catching her one-on-one on video calls, or dropping comments in private messages. It became harder to rely on social pressure to keep it in check, and easier for the coworker to deny it was happening.

She started documenting, and the paper trail told its own story

Once it felt repetitive and deliberate, she began saving everything. Screenshots of chat messages. Notes with dates and times after in-person comments. A short summary after each incident, written the same day so it was clear she wasn’t reconstructing it weeks later.

She also paid attention to the pattern: it spiked after she mentioned anything family-related, even something neutral like a holiday visit or a cousin’s wedding. And it never went the other direction—she wasn’t asking the coworker intimate questions in return. It was a one-way fascination with her reproductive choices.

Within a month, she had enough examples that it stopped sounding like a misunderstanding and started looking like ongoing harassment. The messages weren’t explicit threats, but they were persistent, personal, and increasingly loaded with judgment.

Instead of filing a complaint first, she asked HR about the rules

She didn’t walk into Human Resources demanding punishment. She did something quieter: she asked what the company’s policy was on personal questions and repeated comments about family status. She framed it as wanting guidance on what was considered appropriate workplace conduct and how employees were expected to handle boundary issues.

The HR representative asked if it was about her, and she said yes. She explained the situation in a factual way and mentioned she had saved messages. That changed the meeting’s tone. HR wasn’t just giving a general policy overview anymore; they were listening like this could turn into a formal matter.

HR asked for examples and clarified that questions about pregnancy, fertility, and family planning can cross a line, especially when they’re repeated after someone asks for it to stop. HR also asked whether it was affecting her work, and she admitted it was: she dreaded meetings with the coworker and avoided shared spaces on office days.

At the end of the conversation, HR offered to address it informally first—coaching and a reminder about professional boundaries—or to open a documented complaint. She chose the informal route initially, hoping it would be enough without turning her day-to-day into a feud.

The coworker reacted like the real offense was being reported

Within a week, the coworker’s behavior changed, which told her HR had spoken to them. The direct questions stopped. But the coworker became colder in meetings, cut her out of small discussions, and started responding to requests with clipped, minimal replies.

Then the coworker began implying she’d “gotten someone in trouble” for normal conversation. It wasn’t said outright in a meeting, but it showed up in side comments and a couple of passive-aggressive messages about how “you can’t say anything anymore.”

Work-wise, the tension created practical problems. The analyst needed information from that coworker to complete a shared report, and delays started piling up. She flagged it to her manager in a neutral way—missed handoffs, slower responses—without relitigating the personal topic. The manager adjusted responsibilities so fewer tasks required direct coordination.

HR checked back in and asked whether retaliation was occurring. She was careful with that word, but she did share examples of sudden hostility and exclusion. HR advised her to keep documenting and to send follow-up notes after any concerning interaction, especially if it affected project timelines.

People focused on proof, process, and protecting her job

Others who heard about the situation—coworkers she trusted and friends in other workplaces—were mostly practical. The main advice was to keep everything in writing and to avoid “clearing the air” alone with the person who kept pushing. Several people suggested confirming expectations by email after meetings, so missed handoffs couldn’t be blamed on vague misunderstandings.

Some urged her to skip the informal approach and file a formal complaint immediately, especially because the questions touched on sensitive areas like fertility and marital choices. Others warned that the social backlash can be real in tight teams, and said her manager needed to be looped in early so performance couldn’t be weaponized against her.

A few people pointed out that even if the coworker thought they were being friendly, once someone says stop, continuing is the issue. The repetition is what turns “curiosity” into something more coercive, and workplaces tend to treat it more seriously when there’s a clear record of a boundary being stated.

For now, the overt questioning has stopped, but the atmosphere hasn’t fully recovered. She’s still doing her job, still keeping receipts, and still weighing whether the cold shoulder is enough to justify a formal escalation. What she wanted was simple—basic privacy at work—and she’s learned that sometimes the only way to get it is to ask, directly, what the rules actually are.