nhaliday + judgement + working-stiff   4

How to pass a programming interview - Triplebyte
Mostly intuitive (eg, I had also planned to interview in reverse order and use Python but mention C++ experience), but still very good advice. Summoning/faking enthusiasm will prob be hardest part for me.
programming  career  jobs  tech  recruiting  advice  checklists  working-stiff  interview-prep  system-design  minimum-viable  pls  jvm  python  c(pp)  practice  education  signaling  judgement  prioritizing  list  top-n  metabuch  objektbuch  🖥 
march 2016 by nhaliday
Who Y Combinator Companies Want — Triplebyte Blog — Medium
1. There’s more demand for product-focused programmers than there is for programmers focused on hard technical problems. The “Product Programmer” and “Technical Programmer” profiles are identical, except one is motivated by product design, and the other by solving hard programming problems. There is almost twice as much demand for the product programmer among our companies. And the “Academic Programmer” (hard-problem focused, but without the experience) has half again the demand. This is consistent with what we’ve seen introducing engineers to companies. Two large YC companies (both with machine learning teams) have told us that they consider interest in ML a negative signal [ed.: :(]. It’s noteworthy that this is almost entirely at odds with the motivations that programmers express to us. We see ten times more engineers interested in Machine Learning and AI than we see interested in user testing or UX [ed.: duh].
2. (Almost) everyone dislikes enterprise programmers. We don’t agree with this. We’ve seen a bunch of great Java programmers. But it’s what our data shows. The Enterprise Java profile is surpassed in dislikes only by the Academic Programmer. This is in spite of the fact we explicitly say the Enterprise Programmer is smart and good at their job. In our candidate interview data, this carries over to language choice. Programmers who used Java or C# (when interviewing with us) go on to pass interviews with companies at half the rate of programmers who use Ruby or JavaScript. (The C# pass rate is actually much lower than the Java pass rate, but the C# numbers are not yet significant by themselves.) Tangential facts: programmers who use Vim with us pass interviews with companies at a higher rate than programmers who use Emacs, and programmers on Windows pass at a lower rate than programmers on OS X or Linux.
3. Experience matters massively. Notice that the Rusty Experienced Programmer beats both of the junior programmer profiles, in spite of stronger positive language in the junior profiles. It makes sense that there’s more demand for experienced programmers, but the scale of the difference surprised me. One prominent YC company just does not hire recent college grads. And those that do set a higher bar. Among our first group of applicants, experienced people passed company interviews at a rate 8 times higher than junior people. We’ve since improved that, I’ll note. But experience continues to trump most other factors. Recent college grads who have completed at least one internship pass interviews with companies at twice the rate of college grads who have not done internships (if you’re in university now, definitely do an internship). Experience at a particular set of respected companies carries the most weight. Engineers who have worked at Google, Apple, Facebook, Amazon or Microsoft pass interviews at a 30% higher rate than candidates who have not.

startups  career  planning  jobs  sv  yc  recruiting  long-term  data  analysis  tactics  🖥  success  empirical  working-stiff  transitions  progression  tech  top-n  values  multi  libraries  software  engineering  interview-prep  judgement  signaling 
december 2015 by nhaliday

bundles : disciplinegrowthstarstechie

related tags

advice  analysis  best-practices  business  c(pp)  career  checking  checklists  class  class-warfare  commentary  context  coordination  correctness  culture  dan-luu  data  decision-making  devops  education  elite  emotion  empirical  engineering  error  essay  facebook  google  healthcare  info-dynamics  institutions  interview-prep  jobs  judgement  jvm  labor  libraries  list  lol  long-term  management  media  medicine  meta:science  metabuch  minimum-viable  multi  nitty-gritty  objektbuch  open-closed  org:nat  organizing  outcome-risk  persuasion  phalanges  philosophy  planning  pls  practice  pragmatic  prioritizing  programming  progression  psychology  python  rant  recruiting  risk  science  scitariat  security  signal-noise  signaling  slippery-slope  social  social-psych  software  startups  stories  study  success  sv  system-design  tactics  tech  techtariat  things  thinking  top-n  transitions  trust  twitter  uncertainty  unintended-consequences  values  water  working-stiff  wtf  yc  🖥 

Copy this bookmark: