Omind isn’t a lab. Our code runs inside Fusion CX operations every day — 20,000+ employees, 41 delivery locations, millions of customer conversations. If you want to ship AI that gets pressure-tested in production the day after release, not left in a demo environment, we’re hiring.
We’re not going to pretend we’re Silicon Valley with pool tables and stock options. Here’s what we actually offer that most AI shops can’t.
Most AI engineers never see their work run at enterprise scale. Here, your voicebot dials a real customer on Tuesday. Your QA model scores 10,000 calls before Friday. We don’t have a “demo environment” problem — we have 20,000 people on live floors who will tell us within hours if something’s broken.
Sit next to a contact center supervisor for a day. Listen to what an AHT spike actually sounds like. Watch a QA team argue about a scorecard. We build software for people we can literally walk over to. That proximity to real users is the thing most AI startups have to fake with “customer research.”
Fusion CX has been running operations since 2004. That means we’re not one funding round away from shutting the product down. We’re building for the long horizon — multi-year customer relationships, real compliance frameworks, categories we expect to matter a decade from now.
BFSI compliance frameworks. HIPAA-covered healthcare deployments. RBI-regulated collections. PCI-compliant processing. This isn’t “move fast and break things” territory — this is “your code has to defend itself in an audit.” Which is harder, rarer, and more interesting engineering.
Five roles open right now across engineering, customer success, and implementation. Both India offices actively hiring.
We hire people who’ve either been in a contact center, supported one, or can walk into one and understand what’s going on within a day. If you’ve spent your career on pure SaaS without touching the back office of a real operation — you’ll have to do some unlearning. If you’ve been deep in BPO, CX, or enterprise support — you’ll be right at home.
We care about velocity, but not at the expense of the audit trail. Our customers are BFSI compliance officers and HIPAA-covered healthcare organisations. A broken deployment isn’t a missed sprint — it’s a regulator letter. We hire engineers who know the difference between “it works on my machine” and “it defends itself in production.”
The work here is cross-functional by default — engineers sit with implementation teams, implementation teams sit with contact-center supervisors, supervisors write tickets. If you need heroics and solo ownership to feel valuable, this probably isn’t the place. If you’re motivated by working alongside people who know operations cold, you’ll thrive.
Compensation, benefits, and the boring-but-important stuff. We prioritise the things that actually matter over the things that photograph well on Instagram.
Health insurance for you, your spouse, your children, and your parents. Mental health support. Annual health checks. No surprise exclusions.
Generous annual leave, sick days, and parental leave. Managers actively push people to take breaks. No unspoken “bad optics” about being off.
Most roles are hybrid with 2-3 days in the office. Some roles require full on-site presence because the work is inherently collaborative with contact-center teams. We say which upfront.
Deployments and customer visits take engineers to US, UK, APAC offices. Bangalore engineers have visited Manila, Kolkata deployments, and US client sites. Your passport will see some use.
Five steps. Roughly four weeks end-to-end. We tell you the steps upfront so you can plan. We commit to response times on our end.
Send us your CV and a short note on which role you’re interested in and why. Generic applications get polite responses — thoughtful ones get fast ones.
Thirty-minute conversation with our hiring lead. You ask us questions, we ask you questions, we establish whether there’s a real fit before going further.
Role-specific. For engineering: a short technical conversation plus a realistic take-home (not a LeetCode puzzle). For CS roles: a scenario walk-through.
You meet the people you’d actually work with. We show you what we’re working on this week, you show us how you’d approach it.
We move fast on offers when we’re confident. References, formal offer, start-date conversation — usually within a week of the team meet.
We’re often hiring for positions that haven’t been posted yet. If you’d fit somewhere in the operator-first model — send a note with your background and what you’d want to build here.
