@NickDragon thanks for posting, this is a hot topic in the community. I agree with @sbessire on willingness to use XML and understanding what is already there in the data model and how to use it.
My two cents is that if I were hiring someone today I would be looking for people with techno/functional ERP experience. Understanding of the domain goes a long way in speeding up the learning curve and anyone who has worked with other ERP systems will understand customers, orders, invoices, products, etc. This might also be a way to get around the tech problem. People that have worked in environments like SAP, Oracle, Netsuite, etc. use the tools available in those systems and will have different expectations about tools. The primary skill set they bring to the table is ERP, not general / custom software development.
There will always be a need for specialized skills to build apps that interface with Moqui. Brainfood has shown some examples of their work in our community calls and if you go the direction of headless commerce you can build a UI using whatever you want. As long as well defined APIs are exposed to those developers you can maintain a clean separation of responsibility and they do not need to know or care what is under the hood.
2 Likes