ISC is a well-established non-profit corporation with a mission to provide open source solutions to help sustain the infrastructure of the Internet and protect against monopoly and centralized control.  We are experts in networking and open source.  The team is spread around the globe and works 100% remotely, although we stay in close communication via chat and frequent video calls.

Kea is a popular open source DHCPv4 and v6 server for Unix/Linux used by Internet service providers and enterprises with many features, including a well-documented RESTful API. BIND 9 is a widely-deployed DNS software system that performs a critical function on the Internet. Both Kea and BIND are considered reference implementations of the Internet standards in their areas. Stork is an easy-to-use graphical management tool that enables the operator to visualize the status and manage the configuration of one or more Kea or BIND servers.

We are seeking a QA engineer to work on testing Stork and occasionally contribute to Kea's testing efforts. The tests will cover a variety of subjects. The team focuses on always writing fully automated tests that cover UI testing, system testing for the backend, performance, installation, upgrades, stability, and scalability. The engineer will occasionally work on replicating real-world problems to test our customers’ specific cases. We do use CI (Continuous Integration) extensively, for all of our projects.

Both the tested software and test environments will be open source. The code will be developed openly and made publicly available on ISC's GitLab and  GitHub.

Technologies used by QA: Python, Playwright, Scapy, Fabric, Docker, Incus, Packaging (DEB,RPM,APK), Jenkins, AWS, GitLab

The technologies used in Stork: Go, Angular, Typescript, Docker, PostgreSQL

The technologies used in Kea are: C++14, Boost, STL, MySQL, PostgreSQL

Responsibilities:

• Working with the team to design, develop, and maintain test cases, test environments, and custom testing tools.

• Monitor executions of existing automated tests, investigating failures, and reporting bugs.

• Checking documentation.

• Release engineering.

Time constraints:

• 12 months (fixed term contract)

• Availability to join in the coming weeks would be considered a strong advantage.

Required Skills

• At least 2 years of experience as a QA test automation developer, QA software test developer, or similar role

• Strong general troubleshooting skills, with the ability to assess, document and solve complex issues

• Experience with installing, maintaining, and troubleshooting Unix-like systems (Linux, BSDs)

• Practical experience with Python (or experience in similar language and a willingness and ability to learn Python)

• Ability to communicate freely in English (verbal & written)

Valuable Skills

• Knowledge of IPv4 and IPv6 networking, both from a theoretical and a practical standpoint

• Understanding of the DHCP protocol

• Practical experience with Kea, ISC DHCP, or other DHCP implementations

• Practical experience with GitLab CI and/or Jenkins

• Knowledge of virtualization technologies (Docker, Incus, VMware, VirtualBox)

• Practical experience with software packaging (DEB, RPM, APK, …)

• Practical experience with Git

• Knowledge of testing frameworks like pytest, playwright

Educational Requirements

Bachelor's Degree in a scientific or technical subject, preferably computer science or computer networking. Alternatively, sufficient professional experience in network-related fields.

Location

Although ISC's headquarters is in Newmarket, NH (USA), most of ISC's staff work from their homes.

It is important that you are able to work during the European and US East Coast business day for collaboration with the rest of the team. Most of our developers and support customers are in Europe and the US.

This position is suitable for working from home and for a person with children.

The entire DHCP/Stork QA team works from home, so you will be managing your own work environment. We communicate constantly via instant messaging and email and have regular team meetings several times a week.

We expect that staff work forty hours a week, but within parameters set by their manager (e.g., available for meetings, having some overlap with other team members), staff can choose their own working hours.

Note that occasional international travel may be required to attend company and team meetings and/or conferences (approximately 1-2 times a year).

To learn more about ISC and its critical role in the Internet community, visit https://www.isc.org.