A few years ago, my workday looked like this — long before I knew this chaos was shaping how I became a Business Analyst.

Late check-ins, angry guests, billing issues, last-minute room changes, and constant coordination across teams.

No requirements.
No sprints.
No Jira.

Just pure operations chaos.

What I didn’t realize back then?
That chaos was quietly training me for IT.

The Pattern I Didn’t See Back Then

Hotels run on systems. Lots of them.

• PMS tools
• Reservation platforms
• Billing engines
• Internal dashboards

Whenever a new system was rolled out, I wasn’t just using it — I was poking it, questioning it, figuring out why it worked the way it did… and then explaining it to everyone else.

That curiosity kept repeating itself.

And slowly, a pattern emerged:

• Why is this workflow designed this way?
• Why does one change break five things?
• Why do users struggle with tools meant to “help” them?

I didn’t know it yet — but I was already thinking like a Business Analyst.

The Moment Business Analysis Finally Clicked

When I discovered Business Analysis, it didn’t feel new.
It felt familiar.

Because BA work is really about:

• Translating messy human needs into something structured
• Mapping processes end-to-end
• Standing between users, operations, and tech — and making sure nothing gets lost

That’s hotel operations… just with better documentation.

Sharajman Technologies: Where the Transition Became Real

Let’s be honest — transitioning into IT isn’t easy.

New language.
New tools.
New expectations.
Imposter syndrome on full volume.

This is where Sharajman Technologies changed everything.

They didn’t just “hire” me.
They invested in me.

Real power-sector projects.
Real clients.
Real consequences.

No sandbox. No training-only bubble.

At Sharajman, I learned how to:

• Extract clear, actionable requirements from vague conversations
• Work inside Agile without losing structure
• Create process flows, user stories, and BA documentation that actually gets used
• Break ugly, complex problems into clean, solvable pieces
• Think like a Business Analyst, not someone “trying to switch careers”

This journey reinforced a key belief that defines how we work at Sharajman Technologies: strong outcomes come from combining domain understanding with structured problem-solving. With the right exposure, mentorship, and trust, individuals can quickly adapt to new domains and deliver meaningful impact on complex projects.

That exposure rewired how I think.

What My Role Looks Like Today

Today, my job is simple — but not easy.
Make sure technology solves real business problems.

That means:

• Understanding user pain before writing a single requirement
• Designing flows that reduce friction instead of adding steps
• Working closely with developers, QA, PMs, and stakeholders
• Making sure features don’t just exist — they work

The funny part?

I’m still using the same core skills I learned in hospitality:

• Communication
• Operational thinking
• Staying calm when things go sideways
• Solving problems under pressure

Only now, I have structure, tools, and frameworks to amplify them.

Same Story. New Chapter.

My journey from hospitality to IT wasn’t clean or predictable.
It was uncomfortable. Confusing. Sometimes scary.

But it was worth it.

I don’t see my past and present as separate careers anymore.
They’re chapters of the same story.

As N. R. Narayana Murthy said,
“Growth is painful. Change is painful. But nothing is as painful as staying stuck somewhere you don’t belong.”