I notice there's no reference to soft skills here.
Is that because:
a) You wanted to keep the post focused and there's already enough content
b) That's not the part of interviews you see people have problems with
c) That's not part of the service you provide
d) <input type="text" placeholder="Enter your own answer" />
I think this is true in 99.9% of cases; however, last year in rare honest feedback from an interview with a large (fortune 100) company I was told that I came across as “too enthusiastic”... which was a bit of a shock since I usually receive the opposite response. So again, it does depend on the interviewers but generally you’re probably better off going with enthusiastic.
Let me just up the pedantry ante one more notch...
It’s “demeanor”, not “demeaner” 😉
Generally speaking, I would tend to agree- however, in terms of interviewing I would say being “enthusiastic”/“passionate” are definitely skills/buzzwords that can check a lot of boxes if you do them the right way. So in that sense, I think they also qualify as skills in this particular arena.
Urban legend, former IMDb editor, conference speaker, Seattle CoderDojo organizer. Love finding inspiration in dev tools and products, then sharing it with dev communities.
Location
Seattle, WA
Education
BA in Creative Writing, self-taught + some certification courses in modern programming languages
I'd say it's because this is the coding interview, not the behavioral interview. :-)
To be fair, I'm a non-traditional coder, left my last SDE role around 7 years ago to write developer docs, and have worked as a developer evangelist or developer documentation writer for most of the past 7 years.
I took the Triplebyte practice interview this weekend to see how well I would do.
I consider myself a good debugger and we were working in a language I knew, but coming into a barely-commented codebase with uncommented failing tests and a time limit, I think that was the hardest part. It was also deep proof of the old adage: "Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live." If I actually inherited code like that, I'd be upset to say the least.
I'll get my results later in the week. I'll be curious to see what kind of feedback I get and whether I passed.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I notice there's no reference to soft skills here.
Is that because:
a) You wanted to keep the post focused and there's already enough content
b) That's not the part of interviews you see people have problems with
c) That's not part of the service you provide
d) <input type="text" placeholder="Enter your own answer" />
Well, I think that "Be enthusiastic" is the most important soft skill advice :)
I think this is true in 99.9% of cases; however, last year in rare honest feedback from an interview with a large (fortune 100) company I was told that I came across as “too enthusiastic”... which was a bit of a shock since I usually receive the opposite response. So again, it does depend on the interviewers but generally you’re probably better off going with enthusiastic.
must...resist...urge...to...make...pedantic...reply...
beingenthusiasticisademeanernotaskill
Let me just up the pedantry ante one more notch...
It’s “demeanor”, not “demeaner” 😉
Generally speaking, I would tend to agree- however, in terms of interviewing I would say being “enthusiastic”/“passionate” are definitely skills/buzzwords that can check a lot of boxes if you do them the right way. So in that sense, I think they also qualify as skills in this particular arena.
I'd say it's because this is the coding interview, not the behavioral interview. :-)
To be fair, I'm a non-traditional coder, left my last SDE role around 7 years ago to write developer docs, and have worked as a developer evangelist or developer documentation writer for most of the past 7 years.
I took the Triplebyte practice interview this weekend to see how well I would do.
I consider myself a good debugger and we were working in a language I knew, but coming into a barely-commented codebase with uncommented failing tests and a time limit, I think that was the hardest part. It was also deep proof of the old adage: "Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live." If I actually inherited code like that, I'd be upset to say the least.
I'll get my results later in the week. I'll be curious to see what kind of feedback I get and whether I passed.