Remote-first, not remote-tolerated
There is no headquarters that everyone else dials into. Decisions get written down so the team is not split between people in the room and people on a call.
Chatoly is a remote-first team building AI support that answers from real business knowledge and knows when to hand a conversation to a person. If that problem interests you, we would like to hear from you.
How we hire
One short form. No portal, no account, no black hole.
Every application lands in an inbox a person reads. You will hear back either way.
Open roles
Every role is fully remote. Each listing states the regions we can hire in and the timezone overlap the work needs.
Own features end to end across the Chatoly dashboard and marketing surface, from the data model through to the interface support teams use every day.
Own the part of Chatoly that decides what the assistant knows and whether it should answer at all. Retrieval quality and confidence scoring are the product, not a layer on top of it.
Build the APIs, webhooks, and billing plumbing that everything else at Chatoly depends on, with the reliability a customer-facing chat product requires.
Own the embeddable widget that runs on our customers' websites. It has to be fast, accessible, and impossible to break, on sites whose code we do not control.
Build and maintain the connections into Shopify, WooCommerce, Slack, Zapier, and the help desks our customers already run their business on.
Keep Chatoly available and fast. Our customers put us on their storefronts, which means our downtime shows up on their revenue pages.
Build the test coverage that lets a small team ship quickly without breaking customer conversations, including the harder problem of testing AI behaviour.
Turn conversation data into the reporting customers use to justify the spend, and the internal numbers we use to decide what to build next.
Decide what Chatoly builds next, grounded in real customer conversations rather than a feature request spreadsheet sorted by vote count.
Design the workspace where support teams manage AI conversations, and the chat experience their customers see. Both have to feel calm under pressure.
Own Chatoly's documentation. Most support tickets are a documentation problem, and good docs are the highest-leverage thing we can write.
Own organic growth across a large, multilingual site, including how Chatoly shows up in AI-generated answers rather than only in blue links.
Write the guides and playbooks that help support and ecommerce teams launch AI safely. Useful content, not keyword filler with a call to action bolted on.
Own Chatoly in Arabic, French, Spanish, and Chinese, across the product, the site, and the assistant itself. Translated is not the same as localized.
Own paid acquisition end to end, with real accountability for what each channel costs and what it actually returns.
Own the journey from signup to active customer. Most trials fail at setup, and lifecycle marketing is how we fix that at scale.
Start conversations with support and ecommerce teams who have a real automation problem, and qualify honestly enough that the pipeline means something.
Own deals from qualified conversation through to signature, with a consultative approach that suits a product buyers can evaluate themselves.
Make sure customers reach real outcomes with Chatoly, not just a successful install. Retention here is earned through results rather than check-in calls.
The technical counterpart in sales and onboarding. You prove Chatoly fits a customer's stack, then make sure the first deployment actually works.
How we work
Remote work fails when it is bolted onto an office-shaped company. These are the tradeoffs we have made deliberately, including the ones that will not suit everyone.
There is no headquarters that everyone else dials into. Decisions get written down so the team is not split between people in the room and people on a call.
Meetings are the exception. We keep a small overlap window for real-time conversation and leave the rest of the day free for focused work.
Proposals, tradeoffs, and postmortems get written up. It is slower in the moment and much faster over a quarter.
You will own whole problems rather than tickets, and you will talk to customers directly. That suits some people and frustrates others.
Hiring process
Five steps, and we tell you where you stand at each one. If you are not a fit, you will get a clear answer instead of silence.
Fill in a short form with your CV or LinkedIn, where you are based, and a few lines on why the role fits. It takes about five minutes.
A 30 minute conversation about your background, what you want to work on, and how the team actually operates day to day.
A short, paid, realistic task close to the work itself. We do not ask for unpaid project work or multi-day take-home assignments.
You meet the people you would work with, ask hard questions, and see how decisions get made before you commit.
We move quickly once we are confident. You get the full picture on scope, compensation, and expectations in writing.
Nothing matching?
If none of the roles above fit but you think you would be valuable here, tell us what you would want to own.