Why we’re hiring

Mimio is building the first agentic data analyst for small businesses.

 

Enterprise software has forgotten smaller businesses. Small businesses are unable to make sense of their data. They are unable to make data-driven decisions. Data analysts and the tools that they use today are prohibitively expensive for most businesses.

 

Mimio is here to change that.

 

You’ll be joining a team of second time founders. We’re funded. We know what we are going to build and have our first customers ready and waiting.

 

We want you to join our team and help us rapidly ship our MVP and iterate toward product/market fit.

 

As our Founding Engineer, you will be responsible for building a product that our first 20 customers love. You’ll be defining our stack and architecture. You’ll balance the need to build reliable software, with the need to iterate quickly. You’ll find new ways of combining deterministic software with probabilistic models.

​

Who we’re looking for

We’re looking for someone who:

 

• Finds deep satisfaction in shipping quality software to customers and gets energy from seeing the direct positive impact of what they build.

• Has spent a few years shipping software at scale. Ideally at a product-focussed company, working in the public cloud (AWS, Azure, GCP etc.)

• Is ambitious and ready to take ownership of complex problem-spaces.

• Has worked with a wide range of technologies and is comfortable articulating trade-offs in architectural discussions.

• Is a self-starter. You’ll be comfortable prioritising your own time and operating in a low-bureaucracy environment.

• Has an interest in data-driven decisions/data warehousing/data visualisation.

• Takes work seriously but doesn’t take themselves too seriously. We’re here to have fun, as well as build a great product.

​

About the role

Reporting to Pete, our Technical Co-Founder, and alongside our Founding Data Scientist, you’ll be the foundation of our engineering team.

 

Work will include:

• Defining and working across our stack.

• Building and managing our infrastructure in our selected cloud, embedding good practices like CICD and Infrastructure as Code.

• Shipping regular – daily – updates to the product. You will not be encumbered by process or a legacy codebase.

• Developing and implementing best practice for security.

​

FAQs

 

Will I have to go to an office?

 

No. We are deliberately building a globally distributed team.

 

What are the working hours like?

 

We think 9-6pm UK brings a good working cadence, but we are not particularly dogmatic about this providing work gets done. There will be times where you will have to work outside of these hours, but we strive towards a sustainable iteration velocity, and will endeavour to keep these times to a minimum.

 

Will there be opportunities to travel?

 

We believe strongly in the value of in-person time, so there will 1-3 times a year where we want to get the team together face-to-face.