ARTICLE · SELF IMPROVEMENT · 12 MIN READ

The Corporate Fraud That Never Existed

New role, higher pay, and the terrifying certainty that I was a total fraud. This is how I survived my first 3 months in the deep end.

I lived the life of a corporate fraud for about three months last year. At least, that's what I believed. Every day, I walked into meetings convinced that sooner or later someone would realise I had absolutely no business being there and expose me for the imposter I thought I was. The worst part? It started just after I got promoted to my new role as Process Change and Digital Implementation Analyst.

When my my former boss and my predecessor in this role told me that they wanted me to take over the enterprise digital business space, I was skeptical. I didn't think I was the one. Sure, I had handled projects before in my graduate executive rotations, but I didn't think they were the same thing. Did I tell them that though? Hell no! I sucked it up and convinced myself I could do it. And everyone around me believed I could too. I had acquired relevant skills, participated in successful projects, and earned the trust of people who believed I was capable of leading products from conception to delivery. But internally, I felt completely incapable. And to be fair, I thought I had good reasons to feel that way.

I didn't have a technical background, unlike my predecessor whose whole academic journey was exactly this role. In fact, I got to find out they created this role specifically because of him and he was practically the first person to assume it. That did not increase the pressure on me at all now, did it? Secondly, I was young, quite new to Telco with barely 2 years into my graduate executive journey, and hadn't fully had a chance to be the one that had to call the shots and make key decisions in my career journey. Saying I felt like a fraud is an understatement.

Nevertheless, I allowed myself to be talked into taking this role, did the interviews, passed, and for the first time since I started my career journey, I was not excited to see a "Congratulations, you got the role" email. The jump in numbers was not even enough to put a smile on my face. Instead of feeling accomplished, I felt something else: fear. Not the fear of failure itself, because I was ready for that part, but the fear of being exposed. I worried that someone would eventually discover that I was not as competent as they thought I was. I feared that my colleagues, stakeholders, and executives would realise they had made a mistake. Every meeting felt like a test. Every decision felt like a potential mistake. Every success felt temporary.

It would take several months before I learned and accepted that there was a name for what I was experiencing: imposter syndrome.

What Is Imposter Syndrome?

Imposter syndrome is the persistent feeling that one's achievements are undeserved and that one's success is due to luck, timing, or deception rather than competence. People experiencing it often live with the fear that they will eventually be "found out" as frauds despite evidence to the contrary.

First coined in 1978 by psychologists Pauline Clance and Suzanne Imes, imposter syndrome isn't a mental illness; it is a psychological pattern where high-achieving individuals are unable to internalize their accomplishments. Instead, they harbor a persistent, internalized fear of being exposed as a "fraud." No matter how many successful project rollouts or positive performance reviews I accumulated, the internal narrative remained unchanged: I am just lucky, and my incompetence will inevitably be unmasked.

My typical Tuesday perfectly illustrates why I used to feel like a fraud.

At 10:00 AM, I am in a deep-dive session with software developers and technical leads. They are tossing around architectural terms and system constraints. My brain instantly triggers an alarm: Are my user stories technical enough? Do I understand the API integrations deeply enough to speak their language? How do relay back to my business stakeholders that what they are asking for is technically impossible?

At 11:30 AM, I pivot. I walk into a workshop with frontline business operations teams who are looking to digitise their daily operations. Suddenly, the anxiety shifts shapes. Now, I am listening to raw operational frustrations, and the inner voice mocks me from a different angle: Do you actually know what it feels like to handle hundreds of these manual requests a day, or are you just imposing a shiny, detached digital framework onto their real-world chaos? How well can the team adopt the new digital flows once it is fully implemented?

Suddenly, I was expected to make decisions where there was no obvious right answer. Should we prioritize Feature A or Feature B? Was this customer complaint significant enough to influence the roadmap? Were we solving the right problem in the first place?

For a long time, because I was neither the deepest technical expert nor the longest-serving operational veteran in the room, I convinced myself I didn’t belong in either space. I felt like an outsider standing on a bridge, technical enough for neither side and expert enough for neither room. Yet my entire role existed because somebody had to stand on that bridge.

And coupling all these decisions with my part time law school classes and everyday life decisions was crippling. Some days I cried. Other days I stayed in bed questioning whether I had made the biggest mistake of my career. And more than once, I seriously considered giving up.

The Shift from Doing to Deciding

Ironically, imposter syndrome tends to affect high achievers the most. Psychologists point to a mix of personality traits and environmental triggers. It thrives in high-stakes environments, during career transitions, and among people with high perfectionist tendencies. The more responsibility they are given, the more they question whether they truly deserve it.

Looking back, my transition into product management created the perfect environment for these feelings to thrive. In many professional roles, success is relatively straightforward. You complete assigned tasks, solve defined problems, and produce measurable outputs.

This role fundamentally requires stepping into unfamiliar business domains, diagnosing inefficiencies, and driving massive changes without having absolute, long-term authority over the people doing the day-to-day work. The mismatch between the high impact of the role and the lack of traditional, operational authority creates a psychological friction point.

I discovered that product management is less about having all the answers and more about making informed decisions with incomplete information. Unfortunately, my brain interpreted uncertainty as incompetence.

Whenever I did not immediately know the answer to a question, I assumed it was because I lacked the knowledge necessary for the role. I failed to appreciate that uncertainty is not a sign of weakness in product management; it is the nature of the work.

It took months of agonizing over meetings to realize the fundamental truth: The value I bring isn't in mastering one specific silo. The magic is the bridge itself. My asset is the ability to translate technical capability into tangible business value, and to transform operational pain points into clear, executable technical requirements.

The Many Faces of Imposter Syndrome

My experience did not manifest as obvious self-doubt. Instead, it appeared in subtle ways.

I overprepared for meetings. What should have taken an hour often took three. I reviewed presentations repeatedly, anticipating questions that might never be asked.

I started having mental breakdowns when project deadlines were not met and stakeholders were on my neck for update. I quickly learnt the art of managing and anticipating project delays and finding ways and means to communicate to stakeholders before an escalation was required

I struggled to accept praise. Whenever a project succeeded, I attributed the outcome to the efforts of engineers, designers, stakeholders, or fortunate circumstances. I rarely gave myself credit. I just brushed off everything and moved on to the next thing. For months, it felt like I was holding a breathe each time a project was ongoing and completion only gave me a brief chance to let out that breathe before inhaling again for the next task.

I compared myself constantly. If I spoke to an engineer, I felt insufficiently technical. If I met a designer, I felt creatively limited. If I interacted with a senior product leader, I felt inexperienced.

What I failed to realise was that I was comparing my weaknesses to everyone else's strengths.

I was also hesitant to ask questions. I worried that asking for clarification would reveal gaps in my knowledge. This led to a lot of time being wasted on bottlenecks that could've easily been resolved with a phone call or teams meeting. Ironically, some of the most effective product managers I later encountered were the people who asked the most questions.

The Cost of Feeling Like a Fraud

For a long time, I treated imposter syndrome as a harmless internal struggle. It was not.

It affected my confidence and slowed my decision-making. I spent excessive time seeking reassurance and avoiding mistakes rather than creating value.

More importantly, it prevented me from fully embracing opportunities to learn. When your primary goal is to avoid looking incompetent, you become less willing to take risks, ask questions, or admit what you do not know.

In a role built on continuous learning, that mindset can become a significant obstacle.

What Changed My Perspective

After being in fear or flight mode for about 4 months, I finally started to get the hang of things and several lessons transformed how I viewed myself and my role.

First, I realised that nobody has complete certainty. Many of the leaders I admired were not operating with perfect knowledge. They simply had more experience making decisions under uncertainty. My stakeholder management became significantly better. I learned the art of "extending timelines", managing expectations and setting realistic timelines for project delivery. But I won't lie, I did a lot of stakeholder swerving the first few weeks. So if you were one of my stakeholders last year and happened to see me disappear into another corridor after making eye contact with you, or requested updates that were left on read, there's a good chance I was actively avoiding the update conversation. Not my finest professional moment. My bad, my bad.

Second, I learned that competence at higher levels looks different. I had assumed that success would come from knowing everything. Instead, success depended on communication, judgment, prioritization, adaptability, and the ability to learn quickly. I had to accept that I really lacked a lot of knowledge in my role and take the initiative to learn. I also started to ask a few mentors questions and tried to understand how they handled things in their space. Their tips and guidance saved me. And even though I am not 100% where I feel I should be, I have seen a significant improvement in how I work now.

Third, I came to understand that growth often feels uncomfortable. The feeling of being stretched beyond your capabilities is frequently a sign that you are developing new ones. It's just like doing leg days at the gym. Anyone who has done a good leg day knows just how bad the days after feel. But with time, you start to appreciate the wobbly legs and admire how amazing you look in the mirror.

Most importantly, I learned to separate feelings from facts.

The feeling that I did not belong was not evidence that I lacked competence. It was merely a feeling. The facts told a different story: I was delivering results, learning continuously, and earning the trust of colleagues. This has manifested in many ways. I handle bigger projects now without the crippling fear. I refuse to allow my lack of knowledge of system flows, or the flaws in technical execution to deter me from finding solutions to issues that come up. And I have mastered the art of saying no to new projects that were not scoped into my roadmap for the year without feeling like it is a sign of laziness.

A Message to Other New Professionals

Looking back, the funny thing is that there was never actually a fraud in the room. There was a young professional learning a difficult role. There was someone trying, failing, learning, adapting and growing in real time. The fraud only existed in my head.

And if you're reading this while feeling exactly the way I did a year ago, perhaps yours does too.

You may believe that everyone around you has everything figured out. They do not.

You may believe that confidence comes before competence. Often, it does not.

You may believe that feeling uncertain means you are unqualified. In many cases, it means you are growing.

Today, I still experience moments of doubt. The difference is that I no longer treat those moments as evidence that I am in the wrong room. Instead, I see them as reminders that I am continuing to learn.

The irony of imposter syndrome is that it often affects people who care deeply about doing good work. The challenge is not eliminating self-doubt entirely. The challenge is refusing to let it define your understanding of your own abilities.

Sometimes, the voice telling you that you do not belong is not exposing a truth. It is merely resisting your growth.

Back to top ↑

Loading the full page…