Backend Interviewing Process at Wix Engineering

https://www.meetup.com/Wix-com-tech-talks-in-Vilnius/

Transcript

1. Pijus Navickas, Software Engineer Backend Interviewing Process at Wix Engineering pijusn@wix.com https://pijusn.eu
2. Know Wix 01
3. Wix.com Wix.com
4. Site-Builder Wix.com
5. Business Domains Wix.com
6. Structure Wix.com "verticals" "companies" Autonomous group of cross-functional teams. "guilds" Community of people of the same profession. Blog Server
7. Agile? Yes, but implementation depends on team
8. Technologies (server) Wix.com … pretty sure I'm missing something
9. DevOps? We have DevOps-oriented culture
10. You don't code, You develop. You own it.
11. Wix Engineering Locations Ukraine Kiev Dnipro Israel Tel-Aviv Be’er Sheva Haifa Lithuania Vilnius ROW US, Canada, Berlin and ROW
12. ~1000 (micro/macro/mega)services
13. ~700 developers
14. ~50 BE engineers in Vilnius
15. Being a great engineer 02
16. Passion may be expressed as... ▪ Side-projects. ▪ Watching talks. ▪ Reading books & articles. ▪ Following news. ▪ Doing talks. ▪ Knowing something really deep. ▪ ... Great Engineer
17. 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?"
18. Key principles ▪ Readable over writable. ▪ Simple over smart. ▪ Automated over manual. Great Engineer
19. Readable over writable ▪ Naming matters. ▪ Declarativity is better*. ▪ Expressive design. ▪ Avoid noise. ▪ Related to simplicity. Great Engineer *except when it's not
20. Simple over smart ▪ Small units are helpful. ▪ Avoid over-engineering. Great Engineer
21. Automated over manual ▪ Tests are mandatory. ▪ We are lazy. ▪ Also acts as documentation. Great Engineer
22. Interview Process 03
23. Homework Assignment Technical Interview Typical Flow Hiring Process HR Interview Team Lead Interview + 1-2 evenings 3 hours
24. Homework Assignment 04
25. Homework Assignment Technical Interview Typical Flow Hiring Process HR Interview Team Lead Interview +
26. Purpose ▪ You get to know Wix a little. ▪ We get to know you a little. ▪ Test your coding skills. Homework Assignment
27. Evaluation ▪ Technical requirements. ▪ Code. ▪ Design. Homework Assignment
28. 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
29. 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.
30. Preparation (books) Homework Assignment
31. Technical Interview 05
32. Homework Assignment Technical Interview Typical Flow Hiring Process HR Interview Team Lead Interview +
33. Purpose ▪ Test your problem solving. ▪ Test your reasoning. ▪ Test your system design skills. ▪ Test your ability to communicate your ideas. Technical Interview
34. ▪ Thought process. ▪ Knowledge. ▪ Logic. Evaluation Technical Interview
35. ▪ 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
36. Preparation (books) Technical Interview
37. Preparation (lots of material) Technical Interview https://github.com/checkcheckzz/system-design-interview
38. Remaining Stages 06
39. Homework Assignment Technical Interview Typical Flow Hiring Process HR Interview Team Lead Interview +
40. I don't know. Good luck.
41. Join Us 07
42. https://jobs.wix.com Join Us
43. Notable points / tips ▪ Better too much than too little. ▪ Learn, improve and come back. Join Us
44. Q&A pijusn@wix.com https://pijusn.eu
45. Thank You pijusn@wix.com https://pijusn.eu