Backend/platform engineer with 6 YOE. I started in DevOps consulting, building automation, CI/CD, and Terraform/Packer workflows for Fortune 500 clients, then moved into backend engineering on a healthcare claims/payments platform. Recent work includes owning a greenfield ingestion service from first commit to production, shipping cross-service billing integrations, resolving P1 performance issues, and supporting production services through Kubernetes, CI/CD, and observability ownership. Cut runtime by 90% on one client-sensitive workflow.
Backend/platform engineer with 6 YOE. I started in DevOps consulting, building automation, CI/CD, and Terraform/Packer workflows for Fortune 500 clients, then moved into backend engineering on a healthcare claims/payments platform. Recent work includes owning a greenfield ingestion service from first commit to production, shipping cross-service billing integrations, resolving P1 performance issues, and supporting production services through Kubernetes, CI/CD, and observability ownership. Cut runtime by 90% on one client-sensitive workflow.
I've had completely the opposite experience. I've asked for it to research things and it's just told me to "paste xyz into google". Just now I revisited a chat that's 5 days old and asked it to check again (because what I was looking for might have changed), and it said "no".
Remote: Yes, open to a few office visits per year
Willing to relocate: No
Technologies: Java, Spring, Python, Rust, Bash, Kubernetes, Terraform, RabbitMQ, PostgreSQL, AWS, Prometheus/Grafana
Résumé: Available by email
Email: [email protected]
Backend/platform engineer with 6 YOE. I started in DevOps consulting, building automation, CI/CD, and Terraform/Packer workflows for Fortune 500 clients, then moved into backend engineering on a healthcare claims/payments platform. Recent work includes owning a greenfield ingestion service from first commit to production, shipping cross-service billing integrations, resolving P1 performance issues, and supporting production services through Kubernetes, CI/CD, and observability ownership. Cut runtime by 90% on one client-sensitive workflow.