Integration Engineer

The Role We're hiring an Integration Engineer to join our engineering team and own the connective tissue between ConstructionClock and the systems our customers already rely on — payroll platforms, accounting systems, project management tools, and more. You’ll play a key, hands-on role in designing, building, and maintaining the integrations that keep data flowing reliably between ConstructionClock and partners like Procore, QuickBooks, and ADP.

You’ll be building integrations that move high-stakes data — payroll, time records, job costs — where silent failures aren’t an option. Reliability, observability, and thoughtful API design matter here.

This role is ideal for someone who takes extreme ownership of the systems they build, thinks deeply about API contracts and failure modes, and enjoys working across the stack to ensure data flows cleanly from third-party sources into a well-designed internal model.

This is a

full-time, in-office role based in Winnipeg, MB , with flexibility for some remote work.

What You’ll Be Doing Integration ownership

API Lifecycle Management:

Proactively monitoring third-party changelogs and API documentation to ensure integrations remain functional as external platforms evolve.

Release Auditing:

Reviewing upcoming releases from partners (e.g., Procore, QuickBooks, ADP) to identify security vulnerabilities or breaking changes before they impact the live environment.

API Service Management:

Managing the full lifecycle of API services, including versioning strategies, rate-limiting, and developer portal maintenance to ensure high availability for integration partners.

Error Handling & Observability:

Implementing robust logging and alerting systems to catch sync failures in real-time, specifically for high-stakes payroll or record-keeping transactions.

OpenAPI Specification & Design:

Authoring and maintaining OpenAPI/Swagger definitions to standardize internal and external integration contracts, ensuring consistency across all service endpoints.

Cross-functional partnership

Cross-Functional Communication:

Serving as the technical bridge between backend systems and frontend teams to manage feature deprecation and ensure "sunsetting" plans are executed smoothly.

Product Collaboration:

Partnering with Product Managers to evaluate the feasibility of new third-party features and designing the architecture to bring those features into your own ecosystem.

What We’re Looking For Experience

5+ years of experience in integration engineering, backend development, or closely related role.

Minimum Bachelor’s degree in Computer Science or a related technical field.

Core craft

Expertise in Web Services:

Deep proficiency with REST, SOAP, and GraphQL APIs, including a strong understanding of authentication protocols like OAuth2 and SAML.

Advanced API Design:

Expertise in OpenAPI (Swagger) standards, RESTful architectural patterns, and designing idempotent APIs that handle retries and failures gracefully. Design of external APIs intended for third party use.

Data & systems

Non-Relational Database Management:

Strong proficiency in MongoDB or similar NoSQL databases, specifically focusing on schema design for diverse third-party data and optimizing aggregation pipelines for reporting.

Asynchronous Processing:

Experience with message brokers and task queues (e.g., RabbitMQ, Kafka, or AWS SQS) to handle high-volume data syncing without slowing down the main application.

Data Transformation & Mapping:

Skill in handling and transforming complex JSON and XML payloads, with a focus on mapping unstructured or semi-structured data into consistent internal formats.

Security & compliance

Security & Compliance:

A firm grasp of web security best practices, including encryption at rest and in transit, and the ability to conduct "least-privilege" API scoping to protect sensitive financial data.

Multi-Tenant Security & Compliance:

Understanding of Tenant Isolation strategies (e.g., logical separation via tenant_id vs. physical separation).

Quality & testing

Comprehensive Software Testing:

Experience implementing a multi-layered testing strategy, including Unit Testing for logic, Integration Testing for API contracts, and End-to-End (E2E) Testing to ensure data flows correctly from third-party sources to internal storage.

Nice-to-Haves

Domain Knowledge:

Familiarity with the specific logic of the industries involved—such as understanding payroll tax calculations or construction project cost codes.

#J-18808-Ljbffr