1

Network Engineer Jobs in Quebec (NOW HIRING)

Infrastructure & Technical Leadership Own performance end to end, from the network edge through in ... Solid engineering fundamentals in Python, Go, or Rust. That's a preference, not a gate: deep ...

Own performance end to end, from the network edge through in\-memory stores - instrumenting ... Solid engineering fundamentals in Python, Go, or Rust. That's a preference, not a gate: deep ...

New

Own full-stack performance from the network edge to in-memory stores -- instrumenting, monitoring ... Strong engineering fundamentals in Python, Go, or Rust. A preference, not a gate -- deep systems ...

New

Working closely with engineers and cross-disciplinary teams, you will provide technical leadership ... Builds memory regression tests that run in CI - not just point-in-time snapshots Networking ...

The goal: one unified network open to any person and any device, worldwide. Connection without ... The Opportunity We're looking for a Staff Front-End Engineer to join our growing engineering team ...

Knowledge of SCADA systems, industrial networking, and data acquisition platforms; Experience with Python, C#, or similar programming languages is considered an asset; Familiarity with hazardous area ...

Knowledge of SCADA systems, industrial networking, and data acquisition platforms; Experience with Python, C#, or similar programming languages is considered an asset; Familiarity with hazardous area ...

Knowledge of SCADA systems, industrial networking, and data acquisition platforms; Experience with Python, C#, or similar programming languages is considered an asset; Familiarity with hazardous area ...

Showing results 21-40

Network Engineer information

What does a network engineer do?

A Network Engineer is responsible for designing, implementing, and maintaining the computer networks that support in-house voice, data, video, and wireless network services. They ensure network reliability and performance, troubleshoot issues, and optimize network security. Network Engineers work with hardware and software, coordinate with other IT professionals, and often manage upgrades or expansions to meet an organization's needs.

What are the key skills and qualifications needed to thrive as a network engineer, and why are they important?

To thrive as a Network Engineer, you need a solid understanding of network protocols, routing and switching, and typically hold a degree in computer science or a related field. Familiarity with tools like Cisco IOS, network monitoring software, and certifications such as CCNA or CCNP are highly valued. Strong problem-solving skills, effective communication, and the ability to work well under pressure set top performers apart. These skills ensure the reliable design, implementation, and maintenance of network infrastructure, which is critical for organizational connectivity and security.

What does a network engineer do?

Network Engineers support and optimize all processes for maintaining a company’s computer network, selecting and deploying software and hardware and making local area networks (LANs) and wide area networks (WANs) accessible, and making sure that company personnel can securely access the internet to complete work. Network Engineers also analyze network performance, configure network features based on client needs, and develop guidelines for acceptable network use.

What is the difference between Network Engineer vs Network Administrator?

AspectNetwork EngineerNetwork Administrator
CertificationsCCNA, CCNP, CompTIA Network+CCNA, CompTIA Network+
Work EnvironmentDesigning, implementing, and troubleshooting network infrastructureManaging and maintaining existing network systems
ResponsibilitiesNetwork design, configuration, and optimizationMonitoring, maintaining, and supporting network operations
Industry UsageIT, telecommunications, large enterprisesCorporate, small to medium businesses, educational institutions

While both roles involve working with networks, Network Engineers focus on designing and building network systems, whereas Network Administrators manage and support existing networks. Understanding these differences helps organizations assign the right responsibilities and professionals for their network needs.

What are some common challenges network engineers face when managing large-scale enterprise networks?

Network Engineers working with large-scale enterprise networks often encounter challenges such as ensuring network security across multiple locations, minimizing downtime during upgrades or maintenance, and troubleshooting complex connectivity issues. They may also need to balance high availability with performance, manage diverse hardware and software, and coordinate with cross-functional teams like cybersecurity and IT support. Staying updated with rapidly evolving technologies and addressing scalability concerns are key aspects of the role.
What are the most commonly searched types of Network Engineer jobs in Quebec? The most popular types of Network Engineer jobs in Quebec are:
What are popular job titles related to Network Engineer jobs in Quebec? For Network Engineer jobs in Quebec, the most frequently searched job titles are:
What job categories do people searching Network Engineer jobs in Quebec look for? The top searched job categories for Network Engineer jobs in Quebec are:
Infographic showing various Network Engineer job openings in Quebec as of August 2026, with employment types broken down into 1% As Needed, 81% Full Time, 11% Part Time, 1% Temporary, and 6% Contract. Highlights an 91% Physical, 2% Hybrid, and 7% Remote job distribution.

Research Software Engineer (hybrid Montreal)

Calliere

On-site

Full-time

Posted 5 days ago


Job description

Location: Montreal Employment type: Regular, full-time Team: Technology / Engineering Start date: As soon as possible. 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.

We work with curiosity, mutual respect, and open minds. The people who do well here believe that how 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.

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. 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.

How You Will Make an Impact Discovery & Research Grow our event-driven approach across exchange feeds, market news, social platforms, and infrastructure telemetry. Stand up quick analyses in Python/Jupyter to gauge signal quality, then convert what you learn into concrete system improvements. LLM & Agentic Systems 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).

Deploy LLMs where they truly earn their place (extraction, classification, triage, faster research) and knowingly skip them where they don't. Infrastructure & Technical Leadership 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. Drive green-field builds, design reviews, and post-mortems.

Requirements What You Bring Core Three to five years building real-time or data-intensive systems (we care more about depth and trajectory than the precise year count). 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.

Solid engineering fundamentals in Python, Go, or Rust. That's a preference, not a gate: deep systems experience in another serious language carries over. Strong grasp of network programming and protocols: TCP/UDP/IP, DNS, BGP, HTTP(S), WebSocket, QUIC.

Taking rapid POCs to production while confirming statistical significance, iterating quickly, shipping, and explaining the outcome clearly to technical and non-technical audiences alike. A Bachelor's or Master's in Computer Science, Data Science, Mathematics, or a comparable field. Who Thrives Here 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: You want problems that are truly hard and measurable, where the scoreboard is real and visible inside the team. You move quickly without cutting corners, and you'd rather ship, measure, and adjust than deliberate indefinitely.