DevOps Engineer

Company Description Wellness360 is a software-as-a-service (SaaS) wellness technology platform that provides comprehensive population health management solutions to Healthcare Providers, Payers, Benefits Brokers, Wellness Companies, and Employers. The platform focuses on behavior change to transform the healthcare system into a proactive and preventive healthcare model. Wellness360 offers personalized strategies and active support to improve health and reduce chronic disease risks, with industry-leading solutions aiming for better employee health and reduced healthcare costs.

Role Description This is a full-time onsite role for a DevOps Engineer at Wellness360. The role involves tasks such as software development, continuous integration, integration, Kubernetes deployment, and Linux system management.

WE ONLY CONSIDER APPLICATIONS WHO COMPLETE THE FOLLOWING CASE STUDY by July 12th 2026. Please Submit your case study to eng-jobs@wellness360.co CASE STUDY Automating Infrastructure Provisioning for a Spring Boot Application with Docker, ECR, ECS, and GitHub Actions Scenario: You're tasked with automating the infrastructure provisioning for a simple Spring Boot application (https://github.com/nreddywellness360/taskmaster ), leveraging Docker, ECR, and ECS for containerization and deployment. You'll utilize GitHub Actions to orchestrate the entire CI/CD pipeline. Specifics: Technology Stack:

• Cloud Provider: AWS
• Virtualization: AWS ECS (Elastic Container Service)
• Containerization: Docker, AWS ECR (Elastic Container Registry)
• Infrastructure-as-Code: Terraform (or AWS CloudFormation)
• CI/CD: GitHub Actions
• Monitoring: Prometheus and Grafana (or cloud provider's monitoring service)
• Application: A simple Spring Boot web application (e.g., a REST API)
• Tasks: 1. Infrastructure Provisioning:
• Use Terraform to create the necessary AWS resources:
• VPC with subnets
• Security Groups
• ECS Cluster
• ECS Task Definitions
• ECS Services
• Load Balancer (if applicable)
• ECR Repository: Create an ECR repository to store Docker images.
• Configure networking rules (e.g., allow SSH, HTTP/HTTPS traffic) 2. Containerization:
• Create a Dockerfile to build and package the Spring Boot application.
• Use a suitable base image (e.g., OpenJDK)
• Include application dependencies and configurations 3. Deployment:
• Build and Push to ECR: Build the Docker image and push it to the ECR repository within the GitHub Actions workflow.
• Deploy to ECS: Deploy the ECS Task Definition and Service, referencing the image in the ECR repository. 4. CI/CD Pipeline (GitHub Actions):
• Build Stage:
• Trigger the pipeline on code commits.
• Build the Docker image.
• Run unit and integration tests (e.g., using JUnit, Mockito).
• Push the Docker image to the ECR repository.
• Deploy Stage:
• Update the ECS Task Definition to use the latest image from ECR.
• Update the ECS Service to deploy the updated Task Definition.
• Testing Stage:
• Perform automated tests against the deployed application (e.g., using tools like Postman or a dedicated testing framework). 5. Monitoring and Logging:
• Set up Prometheus to collect metrics from the application, ECS, and other AWS services.
• Use Grafana to visualize the collected metrics (e.g., CPU usage, memory consumption, request latency, JVM metrics, ECS service health).
• Implement basic logging for the Spring Boot application (e.g., to CloudWatch Logs). Deliverables:
• Terraform code for infrastructure provisioning.
• Dockerfile for the Spring Boot application.
• ECS Task Definition and Service definitions.
• GitHub Actions workflow files.
• Grafana dashboards for monitoring .
• Documentation explaining the setup and how to use the system. Evaluation Criteria:
• Functionality: Does the entire system work as expected? Can the Spring Boot application be deployed and accessed successfully through ECS?
• Efficiency: How efficient is the deployment process? How quickly can changes be deployed to production?
• Scalability: Can the ECS service be easily scaled up or down to meet changing demands?
• Maintainability: How easy is it to maintain and update the infrastructure, application, and ECS deployments?
• Security: How well is the ECR repository and ECS cluster secured (e.g., IAM roles, security groups)?
• Best Practices: Adherence to DevOps best practices (e.g., infrastructure-as-code, immutable infrastructure, continuous integration, continuous delivery, security best practices).
• Documentation: Quality and completeness of the documentation.
• Presentation: Clear and concise presentation of the project to the team. • 1+ years of work experience with Amazon Web Services (AWS) • 1+ years of work experience with DevOps