What a First Month at an Indian Startup Really Looks Like

Students arriving from college into a twenty-person company are usually surprised by the same three things. Knowing them in advance makes the first month considerably less stressful.

Nobody will structure your day

In college, the structure is external — timetable, syllabus, exam. In a small company, you get a goal and a rough deadline. What you do on Tuesday afternoon is your decision.

This is not neglect. It is what the role is. The people who struggle are not the ones who lack skill; they are the ones waiting to be told what to do next, and then quietly assuming they are doing badly because nobody has said otherwise.

Two habits fix most of it. Write down what you plan to do each day before you start it. And send a short update at the end of the week, unprompted, saying what moved and what is stuck.

You will be given more context than instruction

A small team does not have time to write specifications for every task. Instead, someone will explain the situation for ten minutes and expect you to work out the next step.

If you did not follow it, say so immediately. "Can I repeat back what I understood so you can correct me" is a completely normal sentence in a working team, and it is far cheaper on day two than on day twenty.

The work is less glamorous and more consequential

Your first task will probably be unglamorous — cleaning a dataset, auditing assets, fixing a backlog of small bugs. It is not a test of your patience. It is genuinely what needed doing, and it is often how you learn the system.

At the same time, the consequence is real. In a small company there is no layer between your work and a customer. That is the trade, and it is the reason a small company is a good first workplace: what you do actually matters, so you learn faster.

Asking for help, calibrated

The rule I give interns: try for thirty minutes, then ask. Write down what you tried before you ask, and lead with it.

"I am stuck on the deployment step — I tried the staging config and got this error, and I checked the runbook but it does not cover this case" gets a useful answer in two minutes. "It is not working" starts a ten-minute investigation into what you meant.

What good looks like at the end of month one

You do not need to have shipped something impressive. Realistically, good looks like this:

• You understand what the company sells and who buys it
• You know who to ask about what
• You have finished several small things completely, rather than starting several large things
• People know what you are working on without having to ask

That is a strong first month. The interesting work comes after it, and it comes faster than you expect.