Careers at Virtek · engineering team

Complex systems are built by
people who earn trust

Virtek has more than 60 employees, while its wider delivery network brings together over 100 specialists. Teams are formed around real work—from software and data to infrastructure, cybersecurity, industrial automation and operations.

Open to strong specialists and project teams

Engineering practices

Different disciplines.
One outcome

Specialists join where their expertise changes the result. Architecture, software, security and operations work as one delivery chain rather than isolated contractors.

DEV

Software engineering

Enterprise portals, web services, mobile applications, integrations and industry systems from discovery to production support.

SEC

Cybersecurity

Security architecture, control implementation, identity, monitoring, response and cyber resilience.

INF

Infrastructure and data centres

Servers, storage, virtualisation, networks, backup, facility readiness and cloud environments.

OT

Industrial automation

SCADA, IIoT, telemetry, supervision, equipment integration and secure interaction between operational and corporate systems.

AI

Artificial intelligence and data

Private models, RAG, agent workflows, data platforms, analytics and GPU infrastructure with controlled access.

OPS

Support and operations

Service Desk, monitoring, operating procedures, SLA, diagnostics, recovery and continuous improvement.

ARC

Business analysis and architecture

Process assessments, architecture concepts, requirements, integration models and digital development roadmaps.

ERP

1C and enterprise integrations

1C development, data exchange with external systems, APIs, queues, master data and end-to-end process automation.

BMS

Building and low-current systems

Access control, video surveillance, building management, communications, monitoring and on-site equipment integration.

EUC

Digital workplaces and VDI

Virtual desktops, remote access, user profiles, device management and secure application delivery.

COM

Enterprise communications and cloud

Messaging, video meetings, telephony, file cloud and collaboration in local or managed environments.

VIS

Technical visualisation and 3D

Three-dimensional models, engineering graphics, interactive demonstrations and clear visualisation of complex technical solutions.

Engineering culture

Do more than complete a task.
Own the system

We value autonomy without leaving an engineer alone with risk. Decisions are discussed, tested and documented, and knowledge remains available to the wider team.

Context before technology

Understand the business process, constraints and cost of failure before choosing a stack or architecture.

Validate before production

Important hypotheses go through a test bench, pilot, load test or architecture review.

Documentation is part of delivery

Diagrams, decisions, instructions and change history are created with the system, not after it.

Lifecycle ownership

Design accounts for implementation, support, security, upgrades and recovery from failure.

Development inside the team

Learn through work
that can be validated

Growth is grounded in practice: a mentor helps establish context, adjacent teams broaden engineering judgment, and the laboratory makes it possible to test decisions safely before touching production.

Mentoring

At the start, we agree responsibility, review points and a person who can provide meaningful engineering feedback.

Reviews and learning sessions

We discuss architecture, code, incidents and test results so knowledge does not depend on one specialist.

Virtek Laboratory

We build test environments, compare technologies, reproduce workloads and turn hypotheses into measurable evidence.

Training and certification

Learning is matched to the role, project context and technologies a specialist uses or plans to use.

A laboratory for engineering curiosity

Test a new platform, AI model, resilience design, integration or failure scenario without risking a customer's working system.

Explore the laboratory

Roles and open disciplines

We look beyond keywords
for engineering judgment

Open roles change with the project portfolio. These are disciplines where we regularly meet specialists. The specific role, working format and expectations are discussed after an initial substantive conversation.

Servers · networks · virtualisation

Infrastructure engineer

Design, deployment and diagnostics for enterprise infrastructure and technical facilities.

Discuss this discipline
Protection · monitoring · identity

Cybersecurity engineer

Security architecture and operations, event investigation and continued control improvement.

Discuss this discipline
Web · API · integrations

Backend / Full-stack engineer

Enterprise services, customer portals, integration solutions and internal products.

Discuss this discipline
SCADA · IIoT · telemetry

Industrial automation engineer

Automation, supervision, equipment connectivity and integration of operational data.

Discuss this discipline
LLM · RAG · Data

AI and data engineer

Enterprise AI services, data pipelines, quality evaluation and high-performance infrastructure.

Discuss this discipline
Service Desk · monitoring · SLA

Support engineer

Diagnostics, user communication, service recovery and knowledge-base development.

Discuss this discipline

Internships and early careers

A first assignment should be
real and manageable

An internship is built around a bounded engineering task with a clear outcome, not artificial busywork. Discipline, duration and participation format depend on the candidate's preparation and current team capacity.

  1. Introduction

    Discuss interests, foundational knowledge, available time and the discipline the candidate wants to develop.

  2. Practical assignment

    Select a safe lab or internal scenario with explicit boundaries and completion criteria.

  3. Mentor and feedback

    Hold regular reviews, examine decisions and connect technology with production operations.

  4. Next step

    Use the result to define further learning, project participation or a suitable role in the team.

Meet the team

Tell us
what you can build

Apply for a discipline, propose an internship or discuss working as an external specialist or contractor. A résumé or portfolio link helps us move to a focused conversation sooner.

You do not need to force your experience into a job title. Describe your strongest skills, the problems that interest you and the working format you prefer.