Company
Motion
Annual salary
Not disclosed
Location
United States
Listed
618d ago
- Experience:
- 6+ years
- Workplace:
- Fully remote role. Open to US, Canada, and Western Europe candidates but preference for those working on ET time zone.
- Visa:
- Visa sponsorship not available
- Equity:
- We provide equity in the form of options.
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
Remote (listed in United States). Visa sponsorship not available.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
About the Staff Software Engineer role 🔍
As a Staff Software Engineer on our Platform team, you’ll design, implement, and maintain robust, high-quality backend APIs and services. Your work will directly impact Motion’s core operations and enable teams across the company to use our data across multiple product lines.
**| **Our tech stack: React, Node.js with Express, TypeScript, GraphQL, PostgreSQL, MongoDB, and Azure.
➡️ Explore our Engineering at Motion page to learn more about our team, our work, and how we build together.
What you'd be doing 🛠️
Scoping, designing, and implementing resilient, performant, and high-quality backend solutions.
Working closely with fellow engineers to deliver complex backend features and integrations.
Maintaining and enhancing existing integrations, anticipating future product solutions and making sure our systems scale with Motion’s growth.
Identifying and resolving errors, performance issues, and devex problems in our codebase.
Driving engineering advancements.
Sample projects:
Build a unified API for our insights data to be used by other development teams.
Store insights and metrics from our data providers at scale.
Our ideal fit brings ✨
6+ years of experience building and maintaining large-scale software applications.
Proficiency with our core stack (React, Node.js, TypeScript) is ideal, though we’re open to adjacent tech.
Strong experience with asynchronous message queue systems.
Experience with MongoDB or other document-based databases.
Solid understanding of data modeling, ETL concepts, and simplifying data architecture.
Exceptional written and verbal communication skills with a knack for translating complex technical issues into clear business impacts.
Interest in AI/ML.
Ability to thrive in a fast-paced environment with evolving requirements and priorities.
A pragmatic approach to tackling challenging problems, with a deep interest in understanding and solving business needs.
What you'll love about Motion 💜
Competitive compensation package: We offer competitive compensation, including equity for all employees, health benefits from day one, a monthly health & lifestyle stipend to support your well-being, 20 days of PTO, and a $1,500 work-from-home stipend.
Remote-first with hybrid flexibility: We're a remote-first company with team members spanning Canada, the U.S., and beyond, but also have office spaces in 4 main hubs (Toronto, Montreal, Vancouver, and Porto) for optional hybrid work.
Growth that speaks for itself: Motion has strong product-market fit, 3x YoY growth, second-time founders with deep industry knowledge, and $30M in Series B funding to fuel our momentum.
Opportunity for impact: As an early team member, your contributions will directly shape the product, team, and the future of the company. If you're excited about building, you’ll thrive here!
Award-winning team: We're a low-ego, high-performing team that was just ranked #5 on LinkedIn’s Top 15 Startups in Canada for 2025.
Team connection: To stay connected in a virtual workspace, we get together at least once yearly for a company-wide offsite (this year, we spent a week by the lake in Muskoka, Canada!)
🌎 A note on location: Motion is a fully remote company, but we’re looking for someone in or around one of our hub cities (Toronto, Montreal, or Porto, Portugal) who can work with significant overlap to ET working hours.
Common questions
How do I apply for the Senior / Staff Software Engineer (US) role at Motion? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
Is this role remote? +
Yes, the listing is remote. Fully remote role. Open to US, Canada, and Western Europe candidates but preference for those working on ET time zone. Visa sponsorship not available.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →