Senior Software Engineer (GO)- DNS & Network Systems
Summary
Senior Software Engineer (GO) - DNS & Network Systems at Securly will own the architecture and delivery of a production-grade DNS-over-HTTPS (DoH) resolver in Go, integrating with DNS policy engine and Redis infrastructure, and handling full lifecycle from architecture to AWS deployment.
The Role
As a Senior Software Engineer (GO) - DNS & Network Systems, 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.
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.
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.
Level: L5–L6_____Experience: 8–15 Years_____Location: Pune, India_____Work Type: Hybrid (2 days onsite)_____Reports To: Filter Engineering Manager
What You'll Do
- Architect and build a production-grade DoH resolver in Go, integrated with Securly's DNS policy engine and Unbound infrastructure.
- 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.
- Build an Unbound plugin with filtering business logic to process DoH queries with identity parameters from the URL template.
- Integrate with Redis infrastructure for policy lookups, identity mapping, state management, and feature flags; document failure modes and define graceful degradation behavior.
- Own TLS termination: certificate provisioning, renewal, and ensuring Chrome correctly validates the DoH endpoint certificate.
- Architect and own the CloudFormation deployment stack: NLB, Auto Scaling Groups, Route53.
- 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.
- Mentor junior engineers on DNS fundamentals, Go patterns, and infrastructure-as-code practices.
- Document the new architecture and own knowledge transfer as the system transitions.
Skills & Requirements
Must-Have
- Go (Golang) — expert-level, 5+ years production proficiency. Must be ready to build on day one.
- DNS protocol & architecture — RFC 1035, recursive vs. authoritative resolution, DNSSEC, DNS wire format, Unbound as a recursive resolver.
- DNS-over-HTTPS (RFC 8484) — DoH protocol, HTTP/2 transport, application/dns-message media type, Chrome DoH client behavior.
- Redis — data structures, pipeline usage, policy lookup patterns, performance characteristics, failure mode handling.
- TLS / certificate management — termination, provisioning, renewal, client certificate validation.
- Technical communication — written ADRs, architecture diagrams, tradeoff analyses. L5 engineers leave a written record of major decisions.
Strongly Preferred
- AWS (CloudFormation, NLB, ASG, Route53) — Securly infrastructure is fully CloudFormation-managed.
- Unbound DNS server — operational experience or module-level development.
- SmartPAC / PAC-based proxy architecture — understanding of Securly's existing DID/cookie/DNS-RPC identity system.
Nice to Have
- C/C++ — relevant if Unbound module development requires changes at the C layer.
- Chrome enterprise policy — Google Admin Console, DnsOverHttpsMode, DnsOverHttpsTemplatesWithIdentifiers.
- K-12 EdTech / CIPA compliance / web content filtering domain experience.
Who You Are
- You think in protocols. DNS, TLS, HTTP/2 — you know what happens at the wire level and find that interesting, not painful.
- You are comfortable owning a project end to end: from research and POC through production hardening and deployment, without being handed a spec.
- You write Go that other senior engineers want to read. Idiomatic, tested, observable.
- You have worked on infrastructure other products depend on and understand what production ownership actually means.
- You produce written artifacts (ADRs, position papers, risk registers) to anchor ambiguous decisions rather than leaving them implicit.
- You make other engineers better. Your code reviews are substantive, your design feedback is specific.
What It Means to Be L5 at Securly
L5 at Securly is a Staff Engineer. You are the technical owner, not just an implementer.
- Drive technical direction for your initiative end-to-end: from architecture to production, with minimal oversight from your engineering manager.
- Identify and resolve ambiguity in requirements, system boundaries, and design tradeoffs without waiting for a fully-formed spec.
- Mentor L3/L4 engineers on the team: code reviews, design feedback, pairing, and raising the bar for what production-quality work looks like.
- Partner with your L6 technical lead and the Distinguished Engineer on architectural decisions, surfacing tradeoffs clearly rather than deferring them upward.
- Contribute to cross-team engineering standards: you are expected to influence practices beyond your immediate squad.
- Translate technical context into clear written artifacts that non-engineers (PM, Support, Leadership) can act on.
- Participate in on-call rotation and own the full incident lifecycle for your system: detection, diagnosis, resolution, and retrospective.
About Securly
Securly processes over 1.1 billion requests per day and 54 TB of data daily, protecting more than 20 million students across 20,000+ schools globally. Since pioneering the first cloud-based web filter for K-12 in 2013, Securly has built one of the most trusted, high-scale platforms for student safety, wellness, and engagement. By turning data into meaningful, actionable intelligence, Securly enables schools to identify risk earlier, reduce harmful incidents, and strengthen student support.
We are proud to be consistently recognized as a Top Place to Work, named a Top 40 Most Used EdTech platform, and included on the GSV 150 list as one of the most transformational growth companies in digital learning and workforce skills.
Benefits
- Comprehensive Health Insurance (employee, parents, spouse, children)
- Accidental & Term Life Insurance
- Learning & Development reimbursement
- Paid Time Off
- Public Holidays (10+ per year)
- Retirement Benefits (EPF & gratuity)
- Parental Leave (as per statutory norms)
Equal Opportunity Employer
Securly is an Equal Opportunity Employer committed to inclusion, fairness, and respect. We welcome applicants from all backgrounds, identities, and experiences. #LI-REMOTE #LI-DO1
As published by greenhouse
First Name, Last Name, Email, Phone, Resume/CV, Cover Letter, Location
- Preferred First Name optional
- What is your expected/desired compensation range (required) ?
- What is your current notice period?
- Are you currently serving your notice period? choose one
- What is the earliest date you would be available to start?
- Do you currently reside in Pune, Maharashtra area? choose one
- If you are not currently living in Pune, are you willing to relocate to Pune? choose one · optional
- optional: Please provide your LinkedIn URL or links to GitHub, technical blogs, project repositories, or other work that demonstrates your experience. optional
- This role is a Pune hybrid role — 2 days per week in our Senapati Bapat Road office. Are you comfortable with that arrangement?" choose one
- How many years of professional (post university) software engineering experience do you have? choose one
- How many years have you written production Go (Golang) code — meaning Go deployed to live systems handling real traffic, not tutorials or side projects? choose one
- Which best describes your experience with DNS at the protocol level? choose one
- Have you specifically implemented or worked with DNS-over-HTTPS (DoH)? choose one
- Describe your Redis experience in production systems: choose one
- Have you personally owned TLS certificate management in production — including provisioning, renewal, and ensuring client validation? choose one
- Are you a current employee of Securly? choose one
- Were you referred to this role by a Securly employee? choose one
- If you were referred to this role by a Securly employee please list their name and how you know this person?
- Describe a production system you architected and owned end to end. What was the hardest technical decision you made, what were the options you considered, and what written artifact did you produce to anchor the decision and get team alignment? (150-200 words)**** ____Note: We are testing both architectural depth and L5-level technical communication. Any domain qualifies — infrastructure, networking, security, or backend systems. Generic answers will not advance your application.____ written answer