Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal: ask the recruiter.
-
?
No government sponsor record hereNo government sponsor record covers this employer in this country.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeCanada has no single salary bar: the employer usually needs a positive LMIA.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- No salary bar for this route
- Canada has no single salary bar: the employer usually needs a positive LMIA. Pay at or above the provincial median wage + 20% (e.g. C$36.92/h in Ontario) puts it in the high-wage stream. Source: https://www.canada.ca/en/employment-social-development/services/foreign-workers/median-wage.html, rules effective 2026-07-17.
Canada: Express Entry no longer awards ranking points for job offers (since 25 Mar 2025); a job offer still counts toward Federal Skilled Worker eligibility.
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
Before you apply
Sponsorship unknown
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →
About the role
We’re introducing Rust where correctness, performance, and reliability truly matter.
Narvar is Growing! Narvar is a multi-language platform, and we’re intentional about where we apply Rust. We’re looking for senior engineers to help us bring Rust into the backbone of the system — the parts that must be fast, safe, and correct under real-world scale.
This role is for engineers who want agency: people who enjoy identifying the right problems, choosing the right tools, and owning systems end-to-end. You won’t be handed a narrow ticket queue. You’ll help decide what gets built and how it should be built.
For this role, you should be located in Canada and able to work within EST/EDT or PDT/PST hours. We are fully remote.
Day-to-day
• Design and build high-correctness Rust services that sit on critical platform paths
• Introduce Rust into areas where safety, determinism, and performance are essential
• Own systems from architecture → implementation → rollout → operations
• Make real decisions around concurrency, async boundaries, data integrity, and failure modes
• Work across service boundaries in a polyglot environment (Rust alongside other stacks)
• Collaborate with product, design, and frontend engineers to build systems that are technically sound and product-aware
• Improve reliability, observability, and system behavior through design, not just patching
• Mentor other engineers and raise the bar on system quality and ownership
What We’re Looking For
We care more about judgment and ownership than credentials.
You’re likely a strong fit if you:
• Have built and operated distributed systems in production
• Have deep hands-on Rust experience (not just experiments or side projects)
• Understand where Rust shines — and where it doesn’t
• Are comfortable reasoning about concurrency, async systems, and correctness guarantees
• Have experience designing APIs and data contracts that evolve safely over time
• Have worked with relational and/or NoSQL databases at scale
• Have deployed and operated services in AWS or GCP (We are a GCP Shop though!)
• Take initiative naturally and are comfortable operating with ambiguity
• Communicate clearly and make tradeoffs explicit
Bonus Points
These aren’t hard requirements, but strong indicators:
• You’ve worked in startup or high-ownership environments
• You’ve owned systems in production, including on-call responsibility
• You’re comfortable moving across the stack when needed (backend-first, full-stack aware)
• You’ve influenced architecture by earning trust, not by mandate
• You use modern tooling (including AI-assisted workflows) to increase leverage , not outsource thinking
(Note: we care about outcome and judgment, not how flashy your tools are.)
Why Rust at Narvar?
Because some parts of the system deserve stronger guarantees.
We use Rust where:
• Bugs are expensive
• Latency and throughput matter
• Safety and correctness are non-negotiable
You’ll help define where Rust belongs , not just write Rust in isolation.
Why Narvar (From an Engineer’s Perspective)?
• Real scale, real customers, real impacts
• Startup-level ownership with platform-level impact
• Teams that value thinking, judgment, and responsibility
Low ego, high trust, and room to do your best work
Why Narvar?
We're on a mission to simplify the everyday lives of consumers. Post-purchase is a critical phase of the customer journey. That's why we created Narvar - a platform focused on driving customer loyalty through seamless post-purchase experiences that allow retailers to retain, engage, and delight customers. If you've ever bought something online, there's a good chance you've used our platform!
From the hottest new direct-to-consumer companies to retail’s most renowned brands, Narvar work
Apply on company site ↗