Who sits around you, and how work arrives

The cast

Job adverts describe a role. They rarely describe the room. Most data and AI work happens inside a group that looks roughly like this:

• A business stakeholder who owns a number (revenue, churn, fraud losses, delivery times) and does not care how it is computed.
• A product manager, translating between that person and the team.
• An analyst, answering questions with SQL and charts.
• An analytics engineer, turning raw tables into clean, documented, tested models everyone else builds on.
• A data engineer, moving data from source systems into the warehouse and keeping the pipelines alive.
• A machine learning or AI engineer, when there is a model in production.
• A platform or infrastructure person, often shared across several teams.
• A domain expert (an underwriter, a clinician, a logistics planner) whose knowledge decides whether any of it is correct.

Small companies collapse several of these into one job, which is usually yours. That is not a warning. Doing four of them badly for a year teaches more than doing one of them well, and it is the fastest route to knowing which one you want.

Three shapes, three lives

How the group is arranged changes your day more than the tools do.

Centralised. One data team serves the whole company through a request queue. You see breadth and every part of the business, and you develop shallow domain knowledge because you are never anywhere long. Requests arrive as tickets. The team’s constant problem is that it is a service desk with a backlog.

Embedded. Analysts and engineers sit inside product or business teams and report there. You get deep domain knowledge, real influence, and you are close enough to the decision to change it. The risks are isolation from other data people, no one senior to review your work, and career exposure if the product is cancelled.

Hub and spoke. Embedded people with a dotted line to a central team that owns standards, tooling and career development. Most organisations end up here after trying the other two. It is the best of the three for someone early, because you get a domain and a reviewer.

You can identify the shape in one interview question: ”If I need a number by Friday, who do I ask, and who checks it?”

How work actually arrives

Almost never as a specification. It arrives as:

• A Slack message: “can you pull the numbers for the board deck”.
• A ticket with a title and no body.
• A meeting where three people describe three different problems.
• An incident: a dashboard is wrong and somebody noticed in a leadership meeting.

The first, unteachable-sounding, entirely teachable skill of the job is converting a request into a question with a decision attached. The move is one sentence: ”What will you do differently depending on the answer?” If nobody can answer that, the work is decoration and can wait. If they can, you have just learned what precision the answer needs. A decision to spend fifty thousand rupees needs a rougher number than a decision to change pricing for every customer.

The maturity ladder, and why it decides your year

Data functions sit on a ladder, and where a company sits determines what you will actually do:

1. Spreadsheets. Numbers live in files people email. Your job is extraction and reconciliation.
2. A database or warehouse exists but nothing is documented. Your job is archaeology and writing the same joins repeatedly.
3. A transformation layer (dbt or its equivalent) with tested, documented models. Your job becomes analysis rather than plumbing.
4. A metrics layer, so “active customer” means one thing everywhere. Arguments about definitions stop.
5. Models in production, with monitoring and retraining.

An advert for an AI engineer at a company on rung two is an advert for a data engineer who will spend the first year at rung three. That is not a bad job. It is a different one from the one advertised, and taking it without knowing is how people end a year unable to explain what they learned.

Diagnose it with a single question in the interview: ”Where does the number on your main dashboard come from, end to end?” A confident four-sentence answer means rung three or higher. Hesitation, or “it depends who you ask”, means rung one or two. Both are worth joining. Only one of them matches the advert.