{"id":23,"date":"2022-04-28T21:08:52","date_gmt":"2022-04-28T21:08:52","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/delperspective\/?p=23"},"modified":"2022-04-28T21:08:52","modified_gmt":"2022-04-28T21:08:52","slug":"meta-interviews","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/delperspective\/2022\/04\/28\/meta-interviews\/","title":{"rendered":"Meta Interviews"},"content":{"rendered":"\n<p>This week has been extremely busy. On top of a busy week at work and keeping up with my school work, I had my &#8220;on-site&#8221; interviews at Meta on Tuesday and Wednesday. They were a grind! It was such a relief to be finished with them. Now, the stress of waiting ensues though. <\/p>\n\n\n\n<p>These were actually my very first technical interviews. I began the interview process back at the end of February. After a recruiter reached out to me, I was asked to set up a screening phone interview for a Front End Engineer position. It was a simple 30 minute phone call mostly about core Javascript concepts. Think closures, DOM, Javascript API methods, prototype and inheritance, this, etc. I was immediately informed at the end of the call that I would be moving onto the next steps. <\/p>\n\n\n\n<p>The technical screen&#8230;. This was the first technical interview I have ever done. The anticipation and nervousness leading up to it was extreme. It&#8217;s hard to know what to expect, and I was scared of not knowing. I hold myself to very high standards, and it was intimidating to be judged so openly while coding. However, it wasn&#8217;t nearly as bad as I thought it would be. And by that, I don&#8217;t mean the interview was a breeze and I knew the most optimal solution right away. I mean that walking through my code and problem solving in front of a stranger is not nearly as scary as I thought it&#8217;d be. My interview was actually fairly collaborative, and when I got stumped, the interviewer would help point me back on track. I came out of the technical screen not feeling super confident in my answer, but I did feel confident that I articulated my thoughts and how I problem solved well. I learned a few hours later that I was moved onto the &#8220;on-site&#8221; interviews.<\/p>\n\n\n\n<p>The &#8220;on-site&#8221; interviews&#8230; These interviews are comprised of three separate interviews. Two technicals and a behavioral, both at 45 minutes. The behavioral was a lot of scenario-based questions (i.e Tell me about a time when&#8230;). Although I didn&#8217;t spend as much time preparing for the behavioral as the technical, I still spent a significant amount of time preparing. The behavioral is just as important as the technical! I felt most confident after this interview. The two technicals were definitely more challenging than the screening. I struggled through the problems, finished some and not others, but ultimately, I feel they definitely could have gone worse. I think it&#8217;s important to remember that the interviewers are  there to help you and that they want you to succeed. They don&#8217;t expect perfection, and they understand you&#8217;re nervous. I kept reminding this to myself when my nerves tried to get the better of me. (And worse case, you probably won&#8217;t ever see this person again so who cares if you didn&#8217;t correctly code the fastest way to sort a list).<\/p>\n\n\n\n<p>I&#8217;m not sure if I&#8217;ll get an offer or not, but I am very thankful to have completed this experience. Interview is all about practice and building confidence. This was definitely a learning experience, and I feel more confident already. When it comes time to interview again, I&#8217;ll definitely lean on this experience as a foundation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This week has been extremely busy. On top of a busy week at work and keeping up with my school work, I had my &#8220;on-site&#8221; interviews at Meta on Tuesday and Wednesday. They were a grind! It was such a relief to be finished with them. Now, the stress of waiting ensues though. These were [&hellip;]<\/p>\n","protected":false},"author":12183,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-23","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/posts\/23","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/users\/12183"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/comments?post=23"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/posts\/23\/revisions"}],"predecessor-version":[{"id":24,"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/posts\/23\/revisions\/24"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/media?parent=23"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/categories?post=23"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/delperspective\/wp-json\/wp\/v2\/tags?post=23"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}