Кариерен преход

Тестер Go → Инженер аналитических системи

Не общ съвет за преквалификация, а анализ на дистанцията между две конкретни професии: задачи, умения, темпо, доход и риск.

01 · Начална дистанция

Индекс на реалистичност на прехода

Пет фактора отговарят на по-полезен въпрос от „ще стане ли?“: къде маршрутът е естествено силен и къде са нужни доказателства.

91%strong route

This is a strong route. The strongest support is Task similarity (96%), while the main constraint is Entry accessibility (86%). The index estimates the distance between roles, not your ability.

Skill transfer89%
Task similarity96%
Entry accessibility86%
Market opportunity94%
Resilience gain89%
Начална професияТестер Go · 58%
→
Оценка на обучението3–6 месеца
→
Целева професияИнженер аналитических системи · 27%

02 · Какво се променя в работата

Сравнение на задачите

Работата се измества от Analysis and data към Analysis and data — промяна с 0 точки. Това е основната промяна в начина на работа при прехода.

Тестер GoИнженер аналитических системи96% · profile similarity
Analysis and data
0
People and communication
0
Creation and design
0
Hands-on work
0
Control and accountability
0
Routine operations
0

Тестер Go: high-exposure tasks

Генерация типового кода и конфигураций70%
Подготовка тестов и технической документация66%
Классификация ошибок и анализ журналов62%

Инженер аналитических системи: high-exposure tasks

Генерация типового кода и конфигураций39%
Подготовка тестов и технической документация35%
Классификация ошибок и анализ журналов31%

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

  • knowledge of the sector, terminology and typical work situations
  • комуникация
  • контрол на качеството
  • разбиране на процесите
  • професионална експертиза

Needs development

  • a practical case for the Инженер аналитических системи role
01

a practical case for the Инженер аналитических системи role

Prove it in “Working prototype: Тестер Go → Инженер аналитических системи transition case”: include a distinct output that uses a practical case for the Инженер аналитических системи role.

5 wk
start 42%target 93%

04 · Choose a pace

Три сценария за преход

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

Keep your current job

8mo.4 h/week
139 hours total

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

First applications
6 месеца
Trade-off
Income is protected, but market feedback arrives later.

First apply a practical case for the Инженер аналитических системи role in the current role, then build the portfolio.

Accelerated entry

4mo.12 h/week
208 hours total

Four study blocks weekly, weekly practice and mentor review.

First applications
3 месеца
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

Междинни професии

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

Тестер Go→Проектант рабочих процеси с ИИ→Инженер аналитических системи
in 89%out 89%≈ 10 мес.

Професията Проектант рабочих процеси с ИИ позволява да усвоите част от новите задачи в по-познат контекст, а след това да се насочите към Инженер аналитических системи с по-силни доказателства за уменията си.

Тестер Go→Анализатор данни→Инженер аналитических системи
in 87%out 81%≈ 10 мес.

Професията Анализатор данни позволява да усвоите част от новите задачи в по-познат контекст, а след това да се насочите към Инженер аналитических системи с по-силни доказателства за уменията си.

Тестер Go→Инженер по кибербезопасности→Инженер аналитических системи
in 72%out 64%≈ 18 мес.

Професията Инженер по кибербезопасности позволява да усвоите част от новите задачи в по-познат контекст, а след това да се насочите към Инженер аналитических системи с по-силни доказателства за уменията си.

06 · Evidence over certificates

Проект за портфолио

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

24 hours

Working prototype: Тестер Go → Инженер аналитических системи transition case

Take a real but anonymized situation from your current field and solve it as a Инженер аналитических системи would. The central project task is генерация типового кода и конфигураций.

Your advantage is domain context from Тестер Go. Make it visible: show which beginner mistakes it helps you avoid.

What the project folder should contain

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

What makes the project strong

  • visible use of a practical case for the Инженер аналитических системи role
  • 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

Траектория на дохода

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

Now: €3 010Now€3 010During study: €2 950During study€2 950First offer: €2 776First offer€2 776+1 year: €3 024+1 година€3 024+2 years: €3 480+2 години€3 480Model horizon: €4 990Model horizon€4 990
Now€3 010
During study€2 950
First offer€2 776
+1 година€3 024
+2 години€3 480
Model horizon€4 990
Show long-term salary comparison through 2035
Тестер Go€3 010 → €4 470
Инженер аналитических системи€3 140 → €4 990
Тестер Go · 2026: €3 0102026Тестер Go · 2027: €3 1502027Тестер Go · 2028: €3 2902028Тестер Go · 2029: €3 4302029Тестер Go · 2030: €3 5902030Тестер Go · 2031: €3 7502031Тестер Go · 2032: €3 9202032Тестер Go · 2033: €4 1002033Тестер Go · 2034: €4 2802034Тестер Go · 2035: €4 4702035Инженер аналитических системи · 2026: €3 140Инженер аналитических системи · 2027: €3 310Инженер аналитических системи · 2028: €3 480Инженер аналитических системи · 2029: €3 660Инженер аналитических системи · 2030: €3 860Инженер аналитических системи · 2031: €4 060Инженер аналитических системи · 2032: €4 280Инженер аналитических системи · 2033: €4 500Инженер аналитических системи · 2034: €4 740Инженер аналитических системи · 2035: €4 990

08 · Technology horizon

Как се променя рискът от автоматизация

The move reduces modeled automation exposure by 21 points by 2035, but the target role is not immune: its task mix also changes.

2026
58%Тестер Go27%Инженер аналитических системи
2028
61%Тестер Go33%Инженер аналитических системи
2030
65%Тестер Go40%Инженер аналитических системи
2035
70%Тестер Go49%Инженер аналитических системи

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.

01

Debugging consumes real time

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

02

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.

03

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

  1. 01

    Прегледайте 20–30 вакансии за Инженер аналитических системи и запишете реалните задачи, задължителните изисквания и инструментите.

  2. 02

    Определете връзката с Тестер Go: knowledge of the sector, terminology and typical work situations. Подгответе два примера, в които този опит е дал измерим резултат.

  3. 03

    Научете a practical case for the Инженер аналитических системи role and a practical case for the Инженер аналитических системи role to the level of completing an independent practical task—not merely finishing a course.

  4. 04

    Build a working prototype, publish the code in a repository, and add tests, documentation and a decision record.

  5. 05

    Review 20–30 vacancies and choose only courses or certificates that repeatedly appear in employer requirements.

  6. 06

    Rewrite your résumé for Инженер аналитических системи, 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.