Category: pondering
-
Another great way to think about boosting team engineering productivity. -
Sharing a link https://www.darpa.mil/work-with-us/heilmeier-catechism
DARPA operates on the principle that generating big rewards requires taking big risks. But how does the Agency determine what risks are worth taking?
George H. Heilmeier, a former DARPA director (1975-1977), crafted a set of questions known as the “Heilmeier Catechism” to help Agency officials think through and evaluate proposed research programs.
What are you trying to do? Articulate your objectives using absolutely no jargon.
How is it done today, and what are the limits of current practice?
What is new in your approach and why do you think it will be successful?
Who cares? If you are successful, what difference will it make?
What are the risks?
How much will it cost?
How long will it take?
What are the mid-term and final “exams” to check for success? -
In a response to this LinkedIn post.
Sometimes I think people in tech companies treat interviewing like a hazing ritual because they went through the same process, they think the next set of new hires also needs to jump through the same hoops.
For junior engineering positions, each open position gets 200+ resumes, and they mostly look the same (classes, internships, projects), the coding challenges become a way to stand out.
Actually, I think companies can find talent, it just takes the current employees a lot of time (around 30 hours recruiting person-hours to land one employee) given the hiring funnel.
Some back-of-the-envelope calculations based on my hiring experience in big tech.
50-100 resumes per open role, 10% resumes are suitable for a recruiter call, 50% make it to the hiring manager phone screen, 50% make it to the first 2 rounds of coding challenge, and 1 in 4 during the final rounds get an offer, 1 in 2 will accept. You get around a 0.3% percent chance of working in one of these big tech companies.
-
