Software Engineer, Business Systems

Hands-on cloud experience (GCP preferred; AWS or Azure is fine) with a working understanding of how to compose services rather than follow a tutorial

End-to-end ownership you can point to — a system you designed, built, shipped and then operated. Something that broke in production and you fixed it.

Debugging across system boundaries — when two systems disagree about the same record, you can work out why

Testing and verification instinct — you know your output is correct because you measured it, not because it ran without erroring

Fast on unfamiliar ground — you have picked up a stack you didn't know and shipped it. This matters more to us than prior exposure to any specific technology.

Clear written communication — design notes, runbooks, and documentation are part of the job, not an afterthought