Experience

I learn best when I’m inside the system.

Some lessons come from books.

Others only become clear when you are responsible for real work, real people, real users, and real outcomes.

I have always tried to put myself close to the environments I want to understand. Sometimes that meant building something myself. Sometimes it meant learning from people several steps ahead of me. Sometimes it meant working inside an organization and seeing how decisions, operations, customers, teams, and execution actually connect.

For me, experience is not only about collecting job titles. Every environment I enter should leave me more capable than before.

Founder & Product Lead

EduLens

Building the system I once needed as a student.

EduLens began with a problem I experienced personally and spent years trying to understand more deeply.

What started as a student-guidance idea evolved through customer discovery, product experiments, changing hypotheses, and repeated simplification into a working Student Operating System.

My role has required me to move across product, research, strategy, operations, team building, outreach, partnerships, and execution — not because I am an expert in all of those areas, but because early-stage building often forces the founder to understand enough of each system to keep the company moving.

What I contribute

Product direction
Turning hundreds of user conversations into product decisions, priorities, workflows, and a focused MVP.
Customer discovery
Leading 500+ conversations with students, guardians, international students, counselors, education stakeholders, and study-abroad experts to understand the problem from multiple sides.
Product simplification
Reducing a broad vision of roughly 40 tools and concepts into a much more focused, executable product direction.
Prototyping and shipping
Using basic design, technical understanding, and AI-assisted building skills to create prototypes when speed mattered more than waiting for perfect resources.
Team building
Recruiting, rebuilding, working with technical and industry talent, and learning difficult lessons about ownership, commitment, and co-founder responsibility.
Distribution and outreach
Building relationships with students, ambassadors, experts, mentors, founders, partners, programs, and potential supporters.
Strategy
Thinking beyond product features into trust, behavior, distribution, retention, partnerships, market structure, and long-term positioning.

What this has taught me

Stay close to the problem
The product became clearer when I stopped defending previous versions and kept listening.
A large vision needs a focused first product
Ambition without prioritization creates complexity.
Shipping creates information
A rough working prototype can teach more than weeks of internal debate.
Product is only one part of the company
Trust, distribution, behavior, economics, team quality, and execution matter just as much.
Commitment matters more than credentials
The strongest résumé in the room does not replace ownership.
Communication shapes product perception
If people misunderstand what you are building, that misunderstanding is also something you have to solve.

Capability carried forward

Founder judgmentCustomer researchProduct strategySystems thinkingPrioritizationRapid prototypingTeam leadershipStakeholder communicationDistribution thinkingOperating under uncertainty

Explore why I built EduLens

Junior Executive, Operations

Shikho

Learning how education works beyond the product interface.

Building EduLens gave me one perspective on education technology. Working inside Shikho gives me another.

A product may look simple from the outside, but behind that interface are people, processes, coordination, operations, communication, deadlines, customer needs, internal systems, and thousands of small decisions that determine whether the experience actually works.

My role gives me the opportunity to contribute inside a real EdTech operating environment while developing a deeper understanding of how education businesses function beyond product design alone. I do not see this experience as separate from entrepreneurship — I see it as another environment where I can contribute, observe carefully, and become a stronger operator.

What I contribute

Operational execution
Supporting day-to-day operational work and helping tasks move from planning into execution.
Coordination
Working across people, information, and processes where clear communication and follow-through matter.
Problem solving
Responding to practical operational needs rather than only theoretical product questions.
Reliability
Learning the discipline required to execute consistently inside an established organization.

Note · This section will become more specific as my responsibilities and measurable contributions become clearer.

What I am learning

Products do not operate themselves
What users experience depends on the systems and people behind the interface.
Execution has invisible layers
Operations, coordination, communication, delivery, and process quality can decide whether a good idea actually works.
Scale changes the nature of problems
Problems that are simple with ten users can become completely different at organizational scale.
Organizations require different discipline than startups
Founders can move through intuition and ownership. Larger organizations require processes, coordination, and consistency across many people.
Education is more than software
Student behavior, trust, communication, service delivery, content, operations, parents, and teachers all shape outcomes.

Capability carried forward

Operational thinkingExecution disciplineCross-functional coordinationOrganizational awarenessEducation-industry understandingProcess thinkingProfessional communicationWorking inside established systems

Before the job titles

Some of my most important learning happened before I had a title.

Before university, I deliberately spent time around people and environments that exposed me to worlds I did not yet understand.

Through University of Dhaka residential-hall networks and guidance from students and graduates connected to BUET and Dhaka Medical College, I was exposed early to people thinking seriously about academics, careers, leadership, public service, competition, and ambition.

Later, when I wanted to understand different systems, I reached out directly to people operating inside them — technology, cloud, telecom, startups, consumer businesses, consulting, large organizations. Those conversations included senior people connected to Oracle, Robi Axiata, ShopUp, Uber Bangladesh, Unilever, Nokia, Huawei, and others.

I was not trying to collect impressive names. I was trying to understand: how does this system actually work? That habit shaped the way I approach new environments today.

Rooms I entered early

University of Dhaka halls·BUET·Dhaka Medical College·Oracle·Robi Axiata·ShopUp·Uber Bangladesh·Unilever·Nokia·Huawei

What I learned early

Ask people who have seen the system from above
Articles can explain parts. People with direct operating experience often reveal the structure.
Curiosity opens doors
Many accomplished people are willing to help when the questions are genuine and prepared.
Environment compounds
Spending time around people with higher standards changes what feels possible.
Do not wait for permission to learn
You do not need a formal title before you begin asking serious questions.

How I choose experiences

I am not trying to collect logos. I am trying to accumulate capability.

When I think about a role, company, team, or environment, I ask five questions before the title.

Q01
Can I contribute something meaningful?
Learning should not be extractive. I should create value while I am there.
Q02
Will I be close to real problems?
I learn faster when decisions have consequences.
Q03
Will I work around people better than me?
The quality of people around me affects the speed of my growth.
Q04
Will this environment teach me something I cannot easily learn alone?
Scale, operations, AI, platforms, enterprise systems, product discipline, distribution, leadership — different environments reveal different things.
Q05
Will the capability carry forward?
The best experience does not end when the role ends. It changes what I am able to do afterward.

Founder experience and professional experience are not opposites

I do not see my future as “startup or career.” I see both as parts of the same long-term learning process.

Building a company teaches one set of lessons. Working inside a strong organization teaches another. I want exposure to both.

A startup can teach

speed
ownership
uncertainty
customer discovery
product creation
resourcefulness

An established organization can teach

scale
systems
operational discipline
cross-functional execution
platform thinking
organizational design
long-term product quality

The goal is not to collect experiences randomly. It is to become more capable of building meaningful systems over time.

What I want to learn next

There are systems I still only understand from the outside.

I want deeper exposure to environments where I can contribute while learning more about how the following systems actually work at scale.

Product at scale

How products used by millions remain understandable, reliable, and coherent.

Platforms and ecosystems

How multiple products, users, developers, partners, and business models connect around one system.

AI systems

How AI becomes useful, trustworthy, cost-efficient, and integrated into real workflows.

Large-scale operations

How organizations coordinate across teams, markets, users, and complex processes.

Distribution

How products earn attention, trust, adoption, and repeat behavior.

Organizational excellence

How world-class teams make decisions, maintain standards, and execute over long periods.

I do not know exactly which future environment will teach each lesson. That is part of what makes the journey interesting.

What each experience has actually strengthened

Instead of a generic skills section — the capabilities I have accumulated, grouped by how I use them.

Understand

Customer discovery
500+ stakeholder conversations through EduLens.
Systems thinking
Moving from isolated student problems toward connected navigation.
Problem framing
Repeatedly changing the model as evidence improved.

Build

Product direction
Turning research into priorities, workflows, and product architecture.
Rapid prototyping
Building tangible versions quickly enough to generate feedback.
AI-assisted building
Using emerging tools to reduce dependency and increase execution speed.

Operate

Operations
Professional experience inside EdTech at Shikho.
Execution
Moving work forward under limited resources and uncertainty.
Team building
Building, rebuilding, and learning what real ownership requires.

Connect

Outreach
Students, experts, founders, mentors, investors, programs, and partners.
Stakeholder communication
Explaining complex ideas differently depending on audience.
Relationship building
Learning through people who understand systems from perspectives I do not yet have.

Learn

Self-directed learning
Learning what the situation requires rather than waiting for perfect preparation.
Business
Markets, incentives, trust, strategy, distribution, and company building.
Technical fluency
Enough to prototype, communicate with engineers, and participate in product decisions.

Reflection

A title tells you where someone worked. I care more about what changed because they were there.

For every meaningful experience, I want to be able to answer four questions:

01What did I contribute?
02What did I learn?
03What capability became stronger?
04What can I now do that I could not do before?

That is how I want this page to evolve.

Not as a frozen employment history. As a record of accumulating capability.

Explore the other sides of the journey

See what I’m building

EduLens

See how I got here

My Journey

External proof & documents

Work

Start a conversation

Contact