Integration Engineer

About the role

The Engineering group hires a resourceful Integration Engineer in Vancouver to support platform growth. Configuration for enterprise customers matches specific workflow needs while tracing and fixing bugs and building new integrations. The role targets an individual who will influence company success within a growing startup.

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

Complex integration configurations are created for enterprise customers to match workflow needs and support electrical contractors and distributors as they streamline purchasing processes.

Troubleshooting resolves customer ticket integration issues to maintain reliable software operations that serve electrical contractors and distributors across the nation.

Updates to existing code improve integrations so the software handles multiple workflows efficiently for two applications within one software platform.

Code peer review maintains quality and consistency across the codebase while catching issues early and sharing knowledge among engineering team members.

Documentation for existing and new integrations is created so internal and external users understand system capabilities within the procurement and tool management software environment.

Requirements

Python experience of 1+ years writes and maintains integration logic to work with various software systems in the cloud platform.

SQL technologies experience of 1+ years queries and manages data effectively to support operations for electrical contractors and distributors.

A Bachelor's Degree in Computer Science, Software Engineering or related degree proves foundational training to ensure readiness for complex integration tasks.

Familiarity with Git & Docker manages version control and containerized environments to support the cloud-based platform delivery model.

A client service mentality, adaptability, and open collaboration with other functions address customer needs and serve contractors and distribution experts located coast to coast.

Ownership in your work drives initiatives forward and maintains accountability to advance technology adoption in the construction industry.

Basic accounting working knowledge understands financial workflows and integrations to improve communication between procurement software and contractor accounting systems.

Practical notes

The role is full-time and based in-person Downtown Vancouver. Remote work options are not indicated in the listing. The Vancouver-based team collaborates with industry leaders to refine software workflows.

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

General engineering roles in this field rely on tools such as Git and Docker for version control and containerization.

Proficiency in Python and SQL is commonly required for integration work within construction industry software.

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.