This is a title

138 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
138
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

This is a title

  1. 1. BUILDINGA SoftwareDevelopment TeamKHURRAM VIRANIJAKE HIRSCH-ALLEN
  2. 2. KHURRAMVIRANI @viranikPARTNERFunctional Imperative @func_iwww.functionalimperative.comINSTRUCTORBitmaker Labs @bitmakerlabswww.bitmakerlabs.com
  3. 3. JAKE HIRSCH-ALLEN @jakehirschallenPARTNERFunctional Imperative @func_iwww.functionalimperative.comDIRECTORBD - OODA Technologies @oodatechwww.ooda.caSPMIncentives for Global Health @HealthImpactwww.healthimpactfund.org
  4. 4. DEMAND
  5. 5. INDEED.COMJob Trends
  6. 6. "Software Is EatingThe World”Marc Andreessen, Aug 2011Buy A 10x Software Developer: ItsThe Best Investment You CanMake… Venkatesh Rao, April 2016
  7. 7. TORONTO
  8. 8. TORONTO IS #8Top 20 Startup EcosystemsStartup Genome Report 2012
  9. 9. SR. DEVELOPER80K100KTORONTO:SALARIESJR. DEVELOPER(NEW CS GRAD)50K60K
  10. 10. TheStruggle
  11. 11. SFOYYZ
  12. 12. ANDDETERMINING FITHIRING
  13. 13. THEGENERALISTTHESPECIALIST
  14. 14. FRAMEWORKDeveloperAPPLICATIONDeveloperVS
  15. 15. "Should I hire a Railsdeveloper for my Djangoproject?"Depends...Q:
  16. 16. "Finding GreatDevelopers"Joel Spolsky, 2006
  17. 17. Great developersalready havejobsGo where theyhang out
  18. 18. INTERVIEWING(MOSTLY TECHNICAL)
  19. 19. Real World Example:①  Transcript②  Online Portfolio (apps, twitter, blog, github)③  30m technical phone screen④  Code challenge (1-2hr homework)⑤  3h on-site technical interview⑥  Pair programming with Sr. Dev(on-site half-day session)INTERVIEWING JUNIORS /NEW GRADS
  20. 20. Jr. Ruby on Rails Developer:TECHNICAL REQUIREMENTS
  21. 21. WHITEBOARD: FIZZ BUZZWHY CANT PROGRAMMERS.. PROGRAM?http://www.codinghorror.com/blog/2007/02/why-cant-programmersprogram.htmlFIZZ BUZZ TESThttp://c2.com/cgi/wiki?FizzBuzzTestWrite a program that prints the numbers from 1 to 100.But for multiples of three print “fizz” instead of the numberand for the multiples of five print “buzz”. For numberswhich are multiples of both three and five print “fizzbuzz”.
  22. 22. Have more of your Sr.Devs interview themConversational approach.More focus on past experience than writingFizzBuzzDiscuss design patterns they like and solvearchitecture problems, instead of SQLstatementsINTERVIEWING SR.DEVELOPER
  23. 23. COMMON QUESTIONS①  But no one on my team (yet) is technicalenough to conduct a technical interview…What then?②  Should I hire a developer that knowslanguage/framework X when we uselanguage/framework Y?Eg: Python/Django <==> Ruby/Rails
  24. 24. MORE THAN JUSTA FOOSBALL TABLECULTURE
  25. 25. DEVELOPERS ARECREATIVEArtists dont work 9 to 5
  26. 26. DEVELOPERS ASPRODUCT DRIVERSesp. when the company IS theproduct
  27. 27. lunchtogetherLUNCHTOGETHER
  28. 28. REMOTETALENTNO, NOT“OFFSHORING”
  29. 29. "Stop whiningand start hiringremote workers""Why We (Still)Believe in WorkingRemotely"
  30. 30. ①  Dont want to relocate②  Dont need to relocate③  "My spouse is going to med school"④  Productivity: "most of our remotedevelopers work longer hours than ourin-office devs."⑤  Collaborative workspaces⑥  Forces better communication⑦  Not widely adopted (yet)WHY?
  31. 31. Works super well with collaborativeworkspaces.Search online for remote full timepositions today and you wont findmuch.... But in a few years almost everyonewill be doing it and it will be a nobrainer.*REMOTE TALENT
  32. 32. REMOTE TALEHow?
  33. 33. EQUITYFOR WHEN $$ ISJUST NOT ENOUGH
  34. 34. EQUITYVery heavily debated topic.① Fairness > %② Vesting③ Slices④  Shotgun clause⑤ Equity ! = Currency⑥ Dilution / Valuation !%#&
  35. 35. CONCLUSION① High Demand: YYZ losing talent to SFO② Remote talent & distributed teams => Future!③ Startups: seek generalists④ Established companies: seek both generalists &specialists⑤ Technical interviews are very important⑥ Go where the talent is⑦ Culture is important to attract and retain talent⑧ Give vesting equity to your founding team
  36. 36. REFERENCESFurther Readinghttp://alittlebitofjake.wordpress.com/2012/04/16/buy-a-10x-software-developer-its-the-best-investment-you-can-make/http://techcrunch.com/2012/11/20/startup-genome-ranks-the-worlds-top-startup-ecosystems-silicon-valley-tel-aviv-l-a-lead-the-way/http://blog.stackoverflow.com/2013/02/why-we-still-believe-in-working-remotely/http://www.joelonsoftware.com/articles/FindingGreatDevelopers.htmlhttp://37signals.com/svn/posts/3064-stop-whining-and-start-hiring-remote-workershttp://online.wsj.com/article/SB10001424053111903480904576512250915629460.htmlhttp://justinjackson.ca/why-distributed-teams-are-more-effective/http://answers.onstartups.com/questions/6949/forming-a-new-software-startup-how-do-i-allocate-ownership-fairly/23326#23326
  37. 37. REFERENCESFurther Readinghttp://foundrs.com/http://www.andrew.cmu.edu/user/fd0n/35%20Founders%27%20Pie%20Calculator.htmhttp://berkonomics.com/?p=1214http://billpayne.com/2011/02/14/startup-valuations-the-dave-berkus-method.htmlhttp://medstars.com/images/docs/modified_berkus_method.pdfhttp://www.bothsidesofthetable.com/2011/10/14/understanding-how-dilution-affects-you-at-a-startup/
  38. 38. QUESTIONS?FIN.

×