{"id":36985,"date":"2019-10-31T22:15:09","date_gmt":"2019-10-31T19:15:09","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-priruchit-dzhuniora\/"},"modified":"2019-10-31T22:15:09","modified_gmt":"2019-10-31T19:15:09","slug":"kak-priruchit-dzhuniora","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/kak-priruchit-dzhuniora","title":{"rendered":"Si e t\u00eb sjell\u00ebsh nj\u00eb junior n\u00eb pun\u00eb?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Si t\u00eb hysh n\u00eb nj\u00eb kompani t\u00eb madhe si junior? Si t\u00eb pun\u00ebsosh nj\u00eb junior t\u00eb denj\u00eb n\u00ebse je nj\u00eb kompani e madhe? N\u00eb k\u00ebt\u00eb artikull do t\u00eb ndaj historin\u00eb ton\u00eb mbi pun\u00ebsimin e t\u00eb rinjve n\u00eb frontend: sesi punuam me detyrat testuese, p\u00ebrgatit\u00ebm intervista dhe nd\u00ebrtuam nj\u00eb program mentorimi p\u00ebr zhvillimin dhe onboarding-in e t\u00eb rinjve, si dhe pse pyetjet standarde p\u00ebr intervista nuk funksionojn\u00eb.<\/p>\n

\"Si
\nUn\u00eb po p\u00ebrpiqem t\u00eb sjell nj\u00eb junior n\u00eb pun\u00eb<\/i>
\n<\/a><\/noindex>
\nP\u00ebrsh\u00ebndetje! Emri im \u00ebsht\u00eb Pavel, un\u00eb punoj n\u00eb frontend n\u00eb ekipin e Wrike. Ne krijojm\u00eb nj\u00eb sistem p\u00ebr menaxhimin e projekteve dhe bashk\u00ebpunimin. M\u00eb jan\u00eb bashk\u00ebngjitur web-it q\u00eb nga viti 2010, kam punuar p\u00ebr 3 vjet n\u00eb nj\u00eb pun\u00eb t\u00eb larg\u00ebt jasht\u00eb vendit, kam marr\u00eb pjes\u00eb n\u00eb disa startup-e dhe kam mbajtur nj\u00eb kurs mbi teknologjit\u00eb e web-it n\u00eb universitet. N\u00eb kompani, marr pjes\u00eb n\u00eb zhvillimin e kurseve teknike dhe programit t\u00eb mentorimit t\u00eb Wrike p\u00ebr junior\u00ebt, si dhe n\u00eb procesin e tyre t\u00eb rekrutimit.<\/p>\n

P\u00ebrse menduam t\u00eb pun\u00ebsojm\u00eb junior\u00eb n\u00eb fillim?<\/h3>\n

\nDerisa jo m\u00eb par\u00eb ne kemi qen\u00eb n\u00eb k\u00ebrkim t\u00eb zhvilluesve frontend n\u00eb nivelin mesatar ose t\u00eb avancuar \u2014 t\u00eb mjaftuesh\u00ebm t\u00eb pavarur p\u00ebr t\u00eb kryer detyrat e produktit pas onboardimit. N\u00eb fillim t\u00eb k\u00ebtij viti kuptuam se d\u00ebshironim t\u00eb ndryshonim k\u00ebt\u00eb politik\u00eb: numri i ekipeve tona produktiv\u00eb u rrit pothuajse dyfish, numri i zhvilluesve frontend u afrua me qind, dhe s\u00eb shpejti parashikohet q\u00eb ky num\u00ebr duhet t\u00eb dyfishohet p\u00ebrs\u00ebri. Ka shum\u00eb pun\u00eb, pak duar t\u00eb lira, dhe n\u00eb treg ka edhe m\u00eb pak, prandaj vendos\u00ebm t\u00eb angazhojm\u00eb djemt\u00eb q\u00eb sapo po fillojn\u00eb rrug\u00ebn e tyre n\u00eb frontend dhe kuptuam se jemi t\u00eb gatsh\u00ebm t\u00eb investojm\u00eb n\u00eb zhvillimin e tyre.<\/p>\n

Kush \u00ebsht\u00eb nj\u00eb junior?<\/h3>\n

\nKy \u00ebsht\u00eb pyetja e par\u00eb q\u00eb ne na erdhi n\u00eb mendje. Ka kritere t\u00eb ndryshme, por parimi m\u00eb i thjesht\u00eb dhe m\u00eb i qart\u00eb \u00ebsht\u00eb ky:<\/p>\n

Nj\u00eb junior ka nevoj\u00eb p\u00ebr shpjegim se cil\u00ebn funksionalitet dhe si t\u00eb b\u00ebhet. Nj\u00eb mid-level duhet t\u00eb shpjegohet se cila funksionalitet \u00ebsht\u00eb e nevojshme dhe ai do t\u00eb merret me zbatimin. Nd\u00ebrsa nj\u00eb senior do t\u00eb t\u00eb shpjegoj\u00eb se pse kjo funksionalitet nuk duhet b\u00ebr\u00eb fare.<\/p><\/blockquote>\n

Dhe n\u00eb nj\u00eb m\u00ebnyr\u00eb ose nj\u00eb tjet\u00ebr, nj\u00eb junior \u00ebsht\u00eb ai zhvillues q\u00eb ka nevoj\u00eb p\u00ebr k\u00ebshilla se si t\u00eb realizoj\u00eb nj\u00eb zgjidhje t\u00eb caktuar. Nga kjo ne vendos\u00ebm t\u00eb fillojm\u00eb:<\/p>\n

    \n
  1. Junior \u00ebsht\u00eb ai q\u00eb d\u00ebshiron t\u00eb zhvillohet dhe \u00ebsht\u00eb i gatsh\u00ebm t\u00eb punoj\u00eb shum\u00eb p\u00ebr k\u00ebt\u00eb;<\/li>\n
  2. Ai nuk di gjithmon\u00eb se n\u00eb cil\u00ebn drejtim d\u00ebshiron t\u00eb zhvillohet;<\/li>\n
  3. Ka nevoj\u00eb p\u00ebr k\u00ebshilla dhe k\u00ebrkon ndihm\u00eb nga jasht\u00eb \u2014 nga lideri, mentori ose n\u00eb komunitet.<\/li>\n<\/ol>\n

    \n\u00cbsht\u00eb gjithashtu disa hipoteza q\u00eb kemi pasur:<\/p>\n

      \n
    1. Do t\u00eb ket\u00eb nj\u00eb stuhi aplikimesh p\u00ebr pozitat junior;<\/i>. Duhet t\u00eb filtrojm\u00eb aplikimet rast\u00ebsore q\u00eb n\u00eb faz\u00ebn e d\u00ebrgimit t\u00eb CV-s\u00eb;<\/li>\n
    2. Filtri i par\u00eb nuk do t\u00eb mjaftoj\u00eb<\/i> \u2014 nevojiten gjithashtu detyra testuese;<\/li>\n
    3. Detyrat testuese do t'i frik\u00ebsojn\u00eb t\u00eb gjith\u00eb<\/i> \u2014 ato nuk jan\u00eb t\u00eb nevojshme.<\/li>\n<\/ol>\n

      \nNatyrisht, kishim edhe nj\u00eb q\u00ebllim: 4 junior\u00eb brenda 3 jav\u00ebsh<\/b>.<\/p>\n

      Me k\u00ebt\u00eb vet\u00ebdije filluam t\u00eb eksperimentojm\u00eb. Plani ishte i thjesht\u00eb: t\u00eb fillonim me nj\u00eb grumbull t\u00eb gjer\u00eb dhe t\u00eb provonim ta ngushtonim gradualisht at\u00eb p\u00ebr t\u00eb p\u00ebrballuar fluksin, por pa e ulur n\u00eb 1 kandidat n\u00eb jav\u00eb.<\/p>\n

      Shpallim vendin e pun\u00ebs<\/h3>\n

      <\/p>\n

      P\u00ebr kompanin\u00eb<\/b>: Do t\u00eb ket\u00eb qindra aplikime! Mendoni p\u00ebr filtrin.<\/p>\n

      P\u00ebr juniorin<\/b>: Mos e frik\u00ebsoni pyet\u00ebsorin para d\u00ebrgimit t\u00eb CV-s\u00eb dhe detyr\u00ebs testuese \u2014 kjo \u00ebsht\u00eb nj\u00eb shenj\u00eb q\u00eb kompania kujdeset p\u00ebr ju dhe ka rregulluar mir\u00eb procesin.\n<\/p><\/blockquote>\n

      \nN\u00eb dit\u00ebn e par\u00eb mor\u00ebm rreth 70 CV nga kandidat\u00eb me \"dijeni n\u00eb JavaScript\". Dhe pastaj m\u00eb shum\u00eb. E m\u00eb shum\u00eb. Ne fizikisht nuk mund t\u00eb ftonim t\u00eb gjith\u00eb p\u00ebr intervista n\u00eb zyr\u00eb dhe zgjodh\u00ebm ata me projektet m\u00eb interesante, nj\u00eb GitHub aktiv ose s\u00eb paku p\u00ebrvoj\u00eb. <\/p>\n

      Por \u00e7far\u00ebdo p\u00ebrfundimi q\u00eb mor\u00ebm n\u00eb dit\u00ebn e par\u00eb \u2014 stuhia kishte filluar. Era e duhur p\u00ebr t\u00eb shtuar nj\u00eb formular pyetjesh para d\u00ebrgimit t\u00eb CV-s\u00eb. Q\u00ebllimi i saj ishte t\u00eb filtroja kandidat\u00eb q\u00eb nuk ishin t\u00eb gatsh\u00ebm t\u00eb b\u00ebnin p\u00ebrpjekjen minimale p\u00ebr d\u00ebrgimin e CV-s\u00eb dhe ata q\u00eb nuk kishin njohuri dhe kontekstin e nevojsh\u00ebm p\u00ebr t\u00eb gjetur p\u00ebrgjigjet e duhura n\u00eb Google. <\/p>\n

      N\u00eb t\u00eb kishte pyetje standart mbi JS, kodimin, web-in, Shkenc\u00ebn e Kompjuter\u00ebve \u2014 ato i di \u00e7do kush q\u00eb ka nj\u00eb ide se \u00e7far\u00eb pyesin n\u00eb intervistat e frontend-it. Cila \u00ebsht\u00eb diferenca mes let\/var\/const? Si t'i aplikosh stilet vet\u00ebm p\u00ebr ekranet q\u00eb jan\u00eb m\u00eb t\u00eb vogla se 600px n\u00eb gjer\u00ebsi? Ne nuk donim ti b\u00ebnim k\u00ebto pyetje n\u00eb intervistat teknike \u2014 praktika tregoi se mund t\u00eb p\u00ebrgjigjesh pas 2-3 intervistave, krejt pa u futur n\u00eb detaje p\u00ebr zhvillimin. Por ato mund t\u00eb tregonin n\u00eb fillim n\u00ebse kandidati e kupton ose jo kontekstin.<\/p>\n

      N\u00eb secil\u00ebn kategori kemi p\u00ebrgatitur 3-5 pyetje dhe \u00e7do dit\u00eb kemi ndryshuar grupin e tyre n\u00eb form\u00ebn e reagimit, deri sa eliminuam ato m\u00eb t\u00eb thjeshta dhe m\u00eb t\u00eb v\u00ebshtira. Kjo na leht\u00ebsoi fluksin \u2014 p\u00ebr 3 jav\u00eb mor\u00ebm 122 kandidat\u00eb<\/b>, me t\u00eb cil\u00ebt mund t\u00eb punonim m\u00eb tej. K\u00ebta ishin student\u00eb IT; djem q\u00eb donin t\u00eb kalonin nga backend n\u00eb frontend; pun\u00ebtor\u00eb ose inxhinier\u00eb t\u00eb mosh\u00ebs 25-35 vje\u00e7are, t\u00eb cil\u00ebt donin t\u00eb ndryshonin radikalisht profesionin dhe kishin b\u00ebr\u00eb p\u00ebrpjekje t\u00eb ndryshme n\u00eb vet\u00eb-arsimim, kurse dhe stazhe.<\/p>\n

      T\u00eb njihemi m\u00eb mir\u00eb<\/h3>\n

      <\/p>\n

      P\u00ebr kompanin\u00eb<\/b>: Detyra e prov\u00ebs nuk i frik\u00ebson kandidat\u00ebt, por ndihmon n\u00eb zvog\u00eblimin e funnel-it.<\/p>\n

      P\u00ebr juniorin<\/b>: Mos e kopjoni testin \u2014 kjo bie n\u00eb sy. Dhe mbani n\u00eb rregull Github-in tuaj!\n<\/p><\/blockquote>\n

      Po t\u00eb kishim ftuar t\u00eb gjith\u00eb n\u00eb intervista teknike, do t\u00eb duhej t\u00eb zhvillonim rreth 40 intervista n\u00eb jav\u00eb vet\u00ebm p\u00ebr junior\u00ebt dhe vet\u00ebm p\u00ebr frontend. Prandaj, vendos\u00ebm t\u00eb kontrollonim hipotez\u00ebn e dyt\u00eb \u2014 p\u00ebr detyr\u00ebn e prov\u00ebs.<\/p>\n

      \u00c7far\u00eb ishte e r\u00ebnd\u00ebsishme p\u00ebr ne n\u00eb testin:<\/p>\n

        \n
      1. T\u00eb nd\u00ebrtosh nj\u00eb arkitektur\u00eb t\u00eb mir\u00eb e t\u00eb shkall\u00ebzueshme, por pa overengineering;<\/li>\n
      2. M\u00eb mir\u00eb t\u00eb b\u00ebsh di\u00e7ka p\u00ebr nj\u00eb koh\u00eb m\u00eb t\u00eb gjat\u00eb, por ta b\u00ebsh mir\u00eb, sesa t\u00eb b\u00ebsh nj\u00eb pun\u00eb t\u00eb shpejt\u00eb dhe ta d\u00ebrgosh me komentin \"do ta p\u00ebrfundoj patjet\u00ebr\";<\/li>\n
      3. Historia e zhvillimit n\u00eb git \u00ebsht\u00eb nj\u00eb kultur\u00eb inxhinierike, nj\u00eb proces iterativ zhvillimi dhe tregon se zgjidhja nuk \u00ebsht\u00eb kopjuar hapur.<\/li>\n<\/ol>\n

        \nK\u00ebtu u pajtuam se donim t\u00eb shqyrtonim nj\u00eb detyr\u00eb algoritmike dhe nj\u00eb aplikacion t\u00eb vog\u00ebl web. Detyrat algoritmike ishin p\u00ebrgatitur n\u00eb nivelin e laborator\u00ebve t\u00eb kurseve fillestare \u2014 k\u00ebrkimi binar, renditja, kontrolli p\u00ebr anagramet, puna me lista dhe pem\u00eb. N\u00eb fund, u ndal\u00ebm te k\u00ebrkimi binar si nj\u00eb variant i par\u00eb p\u00ebr prov\u00eb. Aplikacioni web duhet t\u00eb ishte nj\u00eb loj\u00eb e kryq\u00ebzimit-me-qira p\u00ebrdorur ndonj\u00ebqoft\u00eb framework (ose pa t\u00eb).<\/p>\n

        Gjat\u00eb detyr\u00ebs provuese u p\u00ebrgjigj\u00ebn pothuajse gjysma e djemve t\u00eb mbetur \u2014 na d\u00ebrguan zgjidhjet. 54 kandidat\u00eb.<\/b>. Nj\u00eb informacion i jasht\u00ebzakonsh\u00ebm \u2014 si mendoni, sa realizime t\u00eb loj\u00ebs s\u00eb kryq\u00ebzimit-me-qira q\u00eb jan\u00eb gati p\u00ebr kopjim ka n\u00eb rrjet? <\/p>\n

        Sa?<\/b>N\u00eb t\u00eb v\u00ebrtet\u00eb, duket se vet\u00ebm 3. Dhe n\u00eb shumic\u00ebn e zgjidhjeve kishin pik\u00ebrisht k\u00ebto 3 variante.
        \n\u00c7far\u00eb nuk p\u00eblqeve:<\/p>\n