The job next to the data

The most reliable route, and the least discussed

Large numbers of working analysts and data engineers did not get hired as analysts or data engineers. They were already inside a company, doing something adjacent, and they moved.

This route almost never appears in career advice because it is slow, unglamorous, and impossible to sell a course about. It is also the highest-probability path available to somebody with no relevant experience.

The bridge roles

Any job that sits near data and near a decision:

• Customer support and success: every ticket is a data point, and support has the clearest view of what is broken.
• Operations, dispatch, scheduling, warehouse coordination.
• Quality assurance and testing.
• Finance and back office, accounts receivable, reconciliation.
• Sales operations and CRM administration.
• Field data collection, survey work, clinical or laboratory administration.
• Business process outsourcing roles of any kind.
• Teaching and training, in an organisation with student data.

What they share: you touch the raw material, you learn the domain, and you find out which numbers people argue about.

Why the internal move is so much easier

Three mechanisms, all of them structural rather than about you.

You are a known quantity. The manager has watched you work for a year. Hiring you carries almost no risk, compared with an outsider who interviews well.

Many internal moves are never posted. A team that needs a person and knows one asks for them. There is no queue, no screening software and no comparison against three hundred applicants.

You already have the expensive part. Domain context (which table anyone trusts, why the Mexico numbers are late, what “active customer” means in this company) takes an outsider a year to acquire and cannot be bought. You have it for free.

The twelve-month play

Months 1 to 3: do the actual job well. Nothing else works if this is missing, and everything else follows from the credibility it buys. You are not passing through; you are the person who handles the difficult accounts.

Months 3 to 6: automate one painful thing, for yourself, then share it. The weekly report someone assembles by hand. The rota that is copied between four sheets. Build it small, use it yourself for two weeks so it is proven, then offer it to a colleague. Do not announce a project.

Months 6 to 9: answer a question with a number. Someone in a meeting says “I think refunds are worse on the Lagos route”. Come back the next day with the actual figure and where it came from. Do this three times and you become the person people bring questions to, which is the whole game.

Months 9 to 12: say the sentence. To your manager, directly: ”I want to move toward analytics. What would I need to show, and is there a project with the data team I could take?”

This is the step people skip, and it is the one that works. Managers are not telepathic and generally cannot promote an ambition they have not been told about. Most of them will help, because a motivated internal person is cheaper than a hire.

What you can actually build from inside

Usually you cannot install anything, and there is no budget. The free tools that survive that constraint are more powerful than people expect:

• Google Apps Script: free with a work Google account, runs on a schedule, reads and writes Sheets, Gmail and Drive, and calls APIs. In a Workspace company this is the single highest-leverage skill available to someone in a bridge role.
• Excel Power Query: included in Excel, no admin rights needed, and it is a genuine ETL tool that most Excel users have never opened.
• SQL access, if anyone will grant it. Ask. Read-only access to a reporting replica is a small request that is frequently granted and rarely made.

The paid equivalents (Alteryx, premium Power Automate, a licensed integration platform) do the same work with a procurement process attached.

The risk, and the guard

The failure mode is real: you become the unofficial spreadsheet person for ever, doing two jobs, with the same title and the same pay. Some organisations will happily let this run for years.

Guard against it in two ways. First, agree a review date in writing: an email after a conversation saying ”as discussed, we will look at this again in six months” is enough. Second, keep your own written record of everything you built, with dates and outcomes, because it becomes your Selected work section whether you move internally or leave.

And be willing to conclude that this employer will not move you. A year of building real things on real data is a portfolio, subject to what you are permitted to publish. That is not a wasted year: it is the year that makes you hireable somewhere else.