Skip to content

Join the Team

Grow with us from Miramichi

Our Culture

As a company proud of its Miramichi roots, we foster a collaborative environment inspired by the close-knit spirit of our community. We value curiosity, a strong work ethic, and a relentless drive for excellence. If you're passionate about technology and want to make a real impact from Atlantic Canada, you'll feel right at home.

What this actually is

  • check_circleEarly, and small: You would be working directly with the founders, not three layers below them. What you build is yours to own end to end.
  • check_circleYou grow as it grows: This is a business being built, not a seat being filled. The people who join early shape what it becomes.
  • check_circleReal systems, real users: Automation that runs unattended in somebody’s business. Nothing here is a prototype nobody uses.
  • check_circleRemote or here in Miramichi: Whichever suits the work and suits you.

And plainly: this is a startup. There is no benefits package, no development budget and no HR department — because there is no pretending there is one. If that is the wrong stage for you right now, that is a completely reasonable answer, and we would rather you knew before writing to us.

Open positions

Nothing open right now — and we still want to hear from you

We are a small team and we are not hiring at this moment. We would rather say that plainly than list a role that does not exist and take an hour of your evening for a covering letter nobody was going to read.

That said: good engineers are hard to find and we are always interested. If you build things that hold up when nobody is watching them — automation people actually use, systems that fail loudly instead of quietly, code somebody else can pick up — send us something. We read everything that arrives.

What is useful to send: a short note about something you built and what was hard about it. A repository, a demo or a description are all fine. A CV on its own tells us much less than one paragraph about a problem you solved.

What happens next: a real reply from a person, not an automated acknowledgement. If something opens up that fits, you are the first conversation we have — and if we know someone else hiring for what you do, we will say so.

What you would actually work on

Not a stack list. The kinds of problem that come through the door, and how much of each we have already done.

  • 55Databases and recordsOne place the records actually live, so two departments stop keeping different versions of the same list.
  • 50Web portals and internal sitesAn internal site your staff or your customers use, rather than another shared drive.
  • 30Running AI on your own hardwareReplacing per-seat AI subscriptions with equipment you own
  • 18Reading documents and formsInvoices, forms, statements and reports read into fields you can search, instead of retyped.

Small team, real systems, and work that runs unattended in somebody's business. Nothing here is a prototype nobody uses.