Careers at Wave Tech
We build systems across software, AI, data and infrastructure, for operations that cannot afford for them to fail.
Where you would be working.
- Offices
- Skopje, Macedonia and Belgrade, Serbia
- Products
- 6 built in-house, 3 of them live.
- Part of
- Wave Group, alongside Wave Advisory.
Four capabilities, one engineering practice.
People are hired into one of the four and expected to work across them. A system rarely sits in a single column.
01
Enterprise Systems Engineering
Architecture, backend systems, APIs and integrations designed around complex operations.
02
AI Infrastructure
LLMs, model APIs and multi-agent systems connected into real operational workflows.
03
Data & Intelligence Engineering
Pipelines, processing, NLP and analytical layers that turn distributed data into usable intelligence.
04
Cloud & Platform Engineering
Cloud environments, security, deployment and reliability for systems that have to keep running.
The same four stages, every engagement.
This is what a week here is shaped by, which is worth knowing before a vacancy exists rather than after one is advertised.
Define
We map the workflows, data, integrations and constraints already in place, then set the system boundaries around them.
Architect & Build
We design backend services, APIs, data pipelines and, where AI belongs, LLM APIs and agent orchestration as one architecture.
Deploy & Integrate
We connect the system into existing platforms and data sources, with the environments and access controls around it.
Operate & Scale
We keep the architecture evolving as data volumes, integrations, users and AI workloads grow.
The standard, before the vacancy.
These hold whether or not a role is open, which is why they are set out here rather than inside a job description.
- Systems that have to keep running
- The work is production engineering for operations that cannot stop while it happens. Architecture, failure modes and the cost of a rollback are part of the design conversation rather than a later concern.
- AI as infrastructure, not demo
- Models, APIs and agent orchestration are connected into real operational workflows with the data and access controls around them. Making something work once is not the bar.
- Working from the operation backwards
- Engagements start from what an organisation actually does, and the system boundaries are set around that. Engineers here are expected to understand the operation before proposing the architecture.
- Ownership through to operation
- The practice keeps architectures evolving as data volumes, integrations and workloads grow. What you build is what you continue to be responsible for.
Nothing open at the moment.
Vacancies are listed here when they exist, and only when they exist. The practice does not keep an open pipeline of postings.
Engineers who want to be considered when one opens are welcome to write. Tell us what you have built and what you would want to work on here; naming which of the four disciplines above your work sits closest to is the most useful thing you can send.
Write to the team