Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
To hire Magento developers well, first decide which model fits your store: a freelancer for small, well-defined tasks; an agency for projects that need several skills, continuity and accountability; or an in-house team when Magento is core to your business and there is enough work to keep developers busy year-round. Many merchants end up with a mix, such as an in-house product owner with an agency, or an in-house team backed by specialists. Then test candidates with a practical task that matches the work, not a generic quiz.
This guide gives a decision table by project size, risk and running cost, explains what each model is good and bad at, and provides interview tasks for each.
What kind of Magento skills you actually need
"Magento developer" covers several different jobs. Be specific before you hire:
- Backend developer: PHP modules, plugins and observers, service contracts, APIs, integrations, indexing and performance.
- Frontend developer: themes and templates; Luma (LESS, Knockout.js, RequireJS), Hyvä (Tailwind CSS, Alpine.js) or a headless stack (React, Next.js, GraphQL).
- App Builder developer: JavaScript and Node.js for out-of-process extensions, which Adobe Commerce as a Cloud Service requires.
- DevOps: hosting, deployments, Varnish, OpenSearch, Valkey, monitoring and scaling.
- Solution architect: designs integrations and data flows and makes build-or-buy calls.
One person rarely covers all five well. That fact alone often decides the model.
Decision table: freelancer, agency or in-house
| Factor | Freelancer | Agency | In-house |
|---|---|---|---|
| Best project size | Small, defined tasks: a bug, a small module, a theme tweak | Builds, replatforms, upgrades, integrations, ongoing support | Continuous roadmap with steady, year-round work |
| Skills coverage | One person's skill set | Backend, frontend, DevOps, QA and architecture on demand | Whatever you hire; gaps need hiring or partners |
| Delivery risk | High if the person becomes unavailable; no cover | Lower; team cover and process, but depends on agency quality | Low once established; high during hiring and if a key person leaves |
| Knowledge retention | Leaves with the person unless documented | Retained in the agency team and documentation | Strongest, if people stay |
| Running cost shape | Pay per task or hour; lowest commitment | Project fees or monthly retainer; you pay for management and cover | Salaries, benefits, recruitment, tools and training, whether busy or not |
| Speed to start | Fast | Moderate; discovery first | Slow; hiring takes time |
| Management effort on your side | High; you are the project manager | Moderate; you need a product owner | High; you manage people and process |
| Accountability | Personal; limited recourse | Contractual, with defined service levels | Managerial, through your own organization |
Common hybrid models
- In-house product owner plus agency: you own priorities and acceptance; the agency delivers. Works well for most mid-size merchants.
- Small in-house team plus agency for peaks: your developers handle daily work; an agency handles upgrades, replatforms or specialist areas.
- Agency plus trusted freelancer: a specialist freelancer for one skill, such as Hyvä or a specific ERP, inside the agency's process.
How to choose: three questions
- How much Magento work will you have over the next year? If it would not keep one developer busy most weeks, in-house is hard to justify.
- What happens if your developer is unavailable for a month? If the answer is "we cannot take orders when something breaks", you need cover: an agency or a team.
- Do you have someone to manage the work? Freelancers and in-house teams need a technical lead or product owner. Without one, an agency's project management is part of what you are buying.
Interview tasks for each model
Practical tasks reveal more than questions about how long someone has worked with Magento. Keep tasks short, relevant to your store and paid when they take more than an hour or two.
For a freelancer
- Code review task: give them a small custom module (with a class preference, direct SQL and a missing ACL rule) and ask what they would change and why. Strong candidates spot the risks and suggest plugins, repositories and declarative schema.
- Debugging task: describe a real symptom, for example "category pages slow after an extension install", and ask how they would investigate. Look for profiling, cache checks and log review, not guesses.
- Estimate task: ask them to estimate a small feature and list assumptions. A good estimate comes with questions.
For an agency
- Discovery sample: ask for an anonymized discovery or audit document from a past project. It shows how they think and write.
- Architecture task: describe one of your integrations (for example ERP stock and price sync) and ask for a short proposal: data flow, frequency, error handling and monitoring.
- Team interview: interview the lead developer who would work on your store, not only the sales lead. Ask them the code review task above.
- Process walkthrough: ask them to show a recent deployment pipeline and how a hotfix reaches production.
Our guide on how to choose a Magento development agency lists 20 questions with good and weak answers.
For an in-house hire
- Take-home module: build a small module that adds a product attribute, exposes it in GraphQL and shows it on the product page. Review it for structure, tests and coding standard compliance.
- Pairing session: work through a bug together in your codebase or a sample one. Watch how they navigate unfamiliar code.
- Upgrade discussion: ask how they would plan a move to 2.4.9, which requires PHP 8.5, OpenSearch 3 and Valkey 9. Look for an ordered plan, not a list of commands.
- Build or buy judgment: describe a feature and ask whether they would build it or buy an extension. Our article on building vs buying a Magento extension gives a framework you can compare their answer against.
Do certifications matter?
Adobe offers Commerce certifications at Professional, Expert and Master levels for developers, front-end developers, business practitioners and architects. A current certification shows that someone passed an exam on a recent version, which is a reasonable filter for screening. It does not replace a practical task: certified developers vary widely in code quality and judgment. Verify credentials through Adobe's credential verification or the Credly badge. Our guide to Adobe Commerce certifications explains which certification fits which role.
Red flags in any model
- Edits to core files or vendor code "because it was faster".
- No version control, or code delivered as zip files.
- Requests for shared admin or server logins instead of individual accounts.
- Estimates without assumptions or questions.
- No mention of testing, staging or rollback.
- Unfamiliarity with the Magento version and PHP version you run.
FAQ
Can one full-stack Magento developer run our store?
For a small store with few integrations, often yes, with a hosting partner for infrastructure. Plan for cover during holidays and illness, and make sure code and access are documented.
Should we hire offshore developers?
Location matters less than skills, communication and time-zone overlap for urgent issues. Apply the same practical tasks, and check how emergencies are handled outside your working hours.
What about custom extensions?
Custom modules become part of your upgrade surface, so whoever builds them should follow Adobe's extension patterns and leave documentation. If you need a dedicated build, see Mistri's Magento extension development service.
Next step
If an agency or a hybrid model fits, Mistri's Adobe Commerce development team works either as your full delivery team or alongside in-house developers. Ask us the same interview tasks you would ask anyone else.
Sources
Adobe Commerce certifications overview (Adobe Experience League); Adobe Commerce system requirements (Adobe Experience League); Adobe Commerce as a Cloud Service overview (Adobe Experience League).
