Ask HN: What companies have private offices for programmers?
I've read and heard from lots of programmers who want them, but I've only ever heard of about two software companies that offer them.
careers.stackoverflow.com has "Joel Test" scores for some entries, but companies seem pretty loose with the "quiet working conditions" criterion. One of them claims a point for that, but then brags about their "open layout" office.
I'm not looking for yet another debate over the pros/cons of offices/cubes/open layout, nor a list of earplug/headphone/desk indicators as mitigation.
62 comments
[ 4.1 ms ] story [ 153 ms ] threadEDIT: By the way, I like them, but I write this from a plastic folding table in a warehouse in Brisbane CA (AKA Drone Valley)
http://www.geekwire.com/2014/microsoft-developer-division/
Since then, no particular bit of insanity from Microsoft would surprise us....
You are right to not want open-layout. Peopleware presents a study that music can interfere with creativity.
One other thing I'm seeing is Huddle rooms. They are smaller, ad-hoc offices. Teams can request them to work together on something. My sense is that they are for a short period of time, measured in days to weeks.
I've already filled the whole place with geeky stuff and technical papers/articles/specs/docs/books though.
is that rare? We expect any [programming] intern will be learning some part of the code base and making their first tiny improvements in the first week. Most of the interns have been quite productive by the end of their term... and I'm happy to say that our first intern-to-full-time-employee will be starting in a month or so.
My point is, anyone making over 80k/$40 an hour making their own flight arrangements, filling out their own expense reports, is a waste of valuable time. If I have a guy billing out $200/hr - he's in the office 8 or 9 hours a day max - (most people start and end work the same time everyday) - I don't want him wasting time on that crap. Needs an AA to do it. (Note our expense system sucks and our requirements are exact - you can easily spend an hour on an expense report)..
I'm at Motive right now; the large majority of developers here have their own office. (And we're hiring: developers and testers, no telecom experience necessary, mostly in Austin, TX.)
It's in London, and it's here: http://www.huckletree.com/
We chose this after finding that in our existing coworking space, that the company that moved in to the other side of our desk cluster spent the majority of their time on the phone and were loud about it.
I think the nature of office space is one of the problems with this. Most commercial office space seems to be set up in the open office/cube farm setup. If you wanted private offices, you'd have to pay to construct them yourself, and then wonder if it will cause trouble if you ever leave the space when whoever takes it next doesn't want it. It's much tougher to get private offices until you're big enough to be actually constructing your own buildings, or at least willing to spend money on a pricey build-out of existing office space.
There are exceptions. The previous startup I worked for (in SOMA) used conference rooms as two-developer private offices in our first building and gave all developers two-person private offices in the second one. I don't think the offices were chosen for the purpose of having private offices either (specifically I think the second office was chosen by the company that had just acquired us.)
https://circleci.com/jobs - see also http://blog.circleci.com/silence-is-for-the-weak/
What percentage of your codebase is in Clojure? What have your experiences with it been? (I've really enjoyed using Clojure thus far.)
Do you expect to have a need for a machine learning engineer in the next 0-24 months?
We have tended towards hiring generalists (both in the sense of what they can work on, and what they _want_ to work on). I don't know when that will change, but I don't expect to have a pure-ML position soon.
"we've noticed that the following correlate with the type of people that we want to work with. This is not an exhaustive list, nor a list of requirements (in fact, some of them are contradictory), but more of a rough guideline."
"senior, experienced developers, who have worked on a decent number of products, have a propensity for shipping often, probably with 8-10 years of experience and amazing coding chops (those having left coding behind them—this isn't the company for you, unfortunately)"
So those are two profiles that have worked well for us in the past, but they aren't requirements by any stretch.
We're aware that this is kinda confusing, and also that it's not very friendly to a lot of people we're trying to hire, so we'll be updating pretty soon.