jln

Monzo | Backend, Data, iOS, Android & Web Engineers | London, UK | VISA, REMOTE, INTERNS https://monzo.com/

At Monzo we aim to build the best current account in the world. We are always keen to hear from capable, creative engineers who want to help us accomplish that goal.

Our backend engineering team have a variety of different backgrounds: we have several non-graduates; only a couple of us studied Computer Science; one of the team has a degree in Marketing; some of us have worked in huge companies; some have only ever worked in startups; others are former consultants. As long as you enjoy learning new things, we’d love to talk to you.

We work in project-based sprints, working directly with everyone across the company, from customer support to regulation, product to financial crime, and we run regular knowledge-sharing sessions so you’ll learn heaps about everything from how banks work to effective communication.

We encourage an open and transparent working environment. You can get involved in any aspect of the business you are interested in and, following Stripe’s example, all emails in the company are visible in an email archive. We regularly run hackathons in which people build things on our third party API and we contribute to open source software as much as possible. We’ve also made our product roadmap public and give sneak peeks of features in our community forum.

If you’re unsure about applying or have any questions about the role or team, please don’t hesitate to email our CTO Jonas ([email protected]) directly :) We're very open about what we do in general, so our blog is a good place to learn more about what we do.

* Backend stack: Go, Cassandra, Kubernetes, Kafka, Linkerd/Finagle

* iOS stack: Swift 3, Realm

* Android stack: Kotlin, Java, Realm

Learn more on our careers page: https://monzo.com/careers/

Monzo | Backend, Data, iOS, Android & Web Engineers | London, UK | VISA, REMOTE, INTERNS https://monzo.com/

At Monzo we aim to build the best current account in the world. We are always keen to hear from capable, creative engineers who want to help us accomplish that goal.

Our backend engineering team have a variety of different backgrounds: we have several non-graduates; only a couple of us studied Computer Science; one of the team has a degree in Marketing; some of us have worked in huge companies; some have only ever worked in startups; others are former consultants. As long as you enjoy learning new things, we’d love to talk to you.

We work in project-based sprints, working directly with everyone across the company, from customer support to regulation, product to financial crime, and we run regular knowledge-sharing sessions so you’ll learn heaps about everything from how banks work to effective communication.

We encourage an open and transparent working environment. You can get involved in any aspect of the business you are interested in and, following Stripe’s example, all emails in the company are visible in an email archive. We regularly run hackathons in which people build things on our third party API and we contribute to open source software as much as possible. We’ve also made our product roadmap public and give sneak peeks of features in our community forum.

If you’re unsure about applying or have any questions about the role or team, please don’t hesitate to email our CTO Jonas ([email protected]) directly :) We're very open about what we do in general, so our blog is a good place to learn more about what we do.

* Backend stack: Go, Cassandra, Kubernetes, Kafka, Linkerd/Finagle

* iOS stack: Swift 3, Realm

* Android stack: Kotlin, Java, Realm

Learn more on our careers page: https://monzo.com/careers/

I think you're right: including NGINX in the summary is a distraction, and highlighting it as a link makes the wrong implication. I'm a developer at Monzo, so I've tweaked the blog post to remove the reference. Thanks!

Monzo | Backend, Web or Android Engineer | London | VISA, REMOTE, INTERNS https://monzo.com

At Monzo we aim to build the best current account in the world. We are always keen to hear from capable, creative engineers who want to help us accomplish that goal.

Our backend engineering team have a variety of different backgrounds: we have several non-graduates; only a couple of us studied Computer Science; one of the team has a degree in Marketing; some of us have worked in huge companies; some have only ever worked in startups; others are former consultants. As long as you enjoy learning new things, we’d love to talk to you.

We work in project-based sprints, and take turns to be the floating engineer who handles interrupt-driven work and non-critical bug fixes. We work directly with everyone across the company, from customer support to regulation, product to financial crime, and we run regular knowledge-sharing sessions so you’ll learn heaps about everything from how banks work to effective communication.

We encourage an open and transparent working environment. You can get involved in any aspect of the business you are interested in and, following Stripe’s example, all emails in the company are visible in an email archive. We regularly run hackathons in which people build things on our third party API and we contribute to open source software as much as possible. We’ve also made our product roadmap public and give sneak peeks of features in our community forum.

If you’re unsure about applying or have any questions about the role or team, please don’t hesitate to email our CTO Jonas ([email protected]) directly :) We're very open about what we do in general, so our blog is a good place to learn more about what we do.

Stack: Go, Cassandra, Kubernetes, Kafka, Linkerd/Finagle

Learn more on our careers page: https://boards.greenhouse.io/monzo/jobs/244898

Tesco is licensed in the UK, and so is covered by FSCS [1] (similar to US FDIC) up to £75k.

It's not so relevant here, but in the case that the bank became insolvent (very unlikely in this case), FSCS aims to pay out within 7 days, and will pay all claims within 20 days.

[1] http://www.fscs.org.uk/what-we-cover/

Mondo | iOS Engineer | London, UK – Full Time – ONSITE

We're building the best current account in the world, which means building the best banking app in the world.

We've raised £2M in seed funding and we're hiring for an iOS Developer to join our small team and shape our company.

Competitive salary and equity.

[email protected] / https://getmondo.co.uk/careers/

Mondo | iOS Engineer | London, UK – Full Time – ONSITE

We're building the best current account in the world, which means building the best banking app in the world.

We've raised £2M in seed funding and we're hiring for an iOS Developer to join our small team and shape our company.

Competitive salary and equity.

[email protected] / https://getmondo.co.uk/careers/

Mondo | iOS Engineer, Visual Designer | London, UK – Full Time – ONSITE

We're building the best current account in the world, which means building the best banking app in the world.

We just closed £2M [0]. We're hiring for an iOS Developer and a Graphic Designer [1] to join our small team (~14) and shape our company.

Market-rate salary, generous stock options.

[email protected]

[0] http://techcrunch.com/2015/06/30/mondo-gets-passionate/

[1] https://mondo.workable.com/

It's true, though no-one seems willing to name the offending bank in print.

Example: http://www.ft.com/cms/s/0/5d1b0346-2af8-11dd-a7fc-000077b076...

Really nice execution.

Are you able to give a bit more detail on your backend stack and the reasons for your choice or technologies?

Will this stay Android only or are you planning on porting it?

> "train the users" is for me a 30 year mantra that no one out side of geekdom wants to hear

Perhaps a better approach to "training the users" might be for the University to actively attempt to phish its own users on a regular basis.

Those who fall for the phishing could be contacted directly, or have email access limited for some period of time (for example, a reduced sending rate limit).

Making self-phishing a regular occurrence (say, weekly) would train users to recognise and ignore it.

Works really smoothly, seems very thoughtfully put together.

Only criticism would that the "accept request to share location" action button is labelled "share", which I initially glossed over, assuming that it meant "share to social network".

Antitrust law.

Isn't the point of the D in DVCS that this is supported out of the box? What's wrong with:

  root@server# apt-get install git-core

  git@server$ mkdir ~git/repo.git
  git@server$ git init $!

  user@client$ git remote add origin ssh://git@server/repo.git