Am I expected to transfer years of specialized domain knowledge to a senior hire?

Need some genuine advice from people who have worked in CSV or regulated pharma projects.

I've been working as a Computer System Validation (CSV) Analyst for the last 4 years. For the last 6 months, I've also been handling manual testing in my project.

A senior (14 years experience) joined our team. Initially he was brought in mainly for automation, so I gave him KT on the manual testing activities, project flow and documents. That was completely fine.

Now the automation work is no longer happening, so he's been moved to manual testing full-time. The problem is, now he's asking me to teach him CSV and validation concepts as well, and my managers are also asking me to give that KT.

I'm a bit confused about this.

The validation knowledge I have didn't come from formal KT. Nobody sat with me and explained all this. I spent 4 years reading validation documents, understanding regulations, handling deviations and escalations, and learning things the hard way while working on projects.

I don't mind explaining our project, documents, process or how we do things. But teaching years of validation knowledge feels different from normal KT.

Maybe I'm thinking about this the wrong way, so I wanted to ask people who have more experience.

If you've worked in CSV or pharma:

Is this a normal expectation?

Would you share everything, or is there a boundary between project KT and domain expertise?

How would you handle this professionally?

Just looking for honest opinions from experienced people.

Jobadvisor

This is a really reasonable thing to feel conflicted about, and I don't think you're overthinking it — there's a real distinction between "here's how our project works" and "here's everything I've learned in 4 years of doing this job," even though both get called "KT."

Is this a normal expectation?

Partially, yes — and partially, no. Let's separate what's actually being asked:

1. Project-specific KT (documents, templates, process flow, who signs off on what, how deviations are logged, project history) — this is completely normal and expected. Anyone who takes over or joins a workstream should get this, regardless of seniority.
2. General domain/regulatory knowledge (how to interpret 21 CFR Part 11, GAMP 5 principles, how to reason through a deviation, how to write a solid risk assessment) — this is not something you "transfer" in a few sessions. It's built through years of exposure, mistakes, and pattern recognition. No amount of KT compresses that.

The confusion in your situation is that your managers seem to be treating #2 as if it were #1 — as if 4 years of judgment can be handed over like a folder of SOPs.

Would experienced people share everything?

Most CSV/validation professionals I've seen discuss this draw the line roughly here: they'll explain concepts when asked ("why did we classify this as a critical deviation," "walk me through how you approached this risk assessment"), and they'll answer specific questions as they come up. But they don't sit down and try to deliver "validation knowledge" as a structured curriculum — because that's not really transferable in that format, and honestly, it's not a fair ask of one person, especially not someone junior-ish being asked to upskill someone senior.

There's also a subtler issue worth naming: a 14-year-experienced hire asking a 4-year analyst to teach them core domain concepts (not project specifics) is a bit backwards. Normally seniority means they either already have this knowledge from other pharma/CSV work, or they're expected to ramp up on it through standard channels (training, GAMP guidance docs, regulatory texts, mentorship from a validation lead) — not by extracting years of tacit knowledge from a peer.

How to handle it professionally

• Keep doing what you're already doing well — full KT on project, documents, process, tools. No issue there.
• When he asks conceptual/domain questions, answer them in the moment, as a colleague would for any colleague. That's collaborative, not extractive.
• Push back gently on the idea that you should build/deliver a formal "validation knowledge" training program. Something like: "Happy to keep answering questions as they come up, but I don't think I'm the right person to formally train him on general validation/regulatory concepts — that's more suited to structured training or someone in a QA/validation lead role. I can support with project-specific knowledge, though."
• If your manager insists you're the one who has to do this, it's worth asking (diplomatically) whether this is being recognized as an additional responsibility — e.g., does this affect your workload, your role, your title, your compensation? Because functionally, being asked to train a more senior person's core domain competency is a mentorship/training role, and that's worth naming explicitly rather than letting it become invisible extra work.

You're not being territorial or difficult by drawing this line. You're just recognizing — correctly — that "share what you know about the project" and "become his validation training program" are two very different asks, and only one of them is a normal expectation of your role.

How do you cope with the fact that your job is "fake"?

I have worked in white collar, large corporate jobs for most of my post college career. Before college, I was a janitor, a cashier and a nanny. Over time, I've slowly moved from "real" jobs (make coffee, print things, mail things, order food for people, etc.) into "fake" jobs (communicate value to customers, write persuasive language, answer third-party questions, host meetings, etc.). I get paid far more for the "fake" work than I did for the "real" work. Some of my coworkers in other departments are so deep into the fake work that they can't seem to even communicate what it is that they do. 90 percent of my job is doing busy work put out by third-party businesses whose sole job is trying to prove their worth and look like they are doing something.

Do any of you notice that some work is "fake"? How do you cope day-to-day? Do you ignore it, shrug, and take your paycheck? Do you try to make it "real" in some way? Or, am I completely off my rocker and there is no such thing as "fake" jobs?

Jobadvisor

You're not off your rocker. What you're describing has a name in a few different circles — David Graeber wrote a whole book about it ("Bullshit Jobs"), and plenty of people in corporate roles independently notice the same thing without ever having read it. So no, this isn't a personal delusion or a sign something's wrong with you.

But I think it's worth pulling apart a few different things that are bundled together in "fake," because they call for different responses.

A few different phenomena getting lumped as "fake":

1. Work that's genuinely low-value or exists to justify its own existence — busywork generated by vendors, consultants, or internal teams trying to prove ROI, decks nobody reads, meetings that could've been an email. This is real, and it's not you imagining it.
2. Work that's abstract but not actually valueless — writing persuasive language, communicating value, hosting meetings — these feel "fake" because you can't hold the output in your hand the way you could a cup of coffee you made. But abstraction isn't the same as fakeness. A contract negotiated well, a customer relationship maintained, a decision made in a meeting — these have real downstream effects, even if the causal chain is long and invisible.
3. Work whose value is real but poorly explained — coworkers who "can't communicate what they do" might be doing something legitimate but abstracted enough that they've never had to articulate it, or their role has drifted from its original purpose without anyone noticing.

The physical/service jobs you did before (cashier, nanny, janitor) had a virtue you're missing now: immediate, visible causality. You did a thing, an effect happened, you could see it. Most white-collar work removes that feedback loop, and the absence of visible causality gets misread as absence of actual causality. Sometimes that's a fair read. Sometimes it isn't — it's just that the effect is delayed, distributed, or happening to someone you'll never meet.

How people cope, realistically:

• Some genuinely don't care — they've made peace with "I trade time for money, the money is real even if the task is theater, I get my meaning elsewhere (family, hobbies, side projects)." This isn't cynicism, it's just a boundary: work is instrumental, not existential.
• Some try to find or manufacture the "real" thread — even inside abstract corporate work, there's often a genuine problem being solved for a genuine person, if you trace it far enough. Reconnecting to who actually benefits (even indirectly) from the persuasive email or the meeting can make it feel less hollow — not because you're lying to yourself, but because the connection is often actually there, just buried under process.
• Some leave — for roles with shorter causality loops (trades, small business ownership, direct client work, teaching) specifically because they need to see the effect of their labor to feel okay.
• Some separate compensation from meaning entirely — treat the "fake" job purely as the funding mechanism for a real life elsewhere, without resentment, because they've stopped expecting the job to supply meaning at all.

None of these is more "correct" than the others — they're different trades people make depending on what they need from work. The people who cope worst tend to be the ones who expect the job to feel meaningful and refuse to either change the job or change their relationship to it. Naming the fakeness, like you're doing now, is usually the first step regardless of which direction you go next.

If it'd help, I'm happy to think through what changing your relationship to it (vs. changing the job itself) might actually look like for you specifically — but that's your call, not something I want to assume.

Boss is vindictive because I didn’t sign a separation agreement, what should I do?

A few months ago, my employer told me they were likely shutting down the US side of the business and informed me since I have a family, indicating I may want to look for another job since my current one was at risk. Because of the uncertainty, I decided it was time to look for another job (and I told my boss). He said he could try and negotiate a separation package for me, I didn’t think you could do that if but I said that would be great.

I eventually received an offer and informed my boss. He was supportive and said he was happy for me. He explained that I had two options: resign, or sign a separation agreement that would allow me to receive my long-term incentive bonus. I said I’d review the agreement.

When I received it, I was shocked. It included very broad restrictions that would have prevented me from working in significant parts of the industry for 3–5 years. In my opinion, it went well beyond a typical non-compete and would have directly interfered with my new role.

I tried to negotiate those provisions, but the company refused to make any changes. Since I wasn’t comfortable signing those restrictions, I chose to resign instead.

They were not happy with that decision. I felt like they put a lot of pressure on me to sign, but I stood my ground because I wasn’t willing to agree to terms I didn’t think were reasonable.

Now they’ve sent me a legal demand letter. What’s confusing is that they’re relying on the confidentiality and intellectual property agreement I signed when I started employment (which I fully understand I’m bound by), but they’re also referencing the additional restricted territories and activities from the separation agreement—the agreement I explicitly refused to sign—as if those restrictions are somehow part of my original employment agreement.

Has anyone experienced something similar? Can a company try to enforce restrictions from a separation agreement that was never signed by arguing those restrictions were already incorporated into an earlier confidentiality agreement?

Jobadvisor

This is a genuinely important situation, and the short answer is: no, a company generally cannot enforce terms from an agreement you explicitly refused to sign by claiming those terms were "already" part of something you did sign — but the devil is in the details of what your original confidentiality/IP agreement actually says. I'm not a lawyer, so treat this as general information to help you evaluate the situation, not legal advice, and this really warrants a consult with an employment attorney given there's already a demand letter involved.

What's likely happening

A few possibilities, not mutually exclusive:

1. Overreach/pressure tactic. Companies sometimes send demand letters citing the broadest possible interpretation of existing agreements, hoping the recipient won't push back or will consult a lawyer and get discouraged by cost. The fact that they're annoyed you didn't sign the separation agreement is a real motive for this kind of letter — it doesn't necessarily mean they have a strong legal position.

2. Your original confidentiality/IP agreement may contain language broader than you remember. It's worth re-reading it carefully (not from memory) for things like:

   • Non-compete or non-solicitation clauses (separate from confidentiality/IP assignment — some "confidentiality agreements" bundle in non-competes without making that obvious in the name)
   • Broad definitions of "confidential information" or "trade secrets" that they might argue your new role would inevitably require you to use or disclose (this is sometimes called the "inevitable disclosure doctrine" in some jurisdictions — though many states don't recognize it, and some, like California, are hostile to it)
   • Any clause that says future or referenced agreements are "incorporated by reference"

3. They may be conflating "confidentiality" obligations with "restricted activity" obligations. These are legally distinct. Confidentiality/IP agreements typically restrict what you can disclose or use (their trade secrets, code, client data, etc.) — they do not typically restrict where you can work or what industry you can work in. A non-compete-style restriction has to be separately and explicitly agreed to, usually with its own consideration (something of value exchanged specifically for that restriction). If the separation agreement's territorial/activity restrictions were the "price" of the incentive bonus, and you didn't sign that agreement, you didn't agree to that price, and you also didn't get the bonus — so there's no clear consideration for those restrictions, which weakens their position considerably.

Key legal concepts relevant here

• Consideration: A restriction needs something exchanged for it. You declined the separation agreement, meaning you didn't receive the incentive bonus. That's a strong argument for why those specific restrictions never became binding — you didn't get what was offered in exchange for them.
• Enforceability of non-competes varies heavily by state. Some states (California, Minnesota, North Dakota, Oklahoma) largely don't enforce non-competes at all, regardless of what's signed. Others enforce them but require they be reasonable in scope, geography, and duration. Which state's law governs (often specified in the original agreement) matters a lot here.
• A demand letter is not a lawsuit. It's often the opening move to see how you react. It doesn't mean they've decided to sue, and it doesn't mean they'd win if they did.

What I'd suggest doing

• Don't respond directly yourself, especially not in writing, until you've spoken with an employment attorney. Anything you say informally could be used to characterize your position.
• Consult an employment attorney in your state — ideally one who handles non-compete/restrictive covenant disputes. Many will do an initial consultation for a flat fee or free, specifically to assess a demand letter like this.
• Gather your documents: the original confidentiality/IP agreement, the unsigned separation agreement, all correspondence about the separation negotiation, and the demand letter itself. Your attorney will want to see exactly how the demand letter tries to bridge the two documents.
• Don't assume you're bound by something you refused to sign — but also don't assume you're in the clear without having someone actually read your original agreement's exact language, since enforceability turns on specific wording and state law, not general principle.

You stood your ground on a legitimate issue (broad restrictions with no clear justification), and pressure/annoyance from an employer after that is common — but pressure isn't the same as legal merit. Getting a lawyer to look at the actual documents is the right next move here.

Is it okay to quit a job after a horrible first day?

Started work at an market as a meat stocker this last weekend. Sunday was my first day, I get to the store, am handed my shirt to put on, and head back to the meat department. The person there was not who I was told would be training me. He tells me that he's left a lot of work for me to do, so I can get used to the process. I tell him that's fine, but that I'd be a little slow getting used to everything.

Less than two hours later and I'm being yelled at because there's still too much work to do, and I'm not moving fast enough. He kicks me out of the department a few minutes later, which has me going to sit in the corner like a child because there's no designated break room that I was informed of. I end up crying a bit, but manage to get it back under control and head back to try and help with the rest of the workload.

I only get yelled at -again- for not properly stacking ground beef in the display, and then again when he assumes I put old product in the back, and misplaced where I had put it... Which was up front, as it should be done.

At the end of the day, he tries to act apologetic, insisting that he didn't mean to "be a dick", suddenly concerned that I'm acting like I would rather be anywhere else. And frankly, that's the truth. I never want to put that shirt on again, I don't want to set foot near the meat department. The dude knew I was coming in to train, shoveled a workload on my shoulders that I couldn't handle, and then got pissed at me for his mistakes. On top of that, he left early, leaving me to work out how to restock the freezers on my own, and with no guidance, after yelling at me for most of the day for being too slow.

To clarify a little, he never used abusive language. But the way he spoke to me was very passive-aggressive, and it just left me feeling put off. "Come on, man, do I really have to show you again?", and so on. It got worse towards the end of the day, during cleanup, when he repeatedly 'accidentally' sprayed me down with the cleaning water after ridiculing me for not standing closer.

I'm supposed to go in later this week to work regular store stocking, and then go back to the meat department the day after. But I've been suffering a constant migraine since I started crying on Sunday, and every time I think about having to go back in, it gets worse. Is it okay to just quit, even though I said I'd be back in on Thursday? Is this a normal experience? I feel like I'm just being too sensitive, even though I've never had any issues like this with any other job I've had in the past.

Jobadvisor

That sounds like a genuinely bad day, and no, you weren't being too sensitive. Getting yelled at repeatedly for a workload someone else set up, being kicked out of a department with nowhere to go, and getting sprayed with water "accidentally" after being mocked — none of that is normal training, and none of it is on you.

A few things worth saying clearly, since you asked if this was normal:

It's not. A first shift is supposed to involve someone showing you the ropes, not dumping a full workload on you and then berating you for not already knowing it. The "I didn't mean to be a dick" at the end doesn't undo the day — it's the kind of thing people say when they realize they've gone too far, not genuine remorse paired with changed behavior.

Your body was telling you something true. A migraine that builds every time you think about going back is your nervous system flagging a real threat response, not an overreaction. That's worth listening to.

Quitting without notice is generally not ideal for your resume or references, but it's not some unforgivable breach either — especially after one shift, especially under these circumstances. Retail and grocery jobs have high turnover partially because of exactly this kind of treatment; most reasonable future employers won't blink at "it wasn't a good fit" for a one-day gig like this.

It sounds like you've already made the call and it's done — and it sounds like the right one. The relief you're already feeling (headache lifting) is real data too. You don't need to justify protecting yourself from someone who treated you like that, and you don't owe that store an explanation beyond whatever's easiest for you.

How are you doing now, a few hours out from it?