I'm stuck in QA Hell in the Midwest. I started applying a few places in Seattle to be closer to the family. I just got the first ping back.
What's the standard for references in Seattle tech? I have four - three from a previous position and one at my current. (We have 0 support, and I'm one of two engineers.)
Should I expect something like the "Seattle No" if they're not interested? At this point, I'm assuming "we're proceeding with other candidates" as the default.
>>1371883
Polite bump. I'm a stranger in a strange land here.
>>1371883
Bumping, because /g/ was helpful, but this may be a broader question. Does anyone have experience in recruitment in Seattle?
I used to work there and have friends who work at Google and Facebook there. It depends on your experience and where you're applying.
>>1372088
I worked at a major .com, but it's become all clickbait. I have two years' experience in QA automation testing including Appium and Selenium (meaning mobile and desktop).
More than anything, I want something closer to full automation or maybe junior web dev. I wrote a few internal tools and the bulk of my experience in college was geared for web development anyway.
I don't have "the magics," but I can and will put in the time. I've even started applying at Amazon knowing full well what their workload is like.
I'm just not familiar with what's typical in the area. Two interviews and an in-person? A group interview?
