17 ms·

YC startups that are hiring

146 points by yurisagalov 11y ago

Nelkins 11y ago
Not that it matters that much but I notice there's no .NET or C# on the "Technology Used" list. Is there really not a single YC company that uses the .NET stack? I'm not surprised that there's a strong bias toward open source technologies among these companies, but given how widely .NET used elsewhere in the enterprise world I find it pretty remarkable NONE of those companies decided to go with a MS stack.
- Nelkins 11y ago
  Re: the "strong bias toward open source technologies" bit...yes, I know .NET is open source. This is a recent development. Just thought I'd qualify that before someone else mentions it.
- ammon 11y ago
  We got most of the data (more than half) from the founders of the companies directly. The rest we scraped. I bet there are a few on an MS stack, but it's a small percentage
- jbob2000 11y ago
  .NET is expensive. Developers demand higher salaries, libraries that would otherwise be open source cost big bucks, need a large tool chain to get everything up a running.
- omouse 11y ago
  Licensing fees and tech made for large slow enterprise teams. I've seen the shops that have C# or Java as their backend and they move too slow to be a competitive threat. If their frontend is written in Ruby/Rails or Python/Django then maybe they have a chance against the competition but usually they'll be held back by the slow progress made on the backend. For some reason the big slow enterprise mindset gets transmitted through the choice of language. Companies that use Scala or some other JVM-based language are less likely to be enterprisey for example. Licensing fees and management are a big deal for Microsoft. It all relates to the enterprise vs hacker mentality.
  - vonmoltke 11y ago
    I work at a small company writing NLP R&D software. Our core in-house codebase is entirely Java. There is no "enterprise mindset" here; in fact, many of the engineers make fun of that mindset. Choice of language only affects your culture if you believe choice of language affects your culture and let it happen.
    - rattray 11y ago
      > Choice of language only affects your culture if you believe choice of language affects your culture and let it happen. I would disagree with that. I just came from a startup on .NET. The develop/build/test/deploy cycles were really slow (mostly due to tooling/infra, not the language), which meant devs didn't ship frequently and didn't test their code much. That affected the culture quite a bit: no rapid experimentation means no hacker mentality. It may be that you can develop rapidly with C# or Java (I just wouldn't know, I haven't ever used either in a highly-productive environment) but if they hold you back from shipping quickly, they hold you back from the hacker/startup mentality.
  - jaredhansen 11y ago
    > tech made for large slow enterprise teams. This is complete nonsense. It is popular nonsense, but nonsense nonetheless. .NET is a perfectly reasonable tech stack for certain kinds of problems -- for example if your application has to interact regularly with MSFT core APIs, you'd have to have a pretty compelling reason NOT to use the MSFT-native stack. > It all relates to the enterprise vs hacker mentality This too is a story that HN likes to tell itself to justify its preference for this week's hot new javascript framework (or whatever). At the end of the day, different tools are good for different use cases -- and while yes, .NET tends to work better when you're coding to "enterprisey" use cases, that doesn't mean that your product team itself has to operate in a "large slow enterprise" way (Plug: If you're a top notch .NET developer and you want to work with others who are as well, at a place that doesn't treat C# and .NET as second class citizens, hey, drop me a line.)
    - omouse 11y ago
- biot 11y ago
  And most developers use Stack Overflow (which is built on an MS stack) on a regular basis to find answers to their open source technology questions.
- johnymontana 11y ago
  I know Submittable (YC S12) uses C# and the .NET stack. I'm sure there are others.
- swalsh 11y ago
  I wrote C# for 8 years, but switched to Ruby after following an my boss to a new startup that is using Ruby. I advocated for years about how great .net is (and the tools still are the best), but if i'm being honest here. Ruby really is a lot quicker for prototyping. It's the perfect fit for startups.
  - victor9000 11y ago
    Can you elaborate on the benefits of using ruby for prototyping? What's easier to do in ruby?
    - deleted 11y ago
      [deleted]
    - HOLYCOWBATMAN 11y ago
      Getting runtime errors. But seriously if you want something quicker than c# for prototyping just switch to F#. Ruby has only downsides.
  - bliti 11y ago
    OT: Do give Elixir a try. It's like am erlang with ruby syntax.
- kogir 11y ago
  Back in 2005 when I started Loopt I went all in with Windows Server, .NET, and SQL Server. I already knew the tooling[1]. No regrets. It never held us back - product issues did. Now I'm using it again, for the same reasons. I already know it, I'm pretty quick with it, it's predictable, and it works. I'm also old school and will probably deploy physical servers when the time comes. Look at StackOverflow - their whole site runs on a handful of properly configured servers running properly written code. That said, .NET is not sexy. The tooling is expensive (Pro, Ultimate) or crippled (Express). It runs on Windows, which has fallen out of favor[2]. Even though I like .NET, I'd advise anyone new to learn JavaScript first. In my opinion, Node.js is my nightmare realized, but it works, and it's now possible to make things work in the browser and on the server with knowledge of only one language. More bang for your buck. For startups technology choices are incidental when they're not the core of the business. If you're making a database, your tech choices matter. A consumer app? You're more likely to die of a bad product or team drama[3] than fallout from rendering HTML with bash scripts via CGI. So anyway, you don't see more .NET because it's expensive, it's not the best beginner language, and it doesn't run on OS X. Also, the alternatives are much improved - It's hard to argue for .NET over something else because even where it's better, it's not that much better. And most of the time it doesn't matter. [1] Grew up with access to an MSDN subscription. I knew of and played with Linux, but in the pre-virtualization days, I had to reboot to use it. Understandably, I preferred tools I could use on Windows, my primary OS. Also, while it's no longer the case, the MSDN documentation used to be fantastic. I basically taught myself how to program by reading the MSDN docs and tearing apart the sample code and programs. [2] For the same reasons I developed on Windows as a kid, younger developers will want something they can run on OS X directly, or for free in a VM. [3] Like this: https://news.ycombinator.com/item?id=9840419 https://news.ycombinator.com/item?id=9840419 The number of startups that die due to founder drama is astonishing.
  - joeax 11y ago
    > The tooling is expensive (Pro, Ultimate) or crippled (Express). Visual Studio Community 2013 (and 2015) are completely free and nearly fully featured. Gone are the days of Express being a super lightweight VS IDE. I used to buy Pro for side work but now I can get by with Community.
- joeax 11y ago
  I just checked and Microsoft BizSpark is still around. They give free software to startups and even mentorship. https://www.microsoft.com/bizspark/default.aspx https://www.microsoft.com/bizspark/default.aspx
- thaumaturgy 11y ago
  Microsoft's technology stack doesn't seem to be popular with startups and young technology companies, but I don't think that's because of .net itself, but rather because of the barriers presented by the rest of the Microsoft stack. Probably a major driver is the various virtualization and cloud-driven technologies not fitting real well with Microsoft's server environment. Startups want scalable architectures that allow them to easily adjust to changing demands and Microsoft doesn't really offer that right now -- or, at least, they don't offer that as cost effectively as Linode, Digital Ocean, AWS, RackSpace, and so on. If Microsoft did offer something in that arena, I'd expect the licensing costs to be obnoxious. As a recent example, we've migrated two mid-sized office networks recently to Windows domain environments, and that cost the customers extra money just for CALs -- one CAL per domain-connected device (or user account, depending). That sort of licensing scheme is a rounding error cost of operations for the enterprise, but for startups it's a major nuisance. And then there are databases: should Microsoft-stacked startups go with MS-SQL, which is slow and cumbersome and requires maintenance schedules to be developed for it, or should they go with the other default enterprise choice, Oracle, which is stupidly expensive, or should they try integrating MySQL with Windows and hope nothing breaks in the future? They're also not getting to take advantage of the latest and greatest technologies with the Microsoft stack. NoSQL? nginx? The fastest-iterating web technologies right now aren't happening under Microsoft's roof. I don't mean that Microsoft doesn't offer a lot of advanced technology, I mean that the open source world is able to push an update to GitHub one day and everyone can be running the latest and greatest version a few minutes later, and then it can happen again a few days later. Microsoft isn't doing that, so they're lagging behind some bleeding edge developments. And Microsoft has its own history to overcome. They have burned people a lot over the years. Younger people working in technology are largely ignorant of it, so for them, Microsoft has a pretty OK reputation. But us grey beards remember the Microsoft of the 90s and would sooner exit the industry altogether than be stuck with being responsible for a Microsoft stack for the next 10 years. Just do a search for "Microsoft discontinued technology" or similar, and you get a handful of recent results -- since Google has the long-term memory of a goldfish -- but you can start to get the idea: if you build something with the Microsoft stack today, Microsoft might discontinue support or development for some part of it next year and you might be stuck. With open source technology, you can either choose to continue support or development for it yourself, or continue running it unsupported for as long as you'd like. There are options. Vendor lock-in is harmful in the long term and startups have no leverage for dealing with it and I think many of them are at least subconsciously aware of that. Microsoft has its place. If you want stability -- in a slower rate of change sense -- Microsoft is what you want. If you wan to be able to hire people based on their certifications, Microsoft is what you want. If you have a massive IT budget, Microsoft is a choice you can afford. They just aren't the right fit for most tech startups.
stevesearer 11y ago
I'd love for this sort of thing to have a filter with the type of office employees would be working on. That way everyone on Hacker News can apply for the jobs with the offices best aligned with software development sending a positive signal to those companies and hopefully encouraging better office design overall for those types of jobs.
- rgbrgb 11y ago
  Interesting idea. I kind of doubt office layout is a dominating factor in how most people choose their next job though. This should be especially true if you're trying to choose a rocket ship startup right before it blasts off. Office dynamics, location, and layout will all change (and will be shaped by the employees) as the company scales.
  - stevesearer 11y ago
    Yeah, I agree. I mainly mention it because the way people comment about office designs around here, you'd think it was the only factor considered. But it might also just be cathartic to talk about disdain for open plan offices.
    - nostrademons 11y ago
      I had some coworkers that really couldn't deal with noise or open-plan offices. For them, it's really important that they have a quiet private office. For the majority of my coworkers, they didn't care, and did just fine in an open-plan office. I think it's one of those things where if it's important to you, it's really important to you, but it's not important to all that many people. Which would make it a good sorting filter for a job-matching website. I don't think it'd really send much of a signal to companies regarding the relative merits of each, but it sends a very strong signal to employees who care regarding which companies might be a good fit for them.
      - stevesearer 11y ago
        Good point. I imagine it is a similarly strong signal for employees in the same way Remote Work can be. People who want it seem to only want it and nothing else.
elricL 11y ago
I went through the test couple of weeks back. It was pretty interesting take on the screening part. Wanted to see how the phone screen was, but they seem to be out of slots for a long time.
- ammon 11y ago
  Yeah, we've been very busy. Sorry about this. We're focusing more on learning and less on throughput right now. We'll have more spots opening up next week. Send me an email at ammon@triplebyte.com, and I'll make sure we get you in.
cmottau 11y ago
Logo looks familiar...http://www.cisurfboards.com/ http://www.cisurfboards.com/
- stevesearer 11y ago
  I thought the same thing as so many cars in the Santa Barbara area have those stickers on them.
- slayed0 11y ago
  Somebody better call Al (Merrick)
- grey-area 11y ago
  Looks like a FontAwesome icon.
PieSquared 11y ago
Are all of these companies actually hiring? And hiring through TripleByte?
- quadrature 11y ago
  They don't exactly hire through TripleByte, TripleByte filters candidates and "fast tracks" you through to another interview stage at the company. It's a first line of defense.
brobdingnagian 11y ago
Remember - all TripleByte is doing is reinforcing the bad hiring practices that companies already have.
- w1ntermute 11y ago
  Yep - for all their talk about how traditional interviewing is broken, if you go through their screening process, you'll discover that it devolves into the same old puzzles and algorithms questions you get in any other interview. The result being that a terrible software engineer who had spent some time memorizing the highlights of CLRS would do much better on a TripleByte interview than a good software engineer who hadn't spent his spare time studying material orthogonal to his day-to-day work.
  - Harj 11y ago
    Hey, one of the Triplebyte founders here. We do using coding problems but we try hard to mitigate the issues you bring up. We give candidates a selection of problems to choose from and we'll often explain how to solve a problem if it seems they're getting stuck. We're less interested in sudden flashes of insight and more looking to see if someone can write code and implement ideas they talk about. We know it's still not perfect though and our goal is to keep experimenting to find what works best and be open about the results. As we mentioned in our last blog post, we're planning to offer take home tests as an option for our next experiment.
    - grey-area 11y ago
      I found the tests pretty interesting and thankfully not puzzle-like, though a little like an advanced fizzbuzz as it was a series of unconnected methods. I was really hoping for some feedback at the end as to how I did and what the weak areas were, do you offer any feedback at all? Perhaps as well as take home tests you could consider a longer form one which builds a feature using several methods, offering help if required so most people don't get stuck. Say parsing a set of data files, something like that. When hiring I've found walking through something like real work with candidates most useful, and also crucially using the same challenge for all for comparison.
qq66 11y ago
Reminds me of the puzzling: "If you choose an answer to this question at random, what is the chance you will be correct? A) 25% B) 50% C) 0% D) 25%"
- jacquesm 11y ago
  That's really clever.
- hobbyjogger 11y ago
  Good discussion of this little logic puzzle here: https://math.stackexchange.com/questions/76491/multiple-choice-question-about-the-probability-of-a-random-answer-to-itself-bein https://math.stackexchange.com/questions/76491/multiple-choi...
bra-ket 11y ago
hiring or not, this is a great way to browse YC startups
llebttamton 11y ago
Matterport (YC W12) is hiring in Mountain View, CA. http://matterport.com/jobs/ http://matterport.com/jobs/ (Didn't see them listed.)
PascLeRasc 11y ago
Why limit applications to programmers? I looked through manually and found about a dozen companies each with non-programming technical openings, such as for biologists, physicists, or electrical engineers. The "programmer-only" requirement seems self-imposed by the site, and it would be trivially simple to organize non-programming-centric engineering positions. The same puzzles could be used as a barrier to entry, as the same type of thinking is needed in solving problems in scientific research or hardware engineering. It's very hard to find hardware engineering startup jobs, and this is a space where your site could really stand out.

146 points by yurisagalov 11y ago

Not that it matters that much but I notice there's no .NET or C# on the "Technology Used" list. Is there really not a single YC company that uses the .NET stack? I'm not surprised that there's a strong bias toward open source technologies among these companies, but given how widely .NET used elsewhere in the enterprise world I find it pretty remarkable NONE of those companies decided to go with a MS stack.

Nelkins 11y ago
Re: the "strong bias toward open source technologies" bit...yes, I know .NET is open source. This is a recent development. Just thought I'd qualify that before someone else mentions it.
ammon 11y ago
We got most of the data (more than half) from the founders of the companies directly. The rest we scraped. I bet there are a few on an MS stack, but it's a small percentage
jbob2000 11y ago
.NET is expensive. Developers demand higher salaries, libraries that would otherwise be open source cost big bucks, need a large tool chain to get everything up a running.
omouse 11y ago
Licensing fees and tech made for large slow enterprise teams. I've seen the shops that have C# or Java as their backend and they move too slow to be a competitive threat. If their frontend is written in Ruby/Rails or Python/Django then maybe they have a chance against the competition but usually they'll be held back by the slow progress made on the backend. For some reason the big slow enterprise mindset gets transmitted through the choice of language. Companies that use Scala or some other JVM-based language are less likely to be enterprisey for example. Licensing fees and management are a big deal for Microsoft. It all relates to the enterprise vs hacker mentality.
- vonmoltke 11y ago
  I work at a small company writing NLP R&D software. Our core in-house codebase is entirely Java. There is no "enterprise mindset" here; in fact, many of the engineers make fun of that mindset. Choice of language only affects your culture if you believe choice of language affects your culture and let it happen.
  - rattray 11y ago
    > Choice of language only affects your culture if you believe choice of language affects your culture and let it happen. I would disagree with that. I just came from a startup on .NET. The develop/build/test/deploy cycles were really slow (mostly due to tooling/infra, not the language), which meant devs didn't ship frequently and didn't test their code much. That affected the culture quite a bit: no rapid experimentation means no hacker mentality. It may be that you can develop rapidly with C# or Java (I just wouldn't know, I haven't ever used either in a highly-productive environment) but if they hold you back from shipping quickly, they hold you back from the hacker/startup mentality.
- jaredhansen 11y ago
  > tech made for large slow enterprise teams. This is complete nonsense. It is popular nonsense, but nonsense nonetheless. .NET is a perfectly reasonable tech stack for certain kinds of problems -- for example if your application has to interact regularly with MSFT core APIs, you'd have to have a pretty compelling reason NOT to use the MSFT-native stack. > It all relates to the enterprise vs hacker mentality This too is a story that HN likes to tell itself to justify its preference for this week's hot new javascript framework (or whatever). At the end of the day, different tools are good for different use cases -- and while yes, .NET tends to work better when you're coding to "enterprisey" use cases, that doesn't mean that your product team itself has to operate in a "large slow enterprise" way (Plug: If you're a top notch .NET developer and you want to work with others who are as well, at a place that doesn't treat C# and .NET as second class citizens, hey, drop me a line.)
  - omouse 11y ago
biot 11y ago
And most developers use Stack Overflow (which is built on an MS stack) on a regular basis to find answers to their open source technology questions.
johnymontana 11y ago
I know Submittable (YC S12) uses C# and the .NET stack. I'm sure there are others.
swalsh 11y ago
I wrote C# for 8 years, but switched to Ruby after following an my boss to a new startup that is using Ruby. I advocated for years about how great .net is (and the tools still are the best), but if i'm being honest here. Ruby really is a lot quicker for prototyping. It's the perfect fit for startups.
- victor9000 11y ago
  Can you elaborate on the benefits of using ruby for prototyping? What's easier to do in ruby?
  - deleted 11y ago
    [deleted]
  - HOLYCOWBATMAN 11y ago
    Getting runtime errors. But seriously if you want something quicker than c# for prototyping just switch to F#. Ruby has only downsides.
- bliti 11y ago
  OT: Do give Elixir a try. It's like am erlang with ruby syntax.
kogir 11y ago
Back in 2005 when I started Loopt I went all in with Windows Server, .NET, and SQL Server. I already knew the tooling[1]. No regrets. It never held us back - product issues did. Now I'm using it again, for the same reasons. I already know it, I'm pretty quick with it, it's predictable, and it works. I'm also old school and will probably deploy physical servers when the time comes. Look at StackOverflow - their whole site runs on a handful of properly configured servers running properly written code. That said, .NET is not sexy. The tooling is expensive (Pro, Ultimate) or crippled (Express). It runs on Windows, which has fallen out of favor[2]. Even though I like .NET, I'd advise anyone new to learn JavaScript first. In my opinion, Node.js is my nightmare realized, but it works, and it's now possible to make things work in the browser and on the server with knowledge of only one language. More bang for your buck. For startups technology choices are incidental when they're not the core of the business. If you're making a database, your tech choices matter. A consumer app? You're more likely to die of a bad product or team drama[3] than fallout from rendering HTML with bash scripts via CGI. So anyway, you don't see more .NET because it's expensive, it's not the best beginner language, and it doesn't run on OS X. Also, the alternatives are much improved - It's hard to argue for .NET over something else because even where it's better, it's not that much better. And most of the time it doesn't matter. [1] Grew up with access to an MSDN subscription. I knew of and played with Linux, but in the pre-virtualization days, I had to reboot to use it. Understandably, I preferred tools I could use on Windows, my primary OS. Also, while it's no longer the case, the MSDN documentation used to be fantastic. I basically taught myself how to program by reading the MSDN docs and tearing apart the sample code and programs. [2] For the same reasons I developed on Windows as a kid, younger developers will want something they can run on OS X directly, or for free in a VM. [3] Like this: https://news.ycombinator.com/item?id=9840419 https://news.ycombinator.com/item?id=9840419 The number of startups that die due to founder drama is astonishing.
- joeax 11y ago
  > The tooling is expensive (Pro, Ultimate) or crippled (Express). Visual Studio Community 2013 (and 2015) are completely free and nearly fully featured. Gone are the days of Express being a super lightweight VS IDE. I used to buy Pro for side work but now I can get by with Community.
joeax 11y ago
I just checked and Microsoft BizSpark is still around. They give free software to startups and even mentorship. https://www.microsoft.com/bizspark/default.aspx https://www.microsoft.com/bizspark/default.aspx
thaumaturgy 11y ago
Microsoft's technology stack doesn't seem to be popular with startups and young technology companies, but I don't think that's because of .net itself, but rather because of the barriers presented by the rest of the Microsoft stack. Probably a major driver is the various virtualization and cloud-driven technologies not fitting real well with Microsoft's server environment. Startups want scalable architectures that allow them to easily adjust to changing demands and Microsoft doesn't really offer that right now -- or, at least, they don't offer that as cost effectively as Linode, Digital Ocean, AWS, RackSpace, and so on. If Microsoft did offer something in that arena, I'd expect the licensing costs to be obnoxious. As a recent example, we've migrated two mid-sized office networks recently to Windows domain environments, and that cost the customers extra money just for CALs -- one CAL per domain-connected device (or user account, depending). That sort of licensing scheme is a rounding error cost of operations for the enterprise, but for startups it's a major nuisance. And then there are databases: should Microsoft-stacked startups go with MS-SQL, which is slow and cumbersome and requires maintenance schedules to be developed for it, or should they go with the other default enterprise choice, Oracle, which is stupidly expensive, or should they try integrating MySQL with Windows and hope nothing breaks in the future? They're also not getting to take advantage of the latest and greatest technologies with the Microsoft stack. NoSQL? nginx? The fastest-iterating web technologies right now aren't happening under Microsoft's roof. I don't mean that Microsoft doesn't offer a lot of advanced technology, I mean that the open source world is able to push an update to GitHub one day and everyone can be running the latest and greatest version a few minutes later, and then it can happen again a few days later. Microsoft isn't doing that, so they're lagging behind some bleeding edge developments. And Microsoft has its own history to overcome. They have burned people a lot over the years. Younger people working in technology are largely ignorant of it, so for them, Microsoft has a pretty OK reputation. But us grey beards remember the Microsoft of the 90s and would sooner exit the industry altogether than be stuck with being responsible for a Microsoft stack for the next 10 years. Just do a search for "Microsoft discontinued technology" or similar, and you get a handful of recent results -- since Google has the long-term memory of a goldfish -- but you can start to get the idea: if you build something with the Microsoft stack today, Microsoft might discontinue support or development for some part of it next year and you might be stuck. With open source technology, you can either choose to continue support or development for it yourself, or continue running it unsupported for as long as you'd like. There are options. Vendor lock-in is harmful in the long term and startups have no leverage for dealing with it and I think many of them are at least subconsciously aware of that. Microsoft has its place. If you want stability -- in a slower rate of change sense -- Microsoft is what you want. If you wan to be able to hire people based on their certifications, Microsoft is what you want. If you have a massive IT budget, Microsoft is a choice you can afford. They just aren't the right fit for most tech startups.

stevesearer 11y ago

I'd love for this sort of thing to have a filter with the type of office employees would be working on. That way everyone on Hacker News can apply for the jobs with the offices best aligned with software development sending a positive signal to those companies and hopefully encouraging better office design overall for those types of jobs.

rgbrgb 11y ago
Interesting idea. I kind of doubt office layout is a dominating factor in how most people choose their next job though. This should be especially true if you're trying to choose a rocket ship startup right before it blasts off. Office dynamics, location, and layout will all change (and will be shaped by the employees) as the company scales.
- stevesearer 11y ago
  Yeah, I agree. I mainly mention it because the way people comment about office designs around here, you'd think it was the only factor considered. But it might also just be cathartic to talk about disdain for open plan offices.
  - nostrademons 11y ago
    I had some coworkers that really couldn't deal with noise or open-plan offices. For them, it's really important that they have a quiet private office. For the majority of my coworkers, they didn't care, and did just fine in an open-plan office. I think it's one of those things where if it's important to you, it's really important to you, but it's not important to all that many people. Which would make it a good sorting filter for a job-matching website. I don't think it'd really send much of a signal to companies regarding the relative merits of each, but it sends a very strong signal to employees who care regarding which companies might be a good fit for them.
    - stevesearer 11y ago
      Good point. I imagine it is a similarly strong signal for employees in the same way Remote Work can be. People who want it seem to only want it and nothing else.

elricL 11y ago

I went through the test couple of weeks back. It was pretty interesting take on the screening part. Wanted to see how the phone screen was, but they seem to be out of slots for a long time.

ammon 11y ago
Yeah, we've been very busy. Sorry about this. We're focusing more on learning and less on throughput right now. We'll have more spots opening up next week. Send me an email at ammon@triplebyte.com, and I'll make sure we get you in.

cmottau 11y ago

Logo looks familiar...http://www.cisurfboards.com/ http://www.cisurfboards.com/

stevesearer 11y ago
I thought the same thing as so many cars in the Santa Barbara area have those stickers on them.
slayed0 11y ago
Somebody better call Al (Merrick)
grey-area 11y ago
Looks like a FontAwesome icon.

PieSquared 11y ago

Are all of these companies actually hiring? And hiring through TripleByte?

quadrature 11y ago
They don't exactly hire through TripleByte, TripleByte filters candidates and "fast tracks" you through to another interview stage at the company. It's a first line of defense.

brobdingnagian 11y ago

Remember - all TripleByte is doing is reinforcing the bad hiring practices that companies already have.

w1ntermute 11y ago
Yep - for all their talk about how traditional interviewing is broken, if you go through their screening process, you'll discover that it devolves into the same old puzzles and algorithms questions you get in any other interview. The result being that a terrible software engineer who had spent some time memorizing the highlights of CLRS would do much better on a TripleByte interview than a good software engineer who hadn't spent his spare time studying material orthogonal to his day-to-day work.
- Harj 11y ago
  Hey, one of the Triplebyte founders here. We do using coding problems but we try hard to mitigate the issues you bring up. We give candidates a selection of problems to choose from and we'll often explain how to solve a problem if it seems they're getting stuck. We're less interested in sudden flashes of insight and more looking to see if someone can write code and implement ideas they talk about. We know it's still not perfect though and our goal is to keep experimenting to find what works best and be open about the results. As we mentioned in our last blog post, we're planning to offer take home tests as an option for our next experiment.
  - grey-area 11y ago
    I found the tests pretty interesting and thankfully not puzzle-like, though a little like an advanced fizzbuzz as it was a series of unconnected methods. I was really hoping for some feedback at the end as to how I did and what the weak areas were, do you offer any feedback at all? Perhaps as well as take home tests you could consider a longer form one which builds a feature using several methods, offering help if required so most people don't get stuck. Say parsing a set of data files, something like that. When hiring I've found walking through something like real work with candidates most useful, and also crucially using the same challenge for all for comparison.

qq66 11y ago

Reminds me of the puzzling: "If you choose an answer to this question at random, what is the chance you will be correct? A) 25% B) 50% C) 0% D) 25%"

jacquesm 11y ago
That's really clever.
hobbyjogger 11y ago
Good discussion of this little logic puzzle here: https://math.stackexchange.com/questions/76491/multiple-choice-question-about-the-probability-of-a-random-answer-to-itself-bein https://math.stackexchange.com/questions/76491/multiple-choi...

bra-ket 11y ago

hiring or not, this is a great way to browse YC startups

llebttamton 11y ago

Matterport (YC W12) is hiring in Mountain View, CA. http://matterport.com/jobs/ http://matterport.com/jobs/ (Didn't see them listed.)

PascLeRasc 11y ago

Why limit applications to programmers? I looked through manually and found about a dozen companies each with non-programming technical openings, such as for biologists, physicists, or electrical engineers. The "programmer-only" requirement seems self-imposed by the site, and it would be trivially simple to organize non-programming-centric engineering positions. The same puzzles could be used as a barrier to entry, as the same type of thinking is needed in solving problems in scientific research or hardware engineering. It's very hard to find hardware engineering startup jobs, and this is a space where your site could really stand out.