Software Engineer (Full Stack)

About the role

This role builds and launches product features for a SaaS startup transforming construction procurement. The team delivers tools that connect contractors and distributors and streamline operations. You solve real problems and own features that reach users directly.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Product decisions shape features that address contractor and distributor needs in construction workflows.

Bugs are hunted and fixed so the user experience remains seamless as the platform grows.

Customer issues are troubleshot and resolved to keep procurement and operations running smoothly.

Code reviews participate in to uphold quality and spread knowledge across the engineering team.

Systems and APIs integrate to expand what the product can do for distributed teams in the field.

Work documents so teammates can learn, maintain, and extend the codebase over time.

Knowledge grows continuously through mentorship, collaboration, and exposure to new tools in a fast-moving environment.

Requirements

Python and Django or similar stack provide the core backend experience for the platform.

REST APIs work with for at least 2+ years to connect services and data.

SQL databases hold knowledge solidly for storing construction and procurement data.

SaaS or startup experience shapes how you operate in a fast-moving product culture.

Web technologies and full stack development skills connect frontend needs with backend behavior.

Git and Docker familiarity supports daily workflows, with bonus experience in hybrid or remote settings.

Networking basics understanding helps integrate services and diagnose issues across distributed systems.

A customer-first mindset drives problem solving and ties solutions to real user outcomes.

Ownership of your work shows in how you contribute, collaborate, and follow through with the team.

Practical notes

This is a full-time role based in Vancouver at 333 Seymour Street with hybrid arrangements.

Potential travel may occur to engage with customers and partners in the construction sector.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The role centers on full stack development in a SaaS setting focused on construction industry workflows.

Common tools include Python, Django, REST APIs, SQL databases, Git, and Docker.

Expect fast-paced collaboration with direct exposure to product decisions and user impact.

Team culture emphasizes ownership, mentorship, and problem solving for underserved markets.

Growth paths rely on continuous learning and hands-on contributions to a mission-driven platform.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.