01
Make knowledge dependable.
Turn messy websites, files, FAQs, and products into answers a team can inspect and improve.
Careers at BoundBot
Build the systems behind the conversation.
Work on practical AI, customer operations, and the product details that turn a promising demo into a dependable tool.
B
3 conversations openBoundBot roles
Build what comes after the chatbot
ROLEAREA
Full Stack Developer
View role brief
Engineering
Customer Success Manager
View role brief
Customer Success
Digital Marketing Manager
View role brief
Marketing
01
Real product
02
Clear ownership
03
Visible impact
Engineering
Build the system
Success
Make it useful
Marketing
Make it clear
One team
Share the signal
The work
Problems that reach the customer.
Every role touches the same operating question: how do we make AI useful without making the system harder to trust?
02
Make channels feel like one system.
Keep WebChat and messaging conversations consistent without erasing the rules of each provider.
03
Make automation predictable.
Design the path from an incoming question to a rule, action, lead, order request, or handoff.
04
Make human control obvious.
Give teammates the history, source, and controls they need when judgment should lead.
How we work
Follow the real path. Make the next step clear.
Good judgment shows up in the way a problem is traced, framed, shipped, and explained—not in how complicated the solution sounds.
Trace the real path.
Follow the message, request, source, or customer state before deciding what the product should do.
Make the system legible.
The user should understand what happened, why it happened, and what they can do next.
Ship the smallest complete truth.
A focused workflow that works is better than a broad promise held together by placeholder screens.
Treat boundaries as product.
Permissions, provider policies, human judgment, and missing data belong in the experience—not the fine print.
One build loop
From signal to shipped learning
01
Observe
Start with a real customer or teammate problem.
02
Frame
Separate the root path from the visible symptom.
03
Build
Ship the working surface and its boundaries.
04
Learn
Use the next real conversation as feedback.
The pace of the work
Observe. Build. Learn. Repeat.
The loop crosses product, engineering, customer conversations, and go-to-market. Different roles enter at different points; everyone keeps the signal moving.
Evidence beats theater
Show what changed for the user, the system, or the business—not only what shipped.
Open roles
Three ways to shape the same product.
01
ENGINEERING
Full Stack Developer
Build product surfaces across Next.js, NestJS, messaging infrastructure, billing, and the systems that keep conversations moving.
Product UIAPIs and servicesChannel reliability
Apply by email 02
CUSTOMER SUCCESS
Customer Success Manager
Help teams launch, tune, and operationalize agents in real support, sales, knowledge, and handoff workflows.
Agent rolloutWorkflow designCustomer feedback
Apply by email 03
MARKETING
Digital Marketing Manager
Translate product reality into clear positioning, useful content, and demand from teams exploring practical AI operations.
PositioningContent systemsDemand experiments
Apply by email What to send
Make the first email useful.
A clear example of how you think will tell us more than a perfectly polished generic application.
- 01
Choose the problem space.
Tell us which role fits how you think and the work you want to own.
- 02
Show one real piece of work.
A shipped project, decision memo, campaign, workflow, or customer outcome is more useful than a long adjective list.
- 03
Explain your judgment.
Share the tradeoff, constraint, or difficult call behind the result.
- 04
Start the conversation.
Email hello@boundbot.com with the role in the subject line.
Before you apply
The honest answers we can give here.
Role-specific terms belong in the actual conversation, not in guessed copy on a careers page.
Are these the roles currently open for conversation?
Yes. The listed Engineering, Customer Success, and Marketing roles are the areas where we are currently inviting applications and conversations.
What should I include in the first email?
Include the role, a concise introduction, one relevant example of your work, and a short note on the judgment or tradeoff behind it.
Can I apply if my title does not match exactly?
Use the closest role and explain the problem space you are strongest in. Clear evidence and judgment matter more than copying the title word for word.
Where are compensation, location, and employment details?
Those details are not published on this page. Ask for the role-specific terms in your email so the conversation stays accurate.
Bring one real piece of work.