As an engineer, I love Etsy's culture of curiosity. While industry-standard best practices are of course important and are the standard for good reasons, it never hurts to explore and experiment with alternative approaches. Having experienced Etsy from an inside perspective for over a year now, I can definitely attest to the increased freedom, benefit, and satisfaction from exercising the curiosity culture in my day-to-day work.
As a human and just from the "I want to work so I can live my life" perspective, Etsy's benefits, culture (not necessarily just engineering culture), work-life balance, and many other aspects hit the spot for me. Etsy is definitely a people-oriented company, and while all the initiatives and projects ultimately reflect that people-oriented mindset, it also reflects nicely in the company culture for employees, too.
Purely as an engineer, there's just one relatively minor point. Having started as a small startup back in 2005, there are definitely remnants of a bygone era of "wild west coding" at Etsy.
New code that gets churned out nowadays is honestly fine, but it's not entirely rare to come across a codebase that has a lot of legacy code in it still.
With some of the shakeups in the past half a year (as of November '17), there have also been some re-orgs, and while it was overall positive and a great change in my opinion, naturally there are still some kinks to be worked out.
That said, I want to keep it clear that the above two points are actively being worked on, at least within the teams I interact with. They're just points to keep in mind given recent events.
Honestly, great job. I was honestly skeptical about the company's future half a year ago. Now? I'm so stoked. I'm excited.
This is what I wanted out of this stage of my career, and I'm loving it.
Let's kick some butt and make Etsy even more successful.
I applied online and was invited to a 45-minute technical phone interview. This interview was conducted with a current developer. They asked me questions about past and current projects from my resume and then presented a LeetCode easy/medium questio
The process involved a HackerRank exercise focused on debugging a web application. This was followed by a brief, low-stress phone call with a recruiter. If successful, candidates are invited for an onsite interview and provided with accommodation at
The process began with an initial phone screen with an internal recruiter, followed by a 30-minute video call with an engineering manager. This call included a short programming exercise on HackerRank. Next, a one-hour HackerRank exercise presented
I applied online and was invited to a 45-minute technical phone interview. This interview was conducted with a current developer. They asked me questions about past and current projects from my resume and then presented a LeetCode easy/medium questio
The process involved a HackerRank exercise focused on debugging a web application. This was followed by a brief, low-stress phone call with a recruiter. If successful, candidates are invited for an onsite interview and provided with accommodation at
The process began with an initial phone screen with an internal recruiter, followed by a 30-minute video call with an engineering manager. This call included a short programming exercise on HackerRank. Next, a one-hour HackerRank exercise presented