First things first, follow me on Twitter. My ego is way too strong to miss this opportunity to fool a few more victims into following me. Worst part is that I donāt even tweet interesting stuff
What Iām working on? A few things:
Helping @bailey to review all the lovely names weāve been getting. Itās a really exciting and exhausting process. For every potential name we need to check trademarks and general availability, test with real people to get a bit of useful data, etc.
Improve the waiting list experience. We know itās a bit frustrating to wait for a card so weāre trying to give users useful content and better ways to get their cards quickly. @sam and @tristan have done an amazing job on it, youāll see it soon.
Budgeting. This is a big one because it impacts tons of structural parts of the app (both as prepaid and by the time weāre a full bank). Iām working with @zancler to define the master interactions (navigation, notifications, etc.), redefine a few concepts and build prototypes to start testing with users. Weāll share a sneak peek as soon as we have something a bit consistent.
On top of that Iāve been spending some time to define better processes on the way we work and the tools we use, but I donāt want to bore you with all that
Iām now going to nominate @simon (he can tell us about VR and other mindblowing stuff).
task add Do Mondo Daily Diary wait:tomorrow due:tomorrow
(Iām a command line junkie, if you also live in tmux, checkout taskwarrior.org to see what the above means.)
So for the last few weeks iāve been working with @matt and @oliver on moving our infrastructure over from Mesos/Marathon to Kubernetes and CoreOS. Weāve learned a lot, and we think weāre about ready to switch the rest of our developer colleagues over to using the new environments for staging.
For the last week weāve also had a HTC Vive virtual reality headset in the office, combined with my gaming PC i brought from home, weāve had it in pretty much constant use while the entire team had goes various things.
Most popular: Longbow (Part of the The LAB), and the Apollo VR experience.
Hi everyone! My name is Richard, Iām a backend engineer at Mondo. :mondo:
This week I am floating engineer. What does that mean?
Across our technology teams, we generally have two types of work:
flow-driven work, e.g. working on cool new product features
interrupt-driven work, e.g. responding to urgent bugs or customer support
Flow work requires a great deal of focus and concentration. In order for people to excel and do their best work, we try to avoid interrupting them unless there is something really important.
The impact of interruptions on concentration are well-understood:
An interrupted task is estimated to take twice as long and contain twice as many errors as uninterrupted tasks
A programmer takes between 10-15 minutes to start editing code after resuming work from an interruption.
(If you prefer pictures, hereās what happens to an engineer when you interrupt them: ;))
To reduce the cost of these interruptions, one person is nominated as a floating engineer. His or her job is to insulate the other engineers from the various interruptions which inevitably arise throughout the day, so everyone else can focus on their work.
Hereās a sample of a few of the things Iāve been working on this week:
A bug where some merchantās refunds would appear twice in your feed e.g. Bet 365 (because they send a credit authorisation before a presentment)
Adding an ability for us to track cards which get lost in the mail
An data report so @tristan can contact customers who have registered for the waiting list but never downloaded the app
Improving the internal tool we use to apply bank transfer topups
Coordinating communication and managing the Mondo status page during todayās CloudFlare incident
Checking our error reporting tools and triaging any new bugs
Fixing bugs and timeouts on our internal dashboards
A data report for @bailey for everyone who sent in suggestions for new names
Helping out with customer support issues
As well as a bunch of more technical behind-the-scenes stuff to keep everything operating smoothly!
Well. Weāre almost two weeks into choosing a new name (not heard? weāre changing our name!) and so thatās been a pretty unique project to work on. I just published a blog post all about it, in fact, so you can read up on the process there if youāre interested.
In a nutshell, weāve spent time reviewing all the 4,500 unique name ideas, then we did some user testing on the shortlist. Currently weāre working with a team of lawyers to work out if the names we like are OK to trade mark.
Apart from the name change, Iām working on a few other thingsā¦
Working with students to bring Mondo to campuses in September (weāre hosting our first student workshop on Saturday)
my name is Jonas and I joined Mondo this week as their first Android engineer. Itās been some quite exciting first couple of days.
Obviously, I started working on the Mondo Android app immediately. We want to release a few basic features for users that already have a Mondo card in our public beta channel by beginning of July.
Initially, weāre gonna test this beta version with Mondo users that have switched from an iPhone to Android.
Also, weāll invite people with Android devices to our office soon, so they can get a card and start using the app.
From there weāll keep adding more features in quick iterations.
The main things that Iāve worked this week on are:
A home screen that shows your transaction feed
The support chat integration
It was a great first week and Iām looking forward to the next.
Afternoon all, pretty cool we have an Android engineer now rite?
Today Iām working on our KYC (Know Your Customer) / account verification flow. Some of you may have been through the process already
We released the first version of this about a month back, and while that solution works, it still lacks polish. I returned somewhat jetlagged from a trip to NYC last week and have been working on it since, and despite realising this morning I lost almost the entirety of my Fridayās work (the design team switched our syncing system and because @zanclerās an idiot he didnāt make a backup of his file ), I reckon everything should be finished by the end of the day.
Also, as the proud owner of the Worldās Pettiest Designer title, I dedicate a bit of time each day to cleaning up our files and refactoring them to @1x. Despite making up for Fridayās lost work, I should have an hour or so today to push on with this. If thereās one thing I love, itās clean .sketch files.
I nominate @Sam. Double dose of design. 'Til next time
Hey peeps for the past couple of weeks I have been creating new illustrations & animations. These are intended to help new users get to grips with all the different features Mondo has to offer.
Today i have been focused on the welcome screen and initial set of screens you will see when opening the app for the first time. Heres a little sneaky peak of one of these animations.
Hi all Iām a little late - I wrote this yesterday but didnāt get time to post before we headed out for our social ()
Iām responsible for all things people-related and office-related here, as well as a little bit of finance, general admin, and anything else that needs doing.
It feels like no time has passed since I last wrote this back in early May, but weāve had 8 new joiners since then across customer support, regulation and engineering - the teamās growing quickly!
Yesterday I was busy with customer support hiring: two on-site interviews, a couple of initial phone calls, as well as reviewing lots of take-home tasks for various regulatory roles, and a little bit of scheduling for future interviews.
Our hiring process here is split into several stages:
At application, we ask for a CV as well as a paragraph in answer to several questions; these questions help us ensure weāre considering each application on consistent criteria.
The next step is a short initial phone call, usually with me, which covers some general background questions (to understand the personās story and background, as well as why theyāre interested in Mondo) and some job-specific questions which touch on each of the things we view as important to the role. I particularly enjoy the part at the end when applicants ask me all their questions about the company, the culture here, the team and the role itself
After that we send a short take-home task, related to the role itself, which usually takes 1-3 hours. This helps us from biasing towards people who are good as thinking on their feed over people who prefer to reflect before making a decision.
The final stage is where we invite applicants to our office for an interview split in two parts - one to talk about the job itself and the key traits and characteristics; and a second session to find out more about them as a person, their expectations for the role, their career aspirations, and check that the ways they prefer to work fit with how we work here so we can be sure they have a good chance of thriving in the culture weāre growing
And then, finally, references and chatting with the rest of the team in a relaxed context - usually over lunch
Iāve also been writing a job ad for an Office Manager (coming super soon!), rearranging our office social area, getting myself set up so that I can edit our careers page as weāre migrating to a new applicant tracking system, and we had a really interesting security briefing yesterday.
Thanks @thomasageorge !
My name is Richard, Iām a backend engineer at Mondo. :mondo:
Your 
), I reckon everything should be finished by the end of the day.
for the past couple of weeks I have been creating new illustrations & animations. These are intended to help new users get to grips with all the different features Mondo has to offer.
)
