Why This Role Exists
Our team ships two production-bound applications — a Lease Accounting Tool (Flask + MongoDB, ASC 842/GASB 87/96) and a Book Close Validation Agent (FastAPI + React + MongoDB) — that are functionally complete but missing dedicated DevOps ownership. Both currently rely on developers manually running test suites and deployments. We need someone to own CI/CD pipelines, containerized deployment, and production hardening so releases stop depending on manual steps.
What You'll Own
- Stand up CI pipelines (GitHub Actions or equivalent) that auto-run the existing test suites (currently 278 automated tests across Unit/Integration/Exception/Edge categories) on every PR — this is our single most overdue gap on the Lease Accounting Tool.
- Harden and manage Docker Compose-based deployments across dev, QA, and production environments, including zero-downtime rebuilds (docker compose up -d --build) and setting-specific secrets management.
- Implement shared, production-grade rate-limit storage (Redis-backed)
to replace in-memory rate limiting once multiple workers/instances go live.
- Own secret rotation, TLS termination, and JWT/session secret strength enforcement across environments — currently flagged as follow-up hardening items in our Production Readiness Report.
- Set up centralized monitoring/alerting (uptime, error rates, MongoDB health) across both applications, building on existing /healthz endpoints.
- Maintain the dev to QA to main/prod branch promotion workflow, matching our documented Git branching strategy (feature branches into dev into QA into main).
- Own database backup/restore procedures and rollback runbooks for MongoDB-backed services.
- Partner with developers to keep the CI drift-gate in sync (e.g. SOP-rule script mirroring between backend and frontend) so what's displayed always matches what actually runs.
Must-Have Skills
- Docker & Docker Compose in production (multi-service, multi-environment)
- CI/CD pipeline design (GitHub A