Interviewed for what sounded like a backend heavy role and I'm mostly triaging support tickets and writing internal docs. Not sure if this is normal drift that happens everywhere or a sign the team didn't really know what they were hiring for. Still figuring out if it's worth raising or just riding out.
This tracks with basically every job I've had honestly. The JD is more of a rough sketch than a contract, seems to just be how hiring works everywhere.
Had a similar drift happen to me, though mine went the opposite direction, way more scope than the JD implied. Either way it seems like JDs are more of a starting negotiation than an actual contract. Worth raising with your manager directly rather than assuming it'll just fix itself.
Same boat here honestly, mine turned out to be a signal that the team churned right before I joined and just recycled the old req. Worth checking if that's the pattern before reading too much into it.
Honestly this seems more common than not from what I've seen posted here. I'd bring it up in your next 1:1 before it turns into resentment.
This happened to me at my last job too, turned out the team had just written the posting a year before actually opening the role and never updated it. Worth asking directly instead of assuming.
