Springboot developer to create backend and setup AWS infrastructure for webapp

Not worth discussing if you haven't read the job description. ## Project Brief — You will be responsible for solely creating the infrastructure, API and deployment pipelines for the backend. Using Springboot through Java or Kotlin, with the infrastructure and supporting services hosted in AWS. The project we are working on is a web app in the bank/real estate sector. We have already built out the full frontend using NextJS. We have built an initial POC backend using AWS Amplify, we can share the code of that with you - Data structure, cognito setup, S3 configuration, graphQL API. Ideally this new backend will be replacing that API but anything that can be re-used or studied to guide your efforts is appreciated. It would be considered a nice to have if you had experience with React, NextJS and Tailwind and could also update the frontend to use this new API. We will be working in Sprints, with daily standups and weekly planning/refinement. Our PM will work alongside you to help scope out the project and create the necessary Epics/Stories and Milestones. A rough idea of the user groups/data model can be seen in this doc: [login to view URL] This doc was initially used to provide context for the team building the Amplify POC. — The type of engineer we’re looking for: We are looking for a motivated and enthusiastic Engineer excited about laying a firm foundation that can be built upon. You care about scalability, monitoring/latency, and most importantly you seek to understand the product and the business challenge we’re working together to satisfy. Communication is critical for this project, as you will be describing technical requirements, updating stakeholders, engaging with other team members. Fluency in written and spoken english is a strong requirement. A clear history of being the primary contributor and delivering similar projects is required. This can be through github links, etoro history or similar means of proof. - A strong backend in Java/Kotlin with a focus on Springboot, - A history of writing production standard tested code - AWS experience - API Gateway, S3, RDB/Dynamo, EC2, EBS, Cognito etc - Infrastructure as code e.g ansible/serverless/cloudformations/terraform - Experience setting up CD pipelines to deliver into AWS containers — A technical design doc or similar detailed description of your suggested approach will be the first deliverable. This helps us agree on an approach, and verify we haven’t missed anything. A rough structure could be like: [login to view URL] A brief outline of the API deliverables: * Authentication * Authorization * Role based access control * Data Models, Controllers, Services * Business logic with accompanying tests * Scheduled tasks * Emails/messaging * Infrastructure * Database * AWS deployments * Cognito (open to direction on tooling) * Document storage