Senior Software Engineer (GO)- DNS & Network Systems

About this role

<h2>The Role</h2> <p>As a <strong>Senior Software Engineer (GO) - DNS &amp; Network Systems</strong>, you will own the architecture and delivery of Securly's DNS-over-HTTPS (DoH) resolver — a production-grade, identity-aware DNS service that enforces filtering policy at the browser and OS level for millions of students on managed Chromebooks.</p> <p>This is a critical infrastructure role at the intersection of DNS, identity, and network security. You will design and build a high-performance DoH resolver in Go that extracts device and user identity from Chrome enterprise policy URL templates and integrates with Securly's DNS policy engine and Redis infrastructure. You own the full lifecycle: architecture, implementation, TLS configuration, and production deployment on AWS.</p> <p>This role is the technical foundation of a potential simplification of Securly's SmartPAC identity architecture. Done well, it could collapse significant DNS-RPC signaling complexity (DID/cookie system, IP fusing, brokering state) that has been a source of reliability issues. The scope of that architectural decision will evolve with the POC, and you will be the engineer best positioned to inform it.<br><br></p> <div class="meta-item"><hr>Level: <strong>L5–L6_____</strong>Experience: <strong>8–15 Years_____</strong>Location: <strong>Pune, India_____</strong>Work Type: <strong>Hybrid (2 days onsite)_____</strong>Reports To: <strong>Filter Engineering Manager</strong></div> <hr> <h2>What You'll Do</h2> <ul> <li>Architect and build a production-grade DoH resolver in Go, integrated with Securly's DNS policy engine and Unbound infrastructure.</li> <li>Implement identity extraction from Chrome's DnsOverHttpsTemplatesWithIdentifiers URL template variables — mapping encrypted DNS queries to device and user identity, and evaluate the degree to which this approach can replace SmartPAC DNS-RPC signaling.</li> <li>Build an Unbound plugin with filtering business logic to process DoH queries with identity parameters from the URL template.</li> <li>Integrate with Redis infrastructure for policy lookups, identity mapping, state management, and feature flags; document failure modes and define graceful degradation behavior.</li> <li>Own TLS termination: certificate provisioning, renewal, and ensuring Chrome correctly validates the DoH endpoint certificate.</li> <li>Architect and own the CloudFormation deployment stack: NLB, Auto Scaling Groups, Route53.</li> <li>Lead the POC and production hardening phases in collaboration with Securly's Distinguished Engineer; produce a written ADR capturing tradeoffs and the go/no-go recommendation after POC.</li> <li>Mentor junior engineers on DNS fundamentals, Go patterns, and infrastructure-as-code practices.</li> <li>Document the new architecture and own knowledge transfer as the system transitions.</li> </ul> <hr> <h2>Skills &amp; Requirements</h2> <div class="skill-section must"><hr> <h3>Must-Have</h3> <ul> <li>Go (Golang) — expert-level, 5+ years production proficiency. Must be ready to build on day one.</li> <li>DNS protocol &amp; architecture — RFC 1035, recursive vs. authoritative resolution, DNSSEC, DNS wire format, Unbound as a recursive resolver.</li> <li>DNS-over-HTTPS (RFC 8484) — DoH protocol, HTTP/2 transport, application/dns-message media type, Chrome DoH client behavior.</li> <li>Redis — data structures, pipeline usage, policy lookup patterns, performance characteristics, failure mode handling.</li> <li>TLS / certificate management — termination, provisioning, renewal, client certificate validation.</li> <li>Technical communication — written ADRs, architecture diagrams, tradeoff analyses. L5 engineers leave a written record of major decisions.</li> </ul> </div> <div class="skill-section pref"><hr> <h3>Strongly Preferred</h3> <ul> <li>AWS (CloudFormation, NLB, ASG, Route53) — Securly infrastructure is fully CloudFormation-managed.</li> <li>Unbound DNS server — operational experience or module-level development.</li> <li>SmartPAC / PAC-based proxy architecture — understanding of Securly's existing DID/cookie/DNS-RPC identity system.</li> </ul> </div> <div class="skill-section nice"><hr> <h3>Nice to Have</h3> <ul> <li>C/C++ — relevant if Unbound module development requires changes at the C layer.</li> <li>Chrome enterprise policy — Google Admin Console, DnsOverHttpsMode, DnsOverHttpsTemplatesWithIdentifiers.</li> <li>K-12 EdTech / CIPA compliance / web content filtering domain experience.</li> </ul> </div> <hr> <h2>Who You Are</h2> <ul> <li>You think in protocols. DNS, TLS, HTTP/2 — you know what happens at the wire level and find that interesting, not painful.</li> <li>You are comfortable owning a project end to end: from research and POC through production hardening and deployment, without being handed a spec.</li> <li>You write Go that other senior engineers want to read. Idiomatic, tested, observable.</li> <li>You have worked on infrastructure other products depend on and understand what production ownership actually means.</li> <li>You produce written artifacts (ADRs, position papers, risk registers) to anchor ambiguous decisions rather than leaving them implicit.</li> <li>You make other engineers better. Your code reviews are substantive, your design feedback is specific.</li> </ul> <hr> <h2>What It Means to Be L5 at Securly</h2> <p>L5 at Securly is a Staff Engineer. You are the technical owner, not just an implementer.</p> <ul> <li>Drive technical direction for your initiative end-to-end: from architecture to production, with minimal oversight from your engineering manager.</li> <li>Identify and resolve ambiguity in requirements, system boundaries, and design tradeoffs without waiting for a fully-formed spec.</li> <li>Mentor L3/L4 engineers on the team: code reviews, design feedback, pairing, and raising the bar for what production-quality work looks like.</li> <li>Partner with your L6 technical lead and the Distinguished Engineer on architectural decisions, surfacing trade