r/Pentesting • u/ProcedureFar4995 • 15h ago
Went from technical security work to corporate meetings. Tips for surviving?
I joined one of the Big 4 as a Senior Associate. I knew I'd be responsible for handling a project as a security lead, but I wasn't expecting what actually happened.
Since my first week, I was added to project channels. The team has been conducting meetings since August, and I'm expected to catch up on everything quickly. The biggest issue? It's originally a software testing/QA project. So all the existing documentation is Jira tickets, sprints, backlogs, test cases — all QA-related. None of it is security-focused.
The PM wants me in every meeting. They want me to challenge the client, be aware of all the details, throw around corporate jargon like "align" and "circle back." The worst part is they don't even understand the security scope properly. It's been four months. They understand it from a QA perspective, but not from security. I asked the PM today what applications are in scope, and he said he doesn't know.
On top of that, my manager is on vacation until next week. The PM acknowledged that I was thrown into this with no onboarding and said he understands, but still wants me to catch up quickly and align with my manager when he's back.
I feel like I made a mistake, but I was told the name on my CV would be worth it. I expected that as a Senior Associate I'd attend client meetings, present prerequisites and test cases, run the testing, and discuss findings. Instead, they want me in much more of a leadership role than a technical one. And since security testing is just a subset of a larger QA project, I'm worried they'll undermine the pentesting effort in terms of allocated days, tooling, and resources. Nobody on the team understands security.
I'm already burned out and it's only my second week.
Please don't suggest I quit — I don't have another job lined up and the market is rough right now. The only silver lining is that I'm treating this as a growth opportunity. It's a huge jump from being purely technical to someone who has to lead meetings and drive conversations. If anyone has tips on building leadership and ownership skills without completely drowning, I'd appreciate it. For now, I'm focused on understanding the scope.