<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: zata89</title>
    <description>The latest articles on DEV Community by zata89 (@zata89).</description>
    <link>https://dev.to/zata89</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F51757%2F0549649e-4a6b-45f0-a8da-6a600b652de2.png</url>
      <title>DEV Community: zata89</title>
      <link>https://dev.to/zata89</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zata89"/>
    <language>en</language>
    <item>
      <title>What I've learned about technical interviews and job search</title>
      <dc:creator>zata89</dc:creator>
      <pubDate>Fri, 29 Dec 2017 07:51:47 +0000</pubDate>
      <link>https://dev.to/zata89/what-ive-learned-about-technical-interviews-and-job-search-4oof</link>
      <guid>https://dev.to/zata89/what-ive-learned-about-technical-interviews-and-job-search-4oof</guid>
      <description>&lt;p&gt;I've been working since 6 years ago and one of the things that I've suffered is being rejected from good job offers because my technical level. Now this is frustrating because you know that you can handle with the resposibilities of the job, but when you are on the technical interview is difficult to demonstrate. So here are some tricks that I've learned.&lt;/p&gt;

&lt;h2&gt;
  
  
  Don't be afraid
&lt;/h2&gt;

&lt;p&gt;Everybody is always scared. And when you need to answer something that you don't know, or you feel no confidence of your skills, this is demonstrated in the way we talk. But don't be afraid to tell "I don't know" or talk about something you know. If you commit a mistake is not a proof of you lack of knowledge. Nobody can master 100% a technology.&lt;/p&gt;

&lt;h2&gt;
  
  
  Write everything you don't know
&lt;/h2&gt;

&lt;p&gt;After a time, I started to do this trick. Why? Because sometimes this knowledge was frecuently asked by other interviewers. So I started to annotate any concept that I didn't know to research it later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Plan your interview
&lt;/h2&gt;

&lt;p&gt;When you're working, taking interviews is very difficult. Commonly I requested the interviews after my work time, but many times the interviewers can only during the work hours. So in those cases is necessary plan your schedule for the interview. Maybe during the lunch time or in the afternoon when you don't have too much meetings. Also find a place in your work where you can take the call with no problems.&lt;/p&gt;

&lt;h2&gt;
  
  
  Always request the requirements of the job
&lt;/h2&gt;

&lt;p&gt;Many times I've received job offers that sound great, but when I was on the interview, I didn't know many of the questions and that was because I didn't know the technology. So always ask about the job requirements.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check your resume
&lt;/h2&gt;

&lt;p&gt;Your resume must be always the honest vision of your professional background. If you add that you know a technology, you must know that technology, or don't add that to you resume. What you add to your resume, are the weapons that you give to the interviewer for test your knowledge.&lt;/p&gt;

&lt;h2&gt;
  
  
  And finally, see the current job offers
&lt;/h2&gt;

&lt;p&gt;In this times, you must be updated about the technologies that we must use. And with many technologies, we need to be sure that what we're learning is valuable in a company. The job offers gives you an idea of what you should be learning.&lt;/p&gt;

&lt;p&gt;Finally, sorry for my english. I'm non-english-native speaker so if you have any comment, please help me to improve my language skills.&lt;/p&gt;

</description>
      <category>interview</category>
      <category>tips</category>
      <category>career</category>
    </item>
  </channel>
</rss>
