Job description
Fastly | Software Engineers (Senior, Staff, Principal) | REMOTE or ONSITE (multiple countries) | Full-time When you look at the headers of major websites, you’ll see us. If it has to be performant, secure, scaled worldwide, and always-on, it uses Fastly. We're a globally edge cloud platform for performance and security, emphasizing open standards, sustainable engineering, and resilience-by-design. We're hiring across compute, security, platform engineering, network and edge protocols, release engineering, network architecture, client services engineering, and more. Rather than building walled gardens, we co-founded the Bytecode Alliance, heavily upstream our work to open standards, actively author IETF drafts, and power the global infrastructure for open-source Python, Rust, Ruby, OpenStreetMap, and much more. - The Stack: Rust, C/C++, Go, Javascript, Typescript, WebAssembly (Wasm/WASI), Wasmtime, Cranelift, eBPF/XDP, QUIC, HTTP, TLS, TCP, Varnish/VCL, Linux kernel internals, distributed systems, professional services. - Apply: https://www.fastly.com/about/careers
✍️ Tailored application (cached — grounded in your resume)
58 / 100 honest fit
Daniel brings four years of C++/Python systems and test-framework engineering in safety-critical medical devices — validating real-time communication protocols, running root-cause analysis on rare field-found defects, and owning Jenkins CI/CD and AWS-backed pipelines — which maps well onto Fastly's release engineering, platform, and client services tracks where correctness and always-on behavior are hard requirements. He independently designs, deploys, and operates production Flask services on a self-hosted Linux box behind Cloudflare tunnels with gunicorn, rate limiting, cron pipelines, and self-healing watchdogs, so he has real end-to-end ownership instincts, not just test-side experience. The honest gap: no professional Rust, Go, WebAssembly, QUIC, or eBPF/kernel work, and no CDN/edge-scale distributed systems background — he'd be a strong Senior candidate on a C/C++, Python, or release-engineering-leaning team and a stretch for the Staff/Principal edge-protocol or Wasm roles.
Tailored resume highlights
- Designed and maintained scalable Python and C++ test frameworks validating real-time communication protocols and data flows across embedded and cloud components — protocol correctness under real-world conditions, not synthetic happy paths.
- Led root cause analysis of complex field-found issues, reproducing rare defects in-house and driving resolution across multiple teams — the always-on debugging discipline required when failures surface in production, not in test.
- Integrated Python automation frameworks into Jenkins CI/CD, expanding regression and integration pipelines that cut manual effort 40% and made deployments reproducible — release engineering that increases confidence in every ship.
- Built and optimized backend services, REST APIs, and validation pipelines for connected medical devices, using AWS (Lambda, S3, DynamoDB) for scalable data processing and monitoring with reliability and correctness as hard requirements.
- Independently operate a suite of production Flask/Python services on a self-hosted Linux server behind Cloudflare tunnels — gunicorn, hardened endpoints, per-IP rate limiting, automated cron data pipelines, and self-healing watchdogs serving real organic traffic.
"Why this company?" (draft — personalize before sending)
Most of my career has been in medical-device software, where an unreliable release isn't a bad quarter — it's a patient-safety issue. Fastly's resilience-by-design framing, and the fact that you're in the request path for infrastructure people can't afford to have go down, reads to me like the same engineering standard applied at a much larger scale. Concretely, I've spent years writing Python and C++ frameworks that validate real-time communication protocols, and chasing rare, cross-team, field-found defects to root cause — that's the work behind always-on. I also lean heavily on agentic tooling, and I'd rather build on open standards than a walled garden.
Cover letter (review before sending)
Dear Fastly Hiring Team,
I'm applying for your Senior Software Engineer openings. My background is safety-critical medical-device software at Medtronic, where reliability is a regulatory requirement rather than a goal. I've spent four years writing Python and C++ frameworks that validate real-time communication protocols and data flows across embedded and cloud systems, leading root cause analysis on rare field-found defects and reproducing them in-house to drive fixes across multiple teams. I've built and optimized backend services and REST APIs, implemented AWS-based processing and monitoring with Lambda, S3, and DynamoDB, and integrated automation into Jenkins CI/CD to make deployments reproducible — work that cut manual regression effort by 40%.
Outside work, I design, deploy, and operate production Flask services on a self-hosted Linux server behind Cloudflare tunnels: gunicorn, hardened endpoints, per-IP rate limiting, cron data pipelines, and self-healing watchdogs serving real traffic. I use agentic tooling heavily to move from idea to monitored production service in days.
I haven't shipped Rust or WebAssembly professionally, but C/C++, protocol debugging, and correctness-first engineering are what I do daily, and I learn fast.
Daniel Maynard
ATS keywords you have but should add
C/C++Linuxdistributed systemsrelease engineeringcommunication protocolsHTTP / RESTperformance optimizationreliability engineeringmonitoring and observabilityproduction deployment and operationsrate limitingendpoint hardening
Everything is grounded strictly in your resume — review before you submit. Nothing is auto-sent.