How to Map Research Career Paths From PhD to Postdoc and Beyond

A research career is not one fixed ladder. A PhD can lead to another research degree, a postdoctoral role, a research institute position, a public-sector research role, an industry research team, a technical or data-focused position, teaching, policy work, entrepreneurship, or a combination over time. A postdoc can be an important training stage for some people and fields. It is not a universal requirement, and it is not a guarantee of an academic job.

The useful question is not “What job will a PhD guarantee?” No source can answer that honestly. The useful question is: “What kind of research work do I want to develop next, what evidence will I need for it, and which current opportunity gives me a credible way to build that evidence?” This lets you compare a PhD, postdoc, fellowship, research assistant role, or other research position without pretending that any title decides your future.

This guide is for global STEM applicants thinking about research direction. It explains how to map possible paths, read current role descriptions, identify skills and research evidence, and choose a next step using direct sources. It does not promise employment, salary, tenure, fellowship success, immigration approval, or an outcome in a particular country. For finding and checking actual postdoctoral positions, use How to Find and Check Postdoctoral Positions Abroad. For preparing an application with a host, use How to Prepare a Postdoctoral Application and Fellowship Host Proposal.

The short answer: map work, not titles

Start by writing the kind of research work you want to do in the next stage. Do you want to learn how to design studies, develop a method, work with a specialised instrument, lead a defined project, analyse a particular kind of data, collaborate across sectors, build research software, work near patients or field sites, or translate research into a product, policy, or service? A title alone does not answer these questions.

Then find current evidence. A live opportunity or fellowship call can show what a role asks for. A doctoral-school page can show the training environment. A host-group page can show the research questions and methods. A research organisation can show its role in a field. A funder page can explain the purpose and rules of a particular programme. Keep those sources separate from your own preferences and the questions you still need to ask.

Your map should have three columns: what you want to develop, what the role actually offers, and what remains unknown. This keeps the decision grounded. You may conclude that a postdoc is worth exploring because it gives you a named method and project responsibility. You may also conclude that a PhD is the right next step because you need deeper research training first. Neither conclusion is a status judgement. It is a decision about the work in front of you.

What a PhD is designed to develop

A PhD is usually a period of advanced research training built around an original contribution. The exact form differs by discipline, country, university, funder, and project. Some PhDs are mainly individual research projects. Others include structured courses, rotations, cohort training, professional development, industry links, or a defined funded research role. Do not assume that every PhD develops the same skills in the same order.

Research capability, not only a thesis

The visible outcome of a PhD may be a thesis or equivalent research output. The deeper work is learning how to frame a question, find and assess sources, choose and justify methods, collect or create evidence, manage uncertainty, interpret results, respond to critique, and communicate the work responsibly. The balance changes across fields. An experimental PhD may centre on laboratory design and measurement. A computational PhD may centre on data, algorithms, models, and reproducibility. A field-based project may centre on context, access, observation, and ethics. A clinical or applied project may include protocols, partnerships, and complex governance.

When you assess a PhD, look for the work you will actually practise. An opportunity description, group page, facility page, and programme page can each contribute evidence. A university's rank cannot. If you want to become capable in a particular method, find out whether that method is present in the current research environment. If you want to learn how to move between disciplines, look for a programme or project that shows those connections in practice.

Training is part of the route

Doctoral training can include methods courses, research ethics, data management, communication, teaching, career development, researcher wellbeing, peer networks, and formal milestones. The UKRI Statement of Expectations for Doctoral Training is one funder framework that treats research environment, support, and training and development as connected parts of doctoral study. It applies to defined funded contexts, not every PhD around the world. It is useful because it reminds applicants to assess the training system around a project as well as the topic itself.

Ask: which skills do I already have, which skills are essential for the research question, and which skills would I need to develop? Then find the source that shows a route to that development. A facility may describe induction and technical training. A doctoral school may describe methods workshops. A group may show current projects that use an adjacent approach. A programme may name co-supervision or a collaboration. Record the evidence and the limit. A course listing is evidence that a course exists, not proof that it will be available for your project or that it covers every skill you need.

A PhD is not a pause before a “real” career

It is easy to talk about doctoral study as a delay before a future job. That misses the value of the research work itself. During a PhD, you may develop ways of investigating questions, handling evidence, collaborating, writing, presenting, programming, designing experiments, managing a project, working with partners, and reflecting on research integrity. These capabilities can matter in universities, public research organisations, companies, hospitals, charities, government, and other settings.

That does not mean every PhD automatically develops every capability. You should not claim skills you did not actually practise. A good career map records concrete evidence: a project you carried through, a method you learned, a dataset you documented, a research output you contributed to, a collaboration you helped manage, or an audience you communicated with. This is more useful than a list of generic strengths.

The doctoral route should fit the work you need next

If you are choosing a PhD, the immediate question is not whether it is a prestigious title. It is whether the research and training route will help you become more capable in the work you care about. Use How to Assess Research Group and Supervisor Fit Before You Apply to examine the local group and How to Evaluate Doctoral Training Programmes, Networks, and Research Partnerships to examine the larger structure.

What a postdoc can be designed to develop

A postdoctoral role is not one standard job. It can be an employment contract on a defined project, a fellowship developed with a host, a research institute appointment, a mobility route, a clinical or residency-linked stage, or another early-career research position. Its purpose and conditions depend on the opportunity.

A transition, not a universal destination

The NIH description of postdoctoral and residency training describes the postdoctoral period as a temporary stage that can help a newly trained doctorate holder develop greater independence, supported by mentors and career planning. That description is specific to the NIH context, but it captures a useful question for any postdoctoral role: what form of independence, expertise, or research experience is this role designed to build?

One postdoc may give you depth in a specialised technique. Another may let you lead a work package, develop a grant idea, move to a new research setting, manage a small collaboration, work with a unique dataset, or publish a defined project. A third may be mostly a short-term contribution to a larger programme. Do not use the title “postdoc” as evidence that the role will do all of these things.

Employment and fellowship routes differ

An advertised postdoctoral vacancy usually has an employer, a stated project, a contract route, and a current application process. A fellowship may ask you to build an application with a host organisation. The funder call can control eligibility and the proposal; the host can control institutional support and submission; an employer or university may control recruitment after an award.

The MSCA Postdoctoral Fellowships page is one current official example of a host-led fellowship route. It describes the action as supporting researchers holding a PhD who seek research abroad, new skills, and career development. It also shows why the current call and host route matter: applicants develop the proposal with a host organisation, and the specific eligibility, timeline, and funding conditions belong to the current documents. Do not treat a fellowship overview as an open job.

Ask what the role will let you own

Research independence is not a switch that turns on after a PhD. It develops through concrete responsibility. When you read a role, look for evidence about the question, methods, expected contribution, collaborators, research outputs, mentoring, and project boundaries. Is the project defined by a funder? Are you expected to develop a direction within it? Does the role name a host group, co-investigators, facilities, or partners? Is the work mainly individual, team-based, technical, translational, or a mixture?

Do not expect the page to answer every question. Its job is often to recruit, not to publish a career plan. But it should give you enough to decide whether further investigation is sensible. If an essential element is unclear, find the current project, host, facility, or funder page that controls it.

A postdoc is not the only next role after a PhD

Some fields and career directions value postdoctoral research highly. Others may lead directly into industry research, research engineering, data science, public research organisations, policy, clinical settings, teaching, innovation, or another role. The right next step depends on the work you want to build, the evidence you need, and the current opportunities available to you.

Avoid taking a postdoc only because it sounds like the expected next title. Ask whether the role gives you a clear research reason to move: a method you need, a question you want to deepen, a host environment that changes what you can do, a fellowship route aligned with your goal, or a project that develops responsibility. If you cannot identify that reason, keep exploring.

Map roles across research settings

Research happens in more places than a university department. Your career map should include settings, not only job titles.

University-based research

University settings may include doctoral programmes, research groups, core facilities, teaching, student supervision, interdisciplinary centres, libraries, data services, and partnerships. A role can be highly focused on one project or involve a broader mix of research and teaching. The current job or programme page controls the actual duties.

For a PhD, the degree route and research group matter together. For a postdoc, the advertised project and employment terms may be central. In both cases, the wider university environment can affect access to training, facilities, methods communities, and researcher support. Use How to Evaluate a University Research Environment Beyond Rankings rather than treating the institution's name as a proxy for the local setting.

Research institutes and infrastructures

Public research organisations, national laboratories, research hospitals, observatories, institutes, and infrastructure providers can host important STEM research. A PhD may be awarded by a partner university while daily work happens in an institute. A postdoc may be employed directly by the research organisation. An infrastructure may give access to equipment, data, field sites, technical expertise, or an international user community.

The practical question is who owns which part of the route. Identify the employer or host, degree-awarding institution if relevant, research group, facility, and application page. A famous institute does not automatically have a role for you. A university affiliation does not automatically explain an institute-based project. Read the source that controls each condition.

Industry-linked and applied research

Industry-linked research can happen within a university project, a company research team, an applied institute, a start-up, a hospital, a government laboratory, or a partnership. The work may involve product development, methods, validation, systems, data, safety, clinical practice, manufacturing, environmental monitoring, or another real-world setting.

Do not assume that “industry collaboration” means a job offer after graduation or that company work is less rigorous than university work. Ask about the research question, evidence, methods, data, publication or confidentiality conditions, team roles, and formal route. The current opportunity and any published partnership terms are more useful than the label.

Public, nonprofit, and policy-facing research

Government agencies, public laboratories, charities, international organisations, and nonprofits can support or conduct research. They may work on health, environment, infrastructure, data, standards, education, agriculture, security, public services, or other domains. The roles can combine research with evidence synthesis, evaluation, technical advice, implementation, or stakeholder engagement.

This setting may fit you if you want your research questions to connect closely to public needs. It still needs a source-backed assessment. Read the organisation's research pages, current opportunities, project descriptions, and terms. Do not infer the daily work from the organisation's mission alone.

Build evidence of research development

Career planning becomes more useful when you describe evidence rather than traits. “I am passionate about research” may be true, but it does not help you decide which role to pursue. A better record names what you have done, what it shows, and what you want to develop next.

Use a development record

Use only evidence you can support. A draft idea is not the same as a completed method. Attendance at a workshop is not the same as applying the method in research. You do not need to undervalue small contributions, but you should describe them accurately.

Outputs are evidence, not a scoreboard

Papers, datasets, code, reports, protocols, posters, preprints, patents, teaching materials, technical documentation, and public engagement may all be research outputs in different contexts. Their value depends on the field, role, project, and quality of the work. Do not use journal title, output count, or profile metrics as a universal career score.

The DORA declaration cautions against using journal-based metrics as a substitute for judging individual research and researchers. That principle is useful for career mapping. Ask what the output shows you can do. Does it demonstrate careful analysis, a method, a collaborative contribution, transparent documentation, an applied result, or a new research question? This is more meaningful than whether it looks impressive from a distance.

Keep a source for each future claim

When you consider a role, record the source that supports your expectation. If you think it would develop a method, point to the project or group page. If you think it provides a fellowship route, point to the current funder call. If you think it includes a partner setting, point to the opportunity or partner description. If you cannot find a source, write it as a question rather than an expectation.

This habit also improves applications. You can describe why a role fits your development without adding vague claims about what the employer or host will provide.

Research culture and open-science practice are part of the setting

Research career development is not only about individual output. It happens in a culture of methods, data, integrity, collaboration, review, and communication. The details vary by discipline and project, but the questions are worth asking.

Look for practices that make the work understandable

Open science can include sharing research outputs, improving access, building infrastructure, training, collaboration, and transparent research processes. The UNESCO Recommendation on Open Science describes an international framework that includes these elements while recognising that access can be limited by confidentiality, personal information, intellectual property, safety, and other legitimate conditions.

For an applicant, this means you should not assume every group will share every dataset, protocol, or codebase. Instead, look at what the field and project make public. Are methods described carefully? Are repositories or data-management pages visible where appropriate? Does the programme mention research integrity, data stewardship, or reproducibility? Does the group explain its research clearly enough for you to understand the question and method?

These are fit signals, not moral scores. A sensitive health-data project may have strong reasons not to make data public. A commercial collaboration may have confidentiality conditions. The right question is whether the research setting has a clear, responsible approach to the work it does.

Develop skills that travel across settings

Research-specific methods matter, but some practices can support your work in many settings: clear documentation, data literacy, version control where relevant, reproducible analysis, ethical judgement, collaboration, project planning, communication, and the ability to learn a new tool or domain. The exact mix should be guided by your field, not by a generic checklist.

The UNESCO recommendation also points to capacity building, education, digital literacy, data stewardship, and collaboration. Use that as a prompt to inspect the local training environment. You may find a useful course, core facility, community, or research-data service. Do not claim a skill until you have practised it in a meaningful context.

Mobility, networks, and collaboration: opportunities with conditions

Moving between institutions, sectors, disciplines, or countries can change your research experience. It can expose you to a new method, setting, collaboration, facility, or question. It can also introduce practical constraints. Mobility is not automatically good or bad. It is one possible part of a research path.

Read the purpose of a move

Before considering a move, name the research reason. Perhaps you need a facility that is unavailable where you are, a host group that works on your question, a field setting, a cross-disciplinary team, or a fellowship structured around a new research environment. This is stronger than moving simply because “international experience” sounds valuable.

The MSCA Postdoctoral Fellowships route is one example of a programme that explicitly connects mobility, new skills, and career development. Its current conditions are specific to that action. Use it as a model for reading any mobility route: identify the host, research plan, expected development, eligibility rules, funding terms, and current call. Do not copy its rules into another programme.

Networks are sources of evidence, not automatic access

A conference, learned society, research network, consortium, online seminar, or collaborator list can help you discover fields and opportunities. It cannot guarantee a place, a host, a referral, or funding. Use the network to find the current organisations and projects that own the next decision.

If you contact someone through a network, keep the message focused on the research and the published route. Do not ask for a career guarantee or an informal selection decision. A respectful question about a live opportunity or host fit is more likely to be useful.

Keep mobility and immigration evidence separate

Cross-border research may involve visas, permits, work authorisation, insurance, tax, family, and timing questions. They are important, but they should be handled through the employer, university international office, funder documentation, and official government sources that control them. This guide does not give legal advice.

Your career map can note the operational need: “This role is based in this country and includes a stated secondment; I need to check the official documentation route.” It should not turn a programme description into an immigration promise.

Read a role as a development environment

The same title can create very different experiences. Two postdoctoral roles may both say “research fellow,” while one is a focused appointment on an established experimental platform and the other is a fellowship that asks the researcher to develop a project with a host. Two PhD projects may both be funded, while one is embedded in a cohort and the other is a project-specific employee route. Career planning becomes clearer when you read the environment around the role.

Look for the question, method, and boundary

Every serious role should allow you to identify at least part of the research work. What is the question or problem? What methods, data, materials, systems, or setting are visible? What part of the work is defined by the opportunity, and what part might be developed during the role? Who is the host group or organisation?

An advertisement will not always provide a complete research plan. It should provide enough to show whether the direction is close to your own. Follow the links to the group, programme, current project, and facility pages. If a role is too vague for you to understand the work, it may still be legitimate, but you need a clear source or focused question before treating it as a serious career move.

Look for the evidence of development

Then ask what the role could realistically help you practise. The answer might be technical depth, study design, a cross-sector setting, a larger dataset, team coordination, research communication, grant writing, teaching, supervision, or a new field. Do not use broad phrases like “excellent career opportunities” as evidence. Look for the specific work and formal support that could produce the development.

Look for the support structure without predicting people

A role can name a supervisor, mentor, project lead, team, doctoral school, professional-development route, facility staff, or research office. These are useful signals because they show where support may be organised. They do not let you predict how every person will behave or how much time they will have in the future.

Read public support information as a structure. Is there a formal progression process? A programme director? A methods community? A facility training path? A named research group? A current call that describes host responsibilities? These questions help you decide whether the setting is worth exploring. Use How to Assess Research Group and Supervisor Fit Before You Apply for the related group-level assessment.

Check the period and the next decision point

Many research roles are time-limited. This is not automatically a flaw. A defined period can give focus and a clear project boundary. It does mean that you should understand the role's duration, start conditions, review points, and any stated follow-on arrangement. The current contract, call, or programme documentation controls these facts.

Do not fill a fixed-term role with a story about what must happen afterward. A role may strengthen your experience and still leave several next paths open. The right response is to plan the evidence you want to build during the period, then reassess when you have that evidence.

Build a portfolio of evidence, not a personal brand story

The phrase “build your profile” can make research careers sound like marketing. A better idea is to build a record of real work that you can explain. The portfolio will look different across fields and roles, but the principle is stable: keep evidence of the research you have done, the decisions you made, the methods you used, the collaborators you worked with, and the limits you learned to handle.

Keep the work traceable

For a project, save the sources that define the problem, the data or experimental record you are allowed to retain, versioned analysis or code where relevant, a methods note, presentation material, and a short reflection on what you contributed. Follow your institution's rules for confidentiality, intellectual property, data protection, and authorship. Do not keep material you are not authorised to keep.

Traceability is not only for formal publication. It helps you remember how you reached a conclusion and helps a future supervisor, employer, or collaborator understand the kind of work you can discuss. A clear explanation of one carefully completed analysis can be more useful than a long list of unexplained keywords.

Describe collaboration honestly

Research is often collective. You may contribute to a paper, dataset, instrument, field campaign, protocol, software package, literature review, or public report with several other people. Do not overstate ownership. Explain your role in plain language: “I prepared this analysis,” “I developed this protocol under supervision,” “I contributed to the data curation,” or “I coordinated this bounded part of the project.”

This is not modesty for its own sake. It makes your next role decision sharper. If you have already contributed strongly to data analysis but have not designed an experiment, the next development gap is clearer. If you have managed a technical component but not written a proposal, you can look for a role that makes that learning possible.

Use output choices to serve the research question

Open papers, data, software, protocols, reports, and other outputs can help make research more useful and understandable. The right output depends on the project, discipline, permissions, and audience. UNESCO's open-science framework stresses that openness must be balanced with legitimate limits such as privacy, confidentiality, intellectual property, and safety. Do not use open-science language to pressure yourself or others into sharing material that should remain protected.

For career planning, the key question is simple: what evidence of careful work can you responsibly show or describe? It may be a publication, a technical report, a documented workflow, an abstract, a talk, a portfolio item, or a clear account of a project contribution. The form matters less than the honesty and relevance of the evidence.

Use conversations as research, not as a search for certainty

People can help you understand a research path: supervisors, mentors, colleagues, alumni, programme staff, facility contacts, and collaborators may point you to sources or describe a formal process. Their perspective can be useful. It is not a substitute for the current page that controls a decision.

Prepare a focused conversation

Before you speak to someone, identify the question you cannot answer from the official sources. It might concern the research direction, the published application route, the relationship between a programme and a host group, a facility's public access guide, or the difference between a project vacancy and a fellowship route.

Explain what you read and ask one question. “I read the current role description and the group page. The project looks connected to my work on X. Which current source explains whether the role includes Y?” This is more useful than asking someone to decide your entire career or tell you whether a field has a future.

Keep advice in its context

An alumnus may describe their own route. A current researcher may explain how one project works. A mentor may help you see a development gap. None of these perspectives becomes a universal rule. Conditions change by country, field, institution, funding cycle, and personal circumstance.

Record advice as a perspective and return to the direct source for terms, deadlines, eligibility, employment, or funding. This keeps your career map open to human learning without making it depend on anecdotes.

Do not use a network as proof of access

Knowing someone, attending a conference, or participating in an online community can help you discover research and learn its language. It does not mean an opportunity is open, that a host will support a fellowship, or that a partner can employ you. Follow the current public route. Respectful network use is about learning and connection, not extracting promises.

Turn the map into a practical search plan

A career map becomes useful when it changes how you search. Instead of typing only “PhD” or “postdoc,” combine a role term with the question, method, setting, or development need you identified.

Search for work that matches the development gap

If you need advanced microscopy, search a field and method together, then verify the host's facility and opportunity pages. If you need to move from theory to application, search for programmes or projects that name the applied setting and research method. If you want to understand a new field, begin with journals, current group work, and primary research organisations before searching for openings.

The goal is not to eliminate broad searches. It is to make them more useful. Your search terms should reflect the work you want to develop, not only the title you hope to hold.

Maintain three lists

Keep a list of live opportunities that have a current route, research leads where the work is relevant but no route is verified, and development sources such as papers, facilities, field pages, and funder programmes that improve your understanding. Do not mix these lists. A strong research lead is not automatically an application. A live role may not fit your direction. A background source may give you the vocabulary that finds a better opportunity later.

Revisit the map after meaningful new evidence

Update your map after you complete a project, learn a method, receive a decision, discover a new research area, or find a current role that changes your options. Do not update it every week just to feel active. The map should respond to real evidence.

This rhythm prevents two problems: waiting for a perfect long-term plan before applying anywhere, and applying everywhere without a clear reason. You can move forward with a next step while keeping your path open.

Decide when a role is a useful step and when it is not

Not every relevant-looking role belongs in your plan. A useful career map should make it easier to say no when the evidence does not support the move.

A role may be interesting but not developmentally right

You may find a well-funded project in a respected group that simply does not develop the work you need next. Perhaps the role is entirely focused on maintaining a method you already know when you need experience designing research. Perhaps it is in a new field, but the current description does not give you a path to learn the core research question. Perhaps the location or formal conditions make the role unrealistic for your circumstances.

You do not need to call the role bad. Write the narrower conclusion: “The project is relevant but does not address my present development gap,” or “The route is not practical under the current terms.” This leaves room for the role to be right for someone else and prevents you from forcing a story around it.

A role can be valuable even if it is not your final direction

The opposite can also be true. A research assistant, technical, data, or applied role may not be the final direction you imagine, but it can build evidence you need before a later PhD, postdoc, or research transition. The question is whether you can name the evidence. Will it give you a sustained project, a method, an applied setting, a research output, a collaboration, or a clearer question?

Do not rely on a vague promise that it will “look good.” A role is useful when you can connect its current work to a real next development step. If the connection is weak, keep searching.

Make room for non-linear paths

Career paths can include pauses, changes of field, caring responsibilities, work outside universities, part-time study, returns to research, and different kinds of contribution. These are not automatically gaps to hide. They change the evidence and conditions you bring to the next decision.

Do not compare your path to an imagined standard timeline. Read the current role's eligibility and requirements. Explain your relevant experience honestly. If a funder or programme has a specific rule on career breaks, mobility, or experience, use its current official guidance. Do not assume that an example from another programme applies to yours.

Use a stop rule for weak leads

Set a simple limit on your search effort. If you have checked the current opportunity, host, programme, and funding pages and still cannot identify the application owner, research question, or essential condition, pause the lead. Save the direct page and a note about why it was not ready. Then spend the next hour on a source that can move your decision forward.

This protects your time. Research careers have uncertainty, but they should not require you to build an application around missing information.

Review the map at the right time

You do not need a career review every day. Review it when you have new evidence or before you make a decision with real consequences.

Before applying

Check that the role is current, that you can explain the research fit, that the application route is clear, and that you have identified any funding, eligibility, or practical condition that could stop the application. Use the current page, not your memory of a past search.

After an interview or focused conversation

Write down what was confirmed, what remains unknown, and whether the new information changed your development assessment. Do not let a friendly conversation erase a formal gap in the terms. At the same time, do not ignore a useful clarification that points you to a more specific source.

At the end of a substantial project

Update the evidence record. What did you actually learn? Which contribution can you describe? Which method, setting, or responsibility now feels more central to your direction? Which gap remains? This is the most useful moment to revise the next-step criteria.

When your circumstances change

Funding needs, location, health, family responsibilities, immigration status, language, and timing can change which opportunities are practical. Include these conditions privately in your map. They are not separate from career planning. They determine whether an otherwise attractive route is feasible now.

The aim of review is not to create certainty. It is to keep the next decision connected to the research work, evidence, and conditions you actually have.

Build a personal research-career map

The map is not a ten-year prediction. It is a short, revisable plan that connects your current evidence with a sensible next role.

Start with a direction statement

Write two or three sentences about the work you want to grow into. Include the kind of question, research setting, methods, and contribution that interest you. Keep it broad enough to explore and specific enough to compare roles.

For example: “I want to work on reliable, data-informed energy systems. I am interested in combining physical measurement with modelling, and I want to learn how research moves from laboratory evidence to practical design decisions. My next step should give me deeper methodological training and experience in a team that works across those boundaries.”

This statement does not decide whether the next role must be a PhD, a postdoc, or an industry job. It creates criteria for assessing the roles you find.

Name the development gap

Ask what you need before the next step after this one. You may need to learn a method, gain sustained research experience, finish a degree, work with a new dataset, develop project responsibility, or understand a new setting. The gap should be concrete.

Avoid vague gaps such as “I need to become more competitive.” Replace them with evidence you can recognise: “I need supervised experience with this method,” “I need to take a research question from design to analysis,” or “I need to understand the research environment around this application area.”

Compare possible next roles

Make one decision at a time

You do not need to decide your entire career before choosing a PhD. You need to decide whether the next role moves you toward the kind of work you want to be able to do. After that role, you will have more evidence, new interests, and different opportunities.

This is why a map should be revised. If a PhD project changes your methods interest, revise the next development gap. If an opportunity reveals a research environment you had not considered, investigate it. A map that can change is more honest than a rigid plan that ignores the work you actually encounter.

Choose the next role with a source-backed lens

Before committing to a role, compare the evidence at the level of the current opportunity. The organisation's mission, ranking, or famous researchers can be background. The project, host, methods, degree or contract route, funding, eligibility, and work setting should carry more weight.

Write a one-sentence reason for the role

Use this structure: “This role is worth pursuing because it offers [a specific research question, method, setting, or development opportunity] supported by [current source]. I still need to check [a condition that could change the decision].”

For example: “This postdoctoral role is worth pursuing because the current project and group pages show a method I need to deepen in a new application setting. I still need to check the contract conditions and whether the stated data-access route applies to the project.”

If you cannot write a sentence like this, you may be responding to the title rather than the role. Return to the primary sources.

Compare conditions that are not interchangeable

Research fit, funding, eligibility, supervision, location, employment conditions, degree structure, career development, and personal circumstances can all matter. They do not cancel each other out. A very interesting project cannot make an ineligible funding route work. A strong salary cannot repair a research setting that does not let you do the work you care about. An attractive international programme cannot substitute for a clear degree or employment route.

Use How to Compare PhD Opportunities and Make a Defensible Decision when you have real opportunities to compare. Keep career direction as one input among the evidence, not the only one.

A worked career-map scenario

Imagine an applicant who has completed a master's project in environmental data analysis. They enjoy working with sensor data but have not yet led a full research project, learned field measurement, or worked with a long-term monitoring dataset. They are deciding between a funded PhD project on environmental sensing and a short-term research assistant role at an applied institute.

The PhD opportunity has a defined question about sensor reliability, a university group with related publications, a field-station partner, and a doctoral programme. The applicant needs to check the funding and entry terms. The applied role describes data cleaning and reporting for a monitoring programme, but it does not offer a doctoral degree or a clear route to field-method training.

Neither role is automatically better. The applicant's map shows that they want to develop independent research design, field context, and sensor methods. The PhD appears to align more directly with those needs if the formal terms work. The applied role may still be valuable if the applicant needs practical data experience before doctoral study, but its source-backed description does not show the same route to doctoral research training.

The decision note might say: “The PhD is the stronger next research-training option because the current opportunity connects sensor reliability, field setting, and doctoral development. I need to verify funding and eligibility before applying. The applied role remains a useful alternative if I decide that a shorter period of applied data experience is the right immediate step.”

This is a career map, not a prediction. It compares present evidence with a stated development goal.

The Career-Direction Truth Check

Are you comparing real roles, not imagined titles?

Use a current opportunity, programme, employer, funder, or host page. Do not compare “a PhD” and “a postdoc” as abstract status labels.

Can you name the work you want to develop?

State the question, method, setting, or responsibility you need next. “I want a good career” is too broad to guide a source-backed choice.

Does each expectation have a source?

If you expect training, method access, mobility, a partner setting, funding, or a particular role, find the page that states it. If the page does not state it, mark it as a question.

Are you treating a pathway as a guarantee?

A PhD, postdoc, fellowship, network, or institute role can create experience. It cannot promise a future job, visa, grant, tenure, or salary. Keep your conclusion at the level of evidence.

Have you included your own conditions?

Personal circumstances, finances, wellbeing, family responsibilities, location preferences, language, and practical constraints are real parts of a decision. They are not weaknesses in the map. Record them privately and compare them honestly with the current terms.

Is there a sensible next action?

The action may be to search opportunities, read a field source, verify an offer, contact a formal owner with one question, prepare an application, or pause. A useful map always leads to one of these actions.

Keep facts, preferences, and predictions in separate places

Career decisions become confusing when a personal hope is written as though it were a fact. A role description may state that a project is funded for a defined period. You may prefer the location. A mentor may think the work could broaden your network. These are three different kinds of information and they should not be merged into one conclusion.

Use a small separation in your notes:

The same care applies to claims about career sectors. A PhD can be useful in industry, public research, universities, and other settings, but the current role you are considering may not expose you to each of them. A postdoc may develop independence in one context, but it cannot promise a later faculty role. A partnership may create a useful contact, but it cannot promise employment. Write the value of the role at the level it actually supports.

This is not pessimism. It makes the positive reasons more credible. You can say, “This current fellowship route is worth exploring because it combines a host project with a method and setting I want to develop.” You do not need to claim that it determines the rest of your career.

Use a source hierarchy when pages conflict

When two sources say different things, begin with the one closest to the decision. A current vacancy controls the application route. A funder call controls the fellowship terms. A university programme page controls degree and admissions information. A group page controls its public research description. A third-party directory, search snippet, old news item, or social post may help you find the source but should not control the conclusion.

If a current role page is vague while a historic project page is detailed, use the historic page only as context. Ask the named owner where the current details are held. If a host page says one thing and a funder call says another, preserve the difference in your notes and follow the formal source for the rule in question. Do not solve the conflict by choosing the better-looking outcome.

Let a missing answer change the next move

Some unknowns are minor. Others decide whether a role is possible. A missing seminar schedule may not matter. A missing application owner, funding condition, formal host, degree route, essential method, or eligibility rule may matter a great deal. Give those questions priority and stop building the rest of the application until you have found the controlling source or an appropriate contact.

The most useful career map is therefore not a list of ambitions. It is a record of decisions you can explain: what you want to develop, which current role may support it, which source says so, and what you still need to verify.

Use time in a role deliberately

Once you start a research role, career planning does not stop. The role becomes a place to build the evidence that informed your decision. Set a small development intention early: a method you want to understand, a question you want to be able to explain, a collaboration you want to contribute to responsibly, or an output you want to complete carefully.

Review that intention with the actual project rather than forcing it onto the work. The project's needs, supervisor guidance, partner conditions, and ethics or data rules come first. Your personal map should help you notice learning opportunities, not create commitments that the role never offered.

At a natural milestone, record what changed. Perhaps a method turned out to be less central than expected but you learned a stronger way to design an experiment. Perhaps a collaboration showed you that you prefer applied research. Perhaps the work confirmed that you want deeper theoretical training. Each result is useful evidence for the next map.

This is also a good time to update your sources. Replace old opportunity pages with the current role description, project record, programme information, and outputs you can responsibly describe. Your future applications will be stronger when they are built on work you actually completed, not a generic story about career ambition.

Do not wait for a perfect record

Research careers develop through partial evidence. You may not yet have a publication, a large grant, an international network, or every method you want. That does not make a careful next step impossible. Look for a role where your existing preparation is relevant and where the next development is realistic.

The important standard is accuracy. Be clear about what you have done, what you want to learn, and what the current opportunity can genuinely support. This is more persuasive and more sustainable than presenting a polished but unsupported career narrative.

Use the map to keep moving with evidence

Your career direction will become clearer through research itself. The aim is not to prove that one path is universally right. It is to select a next research setting that gives you a real chance to learn the work you care about, then reassess with better evidence.

Explore STEM fields to refine the research language in your map, opportunities to find current routes, and universities to assess the research environments behind them. When you have a specific PhD or postdoc role, return to the controlling source before you make a decision.

Sources for further checking

• NIH: Postdoctoral and Residency Training, for one official description of postdoctoral development and career transition in a defined context.
• NIH Funding Programs by Career Stage, for an official example of research training and career-development programmes by stage.
• MSCA Postdoctoral Fellowships, for a current example of host-led postdoctoral fellowship structure, skills development, and mobility conditions.
• UKRI Statement of Expectations for Doctoral Training, for a funder framework around doctoral training, support, and development.
• SNSF Postdoc.Mobility, for a current example of a mobility fellowship whose call documents control individual conditions.
• DORA: San Francisco Declaration on Research Assessment, for the limits of journal-based metrics as a stand-in for research and researcher assessment.
• UNESCO Recommendation on Open Science, for a wider framework around research culture, capacity building, infrastructure, and collaboration.
• The current opportunity, employer, host group, doctoral-school, funder, and research-organisation pages for the role you are considering. Those pages control the facts needed for your decision.