Canva’s Commitment and Mission
At Canva, we celebrate diversity. We deeply believe that bringing together diversity of thoughts, perspectives and expression is key to building the best product, team and company. We look for many different skills and abilities, as well as how you can enhance Canva and our culture. So, even if you don’t think you quite meet all of the skills listed or tick all the boxes, we’d still love to hear from you!
Our mission at Canva is to empower the world to design and since launching in 2013, we have grown exponentially, amassing over 75 million monthly active users across 190 different countries and a team of over 2,800 people… and the best bit is that we’ve only achieved 1% of what we know we’re capable of.
Join us and design your future.
About Engineering @ Canva
Engineering is a core part of who we are at Canva. We take pride in our software engineering fundamentals and strike a measured balance between getting things done and long term maintainability. We have a flat structure and a tight team where everyone’s input is valued.
We looking for talented individuals with skills across the below Product Engineering specialities:
Frontend
- Knowledge of JavaScript and web technologies (HTML/CSS)
- Experience developing rich applications with HTML/CSS/JS
- Intimate knowledge of cross-browser and cross-device development
- Ability to write high-performance, reusable code for UI components, including appropriate testing
- Passion for performance debugging and benchmarking
- Minimum two years experience
- Computer science fundamentals
- Experience with SVGs
- Experience with graphics programming
- Experience with GLSL / WebGL
- An interest in interaction design
Reliability
- Design and implement processes, tools, automation, and libraries that service teams can use to improve the reliability of the services they own. For instance, adding a new long-awaited feature in our circuit breaker library.
- Introduce chaos engineering to Canva and conduct experiments to identify possible scenarios in which cascading failure might occur and to verify the reliability measures we introduce to prove this works as expected. E.g. discovering what will happen when this newly introduced service goes down? Does the fallback for this rare failure actually work?
- Work with product engineering teams to ensure reliability best practices and tools are rolled out in every service across the whole organization. It’s not enough to create a new throttling library, we want to make sure it’s successfully used in every service.