Who we are and what we do
We use outdoor maps daily, but when we walk indoors, useful maps are missing. From offices to stadiums, people need to find things and know where to go.
Mappedin builds user-friendly mapping tools that make the indoors visible empowering businesses to create experiences that people now expect.
Whether you’re a building manager or a CAD expert, Mappedin enables anyone to create useful indoor maps.
Headquartered in Waterloo, Ontario, we have more than 1.3 billion square feet of space managed within our indoor mapping platform and have ranked as one of Canada’s Top Growing Companies in the Globe and Mail Report on Business for the past three years.
Media :
Who you are and what you’ll do
You love distributed systems architecture, working with the newest technology to solve complicated problems, and want to help us scale to the next 10x.
You care about quality and have high standards for what gets delivered to our customers. You want to blanket your code in high quality automated tests.
The Core Services team, part of Foundations, owns or helps develop many of the back end services the other developers at Mappedin rely on.
You can expect to do a lot of high-leverage work, as the improvements you implement will unlock capabilities for other parts of the dev team, and ultimately deliver a lot of value to Mappedin customers.
You are highly interested in learning about or already have experience in :
- TypeScript, Node, and Jest
- SQL and NoSQL databases, like Postgres and MongoDB
- Test Driven Development
- Rust
What are some challenges?
Mappedin is starting to use Rust, especially in our back end services. If you love Rust, that means there is still a lot of TypeScript code you will need to deal with, and even best case it’s not all going to get migrated.
If you have never looked at Rust before, that means a new and honestly fairly difficult language to learn. It has a lot of benefits, but it does a number of things completely differently from any other language you are likely to know, and will not let you be sloppy.
Mappedin moves fast and we sometimes change directions. We can’t always wait for all the information before we try something.
If you want us to guarantee exactly what you’ll be working on three months from now, we can’t give you that. On the other hand, there is a lot of high value work to do, and it won’t be boring.
Mappedin follows the Test Driven Development methodology to write code that is testable, tested, and only does what it needs to do.
We don’t expect you to be an expert in TDD when you start, but we do expect you to become one, and hold your team to a high standard of testing.
You also own the quality of your own work, and we expect you to prove that with your own integration and end to end tests.