Software engineering
Enterprise portals, web services, mobile applications, integrations and industry systems from discovery to production support.
Careers at Virtek · engineering team
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 teamsEngineering practices
Specialists join where their expertise changes the result. Architecture, software, security and operations work as one delivery chain rather than isolated contractors.
Enterprise portals, web services, mobile applications, integrations and industry systems from discovery to production support.
Security architecture, control implementation, identity, monitoring, response and cyber resilience.
Servers, storage, virtualisation, networks, backup, facility readiness and cloud environments.
SCADA, IIoT, telemetry, supervision, equipment integration and secure interaction between operational and corporate systems.
Private models, RAG, agent workflows, data platforms, analytics and GPU infrastructure with controlled access.
Service Desk, monitoring, operating procedures, SLA, diagnostics, recovery and continuous improvement.
Process assessments, architecture concepts, requirements, integration models and digital development roadmaps.
1C development, data exchange with external systems, APIs, queues, master data and end-to-end process automation.
Access control, video surveillance, building management, communications, monitoring and on-site equipment integration.
Virtual desktops, remote access, user profiles, device management and secure application delivery.
Messaging, video meetings, telephony, file cloud and collaboration in local or managed environments.
Three-dimensional models, engineering graphics, interactive demonstrations and clear visualisation of complex technical solutions.
Engineering culture
We value autonomy without leaving an engineer alone with risk. Decisions are discussed, tested and documented, and knowledge remains available to the wider team.
Understand the business process, constraints and cost of failure before choosing a stack or architecture.
Important hypotheses go through a test bench, pilot, load test or architecture review.
Diagrams, decisions, instructions and change history are created with the system, not after it.
Design accounts for implementation, support, security, upgrades and recovery from failure.
Development inside the team
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.
At the start, we agree responsibility, review points and a person who can provide meaningful engineering feedback.
We discuss architecture, code, incidents and test results so knowledge does not depend on one specialist.
We build test environments, compare technologies, reproduce workloads and turn hypotheses into measurable evidence.
Learning is matched to the role, project context and technologies a specialist uses or plans to use.
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
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.
Design, deployment and diagnostics for enterprise infrastructure and technical facilities.
Discuss this discipline↘Security architecture and operations, event investigation and continued control improvement.
Discuss this discipline↘Enterprise services, customer portals, integration solutions and internal products.
Discuss this discipline↘Automation, supervision, equipment connectivity and integration of operational data.
Discuss this discipline↘Enterprise AI services, data pipelines, quality evaluation and high-performance infrastructure.
Discuss this discipline↘Diagnostics, user communication, service recovery and knowledge-base development.
Discuss this discipline↘Internships and early careers
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.
Discuss interests, foundational knowledge, available time and the discipline the candidate wants to develop.
Select a safe lab or internal scenario with explicit boundaries and completion criteria.
Hold regular reviews, examine decisions and connect technology with production operations.
Use the result to define further learning, project participation or a suitable role in the team.
Meet the team
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.