Senior Full Stack Engineer

About IcePanel

Design and explain complex software architecture.

Tech

Experience with our tech stack is a head start but not essential. We build using Typescript, NodeJS, VueJS, PixiJS, TailwindCSS, Cloud Run, WebSockets, Firestore, Firebase, Cloud Storage and Redis.

The role

# Senior Full-Stack Engineer**Permanent | Full-time | North Vancouver, Canada | Hybrid**## Compensation$170,000 CAD salaryQuarterly profit share (last year averaged \~10k/quarter per person)Stock optionsFlexible (unlimited) holidayHealth benefits---## About IcePanelWe 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 refineThis is not a place to hide. You’ll own what you build.---## The roleYou’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 existsOur stack: TypeScript, Node.js, Vue, Pixi.js, Tailwind, Cloud Run, Firestore, WebSockets---## What “great” looks likeA 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 architecturesYou’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 organizations* Managing 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 companiesIf 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 doesIf 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 forwardAlso, 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)\- Hybrid, not fully remote\- Flexible location a few weeks a year 🏖️---## BenefitsStock optionsProfit sharingLearning budgetConference budgetAnnual retreatFlexible holidayHealth, dental, visionAnd, yes, “weiner” Wednesdays 🌭 and free ice cubes 🧊---## 👋 How to applyTell us about yourself:

Skills

• Google Cloud
• Node.js
• TypeScript
• Vue.js
• Tailwind