AWS DevOps Engineer Needed – Jenkins CI/CD Pipeline for Frontend, Backend & Mobile App (Dev/Staging/Prod)

We are looking for an experienced AWS DevOps Engineer to design and implement a professional CI/CD and deployment architecture for our SaaS application.
Our application consists of separate Frontend, Backend/API, and Mobile App codebases. We need a clean deployment workflow across Development, Staging, Production, and Operations (Ops) environments.
The goal is to establish a reliable, secure, and maintainable AWS infrastructure with Jenkins-based automated CI/CD pipelines following production-grade DevOps practices.
Application Components
Frontend
- Web application
- Separate Git repository
- Independent build and deployment pipeline
Backend
- API/backend application
- Separate Git repository
- Independent build and deployment pipeline
- Background workers/services may also need deployment
Mobile App
- iOS and Android application
- Separate repository/pipeline
- Automated build process
- Environment-specific configuration for Dev, Staging, and Production
Required Environments
We need a clear separation between:
Development (DEV)
↓
Staging (STG)
↓
Production (PROD)

Operations / OPS
• Jenkins
• Monitoring
• Logging
• Deployment tools
• Shared DevOps services

The environments must be isolated appropriately so that development changes cannot accidentally affect Production.
Jenkins CI/CD Requirements
We need Jenkins pipelines for each application component.
Git Repository
↓
Jenkins
↓
Install Dependencies
↓
Lint / Test
↓
Build
↓
Security / Quality Checks
↓
Docker Image Build
↓
Container Registry
↓
Deploy DEV
↓
Deploy STG
↓
Approval
↓
Deploy PROD

Frontend and backend deployments must remain independent. For example, a backend deployment should not require rebuilding or deploying the frontend unless necessary.
We also want proper handling for:
- Feature development
- Production bug fixes/hotfixes
- Rollbacks
- Deployment approvals
- Environment variables
- Secrets
- Git branches/tags
- Docker image versioning
- Build history
- Deployment history
AWS Infrastructure
The freelancer should review our requirements and recommend the appropriate AWS architecture rather than simply installing Jenkins.
Potential AWS services may include:
- EC2 / ECS as appropriate
- ECR
- Application Load Balancer
- Route 53
- ACM/SSL
- S3
- CloudFront
- RDS or other database services where applicable
- ElastiCache/Redis where applicable
- CloudWatch
- IAM
- Secrets Manager / Parameter Store
- VPC, subnets and security groups
- AWS Backup
We want the architecture designed so it can scale as the application grows.
Mobile CI/CD
The mobile application also needs a professional pipeline for iOS and Android.
Expected workflow:
Mobile Repository
↓
CI Pipeline
↓
DEV Build
↓
STG / QA Build
↓
Production Build
↓
App Store / Google Play release process

The freelancer should advise on the best solution for mobile builds, especially considering the macOS/Xcode requirement for iOS.
OPS Environment
We specifically want an OPS environment separated from application environments.
It may contain:
OPS
├── Jenkins
├── Monitoring
├── Centralized Logging
├── Deployment tooling
├── SonarQube / code-quality tooling
└── Other DevOps services

DEV
├── Frontend
├── Backend
├── Workers
└── Supporting services

STG
├── Frontend
├── Backend
├── Workers
└── Supporting services

PROD
├── Frontend
├── Backend
├── Workers
└── Supporting services

The freelancer should recommend whether separate AWS accounts, VPCs, or another isolation strategy is appropriate.
Security Requirements
Security is important. The implementation should include:
- Least-privilege IAM
- No AWS credentials hard-coded in repositories
- Secure Jenkins credentials management
- Proper secrets management
- Private networking where appropriate
- Restricted database/Redis access
- HTTPS everywhere
- Jenkins access restrictions
- Production deployment permissions
- Auditability of deployments
- Backup and recovery strategy
Deliverables
The selected freelancer will be expected to deliver:
1. AWS architecture design/documentation
2. DEV, STG, PROD and OPS architecture
3. Jenkins installation/configuration
4. Frontend Jenkins pipeline
5. Backend Jenkins pipeline
6. Worker/service pipelines where required
7. Mobile application CI/CD design and implementation
8. Docker configuration
9. AWS ECR integration
10. Environment/secrets configuration
11. Production approval workflow
12. Rollback strategy
13. Monitoring and logging configuration
14. Backup/recovery configuration
15. Security/IAM configuration
16. Infrastructure and deployment documentation
17. Knowledge-transfer session with our development team
All scripts, Jenkinsfiles, Dockerfiles, infrastructure configuration and documentation produced during the project must be provided to us.
Freelancer Requirements
We are looking for someone with strong hands-on experience with AWS, Jenkins, Docker, CI/CD, production SaaS infrastructure, Linux and Git/GitHub.
Experience with Next.js/React frontend, Node.js/NestJS backend, Redis, PostgreSQL/MongoDB, mobile CI/CD, AWS ECR/ECS/EC2, CloudFront, CloudWatch and Secrets Manager would be highly preferred.
Please do not apply if your experience is primarily basic server administration or simple Jenkins installation. We need someone who has designed and maintained multi-environment production CI/CD architecture.
When Applying
Please include:
- Examples of similar AWS/Jenkins architectures you have implemented
- Your recommended approach for DEV/STG/PROD/OPS separation
- Whether you recommend EC2, ECS, or another deployment model and why
- Your approach to zero/minimal-downtime production deployment
- Your rollback strategy
- Your approach to secrets and AWS IAM
- How you would handle iOS/Android CI/CD
- Estimated completion time
- Fixed-price estimate