Senior DNS Engineer

Location: Plano TX/McLean VA or Richmond VA (Really want a local for this)

Title: Senior DNS Engineer (Technical test will be required)

Titles Considered: DevOps Engineer / Software Engineer / DNS Engineer / Systems Engineer (though may lean more toward sys admin responsibilities)

Common issues in resumes/candidates:

>Had the right buzzwords but lacked actual hands-on experience

Example: Candidate listed experience with BlueCat and Infoblox but was primarily a software dev and hadnt worked deeply with DNS

>Candidates need to be able to clearly explain their specific contributions especially if decisions were made by others or they joined during implementation

Interview Process

>Candidate will go through a 1-hour interview via Webex

>Includes 2 additional SMEs in the interview panel

Note

-Hands-on DNS experience required - not just API lookups

-Candidates need to be able to clearly explain their specific contributions especially if decisions were made by others or they joined during implementation

-Experience with GCP OCI or Microsoft Azure is acceptable but AWS is preferred

Vast majority is AWS

-This DNS role wont require deep cloud expertise

-X does not need to be a full-stack engineer

SME for DNS-MUST

cloud experience

deep aws experience

core dns experience

automation but not asking for a developer

Have to have hands-on experience with DNS-

HAVE TO KNOW HOW TO MANAGE DNS AND HOW IT WORKS

ADMINSITRATIVE AND HANDSON DNS PLATFORMS- CURRENTLY

Currently using Infoblock-

Also use Blucat

One of these 2 works- any and everything with one of these 2 is KEY!!!!!

If they dont have either but others and have the principles- this works!!

Bind powernsc etc are examples of others

DNS integration Activities- Team focus

DNS-MUST

DNS at Scale- MUST

Hundreds to low thousands of zones within DNS have to do this through automation with Scripting- MUST

Ask candidates this and a MUST

Either Python or Ansible for Scriptiing MUST but if not those language any OO works

AWS- MUST

Route 53- MUST

General experience- EC2 and S3 examples of general experience

Privat link direct connect examples- anything networking within AWS-MUST

If someone has done an infoblock to Bluecat migration- or a DNS Specific Migration from A to B- HUGE PLUS- RARE BUT BIG CHERRY ON TOP

Want to put in place- NSD or Bind- they want to go to authoritive DNS Servers

Have to put Authoritiaive DNS Server in place- MUST

Ask candidates if they have done this- shows they have handson experience

Know difference between primary and swocndery how zonesa work

Scripting and automation- MUST

Scripting Have to be able to script with Python- MUST

If not python it can work

additional intake note I had before we clarified again last week and dont want to erase since some info below is also helpful (2.11.26- TM)

Required:

-Strong understanding of DNS and related protocols such as DHCP as well as DNS security principles and best practices.

-Hands-on experience with AWS Route 53 in addition to commercial and/or open-source DNS platforms. Examples include Infoblox Bluecat nsd/unbound bind PowerDNS etc.

-Scripting/Automation tools such as python ansible

-Experience building infrastructure in AWS (EC2 S3 docker/kubernetes NLB AWS networking including PrivateLink)

Plus:

-No specific certifications required but AWS Solution Architect and/or AWS Advanced Networking are beneficial.