Search jobs

Orchestration & Scale

• Work with the technologies that make large workflows dependable: message and queueing systems, workflow orchestration, job scheduling, retries, idempotency, and backpressure.
• Design for partial failure. Long-running multi-stage pipelines fail in the middle; the interesting engineering is in what happens next.
• Build the observability that makes a slow or wrong run diagnosable — timing, lineage, and intermediate state you can actually inspect.

Agentic Tooling for Essentials

• Build the tooling that lets our agents execute Essentials workflows: data validation and remediation, analysis setup, exception triage, report generation, and the long tail of work that currently requires a human to babysit it.
• Design the harnesses that make agent output trustworthy in a domain where being confidently wrong is unacceptable — evaluation sets, verification steps, constrained tool surfaces, and clear human review points.
• Give agents the context they need to be productive across a large codebase: documentation, schemas, conventions, and project state that stay current.
• Continuously sharpen your own agentic development workflow, and turn what works into practices the rest of the team adopts.

Raising the Bar on the Essentials Team

• Partner with the Engineering Manager and technical leaders to set standards for testing, performance, and agentic practice — and hold the line on them.
• Improve the testing story for a complex service-based architecture: integration and end-to-end coverage that gives engineers and agents fast, honest feedback.
• Mentor through the work — design review, pairing, and code review that leaves the team stronger.

What We're Looking For

• Staff-level engineer. A high-output individual contributor who raises the output of everyone around you with 8+ years of professional hands-on experience.
• Deep experience in complex, distributed, service-based systems — you're comfortable reasoning about failure modes, data consistency, and latency across service boundaries, not just within one service.
• Proven performance and scale work. You've made something big go fast: profiled it, found the real bottleneck, and fixed it without breaking correctness. Experience with large-dataset computation, numerical or statistical workloads, or heavy data pipelines is exactly what we're after.
• Orchestration experience. You've built workflows on message systems, queues, or workflow orchestration tooling, and you know why those abstractions exist.
• Strong across our stack. Python, Go, Node/JavaScript, TypeScript, React, Postgres, and NoSQL stores such as Firebase. You don't need all of them on day one, but you should be genuinely strong in several and unafraid of the rest. Familiarity with caching layers like Redis and the tradeoffs they bring.
• Testing as a first-class skill. Strong end-to-end and integration testing of service-based architectures, with hands-on experience in an e2e framework (Playwright, Cypress, or similar) and a point of view on how to test systems where the interesting bugs live between the services.
• A strong agentic development practice. You use coding agents daily, you tune how you use them, and you build the harnesses that make them reliable — tight test loops, strong CI/CD gates, spec-to-code workflows, and ways of working that produce high-quality output rather than plausible-looking output.
• High autonomy. You can take an ambiguous, high-stakes problem and drive it to a shipped result without being managed through it.
• Cross-team collaboration. You work well across teams and with non-technical leaders, and you can translate technical constraints into business language without dumbing it down.
• Best-practice leadership. You partner with technical leaders to establish standards across the team, and then live by them publicly.

Nice to Have

• Hands-on experience building with AI systems — LLM applications, agent frameworks, retrieval, evaluation harnesses, or model-backed pipelines in production. This is a strong asset for this role.
• Background in statistics, data science, or quantitative analysis — regression modeling in particular.
• Experience in a domain where correctness is non-negotiable and a wrong number carries real consequences.
• Experience working in a large, complex codebase and making it more navigable.

About You

• You like building products people depend on, and you care about the experience of whoever's on the other end — not just whether the pipeline ran.
• You've worked with sensitive data and treat security, privacy, and compliance as part of your job rather than someone else's.
• You've seen customer onboarding up close and know the ways cross-system data flows go wrong in practice.
• You're comfortable in unfamiliar territory — reading a third-party API's docs, tracing a bad record back through a pipeline, and working out what actually happened.
• You want a say in where the platform goes over the long term, and you're eager to grow into that as you learn the domain.
• You are a strong communicator, collaborating effectively with both technical and non-technical teams across levels and functions.
• You assume positive intent, are humble and eager, expect the best from yourself, value partnership over perfection, and provide grace and understanding in stressful situations
• You value a remote work environment and know that it requires greater intentionality on your part to build and maintain strong working relationships
• You are based in Calgary and legally authorized to work in Alberta without need for additional visa support now or in the future.

Why you'll love it here

• 💰 Competitive Compensation. For this role our salary is targeted at $180,000 - $200,000 CAD per year. Final offer amounts are determined by factors such as experience and expertise
• 🏆 Syndio Equity. So you can share in Syndio’s success
• 🏝 20 days annually. We encourage our team to recharge when they need to, plus paid sick & safe time, compassion leave, and voting leave
• 🩺 Additional Private Medical coverage
• 📍 Remote-First (within commuting distance of Calgary) #LI-Remote

Role progression

• In the first month: Ramp on the Essentials codebase, the ingestion → validation → modeling → reporting pipeline, the stack (Python, Go, TypeScript, Postgres, Redis), and the team's agentic development workflow — and, in parallel, form an independent read of where the computation and pipeline are most fragile as datasets grow. You'll contribute at that level rather than through starter tickets. By the end of the month you'll have shipped a meaningful change to a live workflow and shared a written assessment with your manager: the top performance and correctness risks, and where agents can realistically take load.
• By the third month: Own a significant slice of the performance and scalability problem end to end — profiling, finding the real bottleneck, and fixing it (Postgres query plans and indexing, batching and parallelism, caching) without changing what the analysis returns — while troubleshooting failures across service boundaries and designing for partial failure in long-running runs. You'll begin setting technical direction: raising the testing and observability bar, mentoring through review, and standing up the first agent harness with real evaluation gates and human-review points for one Essentials workflow. By this point you'll have delivered a measurable scale or reliability win on a real customer-scale dataset and have an agent reliably carrying part of a workflow.
• Around six months in: Own the architecture that lets the next order of magnitude of data run without a rewrite, and set — not just follow — the team's standards for testing, performance, and agentic practice. You'll drive a high-impact initiative across the AI, Essentials, and Customer Success teams, expand how much of the Essentials workflow agents can carry behind trustworthy eval gates, and mentor other engineers so the whole team's output rises. By six months you're the person the team relies on for how Essentials scales and how agent output is held accountable — measured, as the role defines success, by how much larger and more complex a dataset the team can handle without degrading and how much of the workflow agents carry reliably.

The Interview Overview

Below you'll find an outline of the interview plan for our Staff Software Engineer, Essentials position. Please note that this is what we expect the process to look like; we may ask you for supplemental information or require an additional step before making a final decision.

• 30 min phone call with a member of our Talent Team
• 45-60 min Zoom deep dive with the Hiring Manager
• 90 min Technical Discussion
• Meet the team - 30 min each with 2-3 key stakeholders
• Final interview with Executive Leader

At Syndio, we're building a diverse team that values candor, curiosity, and community. If you share these values and are interested in joining us, we'd love to talk with you even if you don't 100% meet the "about you" listed here. We don't expect anyone to have all the answers, as long as you're willing to learn and grow with us.

Syndio is an Equal Opportunity Employer. We are building an inclusive and collaborative workplace as we grow, and we welcome team members regardless of gender/identity, sexual orientation, race or cultural background, religion, physical disability and age.