Senior Full Stack Engineer

About the role

Senior Full-Stack Engineer

Permanent | Full-time | North Vancouver, Canada | Hybrid

Compensation

$170,000 CAD salary

Quarterly profit share (last year averaged ~10k/quarter per person)

Stock options

Flexible (unlimited) holiday

Health benefits

About IcePanel

We started IcePanel because existing tools suck.

They’re slow, overcomplicated, and built for managers to enforce process, not for engineers to actually enjoy using.

At our previous jobs, we spent too much time in meetings talking about architecture and not enough time actually building. Diagrams got stale, decisions got lost, and nothing felt connected to reality.

So we started building something better. It began as a side project, let us snowboard most days in Whistler for a season, and people kept using it…

We got to nearly $1M USD with just the founders before we hired.

Today we’re a small, profitable team ($3M+ USD ARR) building a collaborative modelling tool for software architecture. We care about staying lean, shipping fast, having fun, and building something people actually love.

How we work

- We keep meetings to a minimum

- We ship weekly

- We work in small teams (usually 2 people) with clear ownership

- We avoid over-engineering, but we care deeply about polish

- We release early, get feedback, and refine

This is not a place to hide. You’ll own what you build.

The role

You’ll build across the entire product:

- Frontend UI/UX (working closely with design)

- Backend APIs and data models

- Real-time systems (WebSockets)

- Infrastructure and migrations

- Fixing, refining, and improving what already exists

Our stack: TypeScript, Node.js, Vue, Pixi.js, Tailwind, Cloud Run, Firestore, WebSockets

What “great” looks like

A great hire doesn’t wait to be told what to do.

In your first couple of weeks, you’ll use the product, find something that feels off, and fix it.

Not because it was assigned. Because it bothered you.

You’ll own meaningful features end-to-end. Examples:

- Git-like workflows for diagramming

- Import and data ingestion pipelines

- Access controls for complex organizations

- Data visualization across large architectures

You’ll make things feel better, not just work.

30 / 60 / 90 days

First 30 days

- Get familiar with the product and codebase

- Ship improvements to areas that feel “off”

- Start contributing to real features

60 days

- Take ownership of a meaningful area of the product

- Improve performance or usability in a noticeable way