Senior software engineer

Back-End / Server Programming Calgary, Alberta, Canada

Profile
Contacts

Summary

Ive been building software for over 11 years, mostly with Java and Spring. Over time, Ive learned that while good code matters, what really counts is building systems that hold up in production and solve real problems for the people using them.

I care a lot about what happens after code is shipped. Thats why I put a strong focus on application monitoring and observability. APM helps you understand how systems behave in the real world and often lets you catch and fix issues before users ever notice.

Im big on clean architecture and avoiding short-term fixes that create long-term pain. I like keeping the bigger picture in mind, making thoughtful decisions early, and helping teams move faster by reducing complexity rather than adding to it.

I also care deeply about how teams think and communicate. Im comfortable asking questions that might sound obvious, because those questions often uncover hidden assumptions, expose alternative approaches, or simply confirm that everyone is aligned. More importantly, they create an environment where people feel safe to ask, challenge, and clarify without embarrassment. In my experience, the best solutions come from shared understanding, not quiet agreement.

I encourage teammates to bring me their challenges, whether technical or product-related, so we can work through them together. And if something doesnt feel right from a user or product perspective, Ill always speak up.

Expectations

Im a senior backend-focused software engineer who enjoys building and evolving systems that actually matter. Most of my work has been around designing, running, and improving production systems where reliability, data integrity, and long-term maintainability are just as important as shipping new features.

Im drawn to complex domains and backend-heavy problems: distributed systems, APIs, data platforms, and event-driven architectures. I enjoy untangling legacy systems, extracting services from monoliths, and shaping clear boundaries in systems that have grown organically over time. I care a lot about observability, performance, and being able to reason about how systems behave in production.

I work best in teams that value thoughtful engineering over noise. I like environments where decisions are discussed openly, trade-offs are explicit, and production is treated with respect. Im comfortable taking ownership of ambiguous problems, influencing architecture, and mentoring through collaboration and example rather than hierarchy.

Im not looking for a management-heavy role or shallow feature work. Im looking for a senior-level role where I can stay hands-on, have real technical influence, and contribute to building software that holds up over time.