What makes working in the Ecosystem Team at Mambu such a unique experience?
“We enrich Mambu’s software with elements provided by our partners to create new banking solutions for all kinds of modern financial institutions. The closest analogy I can think of to make this clearer is car manufacturers. A car is not complete after the engine is built, right? It needs more parts. Similarly, you can look at Mambu as mostly an engine and in the Ecosystem team we’re busy building connectors to all the other parts - we call them partners. We do have many partners to connect to and they are some of the most exciting (fin)tech companies of our age: ClearBank, CurrencyCloud, Marqeta, nCino, (Transfer)Wise, MS Dynamics, Oracle Netsuite, you name it!
How does a typical day at Mambu look like for you?
“The typical day for an integration engineer looks very similar to the typical day of any other software engineer working in an agile environment. What I think is different is that we tackle new problems and explore new business domains more often. You may be working on card payments one day and anti money laundering compliance the next.“
Why did you choose low-code as opposed to conventional programming?
“I didn’t choose low-code, I chose to work on a certain class of problems and a certain domain. Part of my work involves integrating cloud-based products for financial institutions and it turns out that the best tool for this job, given our constraints, is a low-code platform.”
In your opinion, how does low-code add value, as opposed to conventional programming?
“Each low-code platform is different but their main advantage is that they allow you to start working immediately. Low-code platforms handle deployment, monitoring and scaling so we can focus on the business logic. Whereas low-code platforms may add restrictions to what can be built, they also solve difficult problems that developers may not even be aware of (like scalability). Personally, I love conventional programming languages and integrated development environments, but low-code allows you to get things done faster by simply reducing the number of things you need to think about.”
What advice would you give to a software engineer who is thinking of moving to low-code?
To succeed with low-code, a software engineer needs to be pragmatic and focused on the outcome, rather than the technology. Conventional software engineering skills are important, because you can’t solve problems without them, but they are less important than the ability to listen and understand.”
Which key qualifications should applicants have to join the Ecosystem Team as low-code engineers?
“A low-code engineer in our team needs to focus on solving business problems first. We expect integration engineers to be familiar with a wide range of technologies, but technology itself is just a means to an end. Low-code engineers work with high-level abstractions. The point is to build working solutions to clients’ problems as fast as possible, while ensuring they are secure and technically scalable.”
Join the Ecosystem Team and apply for a Low-code Integration Engineer position here.