1

Rust Software Jobs in Quebec (NOW HIRING)

Solid engineering fundamentals in Python, Go, or Rust. That's a preference, not a gate: deep systems experience in another serious language carries over. \n * Strong grasp of network programming and ...

En collaboration avec les autres membres de notre équipe Software, elle contribuera à faire ... Expérience en programmation Rust ou Golang, un atout * Expérience de programmation liée à des ...

En collaboration avec les autres membres de notre équipe Software, elle contribuera à faire ... Expérience en programmation Rust ou Golang, un atout * Expérience de programmation liée à des ...

You will hold a position as a software developer in the research and development team. You will ... Knowledge of low-level languages such as Go, C, or Rust * Knowledge of cloud platforms such as ...

Connaissance de Rust (performance, securite memoire, systemes embarques) * Experience avec GitHub Actions pour les pipelines CI/CD * Familiarite avec les methodologies Agile / Scrum Profil recherche

Expert - Simulation

Montreal, QC · On-site

  • Medical

  • Dental

  • Vision

  • Life

  • Retirement

  • PTO

... Software-In-the-Loop), en temps reel ou en temps de simulation, deployees sur des ressources ... Maitrise de Rust * Experience de la conformite avec la norme FMI (Functional Mock-up Interface)

Showing results 21-28

Rust Software information

What is a Rust software developer?

A Rust Software Developer is a programmer who specializes in using the Rust programming language to build software applications. Rust is known for its focus on safety, speed, and concurrency, making it popular for systems programming, web services, and performance-critical tasks. Rust Software Developers may work on a variety of projects, from operating systems and embedded devices to backend web servers and command-line tools. Their responsibilities include writing, testing, and maintaining code, as well as collaborating with other developers to design robust and efficient systems.

What are the key skills and qualifications needed to thrive as a Rust software developer?

To thrive as a Rust Software Developer, you need a solid background in systems programming, memory management, and proficiency in Rust, often supported by a degree in computer science or related experience. Familiarity with version control systems like Git, build tools such as Cargo, and experience with cross-platform development are typically required. Strong problem-solving skills, attention to detail, and effective communication set outstanding candidates apart. These abilities are essential for building safe, efficient, and reliable software in demanding technical environments.

What are some common challenges faced by Rust software developers when working on large-scale projects?

Rust Software Developers often encounter challenges related to managing complex codebases, especially as projects scale. The language's strict ownership and borrowing rules, while beneficial for safety and concurrency, can make refactoring and integrating with legacy systems more time-consuming. Additionally, since Rust is still a relatively new language, developers may face limited library support or community resources for certain specialized tasks. Collaborating closely with teammates and leveraging thorough documentation helps to streamline workflows and overcome these hurdles.

What is the difference between Rust Software vs C++ Developer?

AspectRust SoftwareC++ Developer
Required CredentialsBachelor's in Computer Science, Rust certifications (optional)Bachelor's in Computer Science, C++ certifications (optional)
Work EnvironmentTech companies, startups, embedded systemsSoftware firms, game development, embedded systems
Industry UsageEmerging in systems programming, web assembly, safety-critical appsWidely used in software, gaming, systems, and embedded development
Search & Comparison IntentUnderstanding Rust's role vs C++ in development

Rust Software developers focus on safe, concurrent programming using Rust, often in modern systems and web assembly projects. C++ Developers work primarily with performance-critical applications across various industries. While both roles require programming expertise, Rust emphasizes safety and modern syntax, whereas C++ is known for its performance and legacy codebases.

What are popular job titles related to Rust Software jobs in Quebec?

For Rust Software jobs in Quebec, the most frequently searched job titles are:

What job categories do people searching Rust Software jobs in Quebec look for?

The top searched job categories for Rust Software jobs in Quebec are:

Infographic showing various Rust Software job openings in Quebec as of August 2026, with employment types broken down into 1% As Needed, 88% Full Time, 8% Part Time, and 3% Contract. Highlights an 86% Physical, 4% Hybrid, and 10% Remote job distribution.

Research Software Engineer (hybrid Montreal)

Calliere

On-site

Full-time

Posted 13 days ago


Job description

\n <\/head>\n \n
<\/h1>

Location:<\/b> Montreal Employment type:<\/b> Regular, full\-time Team:<\/b> Technology \/ Engineering Start date:<\/b> As soon as possible.
<\/p>\n

\n

\n <\/div>

We're a fintech firm with more than three decades spent pairing serious engineering with unusually capable people to build and run financial systems in markets across the globe. We prize independence and the ability to change direction quickly when an opportunity opens, so we operate on our own platform, deploy our own capital, and own the risk that comes with it.
<\/p>

We work with curiosity, mutual respect, and open minds. The people who do well here believe that how<\/i> the work gets done matters as much as the work itself. Expect a high bar, a premium on integrity and invention, and a real appetite for questioning the consensus.
<\/p>

This role lives where research meets infrastructure: you'll form hypotheses, test them fast with hands\-on analysis, and then build the production systems that put the winning ones to work.
<\/p>

LLMs are a core part of how we build here: a first\-class tool, not a side experiment. The engineers who thrive are the ones who can drive an agentic harness as naturally as they read a profiler, and who know precisely where each of those tools stops being trustworthy.
<\/p>How You Will Make an Impact
<\/h2>

Discovery & Research<\/b>
<\/p>\n

    \n
  • Grow our event\-driven approach across exchange feeds, market news, social platforms, and infrastructure telemetry.
    <\/li>\n
  • Stand up quick analyses in Python\/Jupyter to gauge signal quality, then convert what you learn into concrete system improvements.
    <\/li>\n <\/ul>

    LLM & Agentic Systems<\/b>
    <\/p>\n

      \n
    • Design and operate agentic harnesses: tooling, context management, evals, guardrails (that do meaningful work against our data and infrastructure, and own their quality once they're live).
      <\/li>\n
    • Deploy LLMs where they truly earn their place (extraction, classification, triage, faster research) and knowingly skip them where they don't.
      <\/li>\n <\/ul>

      Infrastructure & Technical Leadership<\/b>
      <\/p>\n

        \n
      • Own performance end to end, from the network edge through in\-memory stores - instrumenting, monitoring, and debugging live systems shoulder to shoulder with operations while keeping SLOs tight.
        <\/li>\n
      • Drive green\-field builds, design reviews, and post\-mortems.
        <\/li>\n <\/ul>\n
        \n
        \n <\/div><\/span>
        Requirements<\/h3>What You Bring
        <\/h2>

        Core<\/b>
        <\/p>\n

          \n
        • Three to five years building real\-time or data\-intensive systems (we care more about depth and trajectory than the precise year count).
          <\/li>\n
        • Real depth with LLMs rather than surface familiarity; how these models actually behave (context windows and their failure modes, tool use, structured output, cost and latency trade\-offs, keeping hallucination in check) and how to construct the scaffolding around one: tools, memory, retries, evals, and sensible human\-in\-the\-loop limits. Come ready to walk us through something real you shipped, end to end, including what went wrong.
          <\/li>\n
        • Solid engineering fundamentals in Python, Go, or Rust. That's a preference, not a gate: deep systems experience in another serious language carries over.
          <\/li>\n
        • Strong grasp of network programming and protocols: TCP\/UDP\/IP, DNS, BGP, HTTP(S), WebSocket, QUIC.
          <\/li>\n
        • Taking rapid POCs to production while confirming statistical significance, iterating quickly, shipping, and explaining the outcome clearly to technical and non\-technical audiences alike.
          <\/li>\n
        • A Bachelor's or Master's in Computer Science, Data Science, Mathematics, or a comparable field.
          <\/li>\n <\/ul>Who Thrives Here
          <\/h2>

          This is a competitive, high\-stakes setting, and we're looking for people who are drawn to that rather than merely willing to put up with it. You'll probably recognize yourself here if:
          <\/p>\n

            \n
          • You want problems that are truly hard and measurable, where the scoreboard is real and visible inside the team.
            <\/li>\n
          • You move quickly without cutting corners, and you'd rather ship, measure, and adjust than deliberate indefinitely.
            <\/li>\n <\/ul>\n
            \n
            \n <\/div><\/span>
            \n <\/body>\n<\/html>