Technical ability being judged by familiarity with undocumented business logic
I’m in an environment where technical ability seems to be judged heavily by how familiar you are with the company’s business logic.
The problem is that a lot of this logic is specific business knowledge context held by a few senior people with 15+ years of experience in same organisation It isn’t obvious from the code or queries, and documentation is either missing or incomplete. Asking for documentation—or offering to document what I learn, doesn’t seem to get much traction.
At the same time, using an LLM to help trace code, queries, or reconstruct some of that context is frowned upon, and there’s an expectation that LLM usage should be tagged on deliverables.
So it feels like a strange catch: you’re expected to already know undocumented context, and not knowing it can be interpreted as weak technical ability, but the mechanisms for independently closing that knowledge gap aren’t really encouraged.
Has anyone dealt with this kind of culture? How do you distinguish actual technical competence from simply having years of accumulated company-specific knowledge, and how do you navigate it without constantly depending on the same gatekeepers?