DevOps Engineer

Ox Floors is a multi-market home-services business running a custom enterprise CRM that's replacing our legacy system - serving hundreds of daily users with millions of files. We're moving the platform onto AWS and need a hands-on DevOps engineer, based here on the Treasure Coast, to stand it up correctly and keep it running 24/7. This is a full-time, on-site position in Jensen Beach, FL. You'll work directly with ownership and our development efforts - no layers, real impact. What you'll own The application is already containerized and deployment-ready, with a Terraform starter and CI/CD scaffolding in place. Your job is to take it the rest of the way and own it. First ~90 days:

• Stand up staging and production on AWS from existing Terraform - finish the ECS/Fargate + ALB + Aurora MySQL + S3 + CloudFront setup
• Wire up secrets, TLS, and DNS; get a green GitHub Actions CI/CD pipeline (staging * prod with automated DB migrations)
• Set up monitoring, alerting, automated backups, and a tested restore
• Support a one-time data import into the new database
• Document runbooks so the platform isn't dependent on any one person
• Ongoing:
• Reliability and 24/7 uptime - incident response, scaling, cost control, patching

Do you have experience in MySQL?, * AWS: ECS/Fargate, RDS/Aurora MySQL, S3, VPC, IAM, CloudFront, Secrets Manager, ACM

• Infrastructure-as-Code: Terraform (you'll extend an existing codebase)
• CI/CD: GitHub Actions, Docker
• Databases: MySQL operations - migrations, backups, restore testing
• Observability & on-call: CloudWatch + an APM (Sentry/Datadog), alerting, real incident-response experience
• Security fundamentals: least-privilege IAM, secrets management, WAF/rate limiting
• Comfort reading Node.js / TypeScript (to debug the app*infra boundary)
• Experience with data migrations / ETL
• All infrastructure changes go through Terraform + pull requests - no undocumented console changes
• Least-privilege access, MFA, audit logging (CloudTrail), and break-glass for privileged production access
• You'll communicate clearly with a non-deeply-technical owner - explaining tradeoffs in plain English is essential, * AWS: 4 years (Required)
• MySQL: 3 years (Required)
• Back-end development: 4 years (Required)