Getting your CWNE isn't about passing tests. There is no test.

The hard part is proving you are who you say you are, to a room of sitting CWNEs who will read everything you submitted.

I submitted my CWNE application in December 2023. I'd been working toward it for three years across three companies. This is what the process looks like from inside out.

Before you can open the application, you need five active certifications: CWNA, CWSP, CWAP, CWDP, and CWISA.

I spread mine across three employers over several years. The timing matters because these certs expire on a three-year cycle. If your CWSP lapses while you're finishing CWAP, you'll need to get CWSP again. This link is the CWNP resource for renewals.

First, I got my CWNA through the ACE training program at CDW and had over a year gap before tackling CWSP in early 2022. I then got CWDP, CWISA, and CWAP by late 2023. If possible, take the hardest test first. In my case, I took CWAP mid-way after having troubleshooting under by belt at Cisco, but still barely passed; afterwards, I left CWDP and CWISA for last.

You also need one external certification outside the CWNP ecosystem entirely. A Cisco cert counts. A CompTIA cert counts. The point is to show diversification in networking broadly, not just 802.11 alone. I had a CCNP active at the time of applying.

The application requires a minimum of three years of verifiable, documented, full-time professional experience in enterprise Wi-Fi. "Documented" means more than a resumé line.

The board wants to understand what you actually did on specific deployments. The design decisions you made, the security architecture you chose and why, the technical problem that nearly broke the project and how you resolved it.

A career that spans multiple employers can work in your favor here. Pulling from different environments means your can convey greater skill range across roles. In my case, I pulled design experience from the VAR space and troubleshooting from my time at Cisco support.

This is where most applications fall apart.

Each essay is capped at 1,000 words, and the strong convention among CWNEs is to write one from each of the three professional domains: Design, Security, and Analysis. That maps directly to CWDP, CWSP, and CWAP. One from each tells the board your depth is real across all three tracks, not concentrated in whichever exam you found easiest.

The goal isn't to document what you did. It's to show that you understood why you made the choices you made: what tradeoffs were in play, what you'd do differently, what the vendor documentation didn't cover. The board has read hundreds of these. They can tell immediately whether someone is narrating their resumé or actually thinking through the engineering. Keep your writing concise, objective, and focused on the problem. Do not do any storytelling in these essays.

Plagiarism is taken seriously. CWNP defines it as any authorship claim over material that isn't yours, and a confirmed violation can bar you from reapplying. Write from your own experience. Cite anything you reference. The board is grading whether the thinking is yours.

You need to have published something wireless-related that contributes to the community. Something publicly accessible.

Blog posts work. Public talks work. Some folks have even started podcasts such as WiFi Ninjas. The spirit of the requirement is that you've contributed something back to the Wi-Fi community. I used a wireless design training that was recorded for our support team that had no proprietary or heavily vendor-specific references. Actually, the blogging thing didn’t come along until long after getting CWNE.

Don’t wait too long to start. This is the one requirement you genuinely cannot manufacture at the last minute. The blog requirement alone takes multiple months of consecutive posts.

Three people need to endorse you, preferable colleagues who can speak to your Wi-Fi work specifically. If you know CWNEs in your professional network, this is when that relationship matters. Personally, I would get one current or past manager to vouch for you; they’ll have most visibility on your actual project and competencies as an engineer.

The biggest failure risk is treating the essays like incident reports and not a curated problem statement and resolution. The board wants your reasoning, not your task log.

The second is letting the cert windows lapse. If you're working through the certs, track your expiration dates actively. A lapsed cert while you're finishing the sequence means you're starting over partially. CWNE already takes long enough, don’t make it longer.

The third is underestimating the publication requirement. Start something public now, even if you're years away from applying. A blog, a talk, a documented tool or resource. Anything that exists on the internet with a URL and can be verified by the board works.

There are only a few hundred CWNEs globally. When a credential requires three years of documented experience, five active certs, peer-reviewed essays, and a board decision instead of a multiple-choice exam, there won’t be that many out there. If you've been working in enterprise Wi-Fi for a few years and you have any interest, start heading in that direction today.

That’s all folks,

Eva

If want a reference for what's worth knowing at each stage of your Wi-Fi career, my Wi-Fi Engineer Career Cheat Sheet is linked here.