Build AI that runs on real
contact center floors.
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.
across 2 cities
code will touch
using what you ship
Fusion CX network
Why build here
instead of the other places?
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.
Reason 01
Your code ships to real production on day one.
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.
Reason 02
You get operator context most engineers never do.
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.”
Reason 03
Backing of a large BPO parent, not a runway clock.
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.
Reason 04
You'll work across regulated industries, not just marketing tech.
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.
Open positions.
Five roles open right now across engineering, customer success, and implementation. Both India offices actively hiring.
Full Time
Job category
Engineering
Full Time
Job category
Customer Experience
How we hire
Three things we look for.
Operators first, technologists second..
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.
Ship quality, then ship more.
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.โ
No superstar culture.
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.
What we offer
The fine print.
Compensation, benefits, and the boring-but-important stuff. We prioritise the things that actually matter over the things that photograph well on Instagram.
Compensation
Market-leading pay.
Health & wellbeing
Comprehensive cover for family.
Health insurance for you, your spouse, your children, and your parents. Mental health support. Annual health checks. No surprise exclusions.
Learning
A library budget, not a corporate LMS.
Time off
Real vacation time, actually taken.
Generous annual leave, sick days, and parental leave. Managers actively push people to take breaks. No unspoken “bad optics” about being off.
Hybrid
In-person for what needs it.
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.
Travel
See our global sites, up close.
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.
The process. No games.
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.
01
Apply
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.
02
Intro call
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.
03
Skills round
Role-specific. For engineering: a short technical conversation plus a realistic take-home (not a LeetCode puzzle). For CS roles: a scenario walk-through.
04
Team meet
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.
05
Offer
We move fast on offers when we’re confident. References, formal offer, start-date conversation โ usually within a week of the team meet.
Didn't see the right role?
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.