This article is a part of my DevNet Expert Journey blog series
- Part 1: Decision
- Part 2: Intensive Study Period - Part 1
- Part 3: Intensive Study Period - Part 2
- Part 4: 1st Exam Attempt
- Part 5: 2nd Exam Attempt
- Part 6: 3rd Exam Attempt
- Part 7: This post
Intro #
After three failed attempts, I was ready to throw in the towel. But I gave it one last shot with a different approach. Let’s talk about 4th attempt, which was completely different that the previous ones.
When Giving Up Isn’t an Option #
Looking back, the failure on my third attempt felt like a test—a test of my own resilience, to see if I would keep going or finally give up.
And I almost failed that test. I was so close to walking away.
When I began preparing, my imposter syndrome had already set a limit for me: three attempts. If I couldn’t succeed in three tries, then clearly I wasn’t good enough to call myself an Expert.
That belief led to some of the hardest moments I’ve faced on this journey. You can read my insights on those struggles here.
Now I understand my reaction better - Imposter Syndrome is a real thing.
Under the post, I received comments of encouragement from others and I can’t emphasize enough how much that support meant to me. Knowing people believed in me made it easier not to give up.
I’d given up on too many things in the past: running, building a business and more. I was tired of getting stuck in that cycle of starting something new, working on it for a few weeks, then abandoning it when things got hard.
This time, I wanted to push through, to finally break out of that pattern. I put enormous effort and I didn’t want to waste that because I didn’t feel like doing it anymore.
But there were other pressures too. I was about to start renovating my apartment which is - obviously - not a cheap project. Every time I paid over $2000 to register for the next attempt, I felt like I was moving away from my goals instead of closer. Tasty sandwich I got during the exam couldn’t compensate for it.
In the middle of preparations for my fourth attempt, I went to Croatia with friends. I wanted to fully enjoy it, I’ve tried to put the bad thoughts aside and recover a bit. The break really did help me unwind and stop thinking about my studies and the pressure - at least for a little while.
I would like If I said that vacation completely recharged my batteries. Even though I enjoyed every moment, I couldn’t fully forget about the unfinished work waiting for me. It was like a rock in your shoe — something you can live with, but that quietly drives you crazy all the same.
The Changes Are Getting Closer #
This time, I decided to take a longer break between attempts. In the past, one month was usually enough to refine my strategy and fill any knowledge gaps. But with the release of DevNet Expert v1.1, I didn’t have that option. There was no way to take my fourth attempt under the old version, so I had to adapt and prepare for the new topics, including:
- GraphQL
- Open API Specifications
- AppDynamics
- ThousandEyes
This time I spent 2 months preparing. The downside? I had to make sure my hard-earned knowledge didn’t just evaporate. I was stressed about the possibility of forgetting things that were well known for me before.
Uncovering the Real Problem #
Even though I rested well on vacation, one thought kept spinning in my mind.
What am I doing wrong? Why do I keep struggling with Module 1?
I talked with Andreas, and we came to a surprising conclusion: this wasn’t about a lack of knowledge. There had to be something else holding me back.
On my last score report, Section 1.0 had a significantly lower percentage than any other section. And it wasn’t just a one-time issue — the same pattern showed up on my second and third attempts.
Clearly, I was missing something, so I reached out to Stuart Clark for advice.
We had a great conversation with Stuart not only limited to DevNet Expert. He mentioned that he knew someone who had faced a similar issue and offered to connect me with him.
Within the next few days I got a chat with Marcel. He immediately understood what I was going through as he tackled the same problem himself.
Marcel followed the same rule I did - he sought advice from others when he hit roadblocks. Through that process, he discovered a solution that ultimately helped him pass the exam. He shared a few key tips which helped me approach the exam differently:
- Be open-minded. Don’t assume anything. If you know the answer immediately, probably your answer is WRONG. Approach each question with a clean slate, using the supporting material as a reference.
- Don’t overthink your answers. Be careful with finding a solution - it’s easy to start bringing your OWN OPINION to the scenario which is NOT desirable. Marcel helped me realize I was bringing my opinion unconciously. I was overthinking when trying to find a good answer which resulted in choosing the answer that seemed to be the best FOR ME.
- Pay attention to key words. Words like “must”, “have to”, and “would be nice” determine the strength of constraints in the question Understanding these nuances is critical to finding the right answer.
- They want you to find the answer THEY THINK it’s correct using supporting material, not the answer YOU THINK is the best, based on your experience.
That discussion made me realize I needed to change not just my strategy, but also my mindset. Overthinking and relying on my personal judgment were holding me back, and these tips gave me the clarity I needed to break through those mental barriers.
I attended the techtorial at Cisco Live and watched a few videos by Kurt Claes explaining what to expect during the lab exam. Looking back, I realized they had already covered all of these points - but I hadn’t paid enough attention to those details at that point of time.
Apparently, I needed someone to break it down for me again. Thanks to Marcel for these eye-openers!
Interview with Insider Advocates #
August was a time to slowing down, discovering that there are other interesting things that DevNet Expert :-)
Together with Glenda Low from Cisco Insider Advocates, we worked on interview about my journey. This was very interesting project and I’m happy I’ve been recognized. Very interesting innitiative the break the routine of seeing DevNet Expert concepts over and over again, day by day.
A Step Forward, but Not the Destination #
Three weeks before the exam, I decided to challenge myself by taking the DEVOPS 300-910 exam with no preparation.
I wanted to assess where I stood with my knowledge, and to my surprise, I passed. It was a huge moment for me, especially considering that just seven months earlier at Cisco Live, I had failed the same exam.
Back then, I barely knew or practiced most of the topics. This time, the result was proof of how much progress I had made.
Combining the DEVCOR exam I passed in December 2023 with the DEVOPS exam earned me the DevNet Professional certification.
Certifications at the Professional level are a significant achievement, but for me, it still wasn’t enough. My ultimate goal was the DevNet Expert certification.
Looking back now, I realize that I didn’t truly celebrate earning my DevNet Professional certification.
Sure, there was a moment of satisfaction, but it wasn’t the same as fully appreciating what I accomplished.
Instead - I should’ve appreciated that I had opportunity to take the exam. I should’ve been proud at that point of time because of the knowledge I’ve gathered up to that point.
Team spirit and the Power of Encouragement #
I’m extremely fortunate to work with incredible people who supported me every step of the way.
I’ll always remember a meeting with my Network Technology team where we discussed some challenging topics. As we wrapped up, A. turned to me and said:
Mateusz, go get that number, I want to see your digits!
Those words popped into my mind when I was about to enter the restricted lab zone in Brussels. They gave me a surge of confidence and helped me push past the nerves.
The support didn’t stop there. The number of comments I received on my LinkedIn posts throughout this journey was incredible.
Moments like these remind me that success is never a solo endeavor. It’s the encouragement of others that pushes us forward, even when the finish line feels far away.
Let it All Go, Neo #
I remember a conversation I had with Andreas when we tried to pinpoint what went wrong before my 3rd attempt. From his perspective, I had all the knowledge I needed to pass.
He reassured me of that and encouraged me to stay even more open-minded. He emphasized focusing on the supporting materials - not just to use them, but to extract more from them than I thought was possible.
After the call I was thinking about it and this reminded me about fantastic scene from Matrix movie - one of my favourites - where Morpheus said:
You need to let it all go, Neo. Fear, doubt, and disbelief. Free your mind.
Then Morpheus jumps effortlessly between the buildings.
I tried to “free my mind” heading into my 3rd attempt. Unfortunately, I ended up like Neo in that scene - I fell down.
But that lesson stuck with me. I kept trying to free my mind, to let it all go. I believe that mindset and attitude are the key components in this game. You have to convince yourself that you can make it. You have to believe it.
The Same Trip, but a Different Challenge #
As always, I woke up at 3:30 AM. My flight was scheduled for 6:20 AM, which meant an early arrival at Warsaw airport. The travel was exhausting and far less exciting than my first trip to Brussels.
I went through the same terminal, rode the same bus to Zaventem Airport, and stayed in the same hotel.
The only thing that changed was the exam itself, because of the new exam revision.
At first, the differences weren’t something I wanted to see after studying the same topics for nearly 10 months. But as I thought about it, I realized this revision brought a sense of freshness.
It broke the routine of doing the same things over and over again. I felt like this could be the moment to break the vicious circle of my previous unsuccessful attempts. It was like a spark of belief that this time could be different.
Final Checks #
I wanted to have a perfect experience without unforseen surprises.
After checking in at the hotel, I decided to double-check the road to Cisco’s office. Was there any new construction that might slow me down? Thankfully, everything was clear.
I snapped a quick photo with Devvie hoping it would be my last time here - at least for the DevNet Expert exam. I brought Devvie along for the trip and snapped a quick photo, silently hoping it would be my last one here—at least for the DevNet Expert exam.
When I looked at the photo, I noticed how tired I appeared. It wasn’t just the result of an early flight - it was the weight of this 10-month journey.
For the first time, I seriously started wondering if it might be time to stop in case of another failure. My health, both physical and mental, was beginning to feel the strain.
I decided to postpone those considerations. I had no benefits from being anxious even more.
After confirming that everything was in order, I returned to the hotel.
In the Lab Again #
This morning marked my fourth time standing next to the big “CISCO” logo, waiting for the doors to open a few minutes before 8 AM.
Two colleagues were standing with me - one waiting for his second CCIE Security attempt and the other for his first CCIE Enterprise Infrastructure attempt.
The procedures were exactly the same as before:
Here’s the coffee machine, here you can find the toilets, and right here - there’s the exam room.
I remembered it all by heart.
After signing the document, I found myself sitting in front of the workstation. A few moments later, the title “DevNet Expert Lab Exam v1.1” appeared on the monitor.
“This will be my last attempt” - I told myself. I believed in my capabilities and tried to calm my nerves with two minutes of meditation before clicking “START”. It helped until the first question appeared. :grinning_face:
The changes in Module 1 were immediately noticeable. The exam was still difficult, demanding sharp attention to details.
I kept repeating to myself: they are asking me to provide the solution that they think is correct. I did everything I could hold my personal opinion back this time. Instead, I leaned on the advices I’d received from Andreas, Marcel, Stuart, and others.
When I completed Module 1, I still wasn’t sure how well I had done. But this wasn’t the time to think about that. I took a quick break, had a chocolate bar and a glass of water, and then dove into Module 2.
As I skimmed the task list for Module 2, I was surprised to see a task involving a tool I hadn’t used in a long time.
For a moment, I felt paralyzed. I tried to solve it but eventually decided to skip it. “I’ll come back to it at the end” I told myself.
The same thing happened with a few other tasks — they required more effort than I initially expected and I wasn’t able to solve them immediately.
I refused to let myself get stuck. I pushed forward, knowing I could return to them later with fresh eyes.
When Things Go Wrong #
A few minutes into Module 2, I noticed that the RDP session wasn’t working properly. I tried to troubleshoot the issue on my own, but after a moment, I remembered that I could ask the proctor for help.
I explained the problem, and he quickly moved me to another workstation. Thankfully, this adjustment made a huge difference — the connection quality was significantly better, and I could finally focus on the tasks ahead.
Don’t be afraid to ask for help - Proctor is there for you.
Skipping, Solving, Staying Calm #
I went back to the tasks, constantly reminding myself of one key strategy: skip tasks when you’re stuck. I think this is one of the most important tips I could give to any candidate.
I worked through all the tasks and reached the final stretch: 5 tasks left, 2 hours remaining.
Even though I didn’t solve every task on the first attempt I started to believe that this time, I might actually succeed.
With 2 hours left, I could slow down and approach each task more pricisely. I worked through the remaining list, step by step, until I was left with just two the most demanding ones.
These two tasks were exceptionally difficult for me, but I managed to solve the first one.
I only did it because I knew how to navigate the documentation. This has been one of the most important skills I’ve learned during this journey - how to use the documentation effectively. I’ve learned to navigate it slowly, paying close attention to what I’m reading rather than just skimming for keywords. (Sometimes skimming works, but not always.)
When I finally got that task working, I felt a wave of relief and pride. It was an incredible feeling to solve a challenge I thought was unsolvable, especially since it involved a topic I hadn’t practiced much recently.
The last task remained unfinished. From the few tasks I didn’t fully complete, only one remained incomplete by the end. It was a great score overall, and I couldn’t complain. I felt accomplished of what I had achieved.
Calm Comes with Experience #
After the exam, I felt exactly the same way I did after my previous attempt. Module 1 left me with doubts as always, but on the other hand, I was certain I had passed Module 2.
This time, though, I wasn’t bothered by the results. Constantly stressing about them wouldn’t change the outcome, so it made no sense to waste time or energy overthinking it.
I’ve found the perfect definition for this state of mind, the one where you’re no longer bothered - it’s called experience.
Experience teaches you to let go of what you can’t control, and to focus your energy where it matters most.
The Joy of Success #
I woke up feeling refreshed. The first thing I did was pick up my phone and open my email app. No news yet.
After breakfast, I headed to Zaventem Airport. A few minutes later, my bus to Charleroi arrived. I was just about to board when I got the notification:
“Your Cisco Expert Level Certification exam score report is now available.”
PLEASE! GIMME THAT NUMBER!
I logged into the CCIE portal, and then it hit me - a huge wave of emotion as I saw something completely different from my previous attempts. Instead of the familiar score breakdown by blueprint domain, I saw my number - #20240068.
I was in shock. I’d done it.
I immediately messaged my family, friends, and Jacek, my manager. He spread the news even further, and soon my MS Teams chat was filled with messages of congratulations from my peers.
I tried to savor the moment, to let the excitement last as long as possible. I felt immense pride - not just in passing, but in not giving up.
Later, I posted the news on LinkedIn. The comments exploded, filled with congratulations and celebrations from all corners of my network. At that moment, it wasn’t just my success - it was a shared moment of joy with everyone who had supported me along the way.
Summary #
Even though I’ve achieved what I dreamt of, this isn’t the end of my DevNet Expert journey. Over the next weeks, I’ll be sharing more about the path that got me here and, of course, what we all love: the numbers! I’ll dive into statistics like the hours I spent preparing and the number of books I read.
I also want to reflect on whether all the effort was truly worth it and share my thoughts on the value of the DevNet Expert certification today.
Let’s stay in touch, and thank you so much for being part of this story!
Open up the limit
Past the point of no return
Reached the top
But still you gotta learn how to keep it