I've been in this kind of situation a fair amount. Like everyone else says, breathe, and make sure there's visibility up your management chain. Make it clear y

I've been in this kind of situation a fair amount. Like everyone else says, breathe, and make sure there's visibility up your management chain. Make it clear you haven't been given the tools, and have full transparency when you talk to support. If I am reading this right, everyone - including the vendor - is going to try and nail you. Don't give them an in with dishonesty. You've done nothing wrong, and although it's heresy among techbros, not knowing some random computer thing isn't a moral failing. Unfortunately I also agree with the point about the resume. This won't be the first time your org does this kind of thing. In fact, it might be the standard way they do everything. I've seen that movie before, too. You get lucky, you can even get lucky many times, and luck combined with ability can take you places. But eventually luck runs out, and the situation goes down that toxic orgs always want it go down: with you in the toilet. Then they can go back to fingering each other or whatever it is orgs like this do when they run out of competent staff. Right now, I sort of have a gig like this, but it's a bit more informal, everyone having entered this with eyes open. I told them up front I have zero idea what I'm doing (front end dev), but they seemed alright with that, and I'm picking it up, albeit slowly (NgRx, that is). For my part, I wanted to learn this stuff anyway; functional programming has always been a giant blank spot in my know-how. It's not like my boss dropped down from heaven and said "Add these features to this strange codebase you've never seen before without talking to the developer" then disappeared.