Learning on JavaRush. Job search and interviewing. Part 2.

Good afternoon In this part, I will tell you about writing a resume, portfolio, finding a job, passing interviews, as well as doing test tasks. Part one CV and portfolio writing. As you all know, to get a job you need to write a resume. There are many different articles and tips on how to do this, but I will only tell my opinion. It is desirable to write a resume in English and preferably in the form of a CV (in some vacancies, only this is required). Here is the link to the site, where this can be done online, but it is not necessary to adhere to such a form as there). If you do it on this site, then remove the logos from the resume (they go like headers and footers in the Word). On the first page, you need to indicate all the most important information so that hr would be interested in you. I wrote there the knowledge of languages, the passage of the CodeGym course and briefly what I studied, the internship and what technologies were there. Further, since I went to Android Developer, I wrote all the technologies and libraries that I knew on this platform. Then you can write about design patterns, version control systems, build systems (maven, gradle), as well as what development environments you worked in. After that, write about previous work experience, if any (if it has nothing to do with programming, then just briefly describe what you achieved there, what improvement did you make). Then comes education and at the very end I wrote about my projects. Since you will write the prevailing majority of technologies on the first page, you do not need to repeat yourself 100% and write that all of them are present in your projects - write only the most important. Job search. I started sending resumes somewhere in the middle of spring 2017. Surprisingly, there are very few vacancies at Android Developer, even in Kiev, if you look at the most popular job search sites, there are up to 30 of them, more than half of which want the middle/senior level. But still, they are constantly updated and for the entire period of the search, I think I sent up to a hundred resumes. Initially, in my portfolio there was only a telegram bot, which I talked about in the first articleand the resume itself was still not quite attractive. I didn't receive any call for an interview. After a couple of weeks of sending a resume, I realized that I needed to redo it a little, and I also needed to have at least one android project in my portfolio. At that time I started making my first android app. I continued sending resumes about a month and a half later (all the vacancies had already been updated), when the first version of the application was ready. As for vacancies, they can be very different, but I was always immediately repelled by those in which the employer was too lazy to even check for errors and formatting in the text of the job description. This immediately characterizes the company, and you don’t really want to work there. After I reworked my resume a bit and expanded my portfolio, I began to receive the first invitations to interviews. From the very beginning, two companies were invited to the middle position for one day. This, of course, was a bit of a shock, but still it was nice that they liked my resume. Passing interviews.The preparation for the first interview was very vague. After the CodeGym course and the beginning of studying android, I didn’t study theory at all, but here I had to repeat everything that you know and don’t know about Java and Android in a couple of days. These are moments when you don’t understand where to start and what to learn at all. I sat from morning to evening reading various articles, even opening CodeGym lectures on multithreading. At the first interview, I was not asked for a long time. They immediately realized that I didn’t pull on middle (I got confused even in activity life cycles) and they said that I didn’t fit. But in general, I had very pleasant impressions and the fact that I did not fit was initially clear to me, I just wanted to get the experience of passing interviews. The second interview was very cool. Their team leader asked me for a whole hour on theory and everything that I did not know he explained to me. I was very pleased, even though they did not take me there. The third interview was not technical at all, there the managers told me about the project, they said that the candidate should conduct it himself and it would be nice if he also wrote api in php. After the interview, I already didn’t want to go there, and when they didn’t take me, I was only delighted. The fourth interview was an hour long, 80% of which were asked on the technical part. After the interview, they said that they would drop the test task, but then they wrote that I didn’t fit and they were not ready to drop the test. If we talk about what you need to know ironically for the position of Android Developer (I think for the position of Java Developer as well), then this is OPP. There it will immediately be clear whether you just memorized the name of the basic principles or you know their very essence and can normally use them in practice. You also need to know the life cycles of activities, fragments. The Observable pattern is often asked, as it is quite often used and even underlies the RxJava library. In general, you can’t guess what they will ask about - they can do more bias on java, or maybe on android. For example, I tried very hard to make my portfolio good, and I was only asked about my one project at the last interview. I did not have any algorithmic problems at the interviews. Sometimes they could ask to write on a piece of paper how to implement the singleton pattern, or on the board to write any array sorting. And you need to know this very clearly, because there you are in stressful situations and with a time limit. IN since it is quite often used and even underlies the RxJava library. In general, you can’t guess what they will ask about - they can do more bias on java, or maybe on android. For example, I tried very hard to make my portfolio good, and I was only asked about my one project at the last interview. I did not have any algorithmic problems at the interviews. Sometimes they could ask to write on a piece of paper how to implement the singleton pattern, or on the board to write any array sorting. And you need to know this very clearly, because there you are in stressful situations and with a time limit. IN since it is quite often used and even underlies the RxJava library. In general, you can’t guess what they will ask about - they can do more bias on java, or maybe on android. For example, I tried very hard to make my portfolio good, and I was only asked about my one project at the last interview. I did not have any algorithmic problems at the interviews. Sometimes they could ask to write on a piece of paper how to implement the singleton pattern, or on the board to write any array sorting. And you need to know this very clearly, because there you are in stressful situations and with a time limit. IN and I was asked about my one project only at the last interview. I did not have any algorithmic problems at the interviews. Sometimes they could ask to write on a piece of paper how to implement the singleton pattern, or on the board to write any array sorting. And you need to know this very clearly, because there you are in stressful situations and with a time limit. IN and I was asked about my one project only at the last interview. I did not have any algorithmic problems at the interviews. Sometimes they could ask to write on a piece of paper how to implement the singleton pattern, or on the board to write any array sorting. And you need to know this very clearly, because there you are in stressful situations and with a time limit. INprevious articleI wrote that my friend works as an android developer. Recently, he was offered a job in another company, and since he was leaving, they were looking for a new candidate in his place. He recommended an interview with me. Initially, I was sent to do a test task and was given time for 1 week, taking into account the fact that the sooner you do it, the better. I did the task in 4 days (a friend, as an honest person, did not help me in this matter). After that, I was invited for an interview. At all the interviews that I had, they either immediately ask technical questions, or first talk with hr, and then the technical part. Everything was mixed up here, which was a little confusing. Immediately and for the first time I was asked to write sorting on the board - I began to remember some article on Habré about well-optimized sorting, but since time is limited, I wrote the first one, what came to mind. The interview was more practical, and lasted an hour. After that, they told me that they would give an answer within two weeks, as they still want to look at other candidates. And recently I received a letter that I was invited for a trial period to the position of Android Developer - the joy could not be taken away :) If you are studying android, all the tasks on startandroid and other resources have already passed, then what can I advise you to practice. There is a good all tasks on startandroid and other resources have already passed, what I can advise you to practice. There is a good all tasks on startandroid and other resources have already passed, what I can advise you to practice. There is a goodwebsite. There you generate a list of json objects. Create an android application in which you will load this list (in a separate thread or in a service or using third-party libs) and then display it to the user. Database use either SqlLite or third party Realm. Let there be brief information in the list, and when you click on the list email, a fragment with full information opens. To complicate the task, make adaptation to tablets - split into two screens when rotated to a horizontal position, and one screen in a vertical position (use fragments for this). You can also add a navigation drawer and there are some settings items (change the application language, background, font, etc.). Something similar was in my test task. In general, what I want to say to everyone who has yet to find a job is to write a good resume, since this is the very first, what characterizes you. Choose internships and vacancies only in good companies (at least in those who are not too lazy to properly write a job description). Learn the theory - although sometimes it seems that this is only for interviews, but in practice Google is always at hand, but from my own experience I will say that with the knowledge of all the basic theory, programming becomes easier. After each interview, study all the questions that you did not know the answer to and that you were not very sure about - so after 4-5 interviews you will know the answers to all the most common questions. I also wanted to say that they would not worry, but this is all natural and cannot be taken away - we are not machines :) Link to all the questions that I had at the interviews (you look for answers in Google) - Choose internships and vacancies only in good companies (at least in those who are not too lazy to properly write a job description). Learn the theory - although sometimes it seems that this is only for interviews, but in practice Google is always at hand, but from my own experience I will say that with the knowledge of all the basic theory, programming becomes easier. After each interview, study all the questions that you did not know the answer to and that you were not very sure about - so after 4-5 interviews you will know the answers to all the most common questions. I also wanted to say that they would not worry, but this is all natural and cannot be taken away - we are not machines :) Link to all the questions that I had at the interviews (you look for answers in Google) - Choose internships and vacancies only in good companies (at least in those who are not too lazy to properly write a job description). Learn the theory - although sometimes it seems that this is only for interviews, but in practice Google is always at hand, but from my own experience I will say that with the knowledge of all the basic theory, programming becomes easier. After each interview, study all the questions that you did not know the answer to and that you were not very sure about - so after 4-5 interviews you will know the answers to all the most common questions. I also wanted to say that they would not worry, but this is all natural and cannot be taken away - we are not machines :) Link to all the questions that I had at the interviews (you look for answers in Google) - that this is only for interviews, and in practice Google is always at hand, but from my own experience I will say that with knowledge of all the basic theory, programming becomes easier. After each interview, study all the questions that you did not know the answer to and that you were not very sure about - so after 4-5 interviews you will know the answers to all the most common questions. I also wanted to say that they would not worry, but this is all natural and cannot be taken away - we are not machines :) Link to all the questions that I had at the interviews (you look for answers in Google) - that this is only for interviews, and in practice Google is always at hand, but from my own experience I will say that with knowledge of all the basic theory, programming becomes easier. After each interview, study all the questions that you did not know the answer to and that you were not very sure about - so after 4-5 interviews you will know the answers to all the most common questions. I also wanted to say that they would not worry, but this is all natural and cannot be taken away - we are not machines :) Link to all the questions that I had at the interviews (you look for answers in Google) - to which they did not know the answer and in which they were not very sure - so after 4-5 interviews you will know the answers to all the most common questions. I also wanted to say that they would not worry, but this is all natural and cannot be taken away - we are not machines :) Link to all the questions that I had at the interviews (you look for answers in Google) - to which they did not know the answer and in which they were not very sure - so after 4-5 interviews you will know the answers to all the most common questions. I also wanted to say that they would not worry, but this is all natural and cannot be taken away - we are not machines :) Link to all the questions that I had at the interviews (you look for answers in Google) -questions at interviews Thank you all for your attention and good luck with your employment!