opportunities@robmoritz.me
I'm a dev, I solve problems, especially those which span multiple teams and functions. In my mind, a problem cannot be solved without a full understanding of it, which more often than not, has everything to do with the end user. User experience is front and center, and the beginning of everything I do.
Here are some snippets to get to know me better: I hate silos; process is meant to help us, not hinder us; Come to me with problems, not solutions, and let's work together on a solution; Titles are meaningless; Treat everyone with respect;
Javascript, Typescript, Node.js, React.js, next.js, Apollo Graphql, Serverless, Event-driven and transactional architectures, MongoDB, PostgreSQL, RESTful, test-driven development, CI/CD pipelines
While I've been a full-time employee for years, I doubt anyone wants to know that I spent 3 months in meetings, trying to ensure the designs were actually solving the problem and not a vanity refresh. As such, I'll lay out just the cool parts of my job, which I'd love to talk to you about.
Current project, a long project to migrate users to a new yet-to-be-built app, with an extra spicy wrench of multi-domain where they are "hardcoded" into the IaaS. ask me about it, since it is developing fast. Latest news: I've built out a series of proof of concepts to test the infrastructure migration
A small project, to build a customizable product (aluminium extrusion, so cool yea?) in shopify + visualization of user selection. Reminded me of my attempts at unity dev. Result is a dynamic svg
Investigation into performance bottlenecks in prep for 10x, what do we need to do to support the planned growth. Looked at Heroku dynos, AWS Elastibeanstalks, MongoDB cluster, using IaaS metrics paired with Elastic APM. looked at the current situation, options for the future + ceilings (Vercel is cool for small traffic, but costs grow quickly, or Heroku can have max of n dynos per app)
Frontend + web assembly DuckDB, for running analytics pipelines locally. a data scientist + me, but then DuckDB ui came out, which was exactly what we were building
(Tech) led a complete rethink of the back-end tool, built using Retool (low-code tool)
Patient reported outcome metrics (PROMs), custom form builder, extensible and all the good things, paired with very specific medical science requirements. Heavily regulated space, with government data sharing agreements
Leva was going through a big shift, and the culture (as well as code quality) dropped significantly. Re-structured the engineering department to be more efficient. Fixed processes and opened up comms and transparency, especially between engineering and product.
(Tech) led a team to build a new project using micro-frontends architecture from below. All the usual greenfield problems were on my shoulders (such as, what's the problem we are trying to solve here?)
Designed micro-frontends solution to a specific problem (3 search experiences, which could be unified), which ended up being used across the board in prep for massive hiring push (and then covid happened)
Designed, presented, got approved and facilitated migration from ELB micro-services to the BFF model on serverless. Node.js + Apollo GraphQL
Used-car search experience, as a part of wider car loan pipeline. Amazing customer-centric product, since we weren't selling cars, but loans, so the job was the find our customers the best possible car within their loan amount
Too long ago, don't remember specifics, so here's a brain dump: a lot of Shopify, Wordpress and static sites. MySQL, PHP, Apache, bare-metal servers. as NDS (me+designer), we build out shops selling everything from candles, to luxurious furniture and fitness equipment (shipping calculations on those are nigh on impossible, but that might be due to lack of will to compromise). Projects across the world: Australia, USA, Europe, so a lot of timezones + currencies