Job Description

We are looking for an experienced system engineer to develop, enhance and maintain No-IP's core infrastructure. This role has both system administration and development aspects. We are a network service provider focused on dynamic DNS, and are extending into other service offerings.

Responsibilities

• Develop a solid understanding of No-IP products, infrastructure, architecture, and business model.
• Maintain compute infrastructure, which includes virtualization systems, network gear, a hierarchy of DNS servers, web servers and ancillary systems, such as databases, mail servers, logging and analytics systems, caches and other components of a distributed compute stack.
• Write and maintain core parts of our infrastructure. Many of the network services we provide were written in-house.
• Utilize existing and create new automation. We use a variety of tools to ease the administration of our systems.
• Assist with moving legacy systems to modern infrastructure.

Must Have

• Linux system administration: We are primarily an Ubuntu-based shop, although we are always open to exploring other systems. The specific skills are: experience with the command line, shell scripting, Git and SSH.
• Configuration management: In addition to "hand administration", we need experience with configuration management tools. Currently we have a mix of Salt, Terraform, Kubernetes, and home-grown tools.
• Hybrid-cloud infrastructure: we use AWS as well as bare-metal with Linux virtualization. Experience with virtualized compute, storage, and networking is ideal. We have other VM providers for applications that are less centralized, so flexibility in learning different vendors' systems is essential.
• Virtualization tools: Or primary virtualization technology is Proxmox, and we use Docker and Docker Compose extensively. Kubernetes will be a major part of future efforts. Experience with a few of these (or willingness to dig in and learn them) is crucial.
• Software development: The infrastructure software we've written is in Rust, Go, PHP, Python, Perl, UNIX shell and C, so a background in system-oriented languages is important.
• Communication: Must be able and inclined to share ideas, bring up problems, discuss solutions and technological directions. No-IP has a fairly large and diverse infrastructure, so knowledge sharing is a critical part of what we do.