Cassidy Marble
Team Lead, Backstage subject-matter expert, and DevOps engineer on the Finastra platform workstream, delivered as a consultant through BlankFactor (now Globant). This portfolio groups work into completed, ongoing, and planned items, and notes plainly where a specific role contribution was not documented.
Backstage refresh
Extraction of plugins into their own repositories, refreshed architecture, migration planning, entity model, own-domain go-live, and continuous legacy-parity porting.
Open project pageGitOps delivery platform
The DevOps deep dive: Flux image automation, workload-identity secrets, an in-cluster private npm registry, self-hosted CI runners, and a first deploy that ran hands-off end to end.
Open deep diveDebugging case files
Five production diagnosis stories — a phantom resource deleter caught with a probe matrix, an impossible login root-caused from vendored source, and more. Symptom, investigation, root cause, fix, lesson.
Open case filesProject timeline
The whole arc, dated: from a 106k-line monolith and a blank plan on August 8 to a production GitOps deployment on August 20 — including the days things broke, and what did and didn't compress.
Open the timelineGrafana integration
Read-only dashboards, alerts, catalog ingestion, API design, and stack scaffolding.
Open project pagePlatform integrations
Jira, TechDocs, Nexus, templates, scorecards, and landing-zone alignment.
Open project pageTechnical leadership
Planning, team enablement, code review, stakeholder preparation, and delivery reporting.
Open project pageBackstage deep dive
Technical walkthrough of the migration itself: architecture, phases, decisions, quality metrics, and the cutover plan.
Open deep diveSkills honed for this role
- Backstage plugin architecture and new backend system: directly tied to ongoing plugin separation, published releases, and backend/scaffolder migration.
- TypeScript boundary validation and test strategy: directly tied to reviewed work on unsafe casts, runtime validation, Sonar findings, and 80% coverage rules.
- Grafana API and performance design: directly tied to dashboard reconstruction, API limits, caching, selectors, variables, and stack provisioning.
- Kubernetes, Flux, and GitOps delivery: directly tied to the live refreshed environment — Flux image automation, three-Kustomization blast-radius design, and a zero-manual-step deploy loop proven in production.
- Cloud identity and secrets engineering: directly tied to the self-provisioned Key Vault, workload-identity federation for External Secrets Operator, and a no-plaintext-secrets-anywhere posture across git, CI, and manifests.
- CI/CD platform operations: directly tied to self-hosted actions-runner-controller scale sets across nine repositories, a custom runner image built in-cluster with kaniko, Docker-in-Docker image builds, and a Kubernetes admission policy defending the runners in a multi-tenant cluster.
- Production diagnosis under deadline: directly tied to the five documented case files — version-probe matrices, source-level root-cause analysis inside shipped container images, and empirical elimination over guesswork.
- GitHub App security and organization-scoped access: directly tied to API-rate reduction, read:org permissions, OAuth setup, and organization-based authorization.
- Terraform and landing-zone template design: directly tied to the Grafana stack template, product templates, and network-owned higher-level modules.
- Release engineering and artifact distribution: directly tied to changeset-driven semantic versioning, a private npm registry as the sole immutable artifact channel (with the full release history backfilled and integrity-verified), CI-enforced version-bump checks, and GitHub App tokens for cross-repository automation.
- Technical program leadership: directly tied to work breakdown, Jira hygiene, team assignment, decision logs, operational blockers, and stakeholder demos.
- Executive communication: directly tied to CTO preparation and explaining Backstage as a unified entry point with business value.