How to think over a test task / selection for a Bitrix developer (middle and above)?

Question

1C-Bitrix

My task is to assess the level of the developer who will support and develop the project on Bitrix. The quality of the code from past generations of developers is sad (outsource). Now there is a desire to take the development in house, and set up this process normally: with a review, normal practices, composer, upgrade from php5.3, etc. This is all in other projects and teams, but no one knows how and does not want to work in Bitrix.
Your experience is of interest:
- what test tasks did you use when hunting under Bitrix
- what can be taken as the basis of the test task
- what to look for during an interview
There is, for example, such an article: https://dev.1c-bitrix.ru/learning/ course/index.php...
You can ask to create a component with some simple functionality based on it. But what about Bitrix with licensing? Is it possible to place a ready-made solution on github and make it so that it can be run without problems for verification by cloning?
I worked with bitrix many years ago and I no longer have up-to-date knowledge in this system. I do reviews, but after a few years of using frameworks, it all seems like hell to me. In general, there is some bias towards the subject))
Thanks to the collective mind!

Answer 1

If the task is to evaluate the level of the developer, I would start sequentially, from some basic things to the most complex ones.
From a basic level:
1. Talk to a person how the site template is tripled (in terms of design integration), what files are included in it. Ask about mogositeness. You can hook language files.
2. Chat about components - what files can be included in the component, what data goes into the component. Ask about filtering elements (if they are list elements), about caching.
As a test task for understanding and knowledge of api
1. Offer to make a list of news with filtering by month and year.
2. Display the previous element and the next (you can also use the news list as an example
)
1. This is, of course, a deeper knowledge of the API and the principles of the System.
2. Of course, platform events.
3. Ask about code optimization when developing on bx frameworks.
4. The ability to create your own component (at least by analogy with the already created one)
If the shop:
5. In general, ask about the commerce module of the system, what goes into it (products, sku, groups)
6. Integration with 1s.
7. Setting up payments, warehouses, orders, discounts, deliveries.
8. Filtering and search by catalogue.
Tasks:
For events:
1. To fill in a web form (from the form module), create 2 additional fields, and when adding the result, add the url and the name of the page from which it was sent.
2. Also for web forms to implement a "substitution" of the recipient, the recipient will be set by the field - select, for example, the Office field, and for each office there is a recipient of the letter.
Component:
1. Create your own component such as an accordion or a list grouped by sections. (You can mess with the parameters :)
Well, everyone who is higher level:
1. d7 \ ORM
2. Own modules or complex architectural solutions.
3. Optimization of hosting \ vm under
4. Complex integrations
Here, I didn’t come up with a test task except to write modules)) Most likely there will be a real portfolio of problem solutions.
PS The list dashed off in a couple of minutes, not a panacea, it can be destructured or rethought.

Answer 2

Somehow in TK, among other things, I was asked to create a module for storing data on d7 + orm