Intermediate/Senior Full-Stack Software Developer - Platform

We're looking to hire a Full-Stack Software Developer with excellent technical skills and communication abilities to join our Platform squad.

You will join a team of 5 Full-Stack Developers (including a Team Lead), one Product Manager, one Quality Assurance Specialist and one Product Designer, developing and refining the technical frameworks and tools that empower all our development teams.

Technically speaking, you will work in a serverless ecosystem of microservices deployed on AWS. gaiia is all-in on Typescript, with frontend, backend and infrastructure-as-code all leveraging Typescript.

More pragmatically, as part of the Platform squad, you will have the chance to:

Optimize the availability, performance and security of our cloud infrastructure .

Build internal libraries and DevOps guidelines to help Engineering squads own and maintain their infrastructure.

Craft and optimize our public APIs to provide a stellar developer experience to our technical customers.

Design and maintain robust data pipelines and platforms used by both internal teams and external customers.

Research and develop technical solutions and best practices that improve squads' development, release and maintenance experience .

You will also:

Work on a product that is heavily used every day by loyal customers.

Collaborate with all development squads.

Join a team involved in, surprisingly, all aspects of the gaiia product.

Here are some actual projects you would have worked on recently:

Serverless → CDK migration proof of concept : You'd have paved the way for your organization's move off the Serverless Framework — taking on an end-to-end production service migration to AWS CDK with Docker container Lambdas, then distilling it into a shareable, step-by-step guide any squad could follow with no prior context. You'd have designed the whole approach around safety: running the new setup in parallel with the old one so nothing went live until you were ready, with a clean rollback path if anything went wrong. The real impact wasn't just one migrated service — it was leaving behind a proven playbook that turned a daunting migration into a repeatable, low-risk process for every team after you.