About the Role: Responsibilities, Skills, and Requirements
Ever wondered what it actually takes to keep a fast-moving tech company running smoothly behind the scenes? We're looking for an IT Operations Officer to be that steady hand — the person who spots a problem before it snowballs, keeps developers and marketers on the same page, and makes sure no customer journey hits a dead end. This isn't a "sit quietly and wait for tickets" kind of role; it's for someone who genuinely enjoys the puzzle of operations and gets a kick out of fixing things properly. Based in Business Bay, you'll be at the heart of a team that ships fast and cares about the details.
About the Company
We're a growing IT company in the middle of Dubai's busiest business district, and we've built a culture around ownership rather than job titles. People here wear a few hats, ask a lot of questions, and aren't shy about flagging something that could work better. The office runs on a mix of developer energy and marketing momentum, which means operations is the glue holding it all together — and we treat that role with real respect, not as an afterthought. Expect a team that celebrates small wins, debugs problems together over coffee, and genuinely has each other's backs when a release day gets chaotic.
What You'll Be Doing
- Act as the bridge between developers and the rest of the business, translating technical snags into clear next steps and chasing them until they're actually resolved.
- Monitor customer journeys end to end — spotting friction points, dropped handoffs, or delays before they turn into complaints.
- Own the support ticket queue: triage, prioritise, escalate, and follow up so nothing quietly disappears into the backlog.
- Coordinate with the marketing team on campaign launches and operational dependencies, keeping timelines realistic and everyone aligned.
- Track KPIs and turn raw numbers into reports that actually tell a story — not just spreadsheets nobody reads.
- Keep communication flowing across teams, because half of operations is making sure the right people know the right things at the right time.
What You'll Bring
Must-haves:
- Solid digital literacy — you're comfortable with ticketing systems, dashboards, and picking up new tools quickly.
- Strong communication skills, both written and verbal; you can explain a technical issue to a non-technical colleague without losing patience.
- A natural problem-solver's instinct: you dig into root causes instead of just patching symptoms.
- Relentless follow-up. You don't let things slide just because someone didn't reply the first time.
- Comfort working across functions — developers one minute, marketing the next.
Nice-to-haves:
- Prior experience in IT operations, support coordination, or a similar cross-functional role.
- Familiarity with KPI reporting or basic data analysis.
- Exposure to customer journey mapping or UX-adjacent work.
Not sure you tick every box? We'd still love to hear from you — plenty of great people here learned half of this on the job.
Why You'll Love Working Here
- A central Business Bay location that's easy to reach and surrounded by the city's energy.
- A team culture that rewards initiative over seniority — if you spot a better way to do something, you'll be heard.
- Real variety: no two days look the same, and you'll build skills across development, marketing, and customer experience.
- Room to grow as the company scales — operations is only getting more important here, not less.
- Supportive colleagues who'd rather solve a problem together than point fingers.
Honestly, if you like being the person everyone relies on to keep things moving, this role will feel like a natural fit. Come help us run the engine room.
Common Interview Questions and Tips
To help you prepare and feel confident, here are some questions you might encounter during the interview process for this role.
- Walk me through how you'd triage a support queue when three tickets all claim to be urgent and you can only escalate one. What factors would actually drive your decision?
- Tell me about a time you spotted a problem before it became a real issue — something that would have slipped past most people. How did you catch it, and what did you do next?
- How would you explain a technical blocker to a marketing manager who's two days from a campaign launch and doesn't want to hear about dependencies? Walk me through how you'd handle that conversation.
- What ticketing systems and dashboards have you worked with, and how quickly do you tend to get comfortable with a new tool? Give me a concrete example of picking one up fast.
- Describe a time you had to chase someone relentlessly to get something resolved. How did you keep the pressure on without damaging the relationship?
- If you were asked to build a KPI report that people would actually read, what would you include — and what would you deliberately leave out?
- Picture this: a customer journey has a handoff between two teams, and things keep falling through the gap. How would you figure out where it's breaking and fix it for good?
- Tell me about a time you dug into the root cause of a recurring problem instead of just patching the symptom. What did you find, and what changed as a result?
- You're juggling a developer escalation, a marketing timeline question, and a frustrated customer — all at once. How do you decide what gets your attention first?
- This role sits between developers and the rest of the business. How do you build trust with technical teams who might see operations as an interruption?
- What does "ownership" mean to you in an operations role? Give me an example of a time you took responsibility for something that wasn't strictly your job.
- We're a small team where people wear several hats and priorities shift fast. How do you stay effective when