Join our mission to simplify payments!

At Vipps MobilePay we’re on a mission to make life easier for people and businesses through smart payments and identification solutions. From helping people easily split a bill to making it easy for merchants to accept Vipps anywhere to paying your bills, we are working to simplify your day.

As a developer in Payment Postprocessing you will be part of the team responsible for Vipps MobilePay payments, risk controls, reconciliation, pricing calculation, reporting and settlements to our over 400 000 merchants as well as accounting for internal stakeholders.

The area is rapidly changing to use the best means of processing payments for different customer and merchant needs, while being compliant with current regulations. You will own your work in production, measure their impact and handle any related issues. You will communicate with stakeholders to deliver high quality solutions and take an active part in improving our current tooling, standards and processes.

As we are a vital part of the digital payments infrastructure we are regulated and kept to a very high standard by the financial authorities (and ourselves). We strive to use the best tools for the job, which currently has us working mainly in Go and SQL which run on containers in Azure. Traditionally we are a backend heavy team, but we also dip our feet into frontend code now and then, developing both merchant- and internal facing systems directly improving the experience for our merchants. The frontend development is mainly done in React, but other frameworks are also utilized.

Your academic background in tech, engineering, or a similar field is key. So are your English skills, both written and spoken, to enable seamless communication across teams and locations. Some years of experience with our tech stack or equivalent is a big positive. You are interested in developing data intensive applications, modeling data structures, and can reason about tradeoff between different approaches. Most of all we appreciate team members who voice their thoughts, are curious, and proactively seek solutions rather than waiting for help to arrive. So, if you're passionate about building secure, top-tier software and flourish in a collaborative, data-driven setting, we can't wait to hear from you!

Who are we looking for?

• You have extensive experience in or a willingness to learn about relational databases and data intensive applications.
• You are passionate and pragmatic about your work. You want to write great code and you want to ship. There’s a balance to maintain there and you do your best to find the right balance.
• You enjoy working in a team. You write code with your teammates in mind and you know that you can learn from everyone around you.
• You bring ideas to the table, listen to others’ ideas and you love to improve these ideas
• You believe in what you’re doing here and you take ownership of what you work on. When issues come up, you dive right in and get us back on track. When we celebrate successes, you are humble about your achievements.

What We Value:

• Data-driven design: We as a team have a close relation to our databases and data stored in the databases. More so than what might be the industries standards nowadays. Above clean-code, we value clean data and model our databases accordingly and craftfully. We don't use ORMs in our team, nor are we hiding the database behind abstractions.
• Testing: We believe automated integration tests are required for delivering trustworthy financial products.
• Shipping: We want to constantly be delivering code.
• Collaboration: Our best work is done as a team. We succeed (and fail) together.
• Experimentation: We believe in the merits of hypothesis-driven experimentation, continuous deployment and validated learning.

Do you want to join us in making the world's most loved wallet, replacing hassle with dazzle? Do you say yes to #oneteam, #keepitsimple and #noworries? Let's talk! Applying for this position is as easy as using our products - just click on the button below and answer a couple of questions.