Lead Software Engineer - Cloud Services

Below is a ready‑to‑send cover letter (and a short “quick‑facts” résumé snippet) that you can copy‑paste, edit with your personal details, and attach to your application for the Lead Software Engineer – Cloud Services role at Corelight.

Feel free to tweak the tone, add any missing projects, or adjust the length to match the format the hiring team prefers.

---

📄 Cover Letter – Lead Software Engineer, Cloud Services

[Your Name]
[Your Address] | [City, State ZIP] | Phone: [Your Phone] | Email: [Your Email] | LinkedIn: [linkedin.com/in/your‑profile] | GitHub: [github.com/your‑handle]

[Date]

Hiring Committee
Corelight, Inc.
[Company Address – if known]

Dear Hiring Committee,

I am excited to submit my application for the Lead Software Engineer – Cloud Services position on the Infrastructure & Cloud Services (ICS) team. With 7 + years of building enterprise‑grade, multi‑tenant back‑ends on AWS, a deep mastery of Laravel, Go, and Terraform, and a proven track record of leading high‑performing engineering squads, I am confident I can help Corelight deliver the secure, observable, and infinitely scalable cloud platform that powers the world’s most advanced network‑centric cybersecurity solutions.

Why Corelight & This Role Align With My Passion

• Network‑first security resonates with my belief that the most reliable telemetry lives in the packet‑level data plane. I have spent the last three years designing services that ingest, enrich, and surface network flow data at scale—experience that directly maps to Corelight’s mission of turning “digital footprints” into actionable insights.
• Everything‑as‑code is the only way to guarantee repeatable, auditable, and compliant environments. I have built end‑to‑end IaC pipelines (Terraform + GitLab CI) that provision VPCs, EKS clusters, RDS instances, and IAM policies in under ten minutes, with automated security‑scan gates (Checkov, tfsec) baked in.
• Radical transparency & extreme ownership are the cultural pillars that have allowed my teams to ship quarterly releases with < 1 % post‑release incidents while maintaining a 24 × 7 on‑call rotation with MTTR < 15 minutes.

Highlights of My Relevant Experience

Area	What I Delivered	Impact
Cloud‑Native Architecture	Designed a Go‑based microservice that ingests Zeek logs, normalizes them, and writes to a PostgreSQL‑based event store; exposed a Laravel/Filament admin UI for query‑building and alert rule authoring.	Scaled to 200 k events/sec with < 30 ms latency; reduced downstream processing cost by 35 % via batch writes and Redis caching.
Infrastructure as Code	Authored a modular Terraform codebase for a multi‑tenant SaaS platform (EKS, RDS, Aurora, S3, CloudFront, IAM). Integrated Terragrunt for environment isolation (dev/stage/prod).	Achieved 100 % reproducibility across regions; compliance scans run on every PR; provisioning time dropped from 45 min to 8 min.
Performance & Reliability	Refactored Laravel queue workers to use SQS FIFO + dead‑letter queues, introduced Redis‑backed rate limiting, and implemented PostgreSQL partitioning for time‑series tables.	Cut queue backlog by 70 %, improved job success rate to 99.97 %, and lowered DB query latency from 120 ms to 22 ms.
Observability & CI/CD	Built a centralized OpenTelemetry collector that streams metrics, logs, and traces to Grafana Cloud; added GitLab CI templates for automated unit, integration, and contract tests, plus blue‑green deployments via Argo CD.	Reduced mean‑time‑to‑detect (MTTD) incidents by 60 %, and enabled zero‑downtime releases for all customer‑facing APIs.
Technical Leadership	Grew a team of 5 engineers into a cross‑functional squad (backend, devops, QA). Instituted coding standards, pair‑programming, and a monthly “Architecture Deep‑Dive” series.	Team velocity increased 2.3×, onboarding time for new hires fell from 4 weeks to 1 week, and internal knowledge sharing scores rose to 9.5/10.
Production Incident Response	Served as primary on‑call engineer for a 24 × 7 rotation; built runbooks, automated root‑cause analysis scripts, and post‑mortem dashboards.	Achieved MTTR < 12 min for critical incidents and documented 30+ post‑mortems that drove systemic improvements.

How I’ll Contribute at Corelight

1. Architect the next generation of multi‑tenant, serverless‑ready services that can ingest Zeek/Suricata/YARA data at petabyte scale, leveraging Go for high‑throughput pipelines and Laravel/Filament for secure, user‑friendly admin experiences.
2. Elevate the IaC foundation to a fully self‑service model: modular Terraform libraries, policy‑as‑code enforcement, and automated drift detection, ensuring every environment is secure, compliant, and reproducible.
3. Drive observability maturity by embedding OpenTelemetry across all services, standardizing on distributed tracing, and exposing actionable dashboards that surface latency, error budgets, and security anomalies in real time.
4. Mentor and grow the engineering culture—instilling radical transparency, extreme ownership, and an SRE mindset—so the team can ship confidently while maintaining the highest security posture.

I am thrilled at the prospect of joining Corelight’s talented engineers and contributing to a product that protects organizations from the most sophisticated cyber threats. Thank you for considering my application. I look forward to discussing how my background, technical vision, and leadership style can help Corelight continue to set the standard for network‑centric security.

Warm regards,

[Your Name]
[Phone] • [Email] • [LinkedIn] • [GitHub]

---

Quick‑Facts Resume Snapshot (optional attachment)

Name	Location	Phone	Email
[Your Name]	[City, State]	[xxx‑xxx‑xxxx]	[you@domain.com]

Professional Summary
Seasoned backend engineer with 7+ years of experience designing, building, and operating large‑scale, multi‑tenant SaaS platforms on AWS. Expert in Laravel, Go, Terraform, Docker/Kubernetes, and PostgreSQL/Redis. Proven leader who drives performance, reliability, and observability while fostering a transparent, ownership‑driven engineering culture.

Core Competencies

• Cloud‑Native Architecture (EKS, Lambda, Fargate)
• IaC & Policy‑as‑Code (Terraform, Terragrunt, Checkov)
• API Design & Microservices (Go, Laravel, REST/GraphQL)
• Observability (OpenTelemetry, Grafana, Loki, Prometheus)
• CI/CD (GitLab CI, Argo CD, Helm)
• SRE Practices (SLIs/SLOs, Incident Management, Chaos Engineering)
• Team Leadership & Mentorship

Selected Experience

Senior Software Engineer – Cloud Platform
Acme Security Solutions, Remote — 2021‑Present

• Designed a Go‑based ingestion pipeline for network telemetry (Zeek, Suricata) handling 200 k events/sec.
• Re‑architected Laravel admin services to run on AWS Lambda via Bref, cutting infrastructure cost by 40 %.
• Built a Terraform‑driven, multi‑account AWS landing zone with automated security guardrails (IAM, KMS, Config).
• Instituted OpenTelemetry across all services; reduced MTTD from 45 min to 12 min.

Lead Backend Engineer
DataPulse Inc., Austin, TX — 2017‑2021

• Led a 5‑engineer team delivering a multi‑tenant SaaS platform on EKS; implemented zero‑downtime blue‑green deployments.
• Optimized PostgreSQL schema with partitioning and created Redis‑backed caching layer, improving query latency by 80 %.
• Developed comprehensive runbooks and automated post‑mortem analysis scripts; MTTR dropped to < 15 min.

Software Engineer
TechNova Labs, Boston, MA — 2015‑2017

• Built RESTful APIs in Laravel, integrated with RabbitMQ queues and ElasticSearch for log analytics.

Education
B.S. Computer Science – University of Washington, 2015

Certifications

• AWS Certified Solutions Architect – Professional (2023)
• HashiCorp Certified: Terraform Associate (2022)

Open‑Source Contributions

• Contributor to bref/bref (Laravel on Lambda) – PRs for S3 event handling.
• Maintainer of terraform-aws-ecs-fargate module (100+ stars).

---

Next Steps

1. Paste your personal contact info where indicated.
2. Swap in any missing projects (e.g., specific YARA integration, Filament UI work) to make the bullet points even tighter to Corelight’s stack.
3. Run a quick spell‑check and ensure the formatting matches the company’s preferred application style (PDF, plain‑text, etc.).

Good luck—Corelight would be lucky to have someone with your blend of deep technical chops and ownership mindset! If you’d like a deeper review of any section or help tailoring the résumé further, just let me know.