Careers at Growthy

What you’ll own

• Our accounting-system sync layer: QuickBooks Online today.
• Getting outside bookkeeping firms live. You’ll set them up, watch them close real months, and turn what breaks into fixes.
• A weekly written log of what partners hit and what you did about it.

What you won’t own

Our lead developer owns the core product: the close workflow, the categorization engine, the data model, and infrastructure. Our sales lead finds and signs firms. You own the connectors and the partner’s first months on the product. When your work needs a core change, you propose it and the lead developer decides. Clear lines, few meetings.

This is an engineering role.

No sales quota, no support queue. You will talk to bookkeepers, because that’s where the bugs are.

How you’ll use AI here

• AI coding agents write a lot of the first draft. You write the tests that prove it and read every diff before it ships.
• You’ll use AI to read a new ledger API’s docs fast, map its fields, and draft sandbox tests.
• You’ll turn partner call notes into bug reports with AI, then check them against the logs yourself.

You might be a fit if you

• Have shipped a production integration with an accounting, payments, banking, or ERP API and kept it alive.
• Use AI coding tools every day and check what they give you.
• Write clearly and work well async (our lead developer is in Vancouver, BC).
• Like owning a problem end to end.

Bonus

• QuickBooks Online, Xero, or NetSuite API experience.
• You’ve worked in or with a bookkeeping or accounting firm.

How we hire for this role

A short written application, a 30-minute call, a paid trial project on a real integration problem, then a longer interview about your past work and a reference check. We read everything you send, so write your note the way you’d write a pull request description: what, why, and what you tested.

What you’ll do

• Find bookkeeping firms that fit, reach out, and run discovery calls.
• Learn how each firm makes money: clients, staff, costs, and what they spend on software.
• Sign design-partner firms, then paying firms.
• Hand each new firm to our integrations engineer with clear notes on what was agreed.
• Write the playbook as you go.

How you’ll use AI here

• Research firms and draft outreach with AI, then fix every line before it goes out.
• Turn call recordings into notes and next steps with AI. You check the notes against the call.
• Keep the playbook as a living doc, drafted with AI and edited by you.

You might be a fit if you

• Have sold B2B software or professional services and can walk us through real deals, won and lost.
• Know how an accounting or bookkeeping firm works, or have worked in one.
• Like building the pitch, not only delivering one.
• Tell customers what the product can’t do yet.

Bonus

• You’ve sold to accounting, bookkeeping, or CPA firms.
• You’ve used QuickBooks Online.
• You’ve been an early sales hire at a startup.

How we hire for this role

A short application, a 30-minute call, a paid mock discovery call with a real bookkeeping-firm scenario, then a longer interview about your past roles and a reference check. In your note, tell us the best deal you ever lost and what it taught you.

What you’ll do

• Run our website copy, SEO, email, and social for bookkeepers.
• Test channels with a clear goal and a stop date. Keep what works, cut what doesn’t, and write down why.
• Turn customer firms’ results into case studies, with their OK.
• Work next to our sales lead: send them warm conversations, hear what firms say back.

How you’ll use AI here

• AI tools draft, research, and design. You set the brief, edit every line, and check every claim before it ships.
• You’ll use AI to study what bookkeepers search for and ask about, then decide what to make.
• You’ll use AI to speed up testing: more versions, faster reads on what’s working.

You might be a fit if you

• Have owned a marketing channel and can show what moved.
• Write plainly for busy professionals.
• Use AI tools every day and still sweat the details.
• Like trying things and killing the ones that don’t work.

Bonus

• You’ve marketed to accountants, bookkeepers, or small-business service firms.
• B2B SaaS background.

How we hire for this role

A short application with 2-3 work samples, a 30-minute call, a paid take-home (a one-week channel test plan for reaching bookkeepers), then a longer interview about your past roles and a reference check.

What you’ll own

• What the bookkeeper sees and clicks: review screens, flows, in-app copy, and our design system.
• Shipping those features end to end: watch users, design, write the front-end code, release, measure.
• Sitting with bookkeepers while they close a real month, then writing down what slowed them.

What you won’t own

Our lead developer owns the backend: data model, close logic, the categorization engine, APIs, and infrastructure. Our integrations engineer owns the QuickBooks Online connection. When a screen needs a new API, you propose it and the lead developer decides. Clear lines, few meetings.

How you’ll use AI here

• You’ll build features with AI coding agents every day: prototype in code, not only in a design tool.
• AI writes a lot of first drafts. You set the bar, fix what feels off, and check every diff and screen before it ships.
• You’ll use AI to sort research notes and user sessions, then make the call yourself.

You might be a fit if you

• Have shipped product design you’re proud of, and can show what it changed.
• Write front-end code that makes it to production.
• Have strong taste and can explain it in plain words.
• Like cutting a feature down to the part that matters.

Bonus

• You’ve designed finance, accounting, or data-heavy tools.
• TypeScript, React, Tailwind.
• You’ve run user research sessions.

How we hire for this role

A short application with a portfolio link, a 30-minute call, a paid design-and-build exercise on a real review screen, then a longer interview about your past work and a reference check. In your note, name one screen in any product you use that wastes your time, and how you’d fix it.

What you’ll do

• Set up new customers and teach them Growthy, until they close their first client month.
• Be the first person customers hear from when they have a question.
• Write the help-center articles that answer the next person before they ask.
• Every week, tell our engineers and designer what customers hit, with examples.
• Keep an eye on every account’s health. Catch the ones drifting away, and tell our sales lead when a customer needs more.

What you won’t do

Give accounting or tax advice. Our customers are the bookkeepers; how to book a transaction is their call. You explain what Growthy did and why. Sync errors go to our integrations engineer, screen problems to our product designer, and product bugs to our lead developer.

How you’ll use AI here

• AI drafts replies and help articles. You check every answer against the product before it goes out.
• You’ll use AI to spot patterns across questions and turn ten tickets into one fix request.
• You’ll use AI to summarize customer calls, then read the notes against the call yourself.
• Customer data stays inside the tools we approve. No exceptions.

You might be a fit if you

• Have done customer success, onboarding, or support for software or a professional service.
• Know bookkeeping: bank feeds, reconciliations, month-end close.
• Write clearly and kindly.
• Hate answering the same question twice, so you fix it at the source.

Bonus

• QuickBooks Online or Xero from the user side.
• You’ve built a help center or onboarding program.
• B2B SaaS experience.

How we hire for this role

A short application, a 30-minute call, a paid exercise (answer three real customer questions and write one help article), then a longer interview about your past roles and a reference check. In your note, tell us about a customer you kept from leaving.