At Bluecode we’re building the first European mobile payment scheme that enables cashless payments combined with value-added services. It's a solution from and for Europe; accepted at 20’000 locations, from large and small department stores and supermarket chains to famous events like Oktoberfest.
Why join us?
We are going live with our services in another continent this year (TBA; production tests nearing completion).
Our leadership team has successfully built and sold their companies before, both in Silicon Valley, as well as in Germany.
We are driving the European Mobile Payment Systems Association (EMPSA) initiative, and wrote the spec and prototype for interop between the EMPSA members.
Engineering at Bluecode
We basically do Scrumban, meaning we're largely pull based, but have bi-weekly retrospectives to ensure the feedback loop is triggered. We're also using a Team Topologies model with Value Stream Aligned Teams, Platform Teams, and some Enabling Teams (ok, more like people given our size, eg. we have a Head of Application Security).
building an always on infrastructure with a lot of financial institutions as partners bring interesting challenges when it comes to availability and velocity of delivery. How can we keep moving fast without jeopardizing the platform stability. How can we enable ever more payment scenarios in our platform without introducing accidental complexity. How can we keep the team size small and instead leverage the existing workforce better?
Our payment platform exists as multiple production instances (Europe is live, an African country launch is imminent). Due to that (and also because of production-like integration environments) we don't have the luxury of having manual infrastructure, it has to be highly automated.
We are currently in the process of becoming a more data driven company, to consume both our own data (eg. DevOps metrics like Lead Time for Changes, Change Failure Rate, etc.), but also our application data (Funnel optimization, more A/B testing, performance measures, golden service signals). Do better support objective we're now building out a more full fledged data warehouse with data pipeline and visualization support to enable data democracy. And we're already eyeing other opportunities that this would enable (tool consolidation with spend reduction, ML models to predict user behavior, etc.)
We're building out PR based environments so that we can test changes across the entire system before even merging to master, improving the quality of master without the need to manually switch environments around.
We're building out a stateful property based test suite, to verify the external behavior of our system. This will enable us to do large scale refactorings without fear, and allow us to crank up iteration speed and overall velocity.
Working at Bluecode
We don't have hard rules about hours, except that you're expected to overlap with Europe/Zurich for 5h for most of the days. Apart from that, we have people spread around the globe.
Work from Home
The Engineering organization is fully remote.
We have a yearly conference allowance.
We have a 5 week vacation policy (2 week minimum) with a 10 day rollover.
Interested in this company?
Skip straight to final-round interviews by applying through Triplebyte.