Summary
✨ AI‑Generated
Become the first dedicated product engineer at a small, profitable, globally oriented organization and build its core internal software from the ground up. You will deeply understand how the business operates, determine what should be built, design the information architecture, develop and ship the product, and support it as the organization evolves. Over time, the role may grow into leading a small product and engineering team.
Highlights
Rare founding-engineer opportunity with end-to-end ownership of an internal product. You will shape the product from business discovery and information architecture through development, launch, support, and future team growth, with potential to lead a small team later.
Description
About the role:
We're a small, proudly Canadian based globally facing, female run, profitable, investor free, business that runs on a handful of spreadsheets, inboxes, and one-off documents.
We want to replace that with software we own — a single internal product that becomes the system of record for how the business runs.
You'd be the first and only person doing this work.
You'd talk to us about how the business actually operates, design the tool, build it, ship it to our team, support it, and grow it as we grow.
This is an interactive project that will bend and grow with us.
This is a hands-on builder role that requires a lot of listening and information architecture before building.
Over time it can grow into leading a small product/engineering team, but for the first 12–24 months you are the team, this is not currently a manager role.
What you'll do:
- Sit with the people doing the work.
Learn the business end-to-end.
Decide what to build before deciding how to build it.
- Design the product — information architecture, screens, workflows.
We don't have a designer; you have taste and own the UX.
- Build it as a real web application: data model, backend, frontend, auth, reporting, email, integrations.
Modern, pragmatic,boring-where-it-should-be-boring tech.
- Ship to a handful of internal users first.
Watch them use it.
Fix what's wrong.
Add what's missing.
- Run it in production.
Deployments, backups, monitoring, the occasional 11pm "it's broken" call.
(this is the exception not the rule!) You own uptime.
- Document enough that the second hire (eventually) can pick up where you left off.
- Make architectural choices today that won't trap us when we have 10x the users, customers, or integrations.
What we're looking for:
-Must have at least 5 years experience with Ruby on Rails, Hotwire, Postgres, Tailwind, and Docker-based deploys (Kamal, Fly, Render, etc.), or another similarly pragmatic full-stack toolkit (Django, Laravel, Phoenix, Next.js + Postgres).
-Must have a strong familiarity with the content creator / influencer / talent management space.
-A team player that loves AI and sees a work-friendly AI future that is iterative
-An A+ communicator; we can solve anything as a group!
-Experience using AI to build commercial web apps, and/or experience shipping production web apps end-to-end (or the product/build equivalent).
You've built and operated something real, not just contributed to a slice of someone else's.
-Full-stack and comfortable with all of it: data modelling, backend, frontend, basic devops/deploy.
Bias toward fewer, well-chosen tools over a sprawl of frameworks.
-Strong product instincts.
You can take a vague business problem and turn it into a workable design.
You push back when a request is the wrong solution.
-Strong design sense for internal/business software.
Doesn't need to be flashy; needs to be clear, fast, and respectful of the user's time.
-Comfort working directly with non-technical stakeholders.
You can explain trade-offs in plain language and you don't wait to be told what to do.
-Operational maturity: writes tests where they matter, thinks about data integrity, doesn't ship things they can't roll back.
-Comfortable being the only engineer.
You enjoy it; you're not waiting for a team to validate every decision.
Nice to have:
-Prior experience building internal tools or CRMs for SMBs.
Not required:
- A CS degree.
- Experience at a large tech company.
Most of the relevant skills here aren't taught there.
- Knowledge of our specific stack on day one — taste and judgment matter more than which framework you used last.
How we'll work together:
- Weekly working session with the owner to review what shipped, what's next, and what we're learning.
- You decide the stack, the architecture, the release cadence.
We decide the priorities together.
- Small users, fast feedback.
Expect to ship something usable within the first 4–6 weeks.
What success looks like:
-Most day-to-day functions run through software you built.
You tell us what the 30/60/90 plan is.
Working Terms:
-Full Time, Permanent
- Remote-friendly, our pref is a time-zone between EST and PST.
-Occasional in-person time with the team
- Unlimited vacation
-Access to the tools you want not the ones we have or think you should have
