Fortinet Network Engineer

Job Description

Job Description

Fortinet Network Engineer
Houston, TX Area | Hybrid (4 Days Onsite / 1 Day Remote) | Contract-to-Hire

iSphere is looking for a Fortinet Network Engineer who likes building things better than simply keeping them running. If your idea of fun is replacing yesterday's workaround with tomorrow's solution, this one is worth a look.

You'll join a small, highly technical infrastructure team where your ideas won't disappear into a committee meeting. This isn't a role where you're babysitting legacy hardware waiting for something to break. They're looking for someone who enjoys designing, implementing, and improving enterprise network and security environments while helping shape what's next.

One important note: Candidates must live in the Houston area. This is a hybrid position with four days a week onsite in downtown Houston.

What they're really looking for:

• 5+ years of enterprise network engineering experience
• Strong hands-on experience with the Fortinet Security Fabric
• Experience implementing and supporting FortiGate, FortiManager, and FortiAnalyzer in production environments
• Strong networking knowledge including firewalls, routing, switching, and wireless infrastructure
• Experience troubleshooting complex network and security issues from root cause through resolution
• Familiarity with Cisco networking and mixed Cisco/Fortinet environments
• Strong understanding of enterprise network security best practices
• Excellent communication and problem-solving skills

Bonus points if you have experience with:

• Ansible
• Terraform
• Network automation and Infrastructure as Code (IaC)

You'll spend your time designing and implementing Fortinet solutions, supporting enterprise networking, improving performance, documenting environments, and partnering with a small team that's always looking for smarter ways to do things.

During the interview, expect to talk about projects you've actually built. They're looking for someone who can explain the Fortinet environments they've designed, the problems they've solved, and the decisions they made along the way. If your experience is mostly clicking through firewall rules someone else created, this probably isn't the right fit.

The right person enjoys solving tough technical problems, isn't afraid to challenge "the way we've always done it," and takes ownership from design through implementation.

If you're the kind of engineer who sees a network diagram and immediately starts thinking of three ways to improve it, we'd like to hear from you.