Position: Permanent

Work Environment: Hybrid (3 days in-office)

Location: Calgary

Position Overview

Hammehr invites applications for the role of Solution Architect on behalf of our client for a full-time permanent opportunity. Your job is to help untangle and rebuild the systems that quietly keep a large operation running, sometimes by designing them and sometimes by diving into the code yourself. The company’s goal is to make everyday housing logistics feel simple for tenants and staff, even when the tech behind it is anything but. It’s a place where you’ll be trusted to find your own way forward, but that also means walking into some gray areas: half-finished projects, missing documentation, and systems that only break when no one’s watching.

What You’ll Do

• Write and refactor code that keeps core systems running without drama
• Pair up with developers to sort through legacy logic and find clean exits
• Sketch out architecture ideas in working sessions that move from whiteboard to code fast
• Jump into undocumented systems when something breaks and no one else knows why
• Review pull requests with empathy and an eye for long-term sanity
• Talk through trade-offs with stakeholders who care about outcomes, not acronyms
• Look for the simplest fix that won’t become tomorrow’s tech debt
• Help the team make architectural calls without turning every meeting into a debate

Basic Qualifications

• 8+ years of hands-on software development experience, so you can dive into real code, not just talk architecture
• 2+ years designing service-based or distributed systems that can survive change, scale, and surprise
• Experience working on legacy systems where your ability to read between the lines mattered more than the documentation
• Familiarity with C#, React, and TypeScript in production environments so you can contribute without slowing the team down

Preferred Qualifications

• You’ve worked in complex operational environments where uptime mattered more than elegance
• Experience modernizing large, brittle systems without breaking the parts that still work
• You’ve used domain-driven design or event-driven architecture to make things easier to change later
• You’ve helped coach or mentor developers and know when to speak up and when to step back
• Experience with customer-facing portals, CRMs, or internal tools where small bugs had big consequences

The Challenges

• Some systems only make sense once you’ve broken them and put them back together
• There’s no documentation for the weirdest edge cases, and yet they still affect real users
• You’ll be expected to make architectural decisions before everything is fully scoped or agreed on

Your Impact

• Help the team trust their systems enough to move faster and ship more often
• Turn frustrating legacy workflows into tools people are glad to use
• Make architectural decisions that quietly prevent problems no one will ever see