Scaling the product, helping with new feature development, the chrome extension or a temporary project. We’re looking for a Senior Backend Engineer who doesn’t mind iteration and can tackle the complex world of secure digital communication for high-stakes industries including government agencies, top-tier law firms, and healthcare organizations.

At Zivver, we're leading the charge in building the future of secure communications with a platform trusted by over 6000 organizations across various industries to securely share sensitive information. And we're not stopping there - we're scaling up and we need a Senior Scala Engineer to join our team to take on the challenge of delivering quality, user-friendly solutions that meet the needs of our 11 million users.

In this role, you'll play a vital part in pushing the boundaries of our product and pushing for innovation. You will be responsible for developing high-quality software solutions using Scala and related technologies, and will share your knowledge and expertise within the team, taking the initiative in driving new ways of working. It's not just about ticking off tickets - you'll have the opportunity to make an impact on many levels and help your teammates grow.

Hot takes:

– Your vision is an inspiration for your team members;

– Speed and quality are what you’re about. You know your craft and you get-it-done;

– Not all ideas end up being great, but we need creative thinkers to come up with ideas for great solutions.

What you will do:

– Lead the design and implementation of projects within the team;

– Design and drive technical solutions;

– Promote the application of industry best practices for performance and security within the team, ensuring the Zivver Backend platform is operating at optimal levels;

– Develop new features and maintain the performance of the Zivver Backend platform, including troubleshooting and resolving any issues that may arise;

– Review code of colleagues and suggest improvements, promoting a culture of continuous improvement and excellence;

– Apply the best security practices and identify areas of possible vulnerabilities, contributing to the adoption of a security mindset across the team;

– Suggest improvements in automation and identify edge cases that are not covered, ensuring the platform is robust and reliable;

– Participate in the technical design of product features, collaborating with other teams to deliver high-quality solutions;

– Improve the development experience by enhancing development tools and processes, making the development process more efficient and streamline;

– Review production bugs, errors and alerts, working with other engineers to fix them in a timely manner, and ensuring the stability and scalability of the Zivver platform;

– Successfully triage issues and solve bugs, contributing to the increased stability, scalability and usability of the Zivver platform;

– Contribute to the Zivver Backend Guild and share your experience with others, fostering a culture of knowledge sharing and collaboration.

Benefits:

– An exciting, fast-growing, energetic environment;

– International diverse team with over 30 nationalities – and yes, we offer Dutch classes too!

– We value a healthy life-work balance. We mean it when we say: Take a vacation! We offer unlimited holidays for you to take care of yourself whenever you need it;

– HQ in Amsterdam where you’re able to work a few days a week & full home office support to make sure you’re all set;

– Working from Bali, the US or Spain? Any place, anywhere: we fully support temporary working from X;

– At least €1.000,- per year on personal development budget;

– All the relocation benefits you need for a fresh start;

– Don’t worry about tomorrow: we’ve got you covered with a pension plan.

Expertise you’ll bring:

– 5+ years of experience in software development, with at least 3 years of experience using Scala;

– Experience with microservices and distributed systems;

– Strong knowledge of software development best practices (e.g. testing, code review, continuous integration);

– Experience with SQL (we use Postgres) would be a plus;

– Familiar with ELK stack;

– Familiar with Scala Type-level programming (for example cats/cats effect libs);

– Preferred formal education, and even cooler, a degree in a Computer Science / Software Engineering field;

– Experience with DevOps, including knowledge of containerization, continuous integration/deployment, and monitoring;

– Strategic thinking and ability to balance the need for innovation with the requirement for a reliable and mature product;

– Experience with AWS, including knowledge of EC2, S3, and other core services;

– Understanding of cloud infrastructure best practices will be a plus.

If you’re still reading and excited about this role, we welcome your application even if you think you don’t meet all the requirements. We understand that no candidate is perfect, and would love to hear your story. Keen to learn a bit more? Keep reading...

A day at Zivver Today, you're finishing up a story that updates the way email message bodies are stored in Amazon S3. You need to complete the unit tests, and will create a merge request soon. After that, you ping a few developers for review. While running the pipeline, you notice that a test is failing for which you have some doubts so you connect with the Backend guild on Slack and together you fix the issue in the blink of an eye. You schedule a meeting with the team later this week to discuss the lessons learned and how we can avoid future issues.

Then it is time to take on a key role in the current sprint, leading the development of a highly-complex and technical project. You will need to be able to navigate difficult puzzles and be comfortable reaching out to the team for support, while also sharing your own knowledge and best practices. After a well deserved lunch break, you meet up with the Zivver Backend Guild. During this weekly video call, you share experiences and focus on how to approve our backend from a technical point of view. After a rather productive day so far, you revise your plan for the rest of the day. You help out a colleague reviewing a bunch of internal docs and share your knowledge and best practices. After a quick meeting with the team in the afternoon, you check out your schedule for tomorrow. Great! No meetings until 11. You decide to come in late tomorrow, as you want to go for a run in the morning and know it’s okay to take some back as long as you attend any required meetings and keep your team up-to-date on what you're doing.