Unfortunately, I don't have this experience. In my last job I've had "so-called" hands-on experience with the frameworks and SQL, however it was more of maintenance, not development. If someone asks me to build an application using these from scratch, I'm likely to fail / not understand what I'm doing.
Maintenance and experience working in other people's existing and legacy code is far more valuable since it's where the vast majority of effort happens.
Initial project setup for any new codebase/repository happens only once and takes a short period of time. Long-term maintenance and evolution of that project can last for decades and involve many people. In your current position, being able to create a new project from scratch isn't particularly important as far as experience is concerned. The other experience you mentioned about REST integrations and Cryptography sounds far more valuable.
Since you're not applying for senior or technical leadership positions, the vast majority of jobs out there won't ask you to build brand new projects from scratch by yourself because those are a significant investment for any employer or client; they'd generally insist on having strong technical leadership and involvement from others in the business to make sure that the fundamentals of the project are strong.
In the unlikely event that you are asked to create a new project by yourself, the company would most likely already have other projects and documentation which define a set of patterns and standards that you'd be expected to mirror, or even a start-up template, in which case you'd follow/copy those, but almost certainly with oversight by a senior engineer.
If you have a new project, then any sensible company would want to make sure there's sufficient technical oversight and leadership from senior engineers to support the people doing the 'real' work, and also acting as reviewers/gatekeepers to ensure quality is up to par and be looking out for potential problems
In a typical New project scenario, there also tend to be a whole myriad of issues to grapple with and a lot of different people involved, with a relatively long 'inception' or 'discovery' period before any deliverable project artefacts are created or any code is written, so this is a significant amount of time that you'd have as a developer to understand what you need to do before creating the project.
Before even thinking about the project's code structure you would be involved in project planning, requirements analysis, big-picture architecture; the initial phase nearly always involves a great deal of learning and de-risking for everyone involved in the project - developers are usually tasked with learning any new tools or technologies that they've never used before.
Overall, it's never in any company's interests for any project to be handled exclusively by a single lone-wolf employee, and any sensible employer will already understand the need for a significant ramp-up time for the project team to learn and figure out what they need to do, as well as the need for that team to get plenty of support before the team can be productive.