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

Low-code-разработчик → Инженер безопасност ИИ

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

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

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

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

79%strong route

This is a strong route. The strongest support is Market opportunity (94%), while the main constraint is Entry accessibility (68%). The index estimates the distance between roles, not your ability.

Skill transfer72%

Task similarity80%

Entry accessibility68%

Market opportunity94%

Resilience gain94%

Начална професияLow-code-разработчик · 60%

→

Оценка на обучението6–12 месеца

→

Целева професияИнженер безопасност ИИ · 14%

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

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

Работата се измества от Routine operations към Control and accountability — промяна с 20 точки. Това е основната промяна в начина на работа при прехода.

Low-code-разработчикИнженер безопасност ИИ80% · profile similarity

Analysis and data

People and communication

Creation and design

Hands-on work

Control and accountability

+20

Routine operations

-20

Low-code-разработчик: high-exposure tasks

Генерация типового кода и конфигураций72%

Подготовка тестов и технической документация68%

Классификация ошибок и анализ журналов64%

Инженер безопасност ИИ: high-exposure tasks

Сбор и перенос типових данни32%

Подготовка на стандартни документи27%

Търсене и класифициране на информация23%

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

understanding of the processes that will be digitized
комуникация
контрол на качеството
разбиране на процесите
професионална експертиза

Needs development

ИИ-инструменти
работа с данни
проверка результатов моделей
етика и безопасност
предметная експертиза
профессиональная експертиза

ИИ-инструменти

Prove it in “Applied case: Low-code-разработчик → Инженер безопасност ИИ transition case”: include a distinct output that uses иИ-инструменти.

5 wk

start 30%target 88%

работа с данни

Prove it in “Applied case: Low-code-разработчик → Инженер безопасност ИИ transition case”: include a distinct output that uses работа с данни.

5 wk

start 20%target 92%

проверка результатов моделей

Prove it in “Applied case: Low-code-разработчик → Инженер безопасност ИИ transition case”: include a distinct output that uses проверка результатов моделей.

6 wk

start 22%target 85%

етика и безопасност

Prove it in “Applied case: Low-code-разработчик → Инженер безопасност ИИ transition case”: include a distinct output that uses етика и безопасност.

6 wk

start 42%target 81%

предметная експертиза

Prove it in “Applied case: Low-code-разработчик → Инженер безопасност ИИ transition case”: include a distinct output that uses предметная експертиза.

7 wk

start 32%target 93%

профессиональная експертиза

Prove it in “Applied case: Low-code-разработчик → Инженер безопасност ИИ transition case”: include a distinct output that uses профессиональная експертиза.

7 wk

start 34%target 92%

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

14mo.4 h/week
242 hours total

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

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

First apply ИИ-инструменти 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 месеца
Trade-off: The pace allows market feedback without abruptly ending the current career.

After the foundation in ИИ-инструменти, 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 месеца
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.

Low-code-разработчик→Инженер аналитических системи→Инженер безопасност ИИ

in 89%out 72%≈ 14 мес.

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

First leg →Second leg →

Low-code-разработчик→Проектант рабочих процеси с ИИ→Инженер безопасност ИИ

in 89%out 72%≈ 14 мес.

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

First leg →Second leg →

Low-code-разработчик→Инженер дигитални доказательств→Инженер безопасност ИИ

in 64%out 89%≈ 14 мес.

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

First leg →Second leg →

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.

36 hours

Applied case: Low-code-разработчик → Инженер безопасност ИИ 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 Low-code-разработчик. Make it visible: show which beginner mistakes it helps you avoid.

What the project folder should contain

A working output an interviewer can open, test and discuss
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 иИ-инструменти
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

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

Within the modeled horizon, income may not return to the current level; plan a financial buffer in advance. This is a scenario model, not a pay promise.

Now€2 940

During study€2 881

First offer€1 313

+1 година€1 488

+2 години€1 770

Model horizon€2 680

Show long-term salary comparison through 2035

Low-code-разработчик€2 940 → €4 370

Инженер безопасност ИИ€1 570 → €2 680

Explore current market ↗Search target-role jobs ↗

08 · Technology horizon

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

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

2026

60%Low-code-разработчик14%Инженер безопасност ИИ

2028

63%Low-code-разработчик21%Инженер безопасност ИИ

2030

67%Low-code-разработчик29%Инженер безопасност ИИ

2035

72%Low-code-разработчик40%Инженер безопасност ИИ

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.

Less certainty than it appears

Many decisions in the target role are made with incomplete information, and quality is not visible immediately.

The daily rhythm will change

The target role contains substantially more personal accountability and checking others’ work. That can be tiring even when the occupation sounds appealing in theory.

Entry pay may dip

Modeled average pay in the target occupation is lower. A financial buffer or an internal project may help avoid losing seniority.

10 · Where to start

Suggested sequence

01
Прегледайте 20–30 вакансии за Инженер безопасност ИИ и запишете реалните задачи, задължителните изисквания и инструментите.
02
Определете връзката с Low-code-разработчик: understanding of the processes that will be digitized. Подгответе два примера, в които този опит е дал измерим резултат.
03
Научете ИИ-инструменти and работа с данни to the level of completing an independent practical task—not merely finishing a course.
04
Create a safe lab case with a threat model, detection, response and report without touching third-party systems.
05
Review 20–30 vacancies and choose only courses or certificates that repeatedly appear in employer requirements.
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.