A network lead hires the technician who fixes the ticket and leaves the closet cleaner than they found it. These skills are sorted by when they start paying you back, from the basics a phone screen checks to the switch and firewall work that gets you handed the change window.
| Certificate | Best for | Effort | Worth it? |
|---|---|---|---|
| CompTIA Network+ | People moving from help desk or cabling into their first network technician role | A couple of months of evening study | Worth it early. It's the certificate entry postings name most, and the subnetting practice alone makes you sharper on tickets. |
| Cisco Certified Network Associate (CCNA) | Technicians already touching switches who want to move toward administrator or engineer | A few months of steady study plus lab time | Worth it once you've configured real gear. It's harder than Network+, and passing it tells a lead you can be trusted at the console during a change. |
| Fiber Optic Association Certified Fiber Optic Technician (CFOT) | Technicians who do a lot of physical work, splicing or campus and data center cabling | A short hands-on course, often a few days | Worth it if your role leans on cabling. Skip it if you mostly work tickets and configs, since it won't move a desk-heavy job. |
Exam versions, prices and renewal rules change, so check CompTIA, Cisco or the Fiber Optic Association directly before you book a test.
Configured switches and fixed network problems.
Configured VLANs and port security on 30 Cisco Catalyst switches across 4 floors, cut repeat Wi-Fi tickets by 40% after a site survey and channel plan, and hold CompTIA Network+.
Subnetting, DHCP and DNS. They sit under almost every ticket you'll get, and a screen will test them. Practice cable termination alongside, because hands-on skill is what a lead checks next.
It helps a lot. A couple of used managed switches off an auction site, or Cisco Packet Tracer if you'd rather not buy anything, gives you a place to break things safely.
Not before the basics, but yes eventually. You don't need to write big programs. Being able to pull a config backup from every switch or push the same change to a stack is the kind of scripting that gets noticed.
Routing and firewall work, because that's where design decisions live. Ask to sit in on change windows, read the configs before and after, and volunteer for the next branch office setup.