Small team, short lines, and showing before telling
We have no written vacancies open at the moment. What we do have is an open line: anyone who fits the way the work is done here can get in touch and will hear back from someone who does that work.

What is discussed today is often ready tomorrow
MagicEverse is small, and here that is an advantage. There is no layer between the conversation and the work: whoever has a customer on the phone can open the environment, look in the log and make the change the same day. It also means you do not disappear behind a ticket system. You have one case, you know it, and you are accountable for it — to customers and internally.
The second habit is that we show first and tell afterwards. Before there is an order, a working demo is up in the customer's colours, with their own articles, on its own address. On 20 September 2026 there are 24 of those environments on our servers. That pace asks something of you: preferring something that runs tomorrow over something finished next year, and being willing to say a plan is a bad idea, even when somebody wanted to pay for it.
Real work, with real data
What gets built here involves eight supplier feeds, 74,136 products in eight languages and 15 running web shop environments. So there is little room for an environment where everything is tidy: feeds change, suppliers deliver differently than last month, and there is a log beside it recording what went wrong. The work is therefore less about inventing features and more about making data add up that somebody else's revenue depends on.
No promises we cannot keep, internally either
We would rather quote a number than a promise, and when there is no number we say so. That holds towards customers and it holds here: we do not promise a role that does not exist, progression nobody can deliver or a lead time we have not counted. What there is to say about working at MagicEverse today is on this page — including what is not on it yet.
Being the point of contact, not one link in a chain
Customers call one number, even when it is the supplier feed — and it usually is the supplier feed. So whoever works here touches the whole chain: the feed, the catalogue, the sales environment, the quotations and the administration behind them. That is heavier than one component, and it is also why you see more here in a year than in three years somewhere that puts you on a single layer.
People who want to finish things
Because there are no written roles, we can only say in general terms what fits here. It comes down to three things: you like working with practice rather than with a specification, you do not mind building something that will be looked at tomorrow, and you say when something is wrong. That last one is not a throwaway line: it is the reason there are no figures on this site that nobody has measured.
What kind of work it is depends on who gets in touch. There is work on product data and connections, on sales environments and portals, on the ERP chain from quotation to invoice, on agents and on design. What there is not is a department to disappear into. Tell us in your message what you can do and what you enjoy most, and we will say honestly whether there is work for that here — including when the answer is no.
One email is enough
There is no application portal, no cover letter in a fixed format and no personality test. Send an email saying who you are, what you can do and where you have done it, and that is enough to start. A link to work you have made tells us more than a list of qualifications; a short description of something you ran into and how you solved it tells us the most.
You will hear back from someone who does the work, not from a department. If there is no work that fits you right now we will say so, instead of filing you away and never getting back to you. And if there is something, it goes as it does with customers: first a three-quarter-hour conversation about the work, then something small and real to look at together.
- Who you are and what you can do, in a few lines.
- Where you have done it — a link to work is fine instead of a CV.
- Something you ran into and how you solved it.
- What you enjoy most, so we can say honestly whether there is work for it.
Rather see what we build first?
That works without a form: the references and the demo videos are open, and the page about our way of working shows step by step how a project runs here.
Want to ask something before you send a message? Calling works too; you will speak to someone who is doing the work, not a menu.