We're always interested in meeting talented people
We are not advertising open positions at the moment. Rather than list roles that do not exist, here is how we work and how to introduce yourself before hiring opens.
Why work at RapidRoot
Small team, real ownership
There is no layer between the work and the customer. Whatever you build, you will see it used and hear directly what it did or did not solve.
Infrastructure problems
Messaging and voice at scale involve delivery guarantees, retries, rate limits and real-time state — engineering problems with correct answers.
Applied AI, not demos
Models are used where they hold up in production: drafting, routing, summarising and transcription with human review in the loop.
We write things down
Documentation, decisions and limitations are published. If you like clear thinking made visible, you will fit here.
The principles you would be joining
- Customer first. Decisions start from the operator using the product at 9am on a busy Monday, not from a feature list. If a change does not make their day easier, it waits.
- Build with integrity. We describe what the platform does today and label everything else as planned. That applies to this website, to sales conversations and to documentation.
- Continuous improvement. We prefer small, frequent, reversible changes over long releases. Shipping steadily keeps quality visible and keeps feedback loops short.
- Security by design. Access, data handling and credential storage are considered while a feature is being designed. Retrofitting security is slower and less reliable.
- Transparency. Roadmap stages, limitations and incident details are shared openly. Customers make better decisions when they know what is real.
- Long-term thinking. Communication infrastructure is something businesses depend on daily. We optimise for durability and maintainability over short-term growth.
Future hiring
As the platform moves from early customers to broader availability, we expect to hire across product engineering, platform reliability, design and customer-facing roles. When a role opens it will be posted on this page with the actual scope, location and process — never as a placeholder.
Introduce yourself
Send a short note about what you have built, what you want to work on and anything we can look at — a repository, a product, a piece of writing. We read everything, and we will tell you honestly if there is nothing available.