The hardest thing for someone who has studied programming for a while is finding their first job. This is difficult for many reasons. And I will try to explain to beginners how the process of finding a job as a junior looks from the inside.
Summary
Imagine that you are an employer who has opened the recruitment of people in your company. Check out Head Hunter. There are dozens or even hundreds of ads from applicants. Everyone has at least one resume, the most enterprising ones have more. The same number of people responded to your vacancy. Reading:
Java, HTML, OOP, English, C/C++, literate and delivered speech, Android
Would you take such a person? I would never. I will not open America by saying that a resume is the most important part in a job search. Once again - the MOST important. This is 80% success. This is your train ticket. Maybe you will not reach where you wanted, but the trip will not leave you without new impressions. Already at the time of viewing the list of candidates, mind you - the list , and not the resume itself - the fate of the seekers is being decided. There is no photo, the salary that you would like to receive is not indicated - and you will not be noticed. Asking salary doesn't match experience? Programmer-all-can-and-can? But we are looking for a Java specialist and we know that a person with 5 years of experience cannot request 40 thousand in St. Petersburg. So, your resume is your currency. Its value is proportional to the time invested in it. The summary is complex, thoughtful, interesting - a great demand. In key skills, we write only what we do best. We are looking for a job as a Java programmer - we enter only Java and everything that directly relates to it. C ++ is good, but not in key skills, but in the "Additional Information" section, with the obligatory indication that they had some experience, are familiarwith this technology, there is a theoretical background in anything. No need to lie and enter what you do not know. Save yourself from embarrassment at the interview, take pity on the employer and save his time. If the list of knowledge is small, then it is worth preparing a little more. The atomic bomb effect of resume views can be achieved by linking to a personal git account. Even if there is a test task with a calculator for company N. HR does not understand the code, but she was told that the link to the repository is cool. Perhaps only work experience is cooler, but so far we don’t have it. Self-taught, in my opinion, is more difficult. Yes, it is often heard that the "tower" is optional. But that doesn't mean it's being ignored. In theory, and in practice, a person with a specialized education has at least theoretical knowledge, has taken a course in mathematics. And this is a definite plus in front of the self-taught, whose knowledge is chaotic and incomplete. From personal experience - they did not take an internship at Mail.ru, because they were required to conclude an agreement with the institute. That is, even without education, being only a student, roads may be opened to you where there is no access for self-taught people. Responses Despite the fact that you really want toget your first job, you don't have to respond to everything. Are you sure you want to work in the financial sector? And in genetics? Interested in the front or just the back? Ready to serve six months in testing? Are you sure they won't ask for more? Worse than being unemployed, only doing what you don't like. Read the requirements for the applicant carefully. Just as most employers ignore "do-it-yourself programmer", you should also be wary of companies that list a mixture of languages and various technologies. Read reviews about the company on the Internet, find a website if there is one. How long has the company opened? State or western branch? If you know English, then look for a company that fulfills orders for foreign clients. This may come in handy in the future for a potential move abroad. Interview The most controversial part of the search. It's different for different companies. Some prefer skype, some prefer in person. The first meeting can only be with HR. It happens that despite a good work experience, only due to personal rejection of you by a girl, simply "because", you will not even reach the technical specialists. The questions are also different. At my first interview there were the simplest questions on Java SE. Object class methods, collections, basic understanding of OOP. On others - from "How would you know, in the event of large delays in the application, what exactly is not optimized?" to "What is Java EE, Spring, container in it?" or requests to write your own StringBuilder.reverse() algorithm. A lot has been written about this and this is not the most important thing. And the main thing is that you can learn for yourself about the company. Some interlocutors address you as "You", are patient with your mistakes, try to help get out of the difficulty with hints, realizing that you are worried. Others - openly laugh at the top of their voices in your face. Still others ask to make outright nonsense, like "Write bubble sort from memory on a piece of paper," which puzzles me, because I can't imagine where and why to use this algorithm. In doing so, they refuse your offer to write a mergesort instead. The interview at the company where I now work was quite simple, short and very pleasant. In about 20 minutes, I was asked about my programming experience, the projects I participated in, who I am in general. General questions in breadth. At the end they said: "Here's a test task for you. Upload it to the git and describe yourself by mail within such and such a period. You will be answered then." Later I found out that several other students/graduates were trying to get jobs with me. Someone behaved ugly during the interview, and someone asked for a salary more than me (40,000 rubles), while completing the task incompletely or worse. As a result, I ended up in an incredibly cozy team with a class teacher and a comfortable work rhythm. After/before the technical part, you will have the opportunity to ask questions about the company. Be sure to ask the following: Someone behaved ugly during the interview, and someone asked for a salary more than me (40,000 rubles), while completing the task incompletely or worse. As a result, I ended up in an incredibly cozy team with a class teacher and a comfortable work rhythm. After/before the technical part, you will have the opportunity to ask questions about the company. Be sure to ask the following: Someone behaved ugly during the interview, and someone asked for a salary more than me (40,000 rubles), while completing the task incompletely or worse. As a result, I ended up in an incredibly cozy team with a class teacher and a comfortable work rhythm. After/before the technical part, you will have the opportunity to ask questions about the company. Be sure to ask the following:
What project will you be assigned to?
Java version and project technologies
Will you be a developer or tester (first time)
Your duties/nature of work (fullstack, back)
Salary (if not mentioned in the vacancy), benefits, freebies (from coffee to books and courses)
When an answer will be given whether you are accepted or not (obtain an exact date)
Misc: Schedule, rallies, lunch, vacation and sick leave and their pay etc.
Summarize. It may not be completely transparent, but I wanted to show you that there are no universal situations for how interviews work. Once again, I strongly advise you not to chase after all the vacancies in a row, to act impatiently because of the languishing "if only they took it." Your resume and github profile contributions can land you in the company of your dreams with the right work environment, team, flexible hours, and an atmosphere where you grow like dough professionally. By sending out hundreds of resumes, you risk only getting into some company. Finally , an extensive and more detailed article on the topic from mail.ru. This article is a logical continuation of my first topic at the request of those who read it.
Asking salary doesn't match experience? Programmer-all-can-and-can? But we are looking for a Java specialist and we know that a person with 5 years of experience cannot request 40 thousand in St. Petersburg. So, your resume is your currency. Its value is proportional to the time invested in it. The summary is complex, thoughtful, interesting - a great demand. In key skills, we write only what we do best. We are looking for a job as a Java programmer - we enter only Java and everything that directly relates to it. C ++ is good, but not in key skills, but in the "Additional Information" section, with the obligatory indication that they had some experience, are familiarwith this technology, there is a theoretical background in anything. No need to lie and enter what you do not know. Save yourself from embarrassment at the interview, take pity on the employer and save his time. If the list of knowledge is small, then it is worth preparing a little more. The atomic bomb effect of resume views can be achieved by linking to a personal git account. Even if there is a test task with a calculator for company N. HR does not understand the code, but she was told that the link to the repository is cool. Perhaps only work experience is cooler, but so far we don’t have it. Self-taught, in my opinion, is more difficult. Yes, it is often heard that the "tower" is optional. But that doesn't mean it's being ignored. In theory, and in practice, a person with a specialized education has at least theoretical knowledge, has taken a course in mathematics. And this is a definite plus in front of the self-taught, whose knowledge is chaotic and incomplete. From personal experience - they did not take an internship at Mail.ru, because they were required to conclude an agreement with the institute. That is, even without education, being only a student, roads may be opened to you where there is no access for self-taught people. Responses Despite the fact that you really want toget your first job, you don't have to respond to everything. Are you sure you want to work in the financial sector? And in genetics? Interested in the front or just the back? Ready to serve six months in testing? Are you sure they won't ask for more? Worse than being unemployed, only doing what you don't like. Read the requirements for the applicant carefully. Just as most employers ignore "do-it-yourself programmer", you should also be wary of companies that list a mixture of languages and various technologies. Read reviews about the company on the Internet, find a website if there is one. How long has the company opened? State or western branch? If you know English, then look for a company that fulfills orders for foreign clients. This may come in handy in the future for a potential move abroad. Interview The most controversial part of the search. It's different for different companies. Some prefer skype, some prefer in person. The first meeting can only be with HR. It happens that despite a good work experience, only due to personal rejection of you by a girl, simply "because", you will not even reach the technical specialists. The questions are also different. At my first interview there were the simplest questions on Java SE. Object class methods, collections, basic understanding of OOP. On others - from "How would you know, in the event of large delays in the application, what exactly is not optimized?" to "What is Java EE, Spring, container in it?" or requests to write your own StringBuilder.reverse() algorithm. A lot has been written about this and this is not the most important thing. And the main thing is that you can learn for yourself about the company. Some interlocutors address you as "You", are patient with your mistakes, try to help get out of the difficulty with hints, realizing that you are worried. Others - openly laugh at the top of their voices in your face. Still others ask to make outright nonsense, like "Write bubble sort from memory on a piece of paper," which puzzles me, because I can't imagine where and why to use this algorithm. In doing so, they refuse your offer to write a mergesort instead. The interview at the company where I now work was quite simple, short and very pleasant. In about 20 minutes, I was asked about my programming experience, the projects I participated in, who I am in general. General questions in breadth. At the end they said: "Here's a test task for you. Upload it to the git and describe yourself by mail within such and such a period. You will be answered then." Later I found out that several other students/graduates were trying to get jobs with me. Someone behaved ugly during the interview, and someone asked for a salary more than me (40,000 rubles), while completing the task incompletely or worse. As a result, I ended up in an incredibly cozy team with a class teacher and a comfortable work rhythm. After/before the technical part, you will have the opportunity to ask questions about the company. Be sure to ask the following: Someone behaved ugly during the interview, and someone asked for a salary more than me (40,000 rubles), while completing the task incompletely or worse. As a result, I ended up in an incredibly cozy team with a class teacher and a comfortable work rhythm. After/before the technical part, you will have the opportunity to ask questions about the company. Be sure to ask the following: Someone behaved ugly during the interview, and someone asked for a salary more than me (40,000 rubles), while completing the task incompletely or worse. As a result, I ended up in an incredibly cozy team with a class teacher and a comfortable work rhythm. After/before the technical part, you will have the opportunity to ask questions about the company. Be sure to ask the following:
GO TO FULL VERSION