Software, data & systems engineering
Platform engineering, application development, data systems, infrastructure integration, automation and technical architecture.
Build systems with regional consequence.
Vidran Labs is building a multidisciplinary technology institution across engineering, product, design, research, strategy and applied systems. Roles should be published only when they are genuinely open.
ROLE FAMILIES
The disciplines Vidran expects to build around.
Product thinking for complex systems
Product management, interface design, service design, systems UX and design work that makes technical capability usable.
Questions, markets & institutions
Applied research, technology strategy, sector analysis and work that connects technical decisions to institutional and regional context.
HOW THE WORK CONNECTS
Different disciplines should be able to reason about the same system.
Understand the environment.
Good work starts with users, institutions, infrastructure, constraints and the operating consequences of technical decisions.
Think across layers.
Engineering, product and design decisions should make sense inside the wider software, data and infrastructure system.
Separate what is known from what is assumed.
Research, product status and project decisions should make uncertainty visible rather than covering it with confident language.
Finish the operational loop.
The work has to survive handoff, support, maintenance and the real conditions in which people use it.
WORKING PRINCIPLE
Technical ambition without performance theatre.
Vidran values clarity, curiosity, disciplined execution, evidence and the ability to understand the environment a system enters. The company should not promise culture, benefits, remote policies or career progression publicly until those practices are real and defined.
CURRENT OPENINGS
Roles will appear here when they are genuinely open.
There are no specific vacancies represented on this page unless an active role is explicitly listed below. Vidran may later publish internships, fellowships, graduate pathways or specialist roles when those programmes exist.
A USEFUL INTRODUCTION
Show how you think about consequential systems.
What can you contribute?
Engineering, design, product, research, strategy or another specialist capability relevant to the work.
What have you built or investigated?
Share relevant work, technical writing, products, research, systems or projects where your contribution can be understood.
What kinds of problems matter to you?
Explain the operating environments, sectors or technical questions you want to work on rather than only naming a job title.
TALENT INTEREST
Interested in future opportunities?
You can introduce yourself without treating the message as an application to a role that does not exist. Include your discipline, location, relevant work and the kind of problems you want to help solve.
Introduce Yourself