The short stints on a resume is likely not the only reason you didn’t get to 100%, but unfortunately you should know that it’s seen as a pretty bad signal. The general expectation is 2 years minimum at a gig. If you have multiple short non-contract jobs it raises the concern that a candidate doesn’t commit to their jobs, or that they don’t do well at their jobs and are getting let go.
Company A got their funding pulled and shut down. Company B, where I was actually at for about a year and a half, switched owners and shutdown my entire office. Company C merged into it's main competitor and effectively fired most of us.
I will admit I was at one fantastic job and after around 3 years I probably could of stayed indefinitely. But back then I didn't recognize the value of a solid job. If you land somewhere and you're well liked by people, and able to do quality work, you really should just stay there instead of chasing slightly more money.
He wasn't my manager so I brushed over it and 6 months into working at DO they started 3 rounds of enormous layoffs that were handled so poorly even the executives doing the layoffs got removed by the board.
So I left and got to add another short stint at a company run by craven morons to my resume :)
There are plenty of great orgs out there that will soak with you before making assumptions, but as a rule most startups have fairly inexperienced management unless they are founded by a team that’s been through the rodeo a few times.
That said, the general lack of emapthy from recruiting towards time invested and rejections is astonishing and seemingly cruel or emotionally negligent.
US corps are constrained I think by what they can reveal about denial reasons because they don't want to get sued for discrimination.
That said, it can often feel like, you were kept in the pool as an alt/negotiating foil if they didn't get their first pick, or needed to say "we have another candidate willing to take $YOUR_ASK-$BIG_DELTA.
I think we should approach the hiring gauntlet not as "workshop to see what it's like to work with these folks" but as "battle where we can divine the worst about the people we might choose to work with", but still remain sunny and positive while cannily noting any weirdness.
Hope that helps! :)
Sure, but one would think then the rejection email would have specifics around the interview and where the candidate did not perform well. Not nit picking on the job hops. If job hops were a deal breaker then why waste the candidate's time putting them through full rounds of interviews?
i'm sympathetic to you, it sucks, why cant we all be nice to each other, and my answer to that all is lawyers.
A little while later, the same company reached out and encouraged him to apply again. Five rounds later, and he got passed over a second time.
Fast forward two years and they reached out to him a third time. He's basically convinced that because he's black he's their token DEI interview candidate to make them feel better about themselves while internally promoting the people they actually want, but of course they wouldn't actually say that.
Takes time away from the day job and other candidates.
I don't feel disrespected or anything, just feels weird to spend that much time interviewing someone.
---
- The Firefox browser on my Android tablet is close enough to a desktop one that I have no problem reading your blog post. The nag feels unnecessary, especially given it obscures part of the header. For what it’s worth, the tablet’s screen is 1600 real pixels wide @ 260 ppi, and Firefox for Android tells the CSS that the viewport is 800 “pixels” wide—if “pixels” were 1/96", then it would be somewhat below 600 “pixels”, so I don’t know where it’s getting that value from.
(And now I can’t stop thinking if I could make a thing in CSS that would look like a plain-text RFC on a desktop screen but gracefully reflow on a narrower screen.)
- The lightweight-markup parser seems to have gotten confused around the phrases “tests and whiteboarding” and “why I wasn’t a fit”.
- The HN link at the end doesn’t work (404) because you’re adding &ref=blog.webb.page to every external link and HN doesn’t appreciate extra parameters (from my earlier encounters with this kind of thing, neither does e.g. Wikipedia).
Thank you for taking the time to let me know about these bugs, I'll check 'em out!
I made the screen size nag flush with the header. It's set to appear at 800px and below because that's when the design starts breaking. I don't have any Android devices to test what you're seeing unfortunately. A graceful reflow would be ideal! I'm sure it's possible but I don't have the energy to figure that out.
Because of the manual nature of the RFC-style formatting, Markdown doesn't wrap lines so I have to make those checks...I have a lot of posts so some fell through the cracks.
That sounds like it was a terrible place, but it was a good department in a somewhat hard nosed company. He ended up staying there 10 years.
Certainly we have lots of horrible inefficiencies in my team, but stringing along hiring was not one of them. I understand this is not universal even at our company.
The real reason might be “they didn’t like your vibes” or something like that
SCOTUS has found non-protected categories can still be protected because they are "proxies" for protected categories. One of the classic examples of this are zip codes[0], which was found to be a proxy for race, because it has a "disparate impact" on people of particular races.
For some people, the 'wrong vibes' are often proxies for cultural things - all kinds of body language contribute to vibes and it's easy to accidentally (or on purpose...) discriminate against a whole categories based on vibes. If you tell a candidate "Hey we just didn't like your vibes as much as this other guy", it could affect your exposure to claims that you discriminated against them based on their race.
0: https://en.wikipedia.org/wiki/Texas_Department_of_Housing_an....
I realise it may be somewhat beside your point, but that was a Kennedy+liberals vs conservatives ruling in 2015 - so the current SCOTUS would likely have ruled the other way, and decent odds they overrule it sooner or later. Scalia’s dissent was objecting to the entire idea of disparate impact analysis under the Fair Housing Act, so more likely that gets overruled than this specific application of that idea.
This was a statutory interpretation case though, so if SCOTUS overturns the decision, Congress could reverse that with ordinary legislation, no constitutional amendment required. But who knows whether that will turn out to be politically feasible.
https://en.wikipedia.org/wiki/Texas_Department_of_Housing_an...
(Also, you need to change the last period in the URL to %2E to stop HN from mangling it.)
This was probably wrong, both in terms of interpreting the existing law and as a statement of what the law should be. Sometimes bad facts correlate with race; that should not be a reason to deny using the measure for e.g. hiring or lending.
I don't lie to myself, I know why I do this.
https://en.wikipedia.org/wiki/T%C3%A9l%C3%A9coms_Sans_Fronti...
Honestly these "reasons" they give are usually BS excuses when it basically amounts to they don't like your personality or looks.
It's a contractor life for me, I work for money, not "purpose" or anything else.
Hell my Facebook (technically a fully owned subsidiary to be fair) interview loop was easier. I didn't get the job that time either, but at least it was straight up.
In previous HN threads they said something to the effect that they expect their applicants to have read what’s online about their equal base salary. Equity is not equally applied though.
As they say, you can't get blood from a turnip.
Writing this comment reminded me of a personal experience, story time:
Many moons ago I interviewed at a mature startup in silicon valley, they shipped a tiered storage appliance and were in the process of pivoting to a new storage medium (think transitioning from spinning rust to SSDs, something like that).
This was in-person, and everything went swimmingly well, before departing they stated an intention to make an offer and I should expect an email w/offer attached within a week. I got an offer letter, and accepted immediately, as I was super excited about the stack I'd be playing with.
A week before the start date I get a call from a founder, they said I couldn't start because their funding round didn't come through. The economy was going through some sort of financial crisis and it was one of the many blood baths where silicon valley startups shuttered by the hundreds overnight. So in essence, this was a job I got fired from before I could even start, wee!
What followed was a pretty frustrating few months of interviewing and not getting anywhere.
But there is a silver lining to this story, that founder who called me sat on the board of other storage startups. One of them managed to get some water in this funding desert, and its founders reached out to me at his recommendation. I ended up building some great stuff over 4-5 years at that company.
This isn't the worst though, I recently went through an interview with another startup company, and after six interviews and a take-home project I found myself getting the same generic rejection. The CEO went out of his way to tell me he didn't like my resume since I've had to hop around a little bit to stay employed.
Concerns that should have been handled in the initial call, somehow get pushed back till after I've wasted monumental amount of time.
Things are looking up though, I'm starting a job soon and the entire interview process was more or less a 30 minute phone call with the technical manager. That's it, two days later or so I had a verbal offer. I don't need to change the world, I need to pay my rent.