Nikesh Reddy · Student / Builder / ThinkerBusiness / Technology / AI

Learning how
ideas become
businesses.

I’m Nikesh Reddy, studying AI at Tetr. Over the next seven semesters, I’m learning how to take an idea from a real need to a useful product, bring it to market, and understand the business around it. This is my growing record of the questions, people, and work along the way.

Nikesh Reddy seated by a window, in conversation
Learning AI.Learning the whole business.
Explore. Listen. Experiment. Build. Share.Keep exploring below

01 / A growing body of work

Questions become
something to share.

A video makes an argument. A reflection examines an experience. An idea brief gives a question a practical next step.

I want to understand
the problem deeply.
Then build from
that clarity.

The practice behind this website.

02 / How I learn

I want to stay with a problem long enough to understand who feels it, where the work breaks down, and what would make a difference. Then comes the next challenge: testing a useful solution and learning how its value, delivery, and economics could support a business.

01

Explore

Follow the work step by step. Look for the causes and constraints behind the frustration, and make the assumptions visible.

02

Meet & listen

Learn from people doing the work. Ask about the decisions, constraints, and surprises behind the polished story.

03

Experiment

Turn an assumption into a small test. Apply AI where it helps, compare it with a simpler approach, and check whether the whole task gets better.

04

Build

Make the idea tangible: a working prototype, a useful tool, or a clear explanation someone else can examine.

05

Reflect & share

Write down what changed, publish what I can support, and let the next conversation improve the work.

See the questions guiding the work

03 / Beyond the classroom

Bring the experience
back to the notebook.

One starting chapter and seven semesters ahead. Field Notes is a place to connect conversations, company visits, and practical attempts as this learning unfolds. The notebook contains clearly labeled example formats.

Nikesh in conversation on a technology exhibition floor

The useful detail is often the one I did not know to ask about.

The semester notebook

What changed
the way I think?

A good note keeps the context, the observation, and the next question together. Explore the example formats for a conversation, a company visit, and a practical attempt.

The learning map

From a problem
to a useful product.

A learning map for the whole business: product, AI, brand, launch, marketing, sales, money, and the work that keeps it running.

04 / From the published archive

Learning has
a backstory.

Three published reflections connect this approach to the experiences and questions already in the archive.

Build / ApniDukaan

A storefront is only the beginning.

My published e-commerce reflection follows the work around an order: reaching customers, dealing with suppliers, and earning trust when things go wrong.

Meet / Dubai

Go where the questions get bigger.

My Dubai conference reflection looks at what happens when classroom ideas meet founders, product demonstrations, and the messy detail of real businesses.

Share / Learning out loud

Put the thinking where others can see it.

My reflection on documenting the journey explores why explaining an idea, admitting a gap, and inviting a response are part of learning.

Photo notebook

People, places,
and conversations.

A growing collection of photographs, with a little context for each moment.

  1. Nikesh speaking with another attendee in a busy indoor event space.
    A conversation on the event floor.
  2. Close-up portrait of Nikesh looking out beside a window.
    A moment by the window.
  3. Nikesh looking upward as he walks beside tall bamboo in a sunlit indoor space.
    Among the bamboo, looking up.

For recruiters and teams

Useful work starts
with understanding.

I’m Nikesh, 19, studying AI and entrepreneurship. I’m looking for an internship where I can work on real problems, learn from a team, and take responsibility for a clear piece of work.

How I aim to work

  1. Listen before I build

    Observe the work, ask useful questions, and understand what is difficult for the people doing it. Good problem-solving starts with listening and empathy.

  2. Choose the tool to fit

    Use AI where it helps, check its output, and compare it with a simpler process or a tool the team already uses.

  3. Connect the work

    Look for gaps between teams, information and tools. Share context, document what I learn, and help make handoffs clearer.

  4. Own a clear next step

    Agree on a useful outcome, make progress visible, ask for help early, and be accountable for the work I take on.

Get a sense of how I think.

In a 2025 reflection, I wrote about learning to turn vague requests into clearer requirements. It shows the kind of practical learning I want to keep building on.

Tell me about the work.

Share the problem, what you would like me to contribute, and the time commitment. A clear brief makes it easier to discuss fit and timing.

The work, the duration, and the hours you have in mind.

The details you share are for discussing this opportunity. This form does not sign you up for marketing.

An enquiry starts a conversation. Availability and the arrangement depend on timing, fit, and my studies.