1

Coding Scratch Jobs in Vancouver, BC (NOW HIRING)

Define API specs, data contracts, code quality guidelines, and architectural patterns the team ... If you've built something from scratch, you'll recognize this pace. If you've spent time waiting ...

We have video on for our weekly team syncs and pair-coding/tech discussions. Camera is required to ... Builder: We like making things from scratch. We don't need a playbook to start, and we'd rather ...

Showing results 21-24

Coding Scratch information

What is coding scratch?

Coding Scratch refers to programming with Scratch, a visual programming language developed by MIT for beginners, especially children. Scratch uses a drag-and-drop interface where users snap together code blocks to create interactive stories, games, and animations. It helps learners understand basic programming concepts without having to write traditional code, making it fun and accessible. Scratch is used in schools and coding clubs worldwide as an introduction to computer science.

What are the key skills and qualifications needed to thrive as a Scratch coding instructor, and why are they important?

To thrive as a Scratch Coding Instructor, you need a solid understanding of block-based programming concepts, experience with the Scratch platform, and often a background in education or computer science. Familiarity with educational tools like Scratch, Google Classroom, and basic classroom management software is typically required. Strong communication, patience, and creativity help instructors engage students and adapt lessons to varying skill levels. These skills and qualifications are vital for making coding accessible and enjoyable, fostering problem-solving, and supporting student learning outcomes.

What are some common challenges faced by Scratch coding instructors, and how can they be addressed?

Scratch coding instructors often encounter challenges such as engaging students with varying levels of experience, managing classroom dynamics, and explaining complex programming concepts in simple terms. To address these, instructors can incorporate interactive projects, provide differentiated instruction, and use real-world examples to make lessons relatable. Collaborating with other educators and staying updated with new Scratch features also helps create a supportive and effective learning environment.

What is the difference between Coding Scratch vs Coding Python?

AspectCoding ScratchCoding Python
Required CredentialsNone or basic coding coursesProgramming certifications or degrees often preferred
Work EnvironmentEducational settings, beginner projectsSoftware development, data analysis, automation
Industry UsageEducational tools, introductory codingTech industry, data science, web development
Search & Comparison IntentLearning to code, beginner programmingAdvanced coding, professional development

While Coding Scratch is ideal for beginners and educational purposes, Coding Python is used in professional software development and data analysis. Both roles involve programming but differ significantly in complexity, credentials, and industry application.

Infographic showing various Coding Scratch job openings in Vancouver, BC as of August 2026, with employment types broken down into 1% As Needed, 83% Full Time, 10% Part Time, and 6% Contract. Highlights an 78% Physical, 4% Hybrid, and 18% Remote job distribution.

Senior Software Engineer

Vancouver, BC

Full-time

Re-posted 15 days ago


Job description

Downtown Vancouver (On-Site) Full-Time

Here's Your Chance

The dental industry a $40B global market spanning 28 countries still runs on disconnected systems, manual workflows, and decisions made without data. Most of it has never been touched by modern software engineering, let alone AI.

EviSmart is the dental industry's Autopilot. We build the platform that automates the workflows consuming the industry's time and margin and we build it here, in Vancouver. If you want to architect systems that ship to real customers across North America, Europe, and beyond, and you're done with legacy tech and permission-seeking this is the role.

Why EviSmart

  • Exponential growing. 145% year-over-year SaaS growth. The market has validated what we're building.
  • 28 countries. One platform. The dental industry's Autopilot built out of a 675 W Hastings office.
  • Real AI stack. An in-house AI model R&D team building proprietary intelligence not wrappers.
  • Outcome-driven culture. 50% of variable compensation tied to measurable technical outcomes. You own results, not tickets.

Why Now

The Customer Experience Platform is being built from the ground up. No legacy architecture to fight. No design-by-committee. The person who joins now will define the technical foundation and the standards everyone else builds on.

We're at the stage where architectural decisions made this quarter will still be running three years from now. If you've ever wanted to be the person who sets the bar, this is that moment.

From the CEO

"I'm not looking for someone to execute a technical spec handed down from above. I need someone who looks at our system, sees what's wrong, and tells me directly then fixes it. If you've founded something, run an engineering team through growth and hard pivots, and you're ready to stop being the boss and start being the best engineer in the room, I want to talk."

Paolo Kalaw, CEO, EviSmart

What You'll Own

  •  Own the end-to-end technical design of the Customer Experience Platform balancing short-term delivery with long-term scalability ('design for 100x, build for 10x').
  •  Work hands-on alongside 2-3 engineers (30-50% IC) to bring system designs to production-quality reality.
  •  Define API specs, data contracts, code quality guidelines, and architectural patterns the team builds on.
  •  Hold the line on >99.9% uptime and <0.2 critical production issues per release. You're accountable, not just involved.
  •  Partner with Product and UX to translate real customer workflows into maintainable, scalable systems.

What You'll Get

  • Hands-on access to the full AI toolchain: Claude, Cursor, LLM-powered workflows in production, not a sandbox.
  • Direct line to product, design, and the CEO. No layers, no ticket queues between you and the decision.
  • 50% of variable comp tied to measurable technical outcomes uptime, bug density, scalability gains.
  • Collocated squad model: core team on-site in Vancouver for rapid, focused iteration.
  • Clear trajectory: Principal Engineer Staff Engineer, in a company at 145% YoY growth.
  • Competitive compensation with salary range disclosed at offer.

How We Work

We ship before we're 100% certain. We write things down because we have two offices and memory is lossy. We debate loudly and move without resentment. We run weekly sprint rituals planning, standups, demos and we use automated release gates on compliance, security, and reliability so the quality bar isn't a conversation, it's a gate.

If you've built something from scratch, you'll recognize this pace. If you've spent time waiting for sign-off on architectural decisions you'll notice the difference immediately.

The Question You're Probably Asking

"Is this a real technical leadership role or am I going to be executing someone else's architecture?"  Direct answer: you own the architecture. There's no Principal Engineer above you on this product. You'll make the calls, you'll defend them, and you'll live with the outcomes. We give you a squad, a product roadmap, and full accountability. What you do with it is on you.

EviSmart Engineering

What We Need

  • 7+ years in software development, with 3+ years in technical leadership or architecture including hands-on IC time.
  • Distributed systems and modern web architecture: microservices, APIs, event-driven patterns. Not just familiarity you've built these at scale.
  • Cloud platform experience (AWS preferred). Infrastructure-as-code, Docker, Kubernetes, CI/CD pipelines.
  • Strong command of at least one major stack Python, Node.js/React, Java/Spring, or Go. We use Python, Node.js, React.
  • AI/ML integration experience: LLM APIs, agents, embeddings, document intelligence in production.
  • Compliance and security mindset. HIPAA or ISO 27001 experience is a real plus we operate in healthcare-adjacent territory.
  • Track record of designing for scale: systems that grew 10x to 100x without a full rewrite.
  • Strong communicator able to translate architecture decisions for non-technical stakeholders without oversimplifying.

You'll Stand Out If You Have

  • Leader experience you've been the technical decision-maker, not just a contributor to one.
  • B2B SaaS background, especially in retention or customer engagement products.
  • Experience leading migrations data centres to cloud, monoliths to microservices, legacy to modern.
  • Outcome-based engineering performance models. We use them here and we want someone who's already lived this.

About Our Operating Model

We operate on a Squad Model focused on outcomes, not output. Your team is collocated in Vancouver for rapid iteration. Success is tied to business impact uptime, quality, scalability not story points closed. You'll have weekly rituals, direct customer exposure, and automated quality gates. No bureaucracy between you and shipping.

Technology Stack

  • Cloud: AWS or GCP
  • Backend: Python, Node.js, Go
  • Frontend: React (led by UX Engineer)
  • Data: PostgreSQL; future data warehouse integration
  • Infrastructure: Docker, Kubernetes, Terraform
  • CI/CD: GitHub Actions with automated testing