Griffin Bank | Engineering | REMOTE (UK) Company: We are Griffin Bank. We are a fully authorized, API-first bank; we bank fintechs and startups. We built our own core banking system from scratch.
Experience: We are hiring across broadly across engineering. The things we work on include onboarding and KYC, payments rails, accounting, billing and reporting. We are hiring backend and frontend engineers. We are currently about 80 people, with 30 of them in engineering.
The Clojure version is not AOT'd, so it's measuring startup + compiler time. When properly compiled it should be comparable to the Java implementation.
It's fairly strictly enforced. The reason is that in many jurisdictions, you can accidentally create employment tax liability by working remotely for too long in the country.
Griffin Bank | Engineering | REMOTE (UK)
Company: We are Griffin Bank. We are a fully authorized, API-first bank; we bank fintechs and startups. We built our own core banking system from scratch.
Experience: We are hiring across broadly across engineering. The things we work on include onboarding and KYC, payments rails, accounting, billing and reporting. We are hiring backend and frontend engineers. We are currently about 80 people, with 30 of them in engineering.
Company: We are Griffin Bank. We are a fully authorized, API-first bank; we bank fintechs and startups. We built our own core banking system from scratch.
Experience: We are hiring across broadly across engineering. The things we work on include onboarding and KYC, payments rails, accounting, billing and reporting. We are hiring backend, frontend and design system engineers. We are currently about 80 people, with 30 of them in engineering.
We could in theory bank other banks, but that's not our focus. Our current customers are mostly regulated non-bank financial institutions, E-Money and Client money. As an American analogy, think Square Cash, Venmo, Paypal.
Longer term our aspiration is to also be the business bank for technology companies e.g. Apple or AirBnb or Uber. Currently Goldman is a big player in that space.
It is a tall order, but but it's doable. The most important thing is to reduce the surface area of your application. Our business logic is almost entirely pure. The 'procs' have no side effects, except for things that happen on the other side of a clojure protocol (java interface). That means all side effects can be stubbed out during tests.
Our "user" code has no access to threading libraries. Threading happens in "kernel" code.
What you've described looks more like Amazon's strategy. It's probably more correct to say Google & Facebook are copying Amazon rather than BH.
The core of BH has ~20 employees. Warren Buffet always calls out his subsidiary CEOs for doing a great job, because BH couldn't exist in its current format if he had to manage day-to-day operations in any subsidiary.
The steps in Buffet's algorithm are the same, but the emphasis is different. Amazon builds moats and cashflow, while BH buys stable companies that already produce cashflow. BH doesn't need moats, only profit. Amazon, Google, FB need both moats and profit.
Buffet's algorithm looks more like:
- (1) Identify stable, profitable businesses that WB understands
- (2) if they're a good bargain, and it moves the needle on BH stock, buy
- (3) goto (1)
Tech: Clojure, FoundationDB, Bazel, CLJS, Svelte
https://jobs.ashbyhq.com/griffin/c8eaae48-e84f-4dae-8c34-099...