Asana Engineering Interview Guide
blog.asana.com
Asana Engineering Interview Guide
1–10 of 152 posts
Re: Asana Engineering Interview Guide
#2When does a blog post become a "guide"?
Re: Asana Engineering Interview Guide
#3Much more interesting is the guide that this blog post mentions at https://asana.com/eng/interview-guide.
Re: Asana Engineering Interview Guide
#4Much more interesting is the guide that this blog post mentions at https://asana.com/eng/interview-guide .
Yes! Would be interested in seeing how much coding they ask for when interviewing for devops or ops positions.
Some orgs require only scripting, some go so far as to want application engineers who also know everything about AWS for devops/ops roles.
Disclaimer: I already asked via their google form for this information to be added in their docs.
Re: Asana Engineering Interview Guide
#5Much more interesting is the guide that this blog post mentions at https://asana.com/eng/interview-guide .
Yes! Would be interested in seeing how much coding they ask for when interviewing for devops or ops positions. Some orgs require only scripting, some go so far as to want application engineers who also know everything about AWS for devops/ops roles. Disclaimer: I already asked via their google form for this information to be added in their docs.
I haven't followed the recent updates to our interview process closely but we traditionally looked for general knowledge over specific knowledge. I'm not sure how much that has changed recently though.
Edited In Response To Parent Edit: Thanks for asking! We should definitely make it clearer if there are differences per role.
Re: Asana Engineering Interview Guide
#6Earlier quoted context omitted.
Yes! Would be interested in seeing how much coding they ask for when interviewing for devops or ops positions. Some orgs require only scripting, some go so far as to want application engineers who also know everything about AWS for devops/ops roles. Disclaimer: I already asked via their google form for this information to be added in their docs.
I haven't followed the recent updates to our interview process closely but we traditionally looked for general knowledge over specific knowledge. I'm not sure how much that has changed recently though. Edited In Response To Parent Edit: Thanks for asking! We should definitely make it clearer if there are differences per role.
So very awesome of you. Thank you for the reply!
Re: Asana Engineering Interview Guide
#7Much more interesting is the guide that this blog post mentions at https://asana.com/eng/interview-guide .
I don't really see whats interesting about this either way. Lots of places you interview at tell you what the interview is going to be like and what you are expected to be familiar with. This is just 'write code and we'll be testing you on data structures and algorithms!'
There's some flowery language there about having a genuine desire to want to hire you unlike those 'other evil companies!'... sounds like the same shit pretty much every other company does to me.
Re: Asana Engineering Interview Guide
#8Much more interesting is the guide that this blog post mentions at https://asana.com/eng/interview-guide .
Why is it more interesting? The purpose of the blog post is to explain the rationale for the guide itself and directly links to it. I find it just as interesting to read about why they're doing it.
Re: Asana Engineering Interview Guide
#9Much more interesting is the guide that this blog post mentions at https://asana.com/eng/interview-guide .
I don't really see whats interesting about this either way. Lots of places you interview at tell you what the interview is going to be like and what you are expected to be familiar with. This is just 'write code and we'll be testing you on data structures and algorithms!' There's some flowery language there about having a genuine desire to want to hire you unlike those 'other evil companies!'... sounds like the same…
[deleted]
Re: Asana Engineering Interview Guide
#10> We’ll ask you to solve some coding questions in a language and text editor of your choice. Feel free to bring your own laptop, or we’ll be happy to provide one. Notably, we ask candidates not to compile or run their code during this exercise, and not to refer to online resources.
Every time interviewing comes up, I have this funny feeling about letting people look things up vs. whiteboarding them out. Reading this finally broke something loose:
Coding in interviews should be as hard as the hardest coding you'll do on the job. Heck, anything in the interview should be about how you do things when the job is hard.
Now, this doesn't mean under stress. That may come naturally. But the difference between good and great engineers is decided when the task is hard and information is sparse. Asana is explicitly selecting for people who are going to reason about things from first principles and try to get it right the first time. I admire that they're owning up to that.
They'll pass over people who are exceptionally good at searching / synthesizing information. They'll ding people who focus on tightening the iteration time as a way of learning faster. But that's OK. They've probably built a culture where that kind of person thrives, and they're trying to find more engineers who will thrive at Asana.