Guaranteed Rate

1. DevOps / Infrastructure Engineering
2. Back-end Development (Clojure-based Services)
3. Infrastructure Automation

Infrastructure Modernization: KOPS to EKS Migration

The project involved migrating Clojure-based services from KOPS-managed Kubernetes clusters to Amazon EKS to improve scalability, reliability, and operational efficiency.

Key Challenges & Solutions:

Dark Deploy Strategy:

1. Deployed services to EKS without immediate traffic cutover, ensuring zero downtime.
2. Validated performance and stability before full migration.

Multi-Environment Support:

1. Development → Staging → Production rollout with Terraform-managed infrastructure.
2. Configuration via Vault for secrets and environment variables.

CI/CD Pipeline:

1. GitHub Actions automated builds, testing, and deployments.
2. OIDC-based AWS authentication for secure role assumption.
3. clojure.test suites for post-deployment validation.

Results:

✅ Zero-downtime migration to EKS

✅ Reduced operational overhead and long-term costs

✅ Improved scalability with AWS-native features

Automated Loan Data Deletion Service

A Clojure-based service was developed to orchestrate the safe removal of loan records across interconnected systems, preventing orphaned data or compliance violations

Key Components:

Dependency Validation:

1. Pre-deletion checks to ensure no broken relationships between services.

Service-Specific Logic:

1. Custom modules for different storage systems (PostgreSQL, DynamoDB, S3, Elasticsearch).

   Resilience & Observability:

   1. Retry queues for failed deletions.
   2. Audit logging for compliance tracking.

   Economic Impact:

   1. Retry queues for failed deletions.
   2. Audit logging for compliance tracking.

   Economic Impact:

   1. Saved thousands monthly by eliminating redundant cloud storage costs.

1. Clojure for backend logic (reusable across services).
2. Vault for secure credential management
3. GitHub Actions for CI/CD.

Environments & Deployment

1. Development: Initial EKS migration and internal testing.
2. Staging: Regression and integration validation.
3. Production: Rollout after staging approval.

Deployment Pipeline:

1. Build: Docker images generated from project.clj.
2. Test: Automated clojure.test suites.
3. Deploy: Terraform for infrastructure, GitHub Actions for orchestration.
4. Validate: Dark deploys and QA coordination.
5. Production: Rollout after staging approval.

Technologies & Libraries Backend (Clojure):

1. Duct (application architecture)
2. HugSQL (PostgreSQL interaction)
3. clj-http (API calls)
4. Vault-clj (secrets management)

Infrastructure:

1. Terraform (AWS provisioning)
2. KOPS → EKS Migration
3. Vault (secrets management

Testing & QA:

1. clojure.test (unit/integration tests)
2. GitHub Actions (CI/CD)
3. Observability: Logging, metrics, and retry mechanisms.

Results & Impact:

✅ Successful EKS migration with no service disruption.

✅ Automated, compliant data deletion reducing storage costs.

✅ Unified CI/CD with GitHub Actions and Terraform.

✅ Future-ready infrastructure for scaling mortgage services.