Backend Engineer (Rust) Help us build a greener bank

🦊 About Green-Got
At Green-Got, we believe in transforming the financial landscape as a necessary step to create a sustainable future. We provide modern payment and investment solutions that positively impact the planet. Our team of nearly 50 is dedicated to making finance accessible and engaging for everyone.

You'll join our engineering team and work on the business side of the platform. Customer-facing features, back-office tools, and the workflows that make the bank actually run day-to-day. You'll pair with another engineer and collaborate closely with product, ops, risk, and customer support teams.

We're looking for a backend engineer who thinks like a product engineer: someone who cares about the user problem behind the ticket, pushes back on specs that don't make sense, and ships things that actually solve the problem rather than just match the description.

You should also be comfortable working with AI tools. Whether you love it or are skeptical, AI is part of how we build now.

You don't need to come from a banking background, but you should be curious enough to learn the domain. Banking is messy, the specs are dense, and the regulations matter. The system does not work as the bankers specify it; it works as the developers understand it.

• →Build and maintain our backend. From new customer-facing features to the back-office tools our ops, risk and support teams use daily.
• →Take a problem from "product wants this" to "it's running in production": discuss the scope, design the data model, write the code, write the tests, ship it, watch it, fix what breaks.
• →Sit with product managers and front-end devs early enough to actually shape what gets built, not just implement it.
• →Work with the security and risk teams when what you're building touches money, customer data, or regulatory requirements (which is often).
• →Review your teammates' code seriously. Catch bugs, push back on shortcuts, and learn from what they're doing better than you.
• →When something is slow, broken, or annoying to work with, fix it instead of routing around it.
• →Define your own scope. Your perimeter is what you take over. Autonomy and initiative are non-negotiable. We don't have the time to tell you what to do, and we don't want to.

• You write Rust comfortably and have shipped it in production. You're not still fighting the borrow checker.
• You're solid with PostgreSQL: you can design a schema, write a query that doesn't melt under load, and reason about transactions and indexes.
• You're comfortable in AWS and with a normal git/GitHub workflow (PRs, reviews, rebases, the usual).
• You can write clear English — in code reviews, in docs, in async messages. We don't all share a timezone, so writing things down well matters.
• You sweat the details. In banking, the bug you didn't think mattered is the one that costs us money.

• You've used Temporal, or built something similar yourself.
• You've practiced DDD, CQRS, Event Sourcing, or hexagonal architecture on a real project (not just read the book).
• You know payment systems — cards, SEPA, ledgers, ISO 8583, ISO 20022, Mastercard processing. Any of these is a plus.