Senior Software Engineer

Harvey Nash; Vancouver; On-site; CAD 150,000 - 190,000; Full time

Job summary

Harvey Nash is seeking a Software Development Engineer, Cloud Platform to build the infrastructure that gets vision software onto customer devices securely and repeatably. You will own migration of on-prem systems to a cloud-based deployment with robust access control and cost-aware operations.

You will design a scalable connectivity layer, enable enterprise-grade authentication, and turn internal tooling into reliable products used by other engineers.

Qualifications

• 5+ years building backend or platform infrastructure in production, with ownership.
• Strong cloud experience (AWS preferred) and infrastructure-as-code skills.
• Practical networking and secure connectivity depth including identity management.
• Experience with authentication, authorization, and multi-tenant models.
• Familiar with compliance frameworks such as SOC 2, ISO 27001 or TISAX.
• Fluent Python and experience with job orchestration or data pipelines, observability, and cost.

Responsibilities

• Build the connectivity layer to our devices.
• Migrate deployment to the cloud with robust access control and cost awareness.
• Own how updates are built, versioned, distributed, and applied with RBAC.
• Create a data path from devices to our systems for triage and model training.
• Run infrastructure like a business with cost attribution and lifecycle policies.
• Turn internal tools into products with front doors, docs, authentication, and status alerts.

Skills

Cloud platforms

AWS

Infrastructure as code

Security

Authentication & authorization

Python

Cost management

Observability

Networking

Multi-tenant

Job description

Rate: $150,000 - $190,000 / Annum

The Role

We're looking for a Software Development Engineer, Cloud Platform to build the infrastructure that gets vision software onto customer devices: securely, repeatably, and without a member of our team on the phone with someone's IT department.

Getting software to a device today means threading through customer firewalls, remote-access tools that enterprise security teams increasingly reject, and internal systems only a handful of people know how to drive. You'll replace that with a real platform: a secure, trusted channel to every deployed device, cloud-hosted deployment infrastructure with proper access control, and internal tooling the rest of engineering can use without a guide.

This is a high-ownership role on a small team. The road-map is written but not finished, and you'll have significant say in the sequencing, the architecture, and what we choose not to build.

What You'll Do

• Build the connectivity layer to our devices.
• Make Company easy for enterprise IT to approve.
• Move deployment to the cloud. You'll migrate the systems we use to deploy software and manage our device fleet off ageing on-premise hardware and into the cloud, without a break in service. You'll own how an update gets built, versioned, distributed, and authorized, working with our on-device platform engineer on how it gets applied. Along the way you'll add role-based access control, so pushing an update to a customer's production cell is a deliberate act by someone authorized to do it, not an accident waiting to happen.
• Close the loop between the field and the lab. Devices see failure modes our test data never will. You'll build the path that gets data off a device and into our systems for triage, labelling, and debugging, so field reality feeds back into model training instead of dying in a support ticket.
• Run the infrastructure like a business. Training and storage costs scale with our success, and right now we keep everything forever. You'll build cost attribution down to the team, customer, and engineer, put data lifecycle policies in place, separate development from production, and evaluate additional providers for both cost and capacity headroom.
• Turn internal tools into products. Our internal tooling works, but mostly for the people who wrote it. You'll give it a front door, documentation good enough that another team can use it without our help, sensible authentication, and status tracking that alerts on failed jobs instead of letting them sit unnoticed.

What You Bring

• 5+ years building backend or platform infrastructure in production, with meaningful ownership of systems other engineers depend on.
• Strong cloud experience (AWS preferred) and fluency with infrastructure-as-code; you've made a migration succeed, ideally one where the legacy system couldn't be turned off on day one.
• Practical networking and secure connectivity depth (VPN and tunnelling, NAT traversal, certificate and identity management), plus the judgement to design something a customer's security team will actually approve.
• Real experience with authentication, authorization, and multi-tenant account models, including access control in environments where a mistake has physical consequences.
• Comfort operating under a compliance framework such as SOC 2, ISO 27001, or TISAX, and a willingness to own the infrastructure side of an audit rather than route around it.
• Python fluency and experience with job orchestration or data pipelines, plus instincts for observability and cost.

Bonus: managing fleets of edge or embedded devices, air-gapped or disconnected deployments, containerized delivery to customer hardware, or prior work in robotics, manufacturing, or another industrial setting