Reporting pipeline, the stack (Python, Go, Type Script, 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 Developer, 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 Team45-60 min Zoom deep dive with the Hiring Manager60 min Technical DiscussionTake-home assignment60 min technical interview with a senior engineer to walk through your solution60 min architecture and design discussion30-min final interview Product ExecutiveAt Syndio, we are 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 cooperative workplace as we grow, and we welcome team members regardless of gender/identity, sexual orientation, race or cultural background, religion, physical disability and age.#J-18808-Ljbffr

📌 Staff Software Developer, Essentials (Calgary)
🏢 Syndio
📍 Calgary