ammon

14 ms·

91.
by ammon 8y ago
The conversations involved me asking them to talk through the details of their interview process and decision-making. I think there were good incentives for companies be honest (given the context of us matching engineers with them). I did
92.
by ammon 8y ago
This is the core way we look at it. Our models are hopelessly simplistic, and have no chance of modeling the true complexity of human ability. It's important to stay humble and recognize this. However, what we're competing against
93.
Alphazero’s real secret sauce is MCTS(medium.com)
2 points by ammon 8y ago|0 comments
94.
by ammon 9y ago
I'm one of the co-founders at Triplbyte. What this means is that our statistical model now significantly outperforms our own interviewers (and me) at performing a structured interview, and then making a judgment about whether a candida
95.
by ammon 9y ago
This makes me think of Voyager 1's pale blue dot photograph. https://upload.wikimedia.org/wikipedia/commons/7/73/Pale_Blu... I find the parallel awesome.
96.
by ammon 9y ago
Yeah, we do more than let people skip phone screens (although don't undervalue skipping phone screens and take-home projects at 8+ companies). Companies really do look for different things in interviews. Not all companies look for CS t
97.
by ammon 9y ago
We (Triplebyte) don't ask engineers where they've worked until the end of the final interview. It's the last thing we ask (after all the technical evaluation and scoring is done). We regularly find and pass great programmers
98.
by ammon 9y ago
Yeah, Piet's a curveball! It's a pretty cool (esoteric, totally useless) language however.
99.
by ammon 9y ago
Yup, it's not a test for hiring
100.
by ammon 9y ago
We (Triplebyte) actually tested a while ago whether identifying languages was predictive as an interview question (we thought it might predict general experience / exposure to lots of code). It was not predictive of anything. So this q
101.
by ammon 9y ago
So, we've gathered data on exactly these points over the last 2 years. And what we've found that the decision that gets the best signal is often not what feels most accurate to the interviewer. For example, my guess before running
102.
by ammon 9y ago
That's an interesting idea! The hard part would be convincing companies to trust an external trial week fully (part of what's great about a trial week is the chance to actually see how an engineer will interact with your team &#x2
103.
by ammon 9y ago
Totally. Both things happen.
104.
by ammon 9y ago
An interesting point my co-worker made is that, almost by definition, if an interviewee does not know how to answer a question, they don't know why that question is important or where that type of problem is applied. So from the point
105.
by ammon 9y ago
I like that idea for the question!
106.
by ammon 9y ago
Using pseudocode is a great idea. We've talked about that. We've not done it because we still need to decide what style of syntax to use (and that will still preference certain programmers). But maybe we should think about it agai
107.
by ammon 9y ago
The intent was that node.children would be the giveaway. The question is about BFS, and you'll notice that only one of the answers references the node's children (in a sensible way). The intent was that that would be enough to ans
108.
by ammon 9y ago
I am actually curious to know of cases of insecure string comparison vulnerabilities being exploited. I think there are real cases. But I tried recently to to this against a toy server over my local network, and could not get it to work
109.
by ammon 9y ago
The goal of this quiz is to be a little challenging and fun and maybe educational. It's not to judge whether someone can do a software engineering job! The answers to the graph problems are indeed fairly straight forward. But asking ab
110.
by ammon 9y ago
This quiz is just supposed to be fun :) We opted for speed over security, on the idea that anyone who cared enough to pull out the answers deserves a 100!
111.
by ammon 9y ago
Timing attacks like this still work over a network, you just have to make an LOT of duplicate requests, and average the times. The lucky thirteen attack ( https://en.wikipedia.org/wiki/Lucky_Thirteen_attack ) is a real e
112.
by ammon 9y ago
Well, objects in Java are only accessible via references. So the result is behavior identical to Python and JS (primitives are passed by value, objects are passed by reference)
113.
by ammon 9y ago
:-) Yup. This is just for fun
114.
by ammon 9y ago
For what it's worth, we run our interviews in the language of the engineer's choosing (including clojure), and get people jobs at Clojure and Haskel and C++ companies. We went with Python for this (toy) quiz because it's the
115.
by ammon 9y ago
If you understand the graph traversal algorithms in question, there's nothing to memorize. You can just think through the problems. Is it important to understand graph traversal algos? I don't think it is for everyone. But a lot o
116.
by ammon 9y ago
If people like this, we'll be creating more version (in different languages, and drilling into different areas)
117.
by ammon 9y ago
Hello Ezekg, I am sorry that our process makes you feel bad :( The simple truth is that there are a lot of different ways to be a skilled programmer. One ways is being really good at CS (and to people who want skills in CS, talking about DF
118.
by ammon 9y ago
Either way. It's just supposed to be fun / interesting
119.
by ammon 9y ago
Yup, we see that issue too. But in that case, I think it's python specific (how python handles default values). Ruby, for example, does not have that behavior.
120.
by ammon 9y ago
Unfortunately probably not :( I would love to, but the jobs are just not there. H1Bs are just too hard to get. What I do hope to do is expand out of the US, and get around the issue that way.

More ›