The modern landscape of Information Technology and Systems Reliability Engineering (SRE) demands more than traditional credentials; it increasingly requires demonstrable, hands-on evidence of infrastructure competency. For Braydon Tiffany, an IT operations professional pursuing a career path in Site Reliability Engineering and DevOps, bridging the gap between theoretical knowledge and practical execution became the primary motivation for undertaking the globally recognized Cloud Resume Challenge. Rather than relying on out-of-the-box, proprietary content management systems or simple managed web hosting providers like Wix or Squarespace, Tiffany opted to architect a bespoke, cloud-native infrastructure from the ground up. This initiative not only serves as a dynamic, interactive digital resume and portfolio hosted at braydontiffany.com, but it also functions as a real-world validation of advanced automation, security, and infrastructure-as-code (IaC) methodologies.
Background Context of the Cloud Resume Challenge
Created to address a persistent gap in the tech hiring market—where candidates often possess certifications without practical deployment experience—the Cloud Resume Challenge requires participants to fulfill a rigorous checklist of cloud-native engineering tasks. These typically include static website hosting, secure HTTPS routing, Domain Name System (DNS) configuration, database integration, API development, visitor counting functionality, Infrastructure as Code, and automated Continuous Integration and Continuous Deployment (CI/CD) pipelines. For professionals specializing in SRE and DevOps, the challenge offers an ideal sandbox to implement industry-standard tools under realistic operating conditions. Tiffany’s decision to build his portfolio within this framework was driven by both economic pragmatism and a desire for absolute architectural control. By leveraging cloud-native infrastructure, the project minimizes operational overhead and costs while maximizing deep, hands-on technical exposure.
Architectural Innovations and Hybrid Security Framework
Departing from standard guidelines that often keep all assets strictly within a single public cloud provider, Tiffany integrated a hybrid infrastructure model into his deployment. Notably, rather than storing sensitive authentication credentials and environment secrets directly within cloud provider secret managers, Tiffany utilized an existing HashiCorp Vault instance hosted locally within an on-premises Kubernetes cluster.
This approach provides granular control over JSON Web Token (JWT) workflows and ensures that critical AWS credentials and third-party application secrets remain securely behind an internal Virtual Private Network (VPN) rather than being exposed directly to public cloud environments. The overarching architecture was meticulously planned and mapped using Lucidchart diagrams before physical provisioning commenced, ensuring a clean separation of concerns between frontend presentation layers, serverless backend functions, and secure credential management systems.
Chronology and Implementation Methodology
The execution phase of the project followed a structured chronology, beginning with infrastructure provisioning, progressing through frontend development, and culminating in automated pipeline deployment.
[Phase 1: Architecture & IaC Design]
│
▼
[Phase 2: Hybrid Secret Integration (HashiCorp Vault)]
│
▼
[Phase 3: Frontend Customization & JavaScript Logic]
│
▼
[Phase 4: CI/CD Pipeline Configuration (GitHub Actions)]
│
▼
[Phase 5: Production Deployment & Verification]For Infrastructure as Code, Tiffany evaluated multiple modern tools, ultimately selecting Terraform governed by HashiCorp Configuration Language (HCL). Having attained the Terraform Associate certification in 2025, Tiffany sought to translate academic preparation into practical utility. Although the certification provided a strong foundational knowledge base, the hands-on demands of the challenge yielded deeper insights into complex Terraform mechanics, including the nuanced distinction between data blocks and resource blocks, the strategic utilization of local values (locals), and the scalable application of iterative loops via for_each.
The confidence gained through this project has since inspired Tiffany to expand his IaC footprint to manage secondary home-lab infrastructure, including UniFi network controllers, local HashiCorp Vault applications, and home firewall configurations.
Frontend Engineering and Serverless Integration
As an IT operations specialist whose daily responsibilities traditionally center on backend stability, network management, and server administration, front-end web development represented largely uncharted territory. Rather than building a user interface completely from scratch, Tiffany adopted a professional portfolio template from Start Bootstrap as a structural baseline. This template incorporated extensive HTML and thousands of lines of cascading style sheets (CSS).
Rather than relying purely on automated code generation, Tiffany engaged in active learning, mastering text formatting syntax and semantic class referencing to tailor the visual presentation to his professional identity.
The backend logic incorporated serverless architecture to power an interactive visitor counter. To optimize user experience and prevent artificial metric inflation caused by routine browser refreshes, Tiffany implemented client-side state management utilizing browser localStorage. This mechanism ensures that subsequent page views by the same visitor within a specific session do not repeatedly trigger the serverless API and database increment functions, achieving a cleaner and more reliable telemetry tracking system.
CI/CD Pipeline Automation and Workflow Management
Automation formed the backbone of the project’s deployment strategy. Tiffany established a dual-repository architecture on GitHub—separating the backend serverless code from the web frontend—and integrated native GitHub Actions workflows. Despite this being his first major enterprise-grade implementation of GitHub Actions, the YAML-based syntax proved intuitive.
To maintain structural integrity and prevent configuration drift or unintended production outages, the repositories were configured with segregated branching strategies. A dedicated testing branch acts as a staging environment where automated workflows execute terraform plan checks upon every code commit. Only upon successful verification and validation of the execution plan are changes merged into the primary production branch. This merge event automatically triggers a secondary workflow executing terraform apply to deploy updates live. Additionally, Tiffany incorporated manual workflow dispatches, providing administrative capability to trigger infrastructure teardown (terraform destroy) via explicit human authorization when required.
Industry Implications and Broader Impact
Projects like the Cloud Resume Challenge highlight a broader shift in technical recruitment and professional development. In an era where automated resume-filtering systems and multiple-choice certification exams can sometimes obscure a candidate’s actual engineering acumen, building and maintaining a production-grade cloud infrastructure provides undeniable proof of capability.
For industry observers and prospective employers, Tiffany’s project demonstrates key competencies highly sought after in modern DevOps and SRE roles:
- Pragmatic Security Architecture: Implementing hybrid secret management via HashiCorp Vault demonstrates an advanced understanding of zero-trust principles and credential isolation.
- Rigorous Automation: Utilizing Terraform and GitHub Actions with strict separation between test and production environments reflects mature software engineering hygiene.
- Continuous Professional Growth: The successful transition from IT operations into cloud-native infrastructure design underscores adaptability and a commitment to lifelong technical mastery.
Future Outlook and Maintenance Strategy
Rather than treating the Cloud Resume Challenge as a transient assignment completed solely for resume enhancement, Tiffany has positioned the platform as a long-term professional asset. Plans for future iterations include the integration of a native blogging engine directly into the portfolio ecosystem, as well as enhancements to the visitor counter API to capture richer, more detailed analytical telemetry. By viewing infrastructure as a living, evolving system rather than a static deliverable, Tiffany ensures that his digital portfolio will continue to reflect cutting-edge practices in cloud engineering for years to come.
