Hands-on SRE and network engineering labs built to demonstrate production-level skills targeting roles at Google, and NVIDIA.
| Folder | What it covers | Target Role |
|---|---|---|
/network-labs |
Ethernet · TCP/IP · DNS · DHCP · VLANs · LACP · BGP · Anycast · VXLAN · PXE | G2 Google Edge Networking |
/linux-internals |
Kernel, namespaces, cgroups, /proc, syscalls, boot | G1, G2, A1 |
/sre-observability |
Prometheus, Grafana, Alertmanager, SLO Engine, OTel | G1, A1, N1 |
/ci-cd-pipeline |
Jenkins + Groovy, ArgoCD, GitLab CI, Trivy | A1 Arista |
Languages: Python · Go · Js/Ts · C/C++
OS & Shell: Linux · Bash (processes, permissions, pkg mgmt)
Tooling: Git (branching, conflicts, remotes)
Infra: Kubernetes · Docker · Docker Compose · Terraform · Ansible · NGINX
Networking: Ethernet · TCP/IP · HTTP/HTTPS · DNS · DHCP · VLANs · LACP · BGP · Anycast · VXLAN · PXE
CI/CD: Jenkins · ArgoCD · GitHub Actions · GitLab CI
Cloud: AWS (EC2, EKS, VPC, IAM, S3) · GCP (GKE)
Observ.: Prometheus · Grafana · OpenTelemetry · Alerting · K6
Design: System Design · Design Patterns · Refactoring
Certs: Azure Fundamentals → AWS SAA-C03 (in progress)
| Role | Company | Location | Timeline |
|---|---|---|---|
| SDE Edge Networking | Sydney | 3–5 months | |
| SWE I — SRE (G1) | Sydney | 4–6 months | |
| SRE — Technical Infra (JD Master) | Sydney | 3–5 months | |
| Solutions Architect DevOps | NVIDIA | Sydney (Remote) | 10 months |
| Network SRE | NVIDIA | Santa Clara | 18–24 months |
| SRE HW Infrastructure | NVIDIA | Santa Clara | 18–24 months |
- Repo created + structure defined
-
/network-labs— Ethernet · TCP/IP · DNS · DHCP · VLANs · LACP · BGP · Anycast · VXLAN · PXE -
/linux-internals— kernel lab -
/sre-observability— P1 Observability Platform -
/ci-cd-pipeline— Jenkins Framework - AWS SAA-C03 exam
- First technical post in English (LinkedIn)
