Skip to content
Adaptability

Different environments. Same ability to adapt.

Adaptability isn't simply being comfortable with change. It's entering an unfamiliar environment, understanding what matters, learning quickly, and finding a way to contribute.

I don't need to know everything before I begin. I need to know how to understand the environment.

How I approach the unfamiliar

Three habits that travel with me

Read the room first

Every environment has its own rhythm — a village pipeline site, a drone lab, a support queue. The fastest way in is to watch how work actually happens before changing it.

Reduce the unknown

Unfamiliar problems get smaller when you split them into what you can test and what you have to ask about. Thirteen years of diagnostics taught me to narrow before I fix.

Make it repeatable

A fix that only works once isn't finished. SOPs, tracking systems and KPI visibility are how a personal solution becomes an operating system other people can run.

Carry the transferable part

Tools change between industries. Judgement, structure and care for the person on the other side don't.

Career transitions

Each move carried something forward

The environments changed; the transferable part didn't.

  1. 01

    Graphic Designing

    Design gave me the habit of shaping how something is understood, not just how it works.

  2. 02

    IT Support

    Support work is structured curiosity — narrow the problem, then fix the cause.

  3. 03

    Operations Management

    Operations turned individual fixes into repeatable systems.

  4. 04

    AI Enablement

    Enablement sits between the technology and the humans who need it to make sense.

  5. 05

    Customer Support

    Talking to customers is the fastest way to learn what a product really is.

  6. 06

    Entrepreneurship

    Ownership pulls every other skill into one place at once.

  7. 07

    Online Business

    Online ventures rewarded design, iteration and measurement.

  8. 08

    Offline Business

    Offline ventures rewarded operations, timing and face-to-face trust.

Case studies

Situation → Challenge → Adaptation → Outcome

Each story follows the same four questions: what changed, what made it difficult or unfamiliar, what I learned or approached differently, and what became possible because of it.

  1. 1. Situation

    After the Indian Hume Pipe position was eliminated in July 2021, I moved from water-supply infrastructure into aviation — joining Flytech Aviation Academy in Oct 2022 as an RPA Technician & Lab Instructor.

  2. 2. Challenge

    The domain was new: DGCA-aligned procedures, drone assembly and disassembly, simulators, calibration and crash response — and I had to teach it, not just learn it, to 22+ students.

  3. 3. Adaptation

    I treated the airframe like any other system I had supported for 13 years: break it down, map failure modes, document resolution paths, and coordinate lab, simulator, field-training, maintenance and documentation workflows into one schedule.

  4. 4. Outcome

    78% technical certification pass rate, 84% fleet readiness, 70% less drone downtime and a 64% increase in training efficiency over 6 months. I also earned a DGCA Remote Pilot License (Small Category, VLOS).

Skills transferred

Systems TroubleshootingTechnical TrainingDocumentationField OperationsPreventive Maintenance

The confidence to enter unfamiliar territory

The confidence doesn't come from believing I already know the answers. It comes from trusting my ability to understand the system.

That is a quieter kind of confidence. Less dependent on already being an expert. More dependent on observation, curiosity and learning.

Achievements

What happened along the way.

Achievements are useful markers, but they are not the whole story. Verified milestones, recognition, certifications and measurable outcomes appear here — nothing is listed until it's real.

Jan 2023 – Jan 2033

Remote Pilot License — Small Category (VLOS)

Licensed remote pilot for small-category drones under visual line of sight.

Date to be added

Google APAC Gen AI Academy

Applied Generative AI programme covering Gemini and Vertex AI foundations.

Date to be added

Build with AI Bootcamp, Hyderabad

Hands-on bootcamp building with Google's generative AI tooling.

Date to be added

Project Management with Microsoft Copilot

AI-assisted project planning, tracking and reporting practices.

Date to be added

Zendesk Customer Service Professional Certificate

Professional certification in customer service operations and tooling.

Date to be added

Customer Success Foundations Professional Certificate

Foundations of customer success practice and lifecycle ownership.

Date to be added

Essential Skills in Adobe Photoshop 2025 Professional Certificate

Professional certification in current Adobe Photoshop workflows.

Date to be added

Everyday AI Concepts · AI Literacy for Everyone

Foundational AI literacy training used to support enablement work with non-technical teams.

Date to be added

Leading Teams as a People Manager

Team leadership training applied while managing a 12-member cross-functional team.

Date to be added

Building Resilience

Resilience training taken during a period of concurrent employment and venture building.

Date to be added

Independent Travel Manager Certification

Certification in independent travel management.

Date to be added

Google Fi Telecommunications Workflow & Support Infrastructure Systems

Technical domain training on telecommunications support workflows and infrastructure systems.

Current exploration

Vibe coding — building by describing the intent

The newest unfamiliar environment I walked into. Not learning to code in the traditional sense, but learning to think clearly enough that an AI can build what I'm describing — and to review what comes back.

Why it pulled me in

It's the same instinct that made me learn Apps Script mid-project: if I understand the problem well enough, the tool is negotiable. Vibe coding removes the gap between having a system in my head and seeing it run.

What it actually requires

Specification, not syntax. Deciding what should exist, what shouldn't, where the edge cases sit, and reading every result critically instead of accepting the first thing that renders.

Where it fits my work

It sits alongside the agentic and AI-enablement work — the same question of what to delegate to a machine, what to keep in human hands, and how to keep the output auditable.

Case study — this website

This portfolio was built entirely through vibe coding.

Every page you're reading — the career spectrum, the theme system, the admin dashboard, the grounded assistant, the résumé page — was produced by describing what it should do and why, then reviewing, correcting and re-specifying until it behaved. I made the structural and editorial decisions; the implementation came from working with AI the way I'd work with a capable team member.

Why present it this way

A career that moved across design, IT, operations, aviation, support, AI and entrepreneurship doesn't read well as a linear list. It needed to be explorable — a spectrum you can move through, sections that connect, and an assistant that can answer from the actual content rather than a brochure.

What the build proved

The constraint was never the code. It was clarity: knowing what the site had to say, refusing invented content, and keeping every claim traceable to something real. Same instinct as every other environment — understand how it works, then make it work better.

See the other things built this way →

Hobbies & interests

The personal side

Photography, creative work, learning, travel, technology — whatever is genuinely part of life outside work.

  • Gardening

    Slow feedback loops. Nothing responds to impatience.

  • Meditation

    Practice in noticing before reacting.

  • Cooking

    Process, timing and improvisation in one place.

  • Photography

    Training the eye to see what's already there.

  • Exploring

    New places reset the assumptions you didn't know you had.

Adaptability is easier to show than to claim

If any of these stories sound useful for what you're working on, the next step is a conversation.