Revolut has applied for a UK banking license (PRA and FCA authorisations), but they seem to be encountering difficulties and delays in having them granted.
Revolut's links to Russia are, perhaps, not helping with that.
We're a new Banking as a Service provider (think AWS for financial services) currently seeking authorisation to become a fully regulated bank, so that we can provide safeguarding and client money bank accounts to our customers. We believe that in the future, most financial innovation will happen outside banks rather than inside them, and Griffin will be the platform that all future fintechs use rather than the boring big banks.
We're looking for thoughtful people who strive to be kind in their words and actions. As product designers, we are always looking for ways to simplify complex things and we take security very seriously. As a financial institution, we believe that our customers' trust is our single most valuable asset and we will go above and beyond to earn and keep it.
Our backend stack is Clojure, FoundationDB, Kubernetes and AWS
Our frontend stack is CLJS, Reframe, Reagent, React, Stitches, Storybook, and Playroom
Our build system is Bazel, CircleCI, AWS CDK
We have an office in London but our team are distributed throughout the UK, Ireland, Germany, Sweden and Portugal.
Griffin is building an API-driven online-only UK bank. Think AWS for financial services. We're building APIs to create bank accounts, make payments, issue cards. We believe that in the future, most financial innovation will happen outside banks rather than inside them, and Griffin will be the platform that all future fintechs use rather than the boring big banks. Our tech stack: Clojure, ClojureScript+React, Kafka, Datomic, Kubernetes, AWS.
We're hiring for backend, frontend and infrastructure engineering. See the complete list of jobs at https://griffin.sh/jobs
Griffin | Senior Backend and Infrastructure Engineers | London | REMOTE (UK, Ireland, Germany, Portugal, Denmark, Netherlands)
Griffin is building an API-driven online-only UK bank. Think AWS for financial services. We're building APIs to create bank accounts, make payments, issue cards. We believe that in the future, most financial innovation will happen outside banks rather than inside them, and Griffin will be the platform that all future fintechs use rather than the boring big banks.
Our tech stack: Clojure, Kafka, Datomic, Kubernetes, AWS.
We're hiring for engineering, VPE and more. See the complete list of jobs at https://griffin.sh/jobs
Griffin | Senior Backend and Infrastructure Engineers | London | REMOTE (UK and anywhere supported by boundlesshq.com)
Griffin is building an API-driven online-only UK bank. Think AWS for financial services. We're building APIs to create bank accounts, make payments, issue cards. We believe that in the future, most financial innovation will happen outside banks rather than inside them, and Griffin will be the platform that all future fintechs use rather than the boring big banks.
Griffin is applying for a UK banking license, and we're going to be AWS for financial services. We make it 10x easier for fintechs to launch new financial products.
Our tech stack is Clojure, Datomic, Kafka, Kube, AWS.
In Engineering, we are hiring for Infrastructure, Frontend and Backend. We are also hiring for Product Manager.
Griffin is applying for a UK banking license, and we're going to be AWS for financial services. We make it 10x easier for fintechs to launch new financial products.
Our tech stack is Clojure, Datomic, Kafka, Kube, AWS.
We are hiring for frontend engineering, backend engineering, SRE and Product Manager.
In my experience, STM isn't used because it's very rare to have situations where you need STM but don't need durability. In most production situations, you need to record state changes in a DB or an event log. In that case, the source of truth is now the DB, and your in-memory values are immutable snapshots.
The other reason is that Clojure code is usually well-factored, and most clojurians have listened to Rich and simplified their programs. Not many problems require STM transactions across multiple refs. If you don't have multiple refs changing transactionally, you can use atoms instead for a performance benefit.
We are building an API-first white-label bank in the UK to be the partner bank of choice for fintechs. We want to make it easy for startups to launch prepaid cards, run brokerages, start insurance firms, and more - all over API.
We just closed a £3M seed round. We've got a team of senior banking execs and two engineers already onboard and are looking for a third engineer with strong devops experience. Our CTO was the CTO and co-founder of CircleCI.
Stack is Clojure[Script] / Kafka / Kubernetes / AWS
A complete list of all of our open roles with a bit more detail is here: https://griffin.sh/jobs
Email jobs+hn@griffin.sh to apply
