
Full Stack Engineer
IcePanel
Job description
Permanent | Full-time | North Vancouver, Canada | Hybrid (3 days in office, 2 remote)
Compensation
$120,000 - $170,000 CAD salary (Intermediate > Senior)
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 for software architecture 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 ($4.5M+ CAD 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
-
Work across frontend + backend without hand-holding
90 days
-
Own and ship a complex feature end-to-end
-
Contribute to solving harder problems like:
-
Access control for large organizationsManaging deeply nested architecture models
-
Performance issues with highly connected systems
Current challenges
-
Changing model hierarchies (parents/levels) is complex and fragile
-
Large, highly connected models can impact real-time performance
-
Access permissions donât scale well for large companies
-
LLM assisted architecture documentation and ideation
If those sound interesting, youâll probably enjoy this.
About you
You:
-
Have 6+ years of experience across both large companies and startups
-
Are strong in both frontend and backend
-
Have built things youâre genuinely proud of
-
Care deeply about how things look and feel, not just that they work
-
Take ownership and donât wait for permission
-
Are comfortable working across a large, evolving codebase
-
Can take feedback without ego and adjust quickly
Youâve likely:
-
Built side projects just because something annoyed you
-
Worked across product, UX, and engineering boundaries
-
Shipped real features that people use
Proof of craft (required)
You must show us something youâve built.
-
Portfolio, live apps, screenshots - anything that shows off your skills
-
We care about how it feels to use, not just what it does
If you canât point to something youâve built that feels great, this role isnât for you.
Youâll struggle here if
-
You rely heavily on AI without understanding fundamentals
-
You wait for direction instead of taking initiative
-
You blame others instead of owning problems
-
You lead with ego instead of curiosity
-
You need constant permission to move forward
Also, if you donât actually care about what youâre building, donât apply.
Bonus points
-
Youâve been a founder (even if it failed)
-
You come from a non-traditional background
-
You understand the limits of LLMs beyond surface-level use
-
Youâve spent time in a major tech hub and chose (or want) to work in Canada
Location
-
North Vancouver (5 min from Lonsdale Quay)
-
3 days in office (Tues-Thurs)
-
2 days remote
-
Hybrid, not fully remote
-
Flexible location a couple of weeks a year đď¸
Benefits
Stock options
Profit sharing
Learning budget
Conference budget
Annual retreat
Flexible holiday
Health, dental, vision
âWeinerâ Wednesdays đ and free ice cubes đ§
Interview process
-
Screening questions (AI answers are insta-deletedâŚ)
-
Intro chat (20 mins)
-
Technical call (30 mins)
-
In-person white-boarding session/meet the team (2 hours)
-
Work trial (2 days min + paid)
-
Reference checks
-
Offer letter