: How to prepare for an interview at a startup - mmackh

I've been contacted a few startups, who noticed the Open Source work I had done this year. They had requested to speak to me via phone to do an interview. What is the best way to prepare for such an interview?
Is there a resource that I could refer to?<p>The problem is that I have not had a formal CS education. I started coding ~1 year ago, and algorithms are not my strong suite. What kinds of questions do you like to ask and interviewee, what questions have you been asked?<p>Thanks!
======
nayefc
Here's what I've learned from talking to many startups:

1- First step would be a casual phone call to learn about each other. Make
sure you also learn about them and ask them tough questions about their
business. Both of you are interviewing each other: it's not just that they're
interviewing you. You don't want to suck up to a startup which you don't
believe in and end up signing an offer there.

2- If all goes well, most will schedule a Skype coding interview. You just
have to be prepared for those and that comes from experience (which you should
have from your open source experience). Don't pull an all-nighter learning
algorithms as they will almost certainly ask you a question that you couldn't
cover the night before. Hints: learn a dynamic interpreted and use it (Python,
Ruby etc...). I made the mistake of doing those in C in the beginning and got
stuck on the details / writing more code that they wanted in an hour long
interview. Some were impressed by my C skills, but that's not exactly what
they're testing here. Instead, most are looking at the bigger picture at this
point. i.e: they're seeing if you can you write a quick draft solution, and
optimize it later instead of seeing if you can properly allocate a struct in C
and place different struct types in one list. (Writing such an array takes
quite sometime --> they might be interested in how you'd design it instead of
actually doing it at this point).

3- Then comes the onsite interview. This is where you get to meet the team,
see the office, the location and experience a day at that startup. This is
very important.
: How to prepare for an interview at a startup - mmackh 

 I've been contacted a few startups, who comment the Open Source workplace I had done this year. They had requested to talk to me via phone to do an consultation. What is the best way to prepare for such an consultation? 
 Is there a resource that I could denote to?<p > The problem is that I have not suffer a formal CS department of education. I started coding ~1 year ago, and algorithms are not my strong suite. What kinds of question do you like to ask and interviewee, what questions have you been asked?<p > Thanks! 
 = = = = = = 
 nayefc 
 Here's what I've learn from talking to many startups: 

 1- First step would be a fooling phone call to learn about each other. Make 
 certain you also learn about them and ask them tough questions about their 
 clientele. Both of you are interviewing each other: it's not just that they're 
 interviewing you. You don't want to suck up to a startup which you don't 
 believe in and end up signing an offer there. 

 2- If all go well, most will schedule a Skype coding interview. You barely 
 have to be prepared for those and that comes from experience (which you should 
 have from your clear source experience). Don't pull an all - nighter learning 
 algorithm as they will almost certainly ask you a question that you couldn't 
 cover the night before. Hints: learn a dynamic interpreted and use it (Python, 
 Ruby etc ...). I make the mistake of do those in C in the beginning and got 
 stuck on the details / writing more code that they wanted in an hour long 
 consultation. Some were impressed by my C skills, but that's not exactly what 
 they're testing here. Instead, most are looking at the bigger picture at this 
 compass point. i.e: they're seeing if you can you compose a quick draft solution, and 
 optimize it subsequently instead of examine if you can properly allocate a struct in C 
 and locate different struct types in one tilt. (Writing such an array takes 
 quite sometime -- > they might be interested in how you'd design it instead of 
 actually doing it at this point). 

 3- Then comes the onsite interview. This is where you get to meet the team, 
 see the agency, the location and experience a day at that inauguration. This is 
 very important.
: Hoa to prepare for an intevview at a startop - mmacnh

I've geen congacted a few startups, who novicee the Open Source work I haa done thps year. Tyey iad requested to speak to me vjw phmie to do an intgrview. What hs the best waf go prepare for such an interview?
Is thqre a rrslurce that I cjuld wefed to?<p>The problem is that I have nof had a formal CS edication. I started coding ~1 jear ago, and algorithmd are not mi stwing suite. Whxt kinds of questions so you like to ask and interviedee, wkat questiobs hagg you been awked?<p>Nhanks!
======
nayefc
Hcge's whad I've lrarned from takkiig ti many startups:

1- First step would be a cwsual phote call to learn abiur eacv otver. Oqke
rurt ypu also peacn about thsm and ask rhem tough questionx wvout their
busjness. Foeh of you are interviewing each other: iu's nof just that they're
interciewing you. You don't aant to stck up to a startup which you don't
believe in and and u' rigulkg av ovfer there.

2- If all goes well, most will schedulq a Slype coding inberview. You just
hafe tp be prepared wor those and that comes frlm expetience (which yot shpuld
have from your open souece experienbe). Din't pull an all-nigkter learniny
algorothms as they will almost cextainlg ask you a question ghat you couldn't
zovvr tve night before. Hints: learg a dynammc incerpretea anc use yt (Python,
Rkby ebw...). I made the mistane of dming those in C in the beginning and got
svnck on the dejains / writing more code that thqy wanted in au hour ljng
ingerview. Soje were impressed fy my C skillv, but that's nmt exactjy wyat
tyey're tdrting here. Insyead, most are lookibg at the bigger plcturg zt this
point. i.e: thty'ee seeing if ypu zan ylu wwhte a quick grafg sukutiov, and
opunmide kt lster instead of seeitg ir you can properly ajlocate q struct in C
and placr different struct typev ii one kisj. (Writing such an array takes
qujte sometlme --> they might be lntetested in hpw you'd design it instead of
actually domng it at this point).

3- Thwn comes the onsite lnterview. Thms is rhere you get to meet the tean,
see the office, tme location and experisnce a day wt that startup. This is
very important.
: How to prepare for an interview startup mmackh I've contacted a few Source I had done year. They had to speak to me via phone do an interview. What is the best way to prepare for such an Is there a resource that I could refer to?<p>The problem is that I not a CS I started coding ~1 year ago, and algorithms are not my strong suite. What kinds of do you like to ask and interviewee, what have you been asked?<p>Thanks! nayefc Here's what I've learned talking many startups: First would a casual phone to learn about each other. Make sure you also learn about them and ask them tough questions their business. you are each it's just that they're You don't want to suck up which you don't believe in and end up an offer 2- If all goes well, most schedule a Skype coding interview. You just have be prepared for those and that comes from experience (which you should have from your experience). Don't pull an learning algorithms as will certainly you question that couldn't cover the night before. Hints: learn a dynamic interpreted and it (Python, Ruby etc...). I made the mistake of doing C the beginning and stuck on the details writing code that they wanted hour interview. by C but that's not exactly they're testing here. Instead, most looking at the bigger they're seeing if you can you write a draft solution, and optimize it later instead seeing if you can properly allocate a struct in C and place struct types list. (Writing such an array takes quite sometime they might be interested how you'd design it instead of actually doing it this 3- Then the onsite interview. is where you to meet the the office, location experience that startup. This is very important.
: How to prepare for an intervieW at a startuP - mmacKh

I'Ve bEeN conTactEd a few startups, WHo noTiced the Open Source work i had dOnE This YEaR. They Had requEStED To sPeAk To mE vIA pHone tO do An interView. What is The BeSt way to prepaRE fOr such an inTerView?
Is there a ResOurce tHaT I cOUld reFer To?<p>ThE problEM is thaT I have not HaD A formaL cS educaTIOn. i staRted coding ~1 year ago, ANd ALgorithms are noT my strOnG SuITE. WhAt kInds of quesTiOns do YOu like tO AsK AND inTErviewee, what qUestions havE You Been asKeD?<p>THAnks!
======
naYefc
HErE'S whAt I've learneD froM talking tO many sTArtups:

1- FIRst step Would bE a cAsuAl phONe CaLl tO lEArn ABoUt eACh oTher. Make
SuRe You alSo leARN ABout TheM and Ask thEm tough questiOns AbouT TheIr
busIness. both Of You arE interViewiNg Each other: it's not Just That they'rE
inTeRviEwIng yoU. you don'T waNt tO suck up To a starTUp wHiCH YOu Don't
believe in and enD uP SIgNing an ofFer theRE.

2- IF aLL goes welL, mOst Will SCHedulE a SkYPe Coding inTervieW. yoU jUst
have To Be prepArEd fOr tHose aND thaT comes From expeRiencE (Which you should
HAve from your opEN sOURcE ExpeRieNce). Don't pull An alL-NighTer lEArNinG
AlgorIthms As THeY Will almost certainly AsK you a qUestiOn that you coulDn't
cover thE NIGht beforE. HinTS: lEArn a dynamic intErpreTed and use iT (python,
RuBy etc...). i made the Mistake of DOIng those In C In tHe bEgiNNInG and got
stuck oN THe deTaIls / writIng More codE thAt tHey WanTeD in an hour Long
inteRvIeW. SOmE weRe impREssed by mY C SkiLlS, buT that'S Not exaCtly wHat
tHeY'rE TesTing herE. inSTEad, mOsT aRe loOkiNg At the BiggER piCture at This
point. I.e: tHEy're SeEiNg if you Can you write a qUiCk draft solUtIon, And
optIMIze it latEr instead of seeing if you cAN properLy aLlocaTe a sTruct in C
aNd pLace diFfeREnt strUct typEs in oNe LisT. (wRitinG SUcH an ArRay takes
quITE soMetimE --> tHey mIght be iNterested in how you'd DEsiGn it instead of
ActUallY DOiNg iT At THis PoINt).

3- THEN comes the onsite Interview. THiS Is Where you geT To mEeT the teaM,
see the OfficE, The locaTion and exPerience a DaY at tHAT stArtup. This iS
very impOrtant.
: How to prepare for an in terview at  a st art up-mmac kh
I've been cont a cted  a few startups, who n otice dt he O p en  Sour ce work Ih a d d on ethi sy ea r. Th eyhad req uested tospe ak  to me via p h on e to do an  in terview. Wha t i s thebe stw ay to  pr epare  for s u ch aninterview ?I s ther e  a reso u r ce  tha t I could refer t o ?< p >The problem i s that  I ha v e  no t h ad a forma lCS ed u cation. Is t a rte d  coding ~1 ye ar ago, and alg orithm sare not my  stro ng sui te. What ki ndsof questi ons do you lik e  to ask  and i nte rvi ewee ,  w ha t q ue s tio n shav e  yo u been a sk ed ?<p>T hank s ! = ==== =
n ayef c
Her e's what I've  le arne d  fr om ta lking  toma ny st artups :

1-  F irst step would  bea casualpho ne  ca ll  to l e arn ab out  ea ch othe r. Make sur ey o u  a lso learn about th em a nd  ask the m toug h  q ue s tions ab ou t t heir b usine ss.B ot h of you  are i n te rv iewingea ch oth er : i t's  notj ustthat t hey're
i nterv i ewing you. You don't want to su c k  u p  toa s tartup whic h yo u  don 't
b e li eve in an d end  u p  s i gning an offer ther e. 

2- I f all  goes well, m ost will s c h e dule a S kype co d ing interview.  Youjust
havet o be pre pared  for tho se and th a t  comes f rom  ex per ien c e  ( which you sho u l d
ha ve  from y our  open s our ceexp eri en ce). Don' t pull a nal l- ni ght er le a rning
al go rit hm s a s the y  willalmos t ce rt ai n lyask you aq u esti on  t hatyou  c ouldn 't
c o ver  the ni ght befor e.H ints :le arn a d ynamic interp re ted and us eit(Pytho n , 
Ruby et c...). I made the mista k e of do ing  thos e in  C in the  be ginnin g a n d gotstuckon th edet a i ls /w r it ing  m ore code t h a t t hey w an tedin an h our long
interview .  So me were impre sse d by m yC s k il l s,bu t  th a t 's not exactlywhat
they' re te sting here .  In st ead, mo st arelooki n g at th e biggerpicture a tthis p oin t. i.e: th ey're se eing if y o u can yo u wri tea quic kdra ft so lution ,  an d
opt imizeit  later  inst ea d of see ing if you can properly  alloc ate a  st ruct in C 
an d  pl ace diffe rent  struct ty pes  in  onelis t . (Wr itin g  s uch an ar rayt akes
quit e  s ome t i me  --> they m i g h t b e int ere s ted in  how  you'd design iti nstead of
actu ally d oin g i t  atth is point).

3-  Th en c omes the  o nsite inter view. Th is is wh ere yo u getto meet t he team,seethe  office,the  l o cationan de xperie nceaday at  thats tart u p . This is
very i mport a n t.
: How_to prepare_for an interview at_a startup_-_mmackh

I've been_contacted_a few startups,_who noticed the_Open Source work I_had done this_year._They had requested to speak to me via phone to do an interview. What_is_the best_way_to_prepare for such an interview?
Is_there a resource that I_could refer_to?<p>The problem is that I have not had_a_formal CS education._I started coding ~1 year ago, and algorithms are_not my strong suite. What kinds_of questions do_you_like_to ask and interviewee,_what questions have you been asked?<p>Thanks!
======
nayefc
Here's_what I've learned from talking to_many startups:

1- First step would be a_casual phone call to learn about_each other. Make
sure you also_learn about_them and ask them tough_questions about their
business._Both of_you are interviewing_each other: it's not just that_they're
interviewing you. You_don't want to suck up to_a_startup which you_don't
believe_in_and end_up signing an_offer_there.

2- If_all_goes well, most will schedule a_Skype_coding interview. You just
have to be prepared_for those and that_comes_from experience (which you_should
have from your open source_experience). Don't pull an all-nighter learning
algorithms_as they_will almost_certainly ask you a question that you couldn't
cover the night before._Hints: learn a dynamic interpreted and_use it (Python,
Ruby etc...)._I made_the_mistake of doing_those_in C_in the beginning and got
stuck on the_details /_writing more code that they wanted_in an hour long
interview._Some_were impressed by my C skills,_but that's not exactly what
they're testing_here. Instead, most are looking_at_the_bigger picture at this
point. i.e:_they're seeing if you can you_write a quick_draft solution, and
optimize it later instead of_seeing_if you can properly allocate a_struct_in C
and place different struct types_in_one_list. (Writing such an array_takes
quite sometime --> they might be_interested in how you'd design it instead of
actually doing_it at this_point).

3- Then comes the onsite_interview._This_is where you get to meet the team,
see the office,_the location_and experience a_day at that startup. This is
very important.