.NET engineering
Services, data access, console features and the client. Careful about compatibility and upgrade paths.
The interesting problems sit where the catalog meets the storefront, the tax rule meets the order and the old integration meets the new one.
Services, data access, console features and the client. Careful about compatibility and upgrade paths.
Storefront patterns, accessible interaction and the content that helps a shopper decide.
Test strategy, load measurement and the unglamorous work that keeps a catalog responsive.
Imports, exports, scheduling, reconciliation and the reality of back office systems.
Translate merchant needs into a model, an edition and a realistic delivery sequence.
Languages, currencies, tax markets and the details that make a store feel local.
This redesign does not invent vacancies. If you want to be considered for future work, send a speculative application through the contact form and choose Careers as the topic.
Include the work you are proud of, the part of the stack you know deeply and the kind of commerce problem you want to solve. A short, specific note is easier to route than a generic CV.
A link to a repository, a case study or a technical write up. Tell us what you decided and why, not only which tools you used.
Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.
Tell us the problem you want to work on. That is more useful than a list of technologies.