<\/a><\/noindex><\/p>\nWhy?<\/h3>\n \nI chose the profession of a programmer not by chance and not just because I've heard that it pays well. It all started in the third grade when a friend got a gaming console with a keyboard. It was a gaming console, but with a special cartridge, it turned into a development environment for simple platform games. Later, my parents bought a similar one for me at home and I 'disappeared' into it. <\/p>\n
In school, technical college, and university \u2014 I always chose paths that were as close to computers and information technology as possible. I was confident that I would become a programmer, or as they called it back then, a system administrator \u2014 a 'computer guy'.<\/p>\n
But life makes its own adjustments \u2014 a pressing issue: without experience, you can't get a job, and without a job, you can't gain experience. The main mistake at this stage is ambition. I was sure that I was a great professional and deserved to be paid well, certainly not less than the city average. I turned down many offers myself because of low salaries.<\/p>\n
After six months of searching for a job related to computers, I was unsuccessful. When the money ran out, I had to take a job somewhere that offered a more or less decent salary. That's how I ended up working at a cable manufacturing plant as a regular worker, where I built my career for the next 12 years.<\/p>\n
At 33, I became the head of the department, a quality specialist for cable products with extensive experience and a good salary. But this was not enough; there was no satisfaction, no sense of self-affirmation, no joy from work.<\/p>\n
At that time, the family was financially stable; we could live off my wife\u2019s salary and some savings for a couple of months. This led me to consider leaving everything behind and pursuing my dream. However, dreaming in the kitchen and taking real action are different things.
The second significant event was the personnel changes at the plant where I worked. There was a change in upper management, and all department heads faced strict scrutiny to meet new requirements and standards. The good times were over. I realized I would need to work hard to stay afloat and move forward: learning English, enhancing my qualifications, working more\u2014doing more than was expected of me.<\/p>\n
At that moment, I had the thought: 'It\u2019s time to work hard and study again, so why should I spend my energy and time on something that doesn't bring joy, when I could dedicate them to my dream?'<\/p>\n
How?<\/h3>\n \nThe first thing I did was 'burn my bridges' \u2014 I quit my job. It was radical, but I understood that I couldn't grow in two directions simultaneously. The experience of my initial job search was not in vain, and I started looking for any position just to get 'programmer' in my employment record. This job was about status, about that very 'experience' to help me find better opportunities. Salary didn't matter here. <\/p>\n
I've heard somewhere that when you pursue a goal, the goal starts to come to you. I was lucky as well. I quickly got a position at a small company working for a sole proprietor in microservices. I had no questions about the working conditions or finances; the main thing was the entry in my employment record and the beginning of practical experience accumulation. I realized I was performing the simplest tasks and couldn't proudly say 'I am a Programmer.' There was no confidence in my abilities \u2014 it was just the beginning of my journey. <\/p>\n
That\u2019s why I began to learn. To learn, to learn, and to learn even more... That's the only way.<\/p>\n
I started researching the demand for programmers in my city. I looked at job ads in newspapers and on job search websites, studied tips on the Internet about 'How to ace a programming interview' and gathered information from various sources. <\/p>\n
You need to meet employers' requirements. Even if you don't like those requirements.<\/p>\n
English language<\/h4>\n
When it comes to learning the language, I recommend trying every method you can find. I learned English through various methods and noticed that there is no universal approach. Different people benefit from different techniques. Read books in English (children's books are better, as they are easier to understand), watch movies (both with subtitles and without), attend courses, buy textbooks, check out many seminar videos online, and use various smartphone apps. Once you've tried everything, you'll understand what works best for you. <\/p>\n
Personally, I found that children's stories and the original series 'Sesame Street' helped me a lot (only basic expressions, repeated phrases and words), and it\u2019s also good to study the language through textbooks. Not self-taught, but rather school textbooks. I used a notebook to complete all the exercises. But the most important thing is to force yourself to seek out information in English. For instance, the latest programming books and current editions are always in English. By the time a translation comes out, a new edition is already released.<\/p>\n
Currently, my level is basic, a 'survival' level according to one evaluative system. I can freely read technical literature and express myself in simple phrases, but even this is already a significant advantage in the job market, when you check the box 'English' in the languages section of your resume. My experience shows that an inexperienced specialist with English finds a job more easily than an experienced programmer without English.<\/p>\n
Toolset<\/h4>\n
Job postings don\u2019t always specify the required knowledge of tools, implying that if you\u2019re a programmer, you definitely know git. These requirements are gathered from advice on how to pass a job interview in the field. There\u2019s a lot of such information on the internet, and these articles are often found on job search websites.<\/p>\n
I made a list of tools on a sheet of paper, installed them all on my computer, and only used them. You can\u2019t do without studying and literature here. Changing specialties requires a significant amount of time for self-education.<\/p>\n
Portfolio<\/h4>\n
It was helpful to look at other people's portfolios and mimic their work. Instead of resorting to plain copying, creating my product, even if it replicates someone else's idea, allowed me to gain experience, add a new piece to my portfolio, and avoid wasting time on creative searching.<\/p>\n
It's a great stroke of luck to find a test assignment in job postings. If you continually monitor the job market, sometimes you'll come across tasks from employers \u2014 that's exactly what you need! Usually, these tasks contain the essence, even if they don't provide meaningful benefits as a product. Even if you're not planning to submit your resume to that company, you should definitely complete their task and send it in. Almost always, you'll receive feedback on your work, which will reveal your weaknesses that need improvement.<\/p>\n
Certificates and courses<\/h4>\n
I've decided to pursue certifications only after I feel that I 'can.' I've read a bit about Microsoft certificates, 1C, and various government institutions. The principle is the same everywhere: you need money and knowledge. Either the certificate itself costs money, or you must take special courses before taking the exam, or the entry to sit for the exam costs money. And this still doesn't guarantee that you'll receive the certificate.
However, I haven't spared time, effort, or finances for advanced training courses. Now there are well-developed distance learning systems \u2014 webinars. Most major institutions in the country conduct courses and seminars. There are often good discounts or completely free seminars. I consider the main advantage of such classes to be the opportunity for direct communication with experienced and knowledgeable people. You can always ask questions and ask for feedback on your portfolio work. And as a cherry on top, you receive a completion document for the courses. It\u2019s not a certificate, of course, but it shows the employer your commitment to your goals.<\/p>\n
The most important document \u2014 the resume<\/h4>\n
In the end, I included everything I had in my resume. All work experience, all documents from all courses, including training in occupational safety at the manufacturing enterprise. I listed all my computer skills. I even mentioned my hobbies and interests. And I didn\u2019t regret it!
When?<\/h3>\n How do you know when I'm ready? When should I take action?<\/p>\n
A little over a year after leaving my previous job, there was a stagnation. My work experience accumulated, my skills with the tools improved, my programming experience at work and in my portfolio grew, and I gradually picked up some English. Everything was going according to plan, but inside me, impatience ignited to take the next step and start searching for a serious job. Along with this impatience came doubts: I\u2019m not ready, I won\u2019t succeed, I wasted my time leaving my old job\u2026 and so on.<\/p>\n
To avoid worsening the situation with my bleak mindset, I started to take small actions: I posted my resume on a website and just waited. On one hand, I lacked the confidence that anyone would even listen to me at interviews and that I wouldn't be kicked out in disgrace, but on the other hand, I already had some experience and something to show.<\/p>\n
I saw from the statistics on the site that my resume was being viewed frequently. Sometimes certain companies visited my resume page several times. I felt that the first visit was probably by a recruiter, and the second time it was shown to a manager. I don\u2019t know how it really was, but I got the impression that I had intrigued people, that they were discussing and reviewing my resume. And that already felt like half the battle won!<\/p>\n
I sent my first job application to a well-known large bank. The quality control department was looking for a developer to automate their document flow process. I applied without particularly expecting success, banking on my experience in the quality department. I felt immense surprise and joy when I was invited for an interview!<\/p>\n
I wasn\u2019t hired by the bank, but I got a front-row view of a real programmer interview. I completed test tasks and spoke with managers at various levels. Most importantly, what I understood from the interview results was an assessment of my level as a programmer. I began to realize where I stood, what kind of programmer I was, and what I still didn't know. This is crucial information! Besides the list of missing knowledge, it gave me confidence that I was making progress. Slowly, but I am.<\/p>\n
When I returned home from the interview, I immediately updated the title of my resume to 'intern programmer.' My level didn't qualify as a programmer, so employers didn't fully understand my resume. However, 'intern' was a realistic assessment of my knowledge in this new field.<\/p>\n
The most important step<\/h3>\n
One job vacancy interested me the most. The organization posted a test assignment on the job search website. The task wasn't very difficult, but the way it was structured, the deadlines mentioned, and the technologies I was supposed to use all indicated a serious approach to the matter.<\/p>\n
I completed the assignment, trying to do it ahead of schedule. And I sent it.<\/p>\n
I received a rejection with a detailed analysis of my code. What I did well, and what could have been improved and why. This thorough response intrigued me a lot, and I realized that I wanted to work there. I was ready to visit their office and ask what I needed to learn, finish, or master to get hired. But first, I corrected my code according to the feedback I received and submitted it again. This time, I got a call inviting me for an interview.<\/p>\n
The hardest part of the interview at 35 years old was explaining why I left a good job with a decent salary and started everything from the bottom in a new profession. I wasn't worried about my resume; I could talk through each point, proving that I really knew and could do everything mentioned at the level indicated. But how did I end up here and why?
It's disappointing. I'm used to this phrase meaning a rejection. But there was hope, as everything was done according to the rules in this organization, and they always kept their word. Nevertheless, I continued to search for a job.<\/p>\n
They called me exactly at the specified time and said that they had an offer for me. An internship is an excellent option for a candidate in my position. For three months, I receive a salary and get trained on a real project. It's hard to think of better training, and I agreed without hesitation.<\/p>\n
This is just the beginning<\/h3>\n \n On the very first day of the internship, my direct supervisor explained a crucial idea during the orientation briefing, which I share with everyone when the conversation turns to career changes or those just starting their careers. I didn\u2019t take down the exact words, but the essence stuck with me well: <\/p>\n
Every programmer develops in three areas: Programming, Communication skills, and Personal life experience. It's not hard to find someone who can write good code. Communication skills are a character trait that can be viewed as a constant. However, life experience is in short supply, as most candidates are recent graduates.<\/p>\n
It turns out that I was hired with the idea that I have experience working with real clients on real projects, possess a wealth of diverse knowledge, and I am already prepared to function in a business environment. Therefore, it makes sense to spend time training me as a programmer just as it would to train a good programmer in business interaction.<\/p>\n
For those contemplating a career change, I would emphasize that switching fields to pursue your dream is not only feasible but also in demand in the job market.<\/p>\n
For me, everything is just beginning! <\/p>\n
Now I am a full-time developer at Inobitek, participating in the development of medical information systems. However, I am not yet ready to proudly call myself a Programmer. There is still much to learn in order to independently create software.<\/p>\n
People are right when they say that you should enjoy your work. For that, it's worth \"digging, sweating, and enduring!\"habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"\u0412\u0441\u0451 \u0447\u0430\u0449\u0435 \u0438 \u0447\u0430\u0449\u0435 \u0432\u0441\u0442\u0440\u0435\u0447\u0430\u044e\u0442\u0441\u044f \u043f\u0440\u0438\u043c\u0435\u0440\u044b \u0441\u043c\u0435\u043d\u044b \u043f\u0440\u043e\u0444\u0435\u0441\u0441\u0438\u0438, \u0438\u043b\u0438 \u0441\u043a\u043e\u0440\u0435\u0435 \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438, \u043b\u044e\u0434\u044c\u043c\u0438 \u0432 \u0441\u0440\u0435\u0434\u043d\u0435\u043c \u0432\u043e\u0437\u0440\u0430\u0441\u0442\u0435. \u0412 \u0448\u043a\u043e\u043b\u0435 \u043c\u044b \u043c\u0435\u0447\u0442\u0430\u0435\u043c \u043e \u043f\u0440\u043e\u0444\u0435\u0441\u0441\u0438\u0438 \u0440\u043e\u043c\u0430\u043d\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0438\u043b\u0438 \u201c\u0432\u0435\u043b\u0438\u043a\u043e\u0439\u201d, \u0432 \u0438\u043d\u0441\u0442\u0438\u0442\u0443\u0442 \u043f\u043e\u0441\u0442\u0443\u043f\u0430\u0435\u043c \u043f\u043e \u043c\u043e\u0434\u0435 \u0438\u043b\u0438 \u0441\u043e\u0432\u0435\u0442\u0430\u043c, \u0430 \u0432 \u0438\u0442\u043e\u0433\u0435 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u043c \u0442\u0430\u043c, \u043a\u0443\u0434\u0430 \u0432\u0437\u044f\u043b\u0438. \u042f \u043d\u0435 \u0443\u0442\u0432\u0435\u0440\u0436\u0434\u0430\u044e, \u0447\u0442\u043e \u0442\u0430\u043a \u0443 \u0432\u0441\u0435\u0445, \u043d\u043e \u0443 \u0431\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u0430 \u2014 \u0442\u043e\u0447\u043d\u043e. \u0418 \u043a\u043e\u0433\u0434\u0430 \u0436\u0438\u0437\u043d\u044c \u043d\u0430\u043b\u0430\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28598,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-38094","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t
![\"How](\"\/wp-content\/uploads\/2019\/09\/7349b9aa208fd2ca296662a70430ec35.jpeg\")
More and more examples of career changes, or rather specialization changes, among middle-aged people are becoming common. In school, we dream of a romantic or 'great' profession, we enroll in college based on trends or advice, and in the end, we work in whatever positions we are offered. I am not saying this is the case for everyone, but it certainly is for the majority. And when life settles down and everything is stable, doubts arise about the chosen profession. I am talking not about the job title, but specifically about the specialization \u2014 when a person can call themselves a specialist or a professional.<\/p>\n