387 karma · joined February 19, 2015
Provide economic stability to enough people in the short-term to reach a critical mass of people that have the privilege to care about the longer-term. Until then, I don't see most areas (e.g. many regions in India) have the bandwidth to trade-off short-term economic gain for long-term health.
To clarify: I agree with your point. I just don't see the current economic climate in many parts of the world allow for shaping local policy that promotes long-term environmental stability.
You can never reach that level returns if a business is sitting at 50k/mo.
cntrl+p: go up one line
cntrl+n: go down one line
cntrl+k: cut line proceeding cursor
cntrl+f: forward one char
cntrl+b: back one char
These work everywhere you can type text on Mac: including in this HN text box, in the url bar, etc. I absolutely love these shortcuts...
Perhaps a combination of creating high quality content hyper targeted towards this audience to help them identify companies to work at, prepare for interviews and how to apply & reaching out to programming student organizations, and CS administrations at these schools to set up workshops, etc. Attending career fairs could also be fruitful (or even better, setting up great virtual career fairs for these schools)
College administrators are incentivized to work with you - the more of their students get placed at companies, the more valuable their program becomes in the eyes of future students. E.g. my college used to heavily market av. starting salary and % students placed at graduation.
> so hiring "undervalued" talent is actually a great way for them to attract and hire talent!
This is interesting. I buy that startups without a recruiting brand want to hire undervalued candidates, but I'm skeptical of their demand to hire undervalued AND entry-level candidates / interns, given their stage where they likely need more execution power with less time spent on mentorship / ramping up. Curious to see how targeting this segment pans out in the long-term, but I'm sure with effective sourcing and screening, you can shift the company segment if need be.
"As a new grad without relevant work experience, or as a career shifter without a relevant degree, getting a first job is very painful" - Absolutely true.
I've spent a good chunk of the past few months mentoring a cousin to help him get his first job in Tech. He studied computer science, has a great GPA, can actually build stuff, but went to a not so well known college in California and didn't have any top tech company internships under his belt.
Very few companies responded to his applications (< 1% positive response) and he really had to hustle his way to get noticed (cold emails, milking his and my personal network for introductions to engineering managers, etc).
Companies like TripleByte seem to have shifted more towards the senior software engineer category, so I see tremendous value in targeting entry-level positions.
Questions: How do you plan to effectively source candidates that are able to pass your assessment? I think an interesting starting point would be to work with graduates of not well-known computer science programs. I think people generally under-estimate the difficulty of getting foot in the door at reputed Tech companies, when you didn't study at a top 10 CS program, and they would probably be the closest group, on average, to passing your technical assessment.
In my conversations with fast-growing companies in the Bay, I got the sense that the demand for senior software engineers far outstrips demand for entry-level / internship positions. Have you noticed the same trend, and as a result are you working mostly with already established larger companies?
Congrats again. Always happy to see more people tackle this problem. We need to create a more accessible, meritocratic pathway to work in Tech.
You're right that CURRENT interview screening practices are far removed from actual work, but that will change. I don't think that it's proof that there aren't better assessments (which should be aligned with how work is actually done on the job). If anything, this is an opportunity to experiment more, and find better assessments.
> I disagree that there are objective measures...
I agree that there aren't fully objective measures, and may never be. What I do believe is that you can get SOME signal of competence from, say, someone's code about their competence at building something right now, which is a more objective, impartial signal than what happens in other industries which relies mostly on a behavioral interview (which allows for a lo t of bias to creep in)
Couldn't algorithms reduce racial bias by focusing on evaluating candidates independent of their race, and other personal attributes?
The current screening process provides a low signal of competence, and so companies have to rely more on credentials (degrees, previous company brands) during screening, which means that a lot of skilled people still can't get their feet in the door at companies if they don’t “look right”, and companies fight over a restricted talent pool.
Lack of hiring data for smaller companies means they copy larger company’s interview processes, but there’s no strong forcing function to drive innovation in larger company’s hiring processes (i.e. their success could be despite a bad interviewing process - because they have a brand and offer a lot of perks, hence attracting the best talent, and so they aren’t in a “we have to fix hiring or we will die” mode).
This also really hurts startups - who aren’t in positions to take risks with hiring, and with a lack of good evaluations, have to rely on credentials, which restricts their pool, and makes them compete with the big cos for that talent.
Another important implication of fixing hiring is that it will introduce a powerful forcing function on higher education institutions. If students know that they can get jobs without having “traditional” credentials, but if they can pass, say TripleByte’s, or some other company’s, assessment which is more aligned with what’s required on the job, and is a signal that companies believe in, then students can use money that they would have spent on college to instead actually learn the skills that would be useful on the job.
This movement of money out of higher education, would fund a lot more experiments in learning and education.
I can’t stress how important I think this problem is to solve, and I’m glad companies like TripleByte, interviewing.io, are working on it. We need more companies, more approaches, more experiments in this space.
> there are means to validate a candidate's competency before they are allowed to interview for a position: licensing, required internships, legal certifications/authorizations, authorized relationships, and so forth.
The problems with credentials that you mention:
1. They are often weak signals of actual competence, and in the case that they are decent, there is still a lot of room for improvement through experimenting via a data driven process (current credentialing is, in many cases, outdated, and doesn't map to what actual work is like).
2. They are not accessible by everyone. This is problematic as the means to learning is becoming more accessible (through online education, etc.), but the credentialing is still restricted - since the institutions that hand them out haven't scaled credentialing. There is a lot of opportunity to provide signal for competence that scales... and measures skill that is actually used on the job (which is also changing as technology matures and penetrates other industries - we'll need a credentialing system that can adjust to those changes quickly).
In fact, I'll go as far as to say that this is a bigger problem in non-software industries. At least in software, there is a more objective way to measure a candidate's competence independent from the path they took to gain that competence. This means that people that might not have necessarily had a formal education / credentialing have a sliver of a chance of an opportunity to prove their skill. In other industries, if you don't have the credentialing, you have no shot.
Back in my 2nd year of college, when I first found HN, I was inspired by many cool projects that were posted here. Within a year, I decide to take the plunge to build an app from scratch. Ended up taking a lot longer than I had thought (didn't realized how complicated a simple looking app could be), so I skipped a semester and continued to work on it with a friend. It was a great learning lesson that gave me the confidence to try and build out ideas when I had them and see what would happen, rather than just sit around hoping someone would build things that I would want to use.
Lastly, I admire the culture here that focuses on creating actual value and doing things rather than chasing status. That has been a huge influence for me - as someone who was very influenced by social pressures and craving for status during high school, and early college (e.g. getting into a top college, getting a job at one of the “top” 5 tech companies), I believe I’ve slowly shifted towards valuing actual work that creates value for others in a meaningful way and caring less about other proxy symbols of “success”. I have a long way to go, but I’m grateful to have been exposed to thoughts and a culture that pointed in this direction, during a time when my mind greatly craved the opposite.
Thank you.
My beliefs that I'm in the process of validating further:
-> Poor resume filtering (based on keywords and proxy credentials) reduces the size of the candidate pool - biased to those that have worked at brand name institution, or went to brand name school, which leaves out many talented folks.
-> Technical interviews are low accuracy predictors of competence, which means you have to up-weight previous experience & credentials to reduce risk of bad hire. If you do choose to open up doors to interview candidates from non-traditional backgrounds, due to the greater variance in competence, you have to spend more time interviewing before you make a hire, driving up the costs.
-> Companies are biased towards cheaper, low-risk interviewing. They want to get the talent to meet the business needs, as long as they can do the job and fit the culture ==> paying more to get the talent that they know has greater chance to deliver is totally worth it.
A bigger company has the advantage of having more data about their hiring process, which could lead to more systematic experimentation to improve hiring. They also have a brand that would attract more people - bigger company often correlates with stability, and market rate pay, which are also drawing factors. They also have less risk --> a bad hire, that can be identified relatively quickly and fired, hurts a bigger company less than smaller ones, and they have more money to throw around.
Hiring at startups is tough: Your low-risk talent pool has other, great from a financial perspective, opportunities. Your higher risk talent pool is expensive to validate competence for because industry standard approaches are low-accuracy signals.
Fix interview process to give a higher signal, which allows you to reduce weight on credentials and experience, which allows you to increase size of candidate pool (because you've reduced the risk and cost to validate).
There's a lot of talent in the world that doesn't fall into the low-risk bucket that everyone is competing for.
I'm trying to think through how to assess team skills well that would also fit into the constraints of an interview.
I agree with this.
I think there are ways to notice this during interviews. I'm a fan of a junior engineer interviewing a candidate for a senior position - as a way to see how well they interact. Perhaps the question could be more open ended (e.g. explain x,y,z concepts - maybe oven ones that the interviewer doesn't know but wants to learn). If the junior feels like they had a good interaction, were able to learn, and felt respected through the process, great. If the candidate seemed offended by the lack of experience of the interviewer, then not great.
A highly subjective signal though.
My concern is that oftentimes, there's a lot of context to absorb before being able to contribute, and a few hours wouldn't be enough. Don't want to extend interviews to multiple days --> biases against candidates that have packed interview schedules.
I'm thinking we could structure a problem to take a few hours, and pair program with them, with the interviewers swapping out every hour and half (which would also help test how well the candidate brings someone who doesn't have context, up to speed).
Or perhaps, have multiple candidates work together to solve a problem, and observe how they work together.
> I chose to look for: Priority Setting, Compassion, and Self Development. Once we have some qualities chosen, we develop questions that are specifically meant to test for those qualities.
What are some questions that you used?
I'm not sure high stress environment test is a good measure. I've worked with some amazing teammates before that might have been nervous if in such a situation.
>Present a few scenarios and ask the candidate what they think a team lead / manager should do in that situation.
I like this approach.
Regarding the question examples you gave, do you look mostly for how they reason through those situations, and their ability to put themselves in their teammates' / managers' shoes, or do you also have a spectrum of [right --> wrong] answers for those questions.
> maybe someone else can verify it
I'm really curious to see if anyone has implemented such a test over and over again.. The biggest challenge right now with changing up the interview process is validating the change is tough. You need to use the same challenge in a lot of interviews, and track how well the candidates did over time at their jobs, if hired, in order to be able to verify. Tough to do for a startup.
> There's a popular belief that recruiters favor candidates with CS degrees from prestigious universities. But it turns out that they actually care about what you've done — not where you went to school
But over 40% employers say that they care about your educational qualification. It doesn't' make sense to say "they actually care about what you've done - not where you went to school" with this result. If you don't have a college degree in CS, you're going to have a significantly tougher time getting your foot in the door, so therefore, even if it's not the MOST important credential you need to get a job, it's unfortunately still very important as a pre-requisite. We still don't have a good signal for that kind of preparation if the candidate doesn't have a lot of publically viewable work.
Would love to join some of these groups. There are a few Whatsapp groups that do these imports as well, but those middlemen slap on a significant fee leaving the creators with not much more than what they would get selling locally. Some of the original creators don't know that their sarees are being sold in the US for much higher.
I've been curious about how a transparent platform would work where the platform handles the burden of shipping and international trade legalities for the creator (which can be a huge headache when selling abroad).
> The higher up the scale you go, the less recognizable the languages might look to an English-speaking monoglot.
Author seems to imply a "distance" between 2 languages that would go both ways.
For practical purposes though, I'd think other factors like the popularity of English/Western media and artifacts of British colonialization would make learning English for non-native English speakers slightly easier, than the other way around, as a result of greater chance of previous English exposure.
Is this a technique that's used often? I'm curious what the cost of such a step would be. How much lag would it cause?