Full-Stack Enhancements for Popular Platform
Budget: $40 – $65 USD
Our platform already supports 90,000 active users, and the next growth phase calls for fresh features across the website, both mobile apps, and the underlying Spring-based AWS backend. You will be pairing with a senior engineer, taking well-defined user stories from ticket to production and touching every layer as needed—from a responsive HTML/JavaScript tweak to an Aurora-optimised query or an in-app purchase flow.
Core stack you’ll encounter
• Website: HTML, JavaScript, CSS
• iOS: Objective-C, Swift
• Android: Java
• Backend: Spring Framework, Java, AWS (S3, SES, MSK, CloudFront, EC2 autoscaling, Aurora)
• Payments: Stripe, Authorize.net
• Source & CI/CD: GitHub
Typical workflow
1. Pull the ticket, discuss approach with the senior engineer.
2. Code the change, write/extend tests, open a GitHub PR.
3. Verify in staging, roll out via our existing CI/CD pipeline.
Acceptance criteria for every story
• Clean, well-commented code merged to the main branch.
• Unit and integration tests passing in CI.
• No regression on mobile or web performance budgets.
Scheduling is flexible; steady progress is more important than strict hours. When replying, focus on relevant experience you have with any part of the stack above and highlight projects where you shipped production code at comparable scale.
Core stack you’ll encounter
• Website: HTML, JavaScript, CSS
• iOS: Objective-C, Swift
• Android: Java
• Backend: Spring Framework, Java, AWS (S3, SES, MSK, CloudFront, EC2 autoscaling, Aurora)
• Payments: Stripe, Authorize.net
• Source & CI/CD: GitHub
Typical workflow
1. Pull the ticket, discuss approach with the senior engineer.
2. Code the change, write/extend tests, open a GitHub PR.
3. Verify in staging, roll out via our existing CI/CD pipeline.
Acceptance criteria for every story
• Clean, well-commented code merged to the main branch.
• Unit and integration tests passing in CI.
• No regression on mobile or web performance budgets.
Scheduling is flexible; steady progress is more important than strict hours. When replying, focus on relevant experience you have with any part of the stack above and highlight projects where you shipped production code at comparable scale.