Career transition

Penetration testing Researcher → Data Analyst

Not generic reskilling advice, but an analysis of the distance between two specific occupations: tasks, skills, pace, money and risk.

01 · Starting distance

Transition realism index

Five factors answer a more useful question than “will it work?”: where the route is naturally strong and where proof is needed.

61%major-rebuild transition

This is a major-rebuild transition. The strongest support is Entry accessibility (68%), while the main constraint is Resilience gain (35%). The index estimates the distance between roles, not your ability.

Skill transfer62%

Task similarity67%

Entry accessibility68%

Market opportunity67%

Resilience gain35%

Starting rolePenetration testing Researcher · 18%

→

Learning estimate6–12 months

→

Target roleData Analyst · 51%

02 · What changes in the work

Task comparison

The work shifts from Control and accountability toward Analysis and data, a 33-point change. This is the main behavioral adjustment in the move.

Penetration testing ResearcherData Analyst67% · profile similarity

Analysis and data

+33

People and communication

Creation and design

-2

Hands-on work

Control and accountability

-27

Routine operations

-4

Penetration testing Researcher: high-exposure tasks

Data Analyst: high-exposure tasks

03 · Foundation and gaps

Skill-gap map

The map shows the gap between your starting point and a level you can demonstrate to an employer through work evidence—not simply “know / do not know.”

Already transferable

risk assessment and incident response
threat assessment
procedural discipline
incident response
evidence preservation

Needs development

SQL and data preparation
visualization and forecasting
AI-agent-assisted development
architecture and system design
AI-generated code security
observability and DevOps

SQL and data preparation

Prove it in “Working prototype: Penetration testing Researcher → Data Analyst transition case”: include a distinct output that uses sQL and data preparation.

5 wk

start 28%target 80%

visualization and forecasting

Prove it in “Working prototype: Penetration testing Researcher → Data Analyst transition case”: include a distinct output that uses visualization and forecasting.

5 wk

start 42%target 83%

AI-agent-assisted development

Prove it in “Working prototype: Penetration testing Researcher → Data Analyst transition case”: include a distinct output that uses aI-agent-assisted development.

6 wk

start 44%target 80%

architecture and system design

Prove it in “Working prototype: Penetration testing Researcher → Data Analyst transition case”: include a distinct output that uses architecture and system design.

6 wk

start 21%target 80%

AI-generated code security

Prove it in “Working prototype: Penetration testing Researcher → Data Analyst transition case”: include a distinct output that uses aI-generated code security.

7 wk

start 41%target 77%

observability and DevOps

Prove it in “Working prototype: Penetration testing Researcher → Data Analyst transition case”: include a distinct output that uses observability and DevOps.

7 wk

start 21%target 89%

04 · Choose a pace

Three transition scenarios

The same route affects work, money and fatigue differently. A duration without weekly effort says very little.

Keep your current job

14mo.4 h/week
242 hours total

Two short weekday sessions and one hands-on weekend block.

First applications: 11 months
Trade-off: Income is protected, but market feedback arrives later.

First apply SQL and data preparation in the current role, then build the portfolio.

balanced default

Balanced route

9mo.7 h/week
273 hours total

Three weekly sessions: theory, practice and one end-to-end project.

First applications: 6 months
Trade-off: The pace allows market feedback without abruptly ending the current career.

After the foundation in SQL and data preparation, move into the project and first interviews.

Accelerated entry

6mo.12 h/week
312 hours total

Four study blocks weekly, weekly practice and mentor review.

First applications: 4 months
Trade-off: The new qualification develops faster, but fatigue and a shallow portfolio are real risks.

Start applying before training ends and improve evidence every week.

05 · If the direct jump is too large

Bridge occupations

These are not mandatory stops. They matter when they provide paid experience in the new kind of work before the full move.

Penetration testing Researcher→AI Security Engineer→Data Analyst

in 89%out 62%≈ 14 mo.

The AI Security Engineer role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.

First leg →Second leg →

Penetration testing Researcher→Deepfake Forensics Analyst→Data Analyst

in 89%out 62%≈ 14 mo.

The Deepfake Forensics Analyst role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.

First leg →Second leg →

Penetration testing Researcher→AI Engineer→Data Analyst

in 64%out 87%≈ 14 mo.

The AI Engineer role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.

First leg →Second leg →

06 · Evidence over certificates

Portfolio project

One project cannot replace experience, but it gives an employer something concrete to discuss and shows you can finish real work.

36 hours

Working prototype: Penetration testing Researcher → Data Analyst transition case

Take a real but anonymized situation from your current field and solve it as a Data Analyst would. The central project task is a role-specific task.

Your advantage is domain context from Penetration testing Researcher. Make it visible: show which beginner mistakes it helps you avoid.

What the project folder should contain

A repository or interactive prototype with architecture, tests and a demo
A concise decision memo covering inputs, constraints and two rejected alternatives
A result check using measurable criteria plus one failed approach and what changed
A public 5–7-screen case study with all confidential data removed

What makes the project strong

visible use of sQL and data preparation
a real-world problem rather than a tutorial exercise
a measurable outcome and explicit limitations
enough depth to support technical interview questions

07 · България · pay before tax

Income trajectory

In the baseline scenario, modeled income returns to the current level about 9 months after learning begins. This is a scenario model, not a pay promise.

Now€1 540

During study€1 509

First offer€2 162

+1 year€2 616

+2 years€3 050

Model horizon€3 950

Show long-term salary comparison through 2035

Penetration testing Researcher€1 540 → €2 450

Data Analyst€2 830 → €3 950

Explore current market ↗Search target-role jobs ↗

08 · Technology horizon

How automation risk changes

The target role is not necessarily safer. By 2035, its modeled risk is 38 points higher. Risk reduction should not be the only reason to move.

2026

18%Penetration testing Researcher51%Data Analyst

2028

25%Penetration testing Researcher68%Data Analyst

2030

33%Penetration testing Researcher73%Data Analyst

2035

43%Penetration testing Researcher81%Data Analyst

09 · An honest check

What you may not like

A good career choice is more than a list of benefits. Before studying, check whether you can live with the target role’s daily reality.

Debugging consumes real time

Much of the output is invisible until late; days include root-cause analysis, documentation and detail work.

The daily rhythm will change

The target role contains substantially more working with data and ambiguous conclusions. That can be tiring even when the occupation sounds appealing in theory.

Market pay is not first-offer pay

Even when average pay is higher, a newcomer’s first offer is usually lower. A strong project and domain experience reduce—but do not erase—the gap.

10 · Where to start

Suggested sequence

01
Review 20–30 Data Analyst vacancies and record actual tasks, mandatory requirements and tools.
02
Define the bridge from Penetration testing Researcher: risk assessment and incident response. Prepare two examples where this experience produced a measurable result.
03
Learn SQL and data preparation and visualization and forecasting to the level of completing an independent practical task—not merely finishing a course.
04
Build a working prototype, publish the code in a repository, and add tests, documentation and a decision record.
05
Review 20–30 vacancies and choose only courses or certificates that repeatedly appear in employer requirements.
06
Rewrite your résumé for Data Analyst, add the case and begin with test applications, internships, projects or adjacent tasks at your current employer.

All timelines, salaries and percentages are scenario estimates. They depend on starting skills, location, experience, weekly study time and employer requirements. Validate the route through practitioner conversations, a test project and real vacancies.