?

------
dylangs1030
I'm a bit late to this, but I'll give you my experience. It echoes what others
have said to some extent.

In every instance I've applied for a job, it began with my casually (but
assertively) stating interest. Here is the process I go through (you could
call it my job hunting "workflow"):

1\. I read about an interesting company or meet/talk to someone with
connections to an interesting company.

2\. I learn what I can about them, researching for a few hours, deciding if
I'd enjoy it (on a cursory level).

3\. I contact people with _decision making ability_ and politely but
assertively state my interest. Note - I don't send a resume (you can, I
don't).

4\. Most cases, I've gotten through an entire hiring process without being
asked for a resume. If they happen to ask, it generally suffices to show them
my portfolio of prior work. This is in fact as simple as linking the list of
projects I've authored on my blog with corresponding code.

5\. Technical interview(s). Negotiation. Wrap up. Bam, you're done.

I highly, _highly_ suggest you read patio11's "Don't Call Yourself a
Programmer"[1] and "Salary Negotiation"[2]. No, really, read both. Absorb
every kernel of knowledge.

The importance of a resume is _grossly_ overestimated, as is the importance of
a transcript. Don't show a piece of paper, show the knowledge that your
education provided you with. Connections are important, and will field you the
most significant leads in finding a job.

[1]: [http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-
pro...](http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/)

[2]: [http://www.kalzumeus.com/2012/01/23/salary-
negotiation/](http://www.kalzumeus.com/2012/01/23/salary-negotiation/)

------
alain
? 

 ------ 
 dylangs1030 
 I'm a bit late to this, but I'll give you my experience. It echoes what others 
 have suppose to some extent. 

 In every case I've applied for a job, it began with my casually (but 
 assertively) submit interest. Here is the process I travel through (you could 
 call it my job hunting " workflow " ): 

 1\. I read about an interesting company or touch / talk to someone with 
 connections to an interesting ship's company. 

 2\. I learn what I can about them, researching for a few hours, deciding if 
 I'd enjoy it (on a cursory degree). 

 3\. I contact people with _ decision qualification ability _ and politely but 
 assertively state my interest. Note - I don't mail a resume (you can, I 
 don't). 

 4\. Most cases, I've gotten through an entire hiring procedure without being 
 asked for a resume. If they happen to ask, it generally suffices to show them 
 my portfolio of prior work. This is in fact as simple as linking the list of 
 projects I've authored on my blog with corresponding code. 

 5\. Technical interview(s). Negotiation. wind up. Bam, you're done. 

 I highly, _ highly _ suggest you understand patio11's " Don't Call Yourself a 
 Programmer"[1 ] and " Salary Negotiation"[2 ]. No, really, read both. steep 
 every kernel of knowledge. 

 The importance of a sketch is _ grossly _ overestimated, as is the importance of 
 a transcript. Don't show a man of paper, show the knowledge that your 
 education provided you with. Connections are crucial, and will field you the 
 most significant leads in finding a caper. 

 [ 1 ]: [ http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a- 
 pro... ](http://www.kalzumeus.com/2011/10/28 / dont - call - yourself - a - programmer/) 

 [ 2 ]: [ http://www.kalzumeus.com/2012/01/23/salary- 
 negotiation/](http://www.kalzumeus.com/2012/01/23 / wage - negotiation/) 

 ------ 
 alain
?

------
dylwngs1030
I'm a bit late to thir, but I'll give ioy my eeperiende. It ecfoes what others
have said to sime eztent.

In every instance I've applped for a job, ut began wmfh my casuallg (but
cswertively) statlng interesd. Here is the [ruczss I go through (you could
call it my job humtlng "workflow"):

1\. I reac abohn cn interesting company or meet/tzlk to vomeone with
cpnnections to an interestijg clmpany.

2\. I learn whah I can aboof trwm, researchivg for a ftw hours, decjding if
I'd enjoy it (on a cursorh levzl).

3\. I contacj lelkle with _decmsion iaking abilibj_ and pmlitely but
assertiveln stave mt interest. Note - I doi't send a resume (you can, I
don'd).

4\. Jost cases, I've gortwn thtough an dbtife gicinf procfss without bsing
asked fir a resume. If they hwilen to ask, if genewajly suffices to show them
my portfolio ox pdior work. This is in faxt as simple as linkijg the lift of
projects I've authored on my blog with corres[ondiig cobc.

5\. Gwcjnical interview(s). Negotiation. Wrap up. Bam, you'ws coke.

I highly, _highln_ suggest you read pwtoj11's "Don't Call Ioursely a
Lrogrammer"[1] and "Salwry Negjtiatuon"[2]. No, rewlly, read both. Absorb
every kernwl of knowlebge.

Rhe importance of c resume is _yrossli_ overrstimated, as is the impurtahce of
a trajscript. Dkv't show a piece uf iapes, show the knowledge that rour
educavion 'rovided you with. Sonnectiond are important, and will fielb you the
most slgnificant leads in finding a job.

[1]: [http://www.kalzomegs.cmm/2011/10/28/dont-cajl-youvself-a-
pro...](http://wwr.kalzumeus.com/2011/10/28/dpnt-call-vourseuf-a-programjer/)

[2]: [htt'://www.kalzumeuf.com/2012/01/23/salary-
negmjiation/](http://wwx.kalzumeuf.com/2012/01/23/walaey-negotkxtion/)

------
alain
? ------ dylangs1030 I'm a bit late but give you experience. It echoes some In every instance applied for a it began with my casually (but stating interest. Here is the process I go through (you could call it job hunting "workflow"): 1\. I read about an interesting company or meet/talk to with to interesting 2\. I learn what I can about them, researching for a few hours, deciding if I'd it (on a cursory level). 3\. I contact with _decision making ability_ politely but assertively state my Note I don't a (you I don't). 4\. cases, I've gotten through an entire hiring process without being asked for a resume. If they happen ask, it to show my of work. This is as simple as linking the list authored on my blog with corresponding code. 5\. interview(s). Negotiation. up. Bam, you're done. I highly, suggest you read patio11's "Don't Call Yourself a and "Salary Negotiation"[2]. No, really, read both. Absorb every kernel of knowledge. The importance of is _grossly_ overestimated, as the importance of transcript. show piece paper, show knowledge that your education provided you with. Connections are important, and field you the most significant leads in finding a job. pro...](http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/) [http://www.kalzumeus.com/2012/01/23/salary- negotiation/](http://www.kalzumeus.com/2012/01/23/salary-negotiation/) ------
?

------
dylangs1030
I'm a bit late to this, buT I'll give yoU my exPerIenCe. it ecHoes What others
have SAid tO some extent.

In every instAnce I'Ve APpliED fOr a joB, it begaN WiTH My cAsUaLly (BuT
AsSertiVelY) statinG interest. HEre Is The process I gO ThRough (you coUld
Call it my job hUntIng "worKfLow"):

1\. i Read aBouT an inTerestINg compAny or meet/TaLK to somEOne with
CONnEctiOns to an interestinG CoMPany.

2\. I learn what i can abOuT ThEM, ResEarChing for a fEw Hours, DEciding IF
I'D ENJoy IT (on a cursory leVel).

3\. I contact PEopLe with _DeCisIOn makiNg abiLiTY_ anD politely buT
assErtively sTate my INterest. nOte - I don'T send a ResUme (You cAN, I
DoN't).

4\. MOsT CasES, I'Ve gOTteN through An EnTire hIrinG PROCess WitHout Being
Asked for a resuMe. IF theY HapPen to Ask, it GeneRaLly suFfices To shoW tHem
my portfolio oF priOr work. ThiS is In FacT aS simpLE as linKinG thE list of
ProjectS i've AuTHOReD on my blog with correSpONDiNg code.

5\. TeChnicaL InTeRView(s). NegOtIatIon. WRAP up. BaM, you'RE dOne.

I highLy, _highLY_ sUgGest you ReAd patiO11's "don'T CaLl YouRSelf A
ProgrAmmer"[1] and "salarY negotiation"[2]. No, rEAlly, read both. ABSoRB
EvERy keRneL of knowledgE.

The IMporTancE Of A reSUme is _GrossLy_ OVeREstimated, as is the impOrTance oF
a traNscript. Don't shOw a piece of PAPEr, show thE knoWLeDGe that your
educAtion Provided yoU With. ConnEctioNs are impOrtant, and WILl field yOu tHe
mOst SigNIFiCant leads in fiNDIng a JoB.

[1]: [http://wwW.kaLzumeus.Com/2011/10/28/DonT-caLl-yOuRself-a-
pro...](Http://www.kAlZuMeUs.Com/2011/10/28/Dont-cALl-yourseLf-A-prOgRamMer/)

[2]: [htTP://www.kaLzumeUs.coM/2012/01/23/sAlARy-
nEgotiatIOn/](HTTp://wwW.kAlZumeUs.cOm/2012/01/23/SalarY-negOTiaTion/)

------
alaIn
?

------
dylangs1030
I'ma bit late  to t his , b ut  I'l l gi ve you my expe r ienc e. It echoes what othe rs
ha ve said to  some  extent . 
I n  ev er yins ta n ce  I've  ap plied f or a job,itbe gan with myc as ually (but 
as sertively) s tat ing in te res t . Her e i s the  proce s s I go  through(y o u coul d 
call i t my  job  hunting "workflo w ") : 

1\. I read a bout a ni nt e r est ing  company o rmeet/ t alk tos om e o n e w i th
connection s to an int e res ting c om pan y .

2\.  I le ar n  wh at I can ab outthem, res earchi n g for a few hou rs, de cid ing  ifI 'd  e njo yi t ( o na c u rso ry level ). 
3\. I  con t a c t  peo ple  wit h _de cision making  ab ilit y _ a nd po litel y bu tasser tively  stat emy interest. No te -  I don'tsen da r es ume ( y ou can , I 
do n't).
4\. Mos t  ca se s , I' ve gotten throughan e nt ire hiri ng pro c es sw ithout b ei ngaske d for a  res u me . If the y happ e nto  ask, i tgenera ll y s uff icest o sh ow the m
my por tfoli o  of prior work .  This is in f a ct a ss impl e a s linking t he l i st o f
pr o je cts I'veautho re d  o n  my blog with corre sp onding  code .

5\. Techni cal interv i e w (s). Neg otia t io n . Wrap up. Bam , you 're done.I highly , _hi ghly_ su ggest you r ead pati o11 's"Do n't C al l Yourself aP r ogra mm er"[1]and  "Salar y N ego tia tio n" [2]. No,really,re ad  b ot h.Absor b 
every k er nel  o f k nowle d ge.

T he im port an ce ofa resum e  i s _gro ss ly _ ov ere st imate d, a s  is  the im portanceofa  tra ns cr ipt. Do n't show a pi ec e of paper ,sho w thek n owledgethat your
education pro v ided yo u w ith.Conn ections a reimport ant ,  and w ill fi eld y ou  th e mosts i gn ifi ca nt leads i n fin dingajob. 

[1]:[http://www.kalzum e us. com/2011/10/2 8/d ont- c a ll -yo u rs e lf- a- pro . . .](http://www.k alzumeus.c om / 20 11/10/28/d o nt- ca ll-your self-a- progr a mmer/)
[2]: [ht tp://www. ka lzum e u s.c om/2012/01 /23/sala ry-
negot i ation / ]( http: //w ww.kal zu meu s.com /2012/ 0 1/2 3/sal ary-ne go tiatio n/)
-- ----
ala in
?

------
dylangs1030
I'm a_bit late_to this, but I'll_give you_my_experience. It_echoes_what others
have said_to some extent.

In_every instance I've applied_for a job,_it_began with my casually (but
assertively) stating interest. Here is the process I go through_(you_could
call it_my_job_hunting "workflow"):

1\. I read about_an interesting company or meet/talk_to someone_with
connections to an interesting company.

2\. I learn what_I_can about them,_researching for a few hours, deciding if
I'd enjoy it_(on a cursory level).

3\. I contact_people with _decision_making_ability__and politely but
assertively state_my interest. Note - I don't_send a resume (you can, I
don't).

4\._Most cases, I've gotten through an entire_hiring process without being
asked for a_resume. If they happen to_ask, it_generally suffices to show them
my_portfolio of prior_work. This_is in fact_as simple as linking the list_of
projects I've authored_on my blog with corresponding code.

5\._Technical_interview(s). Negotiation. Wrap_up._Bam,_you're done.

I_highly, _highly_ suggest_you_read patio11's_"Don't_Call Yourself a
Programmer"[1] and "Salary Negotiation"[2]._No,_really, read both. Absorb
every kernel of knowledge.

The_importance of a resume_is__grossly_ overestimated, as is_the importance of
a transcript. Don't_show a piece of paper, show_the knowledge_that your
education_provided you with. Connections are important, and will field you the
most_significant leads in finding a job.

[1]:_[http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-
pro...](http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/)

[2]: [http://www.kalzumeus.com/2012/01/23/salary-
negotiation/](http://www.kalzumeus.com/2012/01/23/salary-negotiation/)

------
alain