Skip to main content

Sr. Backend Engineer - Kotlin

Posted 52 days ago

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Our client has built an annuity administration platform. This was a greenfield project built over the course of the past several years. There are services for Commissions/Pricing-Trading/Licensing/Annuity calculations/File Generation, and this is managed by a team of backend / frontend developers. We are looking to bring someone in to help continue the growth of the system. The Software Engineer will be responsible for a good portion of development working with backend developers, the product owner, and scrum master on breaking down requirements, etc. The back end is made up of microservice containers that are managed using Kubernetes. Kotlin is the primary programming language. Communication between services is done using Apache Kafka, and communication with the front end is done using GraphQL. The development team is 25 people, with a team of 7 backend developers and it operates in a start-up style mode. Some additional languages used includes JavaScript and Python.
Must Have: + Experience creating complex business applications using Kotlin (or Java). + Experience creating microservices using Spring Boot + Experience deploying and maintaining software in a cloud-based infrastructure + Flexibility to adapt to the technology most appropriate to complete a task Nice To Have: + Experience creating GraphQL APIs using Spring Boot + Experience implementing event messaging with Apache Kafka + Experience using Kotlin Flow / Coroutines + Familiarity with PostgreSQL + Experience using Google Cloud Platform services like Cloud Functions and Composer (Airflow) + Experience creating CI/CD pipelines (prefer using GitLab) + Packaging and deploying applications using containers with Kubernetes.
Education/Experience: 5+ years of experience as a developer, preferable in an Insurance or financial services environment. Location +Remote

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this