Senior Full-Stack Engineer.

About the work

Most of our enterprise engagements run six to fourteen weeks. You will typically own one engagement at a time — sometimes two if one is in maintenance — and you will be the technical lead on the project, not a contributor. That means: you decide the architecture, you scope the milestones, you decide what is in and what is out, and you do most of the actual building. We are not a place where seniors hand specs to juniors and review pull requests all day.

Typical projects in the last twelve months: a custom CRM for a healthtech startup (Node + Postgres + React, deployed to AWS), an internal compliance dashboard for a logistics client (Python backend + React frontend), and a pricing engine + API replacement for an e-commerce client.

What you'll actually do

• Lead a discovery week with a new client: understand the problem, write the proposal, scope honestly.
• Design the system. We do not have a fixed stack religion — you choose the stack that fits the work and is one we can maintain.
• Write most of the production code yourself, in a codebase that other engineers (us) will read after you.
• Be the voice on weekly client calls. We do not have account managers; the engineer is the relationship.
• Hand off cleanly — runbooks, docs, the works — when an engagement closes.

What you bring

• Six-plus years shipping production software, including at least two years where you were the senior on the project.
• Strong working knowledge of at least two of: Node/TypeScript, Python, Go. We default to TypeScript for new web work.
• Comfort with Postgres at production scale. You should be able to write a query plan, add an index where one belongs, and explain why most ORMs lie to you about performance.
• Modern React (hooks, server components or equivalent SSR experience). Tailwind / CSS literacy.
• Worked with AWS directly (not just through a PaaS). At a minimum: ECS or Lambda, RDS, S3, CloudWatch.
• Written English good enough to draft a clean technical proposal and run a client call without a layer in between.
• Eligible to work in Canada. We sponsor for senior roles when there is a clear fit, but we are not running an immigration shop — please be honest about your status in your application.

What we are not looking for

• Heavy specialists in one framework. We change stacks per project; people who define themselves by their framework tend to be unhappy here.
• Engineers who want to manage. We have one part-time PM and intentionally no engineering managers. If your career goal is to manage people, we are the wrong place.
• "Move fast and break things" as an identity. Our clients are running real businesses. Move thoughtfully and ship working things.

How we interview

The process is three steps, usually within two to three weeks. We do not believe in tech-screen gauntlets.

• Conversation (45 min) with the founder. Background, what you are tired of at your current job, what you want next.
• Paired technical session (90 min) with one of our engineers. We send you a real problem we have actually solved, and we work through it together on a call. No leetcode, no whiteboarding, no take-home homework on your weekend.
• Reference and closing call. We check two references, we answer every question you have left, we make an offer or we explain why not. Either way, you hear back within a week of the last step.

Benefits, plainly

• Compensation as listed above. We do not negotiate salary based on what you used to earn; we pay the role.
• Hybrid: two days a week in our Concord office or fully remote within Canada. Most of the team comes in Tues / Wed.
• Four weeks paid vacation, plus the week between Christmas and New Year's, which is closed.
• Standard Canadian health and dental, after three months.
• Equipment of your choosing, within reason. We are not going to argue about a keyboard.
• An annual learning budget of $2,500 with no template for how to spend it.

If this sounds like the kind of work you have been looking for, send an email to careers@startpro.ca with a short note, a CV or LinkedIn, and a link to one piece of code or one project you would defend in a conversation. We read every application personally.