Engineering your culture: How to keep your engineers happy

Engineering your culture: How to keep your engineers happy

We all know how difficult (and expensive!) it is to convince brilliant engineers to join our team. The real challenge starts on Day 1 – What can we do to keep them happy and engaged?

After all, "Bored people quit".

If you know you should do better but ran out of ideas how - come on down! We'll talk about how to make their 1st day at work memorable, how to help them build a personal brand, how to figure out and sell our unique strength as a company (GitHub-style), why we should bring them to investors' events and plenty more.

In this talk I'll share 8 tips you could apply to build happier engineering teams.

P.S. If you enjoyed these slides, you'll enjoy my book - leadingsnowflakes.com

3eb531c7e24a17356912c70a6f4755c0?s=128

Oren Ellenbogen

February 23, 2014
Tweet

Transcript

  1. 1.

    @ “No  were harmed in the making of this

    talk” – said no one, ever. Until now.
  2. 2.
  3. 5.
  4. 7.
  5. 10.
  6. 11.
  7. 12.
  8. 13.
  9. 14.
  10. 15.
  11. 17.

    Full-stack Engineer @ Commerce Sciences I write at Lnbogen.com I

    tweet @orenellenbogen You can call me bogen. It’s kinda short, like me. Pronounced: BOO-GEN
  12. 19.

    SoftwareLeadWeekly.com - 14 months - 65 weeks in a row

    - 7 recommendations / week - 455 recommendations so far - 30-40 posts digested / week - 2,600 posts so far - 500-800 words / post (roughly) - 52-60 books The only logical conclusion then?
  13. 20.
  14. 21.
  15. 23.

    • Amazing mission statement organize the world’s information and make

    it universally accessible and useful • Hard to iterate fast (process heavy) • Incredible technology MapReduce, Google FS etc.
  16. 24.

    • Awesome mission statement make the world more open and

    connected • Fast iterations, small teams • Great technology (+ leftovers) PHP – I’m looking at you!
  17. 25.

    • Some lame mission statement make more money than the

    church • Fast iterations, small teams • Great technology, at huge scale!
  18. 26.
  19. 28.

    Explicitly hire for: People who can prioritize & get things

    done on their own They focus on autonomy
  20. 29.
  21. 30.
  22. 31.
  23. 32.
  24. 33.

    Changing code -> … -> something breaks -> lack of

    trust -> slower cycle (process++) -> new department of [trust issue] -> still breaks … -> death (of happiness)
  25. 34.
  26. 35.
  27. 36.

    Changing code -> … -> something breaks -> quick release

    + retrospect -> automate/test stuff -> still breaks -> quick release + retrospect -> automate/test stuff -> …
  28. 37.
  29. 38.
  30. 39.
  31. 41.
  32. 42.
  33. 43.

    “ Google’s mission is to organize the world’s information and

    make it universally accessible and useful. WTF?
  34. 44.
  35. 45.
  36. 46.

    The last person to join the company is responsible to

    create a “starter kit” for the next one to join
  37. 47.
  38. 48.
  39. 49.
  40. 50.
  41. 52.
  42. 53.
  43. 57.

    “ One day I will work for a company that

    does something like this. ”
  44. 58.
  45. 60.
  46. 61.
  47. 64.

    Junior Engineers Practice, practice, practice Experienced Engineers Practice, lead, build

    trust Veteran Engineers Become an expert or pivot (+mentor as a Bar Raiser)
  48. 65.
  49. 66.
  50. 67.
  51. 69.