hobls

10 ms·

91.
by hobls 9y ago
I'm not sure what efforts OP is referring to. I'm not aware of any. Either way, OP makes it sound like Amazon doesn't get blamed for all kinds of things (it does) and like people in Seattle don't think Amazon has entitle
92.
by hobls 9y ago
Fine, but the cafes and restaurants aren't owned by Amazon.
93.
by hobls 9y ago
I dunno about "a few minutes." Everett is at least an hour north of Seattle at most times of day. Redmond is also 30-45 minutes outside Seattle; it's very much not part of the city.
94.
by hobls 9y ago
I'm not sure how carefully Amazon has or has not been managing their appearances in Seattle, but I'd bet that Seattlites in general have a WORSE opinion of Amazon than the general average opinion across the USA. I've lived in
95.
by hobls 9y ago
Just giving examples; I have no idea what the actual reason was. My overall point is that you shouldn't take it as an indication for your engineering ability; an instant rejection means that wasn't the thing.
96.
by hobls 9y ago
Sounds like there was some disqualifying factor you're not aware of. (Citizenship, willingness to relocate, whatever.) No one sends out immediate rejection emails to experienced engineers unless they really have to.
97.
by hobls 9y ago
Oh, whoops. I misread that. <insert gif of homer disappearing into a bush>
98.
by hobls 9y ago
> You have no right to be outraged or offended... What. Of course there is a right to be offended and outraged by someone's opinion. It's the same right that allows someone to share a dumb opinion in the first place.
99.
by hobls 9y ago
The problem is that even things like "how many people touch this class" and "how many external teams do we work with" aren't simple at all. Some external teams are much easier to work with than others. Sometimes you
100.
by hobls 9y ago
Yeah, that's part of what I meant. If the path is totally clear; "add API to existing codebase, write tests, do CR, commit" then I don't think you see as much 10x behavior. If it's a new technology that the team isn
101.
by hobls 9y ago
The area that I see this really come into play is with problems that the developer initially doesn't know how to solve. Some developers learn and adapt 10x faster than the average developer, and it seems like they're never blocked
102.
by hobls 10y ago
They don't have to be big monumental conflicts or fuckups or whatever. And yeah, you should totally have a pre-canned answer. It can be something minor; "I once spent a lot of time implementing feature X, and then I realized I cou
103.
by hobls 10y ago
This is a great comment. Totally agree. > didn't acknowledge when they reached the end of their knowledge Oh man, this one. How hard is "I don't know?" You're not supposed to have the entirety of computer scie
104.
by hobls 10y ago
> not being able to answer off this question... Well it certainly shows a lack of preparation and experience. Here's how I approach those questions. I think about each project I've launched, and whether they're relevant.
105.
by hobls 10y ago
Happy to help! At the very least, just prove that you can keep your mouth shut if you think someone is the worst, heh. That's really all I'm looking for. ;) I also totally understand getting frustrated. I've been a total dick
106.
by hobls 10y ago
> It does however still leave the question "but whose fault that legacy code is?" Heh, I can do this all day. "We accumulated a lot of tech debt on a previous project because of very short deadlines." Or, "the
107.
by hobls 10y ago
> what am I to do when I have to share that I maintained a Rails 4.0.x app for 16 months and was unable to upgrade it even it to 4.1.x because the previous team did a horrific job? The reason I personally care about the skill of talkin
108.
by hobls 10y ago
Added some above.
109.
by hobls 10y ago
> "some of my old coworkers were shit and they deserve the shit-talk they get from me This is just such a red-flag in an interview. I have worked with some terrible people, for sure. But I would never talk about them in an interview
110.
by hobls 10y ago
> These are fair enough, although you did say above that the other coworkers in your old scrappy startups were much worse. Nope, I said the engineers I work with now are consistently better. "My current team is very good" is MU
111.
by hobls 10y ago
I think it's a lot! If you had a reasonably decent answer to the whiteboard questions it's often fine if you don't actually get it right. There are a lot of other ways to screw up an interview.
112.
by hobls 10y ago
The tech giant, for sure.
113.
by hobls 10y ago
Some common ones: - Lack of self awareness and introspection. Not being able to give specific examples of times you've made a mistake and how you learned from it. - Shit talking old coworkers, general attitude that you're great an
114.
by hobls 10y ago
It's also worth noting that those students are probably very inexperienced interviewers.
115.
by hobls 10y ago
I've been a programmer for a bit over ten years. I've worked at scrappy little startups, midsized companies, now for a tech giant for a few years. The engineers I work with at the tech giant are consistently better engineers than
116.
by hobls 10y ago
People always talk about the whiteboard interview, and assume it has the greatest weight, but the other questions are just as important. There are plenty of things being measured, and technical ability is often not the one that disqualifies