We build and grow Magento 2, Shopify and Pimcore platforms for manufacturers and for brands selling B2C, B2B and D2C. We are looking for people who want to own their part of a project, talk straight and grow their skills on real e‑commerce projects.
Open roles1
Freelancer Magento Developer
List checked
You work on tasks where the store exchanges data with an ERP, a PIM, a WMS and other systems. On top of that come new markets, language versions, B2B price lists, payments and development of the platform after go-live. What the work covers depends on the role and the project, but the tasks carry a real business context.
We analyse the current processes, prepare the architecture and move selling onto the new platform. A migration also covers data, SEO, integrations and the way the switch itself is made.
We connect the store to the systems that hold products, prices, orders and stock. A good integration needs an understanding of the process on both sides of the API, not just its documentation.
A platform keeps changing after go-live. The team works through the backlog, performance, security and the next set of selling features.
Code review, testing and documentation help keep one shared standard of work. In technical roles a second developer also reviews your change — that is part of the process and the way knowledge is shared across the team.
Read the case study
Read the case studyThe facts that are the same for the whole team. Work mode and form of cooperation are not among them — they differ between positions, so each posting states them separately.
The same for the whole team
We do not state one work model for the whole company. The mode — remote, hybrid or office — and the form of cooperation belong to a specific role, and you will find them in the posting before you send a CV.
Being allowed to attend a training course does not answer the question of how to reach the next level. Below are the parts of development that work today — with no promises we do not confirm in a posting.
A conversation with your leader once a month: what went well, what is blocking the work, and what you are working on before the next step. A fixed point, not a once-a-year review.
A team meeting once a week, going through solutions from current projects, what we learned from builds, and the things that did not work for somebody.
Work on Magento 2, Shopify, Pimcore and Hyvä across projects of different sizes — from integrations to full B2B builds. Competence grows on projects, not on courses beside them.
Development towards certifications in the technologies we work with. What is supported for a specific certification is settled with the role rather than promised up front for everyone.
Taking part in e‑commerce industry events, including as a speaker. Where we turn up is on the Where to meet us page.
A description of what the next level requires. You know which areas you already have and what you are working on before the next step.
We do not publish the size of a training budget or a list of funded certifications: those terms depend on the role and the form of cooperation, so we state them in the posting and during the process, before any decision is made.
The terms of a specific role are there before you send a CV. Work model and benefits differ between positions and between forms of cooperation, so every posting states them separately.
What every posting states
Building modules and shipping features on e‑commerce platforms, improving existing stores, and integrating them with the systems on the client's side — PIM, ERP and others.
TechnologiesMagento 2, PHP 8+, MySQL, Git, REST, SOAP
Leave your CV in #aurorafuture and tell us which area interests you. The HR team will get in touch once a recruitment matching that area opens.
List checked
Below is the full route. Which stages apply to a given position — in particular whether there is a recruitment task, and whether the interview is a subject-matter or a technical one — is stated in the posting, before you send a CV.
You apply through the form attached to the posting. A CV and the role you are applying for is all it takes.
What you getConfirmation that your application reached us
The HR team checks your experience against the scope of the role, and consults whoever is running the recruitment on the technical questions.
What you getWord on what happens next
Not every position has one, and the posting says so plainly. Where there is one, you know its scope, the deadline and how it will be assessed before you start.
What you getA response to the task within 3–4 days
You talk — remotely or in the office — to the people you could work with. Which kind of interview it is depends on the role. This is the point for your questions about the tasks, the project, the technologies and how the team works.
What you getAnswers on the role, the project and the team
After the interview we come back with a decision within 7 days. You can count on feedback also when the process ends earlier than that.
What you getA decision within 7 days, and feedback
You get the terms in writing: the scope of the role, the form of cooperation, the work mode and the pay. None of it appears for the first time at this point.
What you getThe terms in writing, with no surprises
Once you accept the offer you get the organisational details, a plan for the first days and the support of the person responsible for bringing you into the organisation.
What you getA plan for the first days and someone to onboard you
Recruitment is run in line with article 11a of the Polish Labour Code. We provide equal opportunity, without discrimination on the grounds of gender, age or any other protected characteristic.
Leave your CV in #aurorafuture and tell us which area interests you. We will come back to your application once a recruitment matching your experience opens.
Worth adding to your application
