Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Backend Interviewing Process at Wix Engineering

Backend Interviewing Process at Wix Engineering

Pijus Navickas

June 18, 2019

Transcript

45 slides
  1. Wix Engineering Locations Ukraine Kiev Dnipro Israel Tel-Aviv Be’er Sheva

    Haifa Lithuania Vilnius ROW US, Canada, Berlin and ROW
  2. Passion may be expressed as... ▪ Side-projects. ▪ Watching talks.

    ▪ Reading books & articles. ▪ Following news. ▪ Doing talks. ▪ Knowing something really deep. ▪ ... Great Engineer
  3. Technology stack ▪ Things you use - know well. ▪

    Know the WHY. ▪ Otherwise - doesn't matter THAT much. Great Engineer "Why did you choose …?" "Why is … better?"
  4. Key principles ▪ Readable over writable. ▪ Simple over smart.

    ▪ Automated over manual. Great Engineer
  5. Readable over writable ▪ Naming matters. ▪ Declarativity is better*.

    ▪ Expressive design. ▪ Avoid noise. ▪ Related to simplicity. Great Engineer *except when it's not
  6. Automated over manual ▪ Tests are mandatory. ▪ We are

    lazy. ▪ Also acts as documentation. Great Engineer
  7. Purpose ▪ You get to know Wix a little. ▪

    We get to know you a little. ▪ Test your coding skills. Homework Assignment
  8. Notable points / tips ▪ Direct technical requirements are a

    must. ▪ If something is not specified, use your judgement; code is still evaluated. ▪ Test code is also evaluated. ▪ Avoid adding unnecessary elements; ends up increasing complexity. ▪ Good names help A LOT. ▪ Use tools and language you know well. Homework Assignment
  9. OOP vs FP both are great but... ▪ Know both.

    ▪ Apply FP principles. ▪ Don't go hard-core FP. Homework Assignment Immutable… Pretty much everything. No side-effects. Write declarative code.
  10. Purpose ▪ Test your problem solving. ▪ Test your reasoning.

    ▪ Test your system design skills. ▪ Test your ability to communicate your ideas. Technical Interview
  11. ▪ Verbalise your thoughts. ▪ Don't get stuck for long.

    Ask. ▪ There is rarely a correct solution. ▪ You are not expected to ace everything. ▪ You will be asked WHY questions. Notable points / tips Technical Interview
  12. Notable points / tips ▪ Better too much than too

    little. ▪ Learn, improve and come back. Join Us

More Decks by Pijus Navickas

Other Decks in Technology