How to get the first order for development on No-code
We can confidently say that getting a job in no code even with minimal experience is real!
The most demanded direction in development now is the development of mobile applications.
If you are starting to learn or have already studied one of the no code tools, then you probably expect to find your first order or job soon. We can confidently say that getting a job in no code even with minimal experience is real! But you need to take a few steps so that your destiny finds you.
Start monitoring vacancies and orders from the first day of training
Our first advice to those who enter IT through No-code is to start monitoring vacancies from the first day of training. This must be done for two reasons.
- You will immediately understand the requirements of the market, popular orders, customer expectations, pricing policy. By the time you have the skills and start looking for a job, you will have a plus or minus idea of what exactly the market needs, what price tag you can count on, what to write in the response and in the resume.
- Gather ideas for digital projects and real applications that are in demand. You can even take something and repeat during your studies for training.
Appreciate everything you have
Find and view all study and practice projects you have. Finish everything that was not completed, and finalize the appearance - this is important. Appearance will be the first thing to consider.
Finish work on the appearance and fix the description of each project: what is it - a web, mobile application, service; type — online store, marketplace, community, LMS; number of roles and parties; main functions; software package.
Collect it in a list in free form - then it will be easy to make a portfolio out of it.
Practice as often as possible
As often as possible, open the program in which you study and intend to work. And not only to repeat educational projects after the teacher - do something of your own there as often as possible.
No ideas? Then here are ours.
- Drag and drop elements from the toolbar, customize them, try them out in different ways and in different scenarios.
- Take free templates, copy to your workspace. Come inside, study the device, see the settings of the elements, move, change and break.
- Check out Pinterest or Behance or Dribble for examples of mobile app projects, landing pages, web apps, and services. Analyze and save your favorites. Try to repeat them in whole or in part - for example, reproduce the header or banner you like, repeat the design decision, collect a similar user scenario.
- Make a mobile app for your favorite coffee shop or bakery. Or maybe you don't like the app you saw or used - redesign it to fit your vision. This project can be added to the portfolio.
Design a portfolio
There is such a paradox - the employer requires a portfolio, but often does not even look at it or looks casually. We draw two conclusions - a portfolio is a must and you need to make it as simple as possible.
Therefore, first of all, think about the accessibility of the portfolio.
Make it, for example, simply in Google Docs or in Notion. Let it be a list of projects with their name, links to previews or published projects and their description.
Ask questions
When communicating with a customer or employer, ask as many questions as possible. You need to ask about the development project right away, at the very first interview - so you will immediately understand whether you are suitable for this job and whether the conditions, price, requirements for the project suit you.
Ask everything you, as a developer, need to know about a future project.
- How does the customer see their application? Does he have developments, a design system, project drafts? How many roles are expected in the application? How much data is related to the project? Are push notifications necessary? Are you planning to upload to the stores? How soon do you need to show the prototype - and is it needed?
- Find out everything there is to know about the audience of the project. Ask about the customer's business goals. Do not forget about metrics, about plans for the development of the project.
- Do not forget about the indirect aspects of development. Ask who the design is for, who the UX texts are for, testing. Suddenly everything is on you by default.
By the way, customers often do not know what they want - your task is to extract this information from them. A lot depends on the answers. The price tag for work, the choice of platform and the software package to be used, additional services.
Fix the agreements in any way convenient for you and the customer - this can be a regular Google document. Feel free to form a technical task from this.
Take advantage of No code when looking for a job
The customer wants a prototype - assemble it quickly in one of the programs! You can really make a draft of an application in a few hours and impress the customer with the first version of the product. At the same time, you will better understand what he wants.
You can go even further - through a screen demonstration, show part of the process and clarify the details right along the way.
Be honest and confident
Remember that the employer or customer knows less about no code than you do, so you are a professional compared to him. You may even be a Certified Moxly Expert. Therefore, in a conversation, keep yourself confident - and ask questions about the project!
But try not to exaggerate - don't lie, stay honest. First, be open about what things can and can't be done in no code. Secondly, admit that you can't do certain types of work (if so) - for example, that you feel insecure working with a complex workflow or that you are creating a database for a long time. Perhaps, in this case, you will look for a developer on a subcontract, and this is a normal practice.
