Senior Backend Engineer

We are looking for someone who is eager to:

• Collaborate with other developers to ship new features
• Be in charge of the overall architecture of web applications
• Ensure that we have the right tests and structure in place to make sure that we can move quickly without breaking everything
• Share their knowledge of backend development principles and best practices with the team
• Keep learning new technologies and be on the look-out for new ideas that we should try out

What we are looking for:

• A JavaScript expert
• Experience with complex backend applications in Node and modern JavaScript tooling and libraries (Feathers, NestJS)
• Experience with complex microservices backend architectures with queues, event streams, etc.
• Experience with AWS or other cloud providers
• Quality-oriented mindset: testing, code reviews, code quality, etc.
• Awareness of performance considerations
• A passion for simple, maintainable and readable code that balances pragmatism and performance

How do we build our products?

• For the frontend, we have adopted the micro-frontends architecture with single-spa for building our user interface. All SPAs we build get plugged into our shell. We also build a multitude of SDKs from Web and Mobile (iOS, Android) to CTV and Unity.
• For the backend, we have multiple services (APIs and Lambdas) written in Javascript and Typescript. We leverage PostgreSQL and DynamoDB as our main databases and manage our infrastructure with Terraform and Cloudformation. The principles of infrastructure-as-code are very important to us and we commit everything including KMS-encrypted secrets. Our most important services have 100% code coverage and we deploy our pipeline runners on GCP on a Kubernetes cluster.
• We process hundreds of millions of requests per day and are building our analytics platform on Kinesis Firehose, AWS S3, EMR jobs, and TimescaleDB to provide performant analytics for our clients. Internally we use Athena and Redash.
• We rely on a multitude of AWS/GCP services for building, deploying, serving, monitoring, and scaling our services. We use Gitlab for our code and CI/CD. To manage our issues we use Jira.

Our vision as a team:

• We are building a product and engineering team that is strongly committed to a high level of quality in our products and code. We believe that automation is the key to consistently achieving that along with velocity of development, joy and pride in what we deliver.
• At Didomi we are organized into feature teams and work with 2-week sprints. We do our best to avoid pointless meetings. The majority of the engineering team works remotely from all over the world, the only hard requirement is a 4-hour overlap with CET working hours.
• We rely on automated tests of all sorts (unit, integration, linters, you-name-it!) and continuous integration/delivery to build flexible applications that are able to evolve without breaking. We trust that it enables engineers to focus on the quality of their code and iterate fast without fears of breaking stuff. And when we break stuff, we fix it and learn from our mistakes.

Hiring process:

• An intro call with HR (15 minutes)
• A technical interview with the Engineering Manager (1h)
• A code challenge to build a simple API. This is used as the basis of discussion for the next step. You can find our challenge on https://github.com/didomi/challenges/tree/master/backend.
• A 1h30 code review session and architecture discussion with 2-3 Didomi engineers
• A set of 1:1 30-minute calls with the CTO, engineers, and a product manager


For the code review session, we may require some live coding exercises. For the architecture discussion, we will ask you to sketch an architecture (think of APIs, clients, queues, jobs, etc) and discuss options and trade-offs as we would on a normal day at Didomi.
We respect your time and existing commitments and will work with you to make sure the interview doesn’t take up too much of your time.