I can't imagine that Steam requires that much work. The bulk of the work would probably be dealing with customer service issues, I imagine.

Valve almost never releases games so it makes me wonder what any of their employees do to fill their days. Other gaming companies (that make less money) release massive open-world games basically every other year. Rockstar doesn't release many games but the ones they do release are so complex, massive, and popular that you know they spent their time well.

I'm definitely not saying that I want Steam to become like Activision or anything, I'm just curious what the hell it's like to actually work there. If there's no real hierarchy of leadership, how do you measure performance? How can you know if someone is worth their salary? How do you tell a good employee from a bad employee?

I would honestly pay money to shadow a Valve employee for one week just to know even if I had to sign a ton of NDA's.

Just asking.

Two comments to a post on Hacker News:

I worked at Valve a few years back, and I could write a book about what's wrong there. I think the biggest problem they have -- which the author of this article touched on -- is that "success is the worst teacher." Valve have discovered that cosmetic microtransactions are big money makers, and thus every team at Valve was dedicated to that vision. When I was there (before Artifact started in open development) there were essentially no new games being developed at all. There was a small group that were working on Left for Dead 3 (cancelled shortly after I joined), and a couple guys poking around with pre-production experiments for Half-Life 3 (it will never be released). But effectively all the attention was focused on cosmetic items and "the economy" of the three big games (DOTA, CS:GO, and TF2). One very senior employee even said that Valve would never make another single player game, because they weren't worth the effort. "Portal 2," he explained, had only made $200 million in profit and that kind of chump change just wasn't worth it, when you could make 100s of millions a year selling digital hats and paintjobs for guns (most of which are designed by players, not the employees!)

In theory, employees are allowed to (supposed to, even) work on whatever they think is valuable. In reality, you should be working on whatever the people around you think is valuable or you're gonna get fired really quickly. (Fewer than half of new employees make it to the end of their first year.) This usually means doing whatever the most senior people on the team think is important, both because they should know if they've been there for a while, but also because they wield enormous power behind the scenes.

The problem with a company with no defined job titles or explicit seniority is that there is still seniority, but it is invisible and thus deniable. An example: in my first few months, I was struggling to find a good project and a very senior employee (one of the partners, actually) took me aside and recommended I leave my current team since my heart was clearly not in it and take some time to think about what I really wanted to do, or else I'd get let go. I took his advice seriously, came up with a couple ideas, and then approached him a week or so later to pitch these projects. He got _angry_ at me, stressing that he's not my boss, and that it showed a remarkable lack of initiative that I'd ask someone else at the company what I should work on. So: he has the authority to fire me (or at least to plausibly threaten to fire me) but the moment that authority would mean any responsibility or even the slightest effort to mentor someone, he's just another regular Joe with no special role at all. Similarly, there's no way to get meaningful feedback because nobody really knows who's going to be making the performance evaluations. Sure, you can take advice from someone who's been there for ten years, but if they're not included in the group that's assembled to evaluate you then their guidance is worth nothing.

I worked with some very smart people there, but it was the most dysfunctional and broken work environment I've ever witnessed.

They had 181 people working on all oft their games. Remember when you hate on cs2 its probably like 20 people trying to keep the ship floating.

Hi, I am 17 years old and now I am studying in college (Czech Republic), I am interested in 3D modeling, sculpting and creating models for game characters. Not so long ago I realized that I would like to work in what interests me and not what my parents impose on me. As one of the best options I found Valve but there are a couple things I would like to know about.

1. If I live in the Czech Republic and the office of Valve is in Seattle, if I submit my resume on their website, can I be accepted and will I have to fly to Seattle? (I am morally prepared to have to move in the future if I am accepted)

2. Since there are no big game companies in the Czech Republic (there is Warhorse but they don't need a 3D artist), I can't get work experience in creating characters and 3D models for games. So far I'm practicing just making models when I get home. I try to do a steady 2-3 models a week to build up my hand for the future.

P.S Maybe in time I will have more questions so I will write them below but these were the main ones.

Upd.1 This post was made with the idea that I will be sending my resume to Valve in 4-5 years, not right now

valve as far as we know is small compared to most other tripple A companies being only having around 350 at least thats what were told

and i gotta ask

why?

they run the biggest online game store on the planet

one of the most popular FPS games with csgo

and its obvious they cant manage everything

hell the csgo 2 update (i refuse to call it a sequel cause i hate updates labeled as such) was rushed and removed half the content from the game pressumably because they didnt have the manpower to match the ambition

their other popular fps tf 2 was a bot ridden cheater infested nightmare for 5 YEEEEAAARS and its only recently after 2 seperate community lead protests have they FINALLY started to act

and lets not get started on their joke of a anti cheat VAC is so unbelievebly dogshit that most community servers who have their own 3rd party personal anti cheats are lightyears better maintained then offical valve servers

so i gotta ask why doesnt valve hire more people when they so very clearly cant seem to manage their shit with the people they currently have? its not like they cant most devs would kill to work for valve and theyre one of the most profitable companies on the planet generating billions upon billions in revenue every year

I've studied how Valve works internally a lot because of how different and open the company was and I've thought about potentially working there far in the future when I'm in my late 20s because by god if I'm not interested in a project getting myself to work on it is like trying to find a bot-less TF2 lobby pre 2024

I've heard how the company internally functions has changed and that is what now allows Valve to finally start making games again (ex: Deadlock) but I can't find a singular thing on the matter.

If you're not allowed to explain how it has changed, I'd like to ask how the new structure feels compared to the old one; whenever that freedom of "make whatever you want" and that internal employee idea battle-royale is still there or not.

Now, I'm not 100% certain if I will work at valve or not, but I thought of hearing other peoples thoughts about work environment. Is it a good productive healthy environment, or crunchy, overshift time bad ones?

And other questions like...

How many work hours in a week? How much payment you get for a year? Is there a hierarchy? How is the policy affecting employees? What do employees think about valve, is it in a good way or bad way? And others questions I have in mind

What so you guys think about working at valve?

I'm not looking into working at Valve or any tech-based job, but as someone who enjoys Steam games as well as the Steam Deck, I became curious as to what it's like behind the scenes. Are the employees treated decently or poorly? Or is it a gray area?

The flat structure with no bosses of Valve is widely known, but I'm wondering how far it stretches and how many employees Valve actually has?

I assume, that there is some kind of accounting department or legal department that follows the traditional business system instead of the flat structure. Or does Valve outsource that stuff?

What other stuff do they outsource (support I assume), art? programming?

Preface

In 1996, we set out to make great games, but we knew back then that we had to first create a place that was designed to foster that greatness. A place where incredibly talented individuals are empowered to put their best work into the hands of millions of people, with very little in their way. This book is an abbreviated encapsulation of our guiding principles. As Valve continues to grow, we hope that these principles will serve each new person joining our ranks. If you are new to Valve, welcome. Although the goals in this book are important, it’s really your ideas, talent, and energy that will keep Valve shining in the years ahead. Thanks for being here. Let’s make great things.

How to Use This Guide

This guide isn't about fringe benefits or how to set up your workstation or where to find source code. Valve works in ways that might seem counterintuitive at first. This guide is about the choices you're going to be making and how to think about them. Mainly, it's about how not to freak out now that you're here.

For more nuts-and-bolts information, there's an official Valve intranet (http://intranet). Look for stuff there like how to build a Steam depot or whether eyeglasses are covered by your Flex Spending plan.

This book is on the intranet, so you can edit it. Once you've read it, help us make it better for other new people. Suggest new sections, or change the existing ones. Add to the Glossary. Or if you're not all that comfortable editing it, annotate it: make comments and suggestions. We'll collectively review the changes and fold them into future revisions.

Part 1 - Welcome to Valve

Your First Day

So you've gone through the interview process, you've signed the contracts, and you're finally here at Valve. Congratulations, and welcome.

Valve has an incredibly unique way of doing things that will make this the greatest professional experience of your life, but it can take some getting used to. This guide was written by people who've been where you are now, and who want to make your first few months here as easy as possible.

Valve Facts That Matter

Valve is self-funded. We haven't ever brought in outside financing. Since our earliest days this has been incredibly important in providing freedom to shape the company and its business practices.

Valve owns its intellectual property. This is far from the norm, in our industry or at most entertainment content-producing companies. We didn't always own it all. But thanks to some legal wrangling with our first publisher after Half-Life shipped, we now do. This has freed us to make our own decisions about our products.

Valve is more than a game company. We started our existence as a pretty traditional game company. And we're still one, but with a hugely expanded focus. Which is great, because we get to make better games as a result, and we've also been able to diversify. We're an entertainment company. A software company. A platform company. But mostly, a company full of passionate people who love the products we create.

Welcome to Flatland

Hierarchy is great for maintaining predictability and repeatability. It simplifies planning and makes it easier to control a large group of people from the top down, which is why military organizations rely on it so heavily.

But when you're an entertainment company that's spent the last decade going out of its way to recruit the most intelligent, innovative, talented people on Earth, telling them to sit at a desk and do what they're told obliterates 99 percent of their value. We want innovators, and that means maintaining an environment where they'll flourish.

That's why Valve is flat. It's our shorthand way of saying that we don't have any management, and nobody "reports to" anybody else. We do have a founder/president, but even he isn't your manager. This company is yours to steer—toward opportunities and away from risks. You have the power to green-light projects. You have the power to ship products.

A flat structure removes every organizational barrier between your work and the customer enjoying that work. Every company will tell you that “the customer is boss,” but here that statement has weight. There’s no red tape stopping you from figuring out for yourself what our customers want, and then giving it to them.

If you’re thinking to yourself, “Wow, that sounds like a lot of responsibility,” you’re right. And that’s why hiring is the single most important thing you will ever do at Valve (see “Hiring,” in Part 5). Any time you interview a potential hire, you need to ask yourself not only if they’re talented or collaborative but also if they’re capable of literally running this company, because they will be.

Why does your desk have wheels? Think of those wheels as a symbolic reminder that you should always be considering where you could move yourself to be more valuable. But also think of those wheels as literal wheels, because that's what they are, and you'll be able to actually move your desk with them.

You'll notice people moving frequently; often whole teams will move their desks to be closer to each other. There is no organizational structure keeping you from being in close proximity to the people who you'd help or be helped by most.

The fact that everyone is always moving around within the company makes people hard to find. That's why we have http://user — check it out. We know where you are based on where your machine is plugged in, so use this site to see a map of where everyone is right now.

Part 2 - Settling in

Your First Month

So you've decided where you put your desk. You know where the coffee machine is. ^{in the kitchen} You're even pretty sure you know what that one guy's name is. You're not freaking out anymore. In fact, you're ready to show up to work this morning, sharpen those pencils, turn on your computer, and then what?

This next section walks you through figuring out what to work on. You'll learn about how projects work, how cabals work, and how products get out the door at Valve.

What to work on

Why do I need to pick my own projects?

We've heard that other companies have people allocate a percentage of their time to self-directed projects. At Valve, that percentage is 100.

Since Valve is flat, people don't join projects because they're told to. Instead, you'll decide what to work on after asking yourself the right questions (more on that later). Employees vote on projects with their feet (or desk wheels). Strong projects are ones in which people can see demonstrated value; they staff up easily. This means there are any number of internal recruiting efforts constantly under way.

If you're working here, that means you're good at your job. People are going to want you to work with them on their projects, and they'll try hard to get you to do so. But the decision is going to be up to you. (In fact, at times you're going to wish for the luxury of having just one person telling you what they think you should do, rather than hundreds.)

But how do I decide which things to work on?

Deciding what to work on can be the hardest part of your job at Valve. This is because, as you've found out by now, you were not hired to fill a specific job description. You were hired to constantly be looking around for the most valuable work you could be doing. At the end of a project, you may end up well outside what you thought was your core area of expertise.

There's no rule book for choosing a project or task at Valve. But it's useful to answer questions like these:

• Of all the projects currently under way, what's the most valuable thing I can be working on?

• Which projects will have the highest direct impact on our customers? How much will the work I ship benefit them?

• Is Valve not doing something that it should be doing?

• What's interesting? What's rewarding? What leverages my individual strengths the most?

How do I find out what projects are under way?

There are lists of stuff, like current projects, but by far the best way to find out is to ask people. Anyone, really. When you do, you'll find out what's going on around the company and your peers will also find out about you. Lots of people at Valve want and need to know what you care about, what you're good at, what you're worried about, what you've got experience with, and so on. And the way to get the word out is to start telling people all of those things. So, while you're getting the lay of the land by learning about projects, you're also broadcasting your own status to a relevant group of people.

Got an idea for how Valve could change how we internally broadcast project/company status? Great. Do it. In the meantime, the chair next to anyone's desk is always open, so plant yourself in it often.

Short-term vs. long-term goals

Because we are all responsible for prioritizing our own work, and because we are conscientious and anxious to be valuable, as individuals we tend to gravitate toward projects that have a high, measurable, and predictable return for the company. So when there's a clear opportunity on the table to succeed at a near-term business goal with a clear return, we all want to take it. And, when we're faced with a problem or a threat, and it's one with a clear cost, it's hard not to address it immediately.

This sounds like a good thing, and it often is, but it has some downsides that are worth keeping in mind. Specifically, if we're not careful, these traits can cause us to race back and forth between short-term opportunities and threats, being responsive rather than proactive.

So our lack of a traditional structure comes with an important responsibility. It's up to all of us to spend effort focusing on what we think the long-term goals of the company should be.

Someone told me to (or not to) work on X. And they've been here a long time!

Well, the correct response to this is to keep thinking about whether or not your colleagues are right. Broaden the conversation. Hold on to your goals if you're convinced they're correct. Check your assumptions. Pull more people in. Listen. Don't believe that anyone holds authority over the decisions you're trying to make. They don't; but they probably have valuable experience to draw from, or information/data that you don't have, or insight that's new. When considering the outcome, don't believe that anyone but you is the "stakeholder". You're it. And Valve's customers are who you're serving. Do what's right for them.

There are lots of stories about how Gabe has made important decisions by himself, e.g., hiring the whole Portal 1 team on the spot after only half of a meeting. Although there are examples, like that one, where this kind of decision making has been successful, it's not the norm for Valve. If it were, we'd be only as smart as Gabe or management types, and they'd make our important decisions for us. Gabe is the first to say that he can't be right nearly often enough for us to operate that way. His decisions and requests are subject to just as much scrutiny and skepticism as anyone else's. (So if he tells you to put a favorite custom knife design into Counter-Strike, you can just say no.)

Whatever group you're in, whether you're building Steam servers, translating support articles, or making the ten-thousandth hat for Team Fortress 2, this applies to you. It's crucial that you believe it, so we'll repeat it a few more times in this book.

What about all the things that I'm not getting done?

It's natural in this kind of environment to constantly feel like you're failing because for every one task you decide to work on, there will be dozens that aren't getting your attention. Trust us, this is normal. Nobody expects you to devote time to every opportunity that comes your way. Instead, we want you to learn how to choose the most important work to do.

How does Valve decide what to work on?

The same way we make other decisions: by waiting for someone to decide that it's the right thing to do, and then letting them recruit other people to work on it with them. We believe in each other to make these decisions, and this faith has proven to be well-founded over and over again.

But rather than simply trusting each other to just be smart, we also constantly test our own decisions. Whenever we move into unknown territory, our findings defy our own predictions far more often than we'd like to admit. We've found it vitally important to, whenever possible, not operate by using assumptions, unproven theories, or folk wisdom.

This kind of testing takes place across our business, from game development to hiring, to selling games on Steam. Luckily, Steam is a fantastic platform for business learning. IT exists to be an entertainment/service platform for our customers, and as such it also is a conduit for constant communication between us and them.

Accepted truisms about sales, marketing, regionality, seasonality, the Internet, purchasing behavior, game design, economics, and recruiting, etc., have proven wrong surprisingly often. So we have learned that when we take nearly any action, it's best to do so in a way that we can measure, predict outcomes, and analyze results.

Recruiting can be a difficult process to instrument and measure. Although we have always tried to be highly rational about how we hire people, we've found much room for improvement in our approach over the years. We have made significant strides toward bringing more predictability, measurement, and analysis to recruiting. A process that many assume must be treated only as a "soft" art because it has to do with humans, personalities, language, and nuance, actually has ample room for a healthy dose of science. We're not turning the whole thing over to robots just yet though (*see “Hiring,” in Part 5).

Can I be included the next time Valve is deciding X?

Yes. There's no secret decision-making cabal. No matter what project, you're already invited. All you have to do is either (1) Start working on it, or (2) Star talking to all the people who you think might be working on it already and find out how to best be valuable. You will be welcomed—there is no approval process or red tape involved. Quite the opposite—it’s your job to insert yourself wherever you think you should be.

Teams, Hours, and the Office

Cabals

Cabals are really just multidisciplinary project teams. We’ve self-organized into these largely temporary groups since the early days of Valve. They exist to get a product or large feature shipped. Like any other group or effort at the company, they form organically. People decide to join the group based on their own belief that the group’s work is important enough for them to work on.

For reference, read the article on cabals by Ken Birdwell. It describes where cabals came from and what they meant to us early on.

Team leads

Often, someone will emerge as the “lead” for a project. This person’s role is not a traditional managerial one. Most often, they’re primarily a clearinghouse of information. They’re keeping the whole project in their head at once so that people can use them as a resource to check decisions against. The leads serve the team, while acting as centers for the teams.

Structure happens

Project teams often have an internal structure that forms temporarily to suit the group’s needs. Although people at Valve don’t have fixed job descriptions or limitations on the scope of their responsibility, they can and often do have clarity around the definition of their “job” on any given day. They, along with their peers, effectively create a job description that fits the group’s goals. That description changes as requirements change, but the temporary structure provides a shared understanding of what to expect from each other. If someone moves to a different group or a team shifts its priorities, each person can take on a completely different role according to the new requirements.

Valve is not averse to all organizational structure—it crops up in many forms all the time, temporarily. But problems show up when hierarchy or codified divisions of labor either haven’t been created by the group’s members or when those structures persist for long periods of time. We believe those structures inevitably begin to serve their own needs rather than those of Valve’s customers. The hierarchy will begin to reinforce its own structure by hiring people who fit its shape, adding people to fill subordinate support roles. Its members are also incented to engage in rent-seeking behaviors that take advantage of the power structure rather than focusing on simply delivering value to customers.

Hours

While people occasionally choose to push themselves to work some extra hours at times when something big is going out the door, for the most part working overtime for extended periods indicates a fundamental failure in planning or communication. If this happens at Valve, it’s a sign that something needs to be reevaluated and corrected. If you’re looking around wondering why people aren’t in “crunch mode,” the answer’s pretty simple. The thing we work hardest at is hiring good people, so we want them to stick around and have a good balance between work and family and the rest of the important stuff in life.

If you find yourself working long hours, or just generally feel like that balance is out of whack, be sure to raise the issue with whomever you feel would help. Dina loves to force people to take vacations, so you can make her your first stop.

The office

Sometimes things around the office can seem a little too good to be true. If you find yourself walking down the hall one morning with a bowl of fresh fruit and Stumptown-roasted espresso, dropping off your laundry to be washed, and heading into one of the massage rooms, don’t freak out. All these things are here for you to actually use. And don’t worry that somebody’s going to judge you for taking advantage of it—relax! And if you stop on the way back from your massage to play darts or work out in the Valve gym or whatever, it’s not a sign that this place is going to come crumbling down like some 1999-era dot-com startup. If we ever institute caviar-catered lunches, though, then maybe something’s wrong. Definitely panic if there’s caviar.

Risks

What if I screw up?

Nobody has ever been fired at Valve for making a mistake. It wouldn’t make sense for us to operate that way. Providing the freedom to fail is an important trait of the company—we couldn’t expect so much of individuals if we also penalized people for errors. Even expensive mistakes, or ones which result in a very public failure, are genuinely looked at as opportunities to learn. We can always repair the mistake or make up for it.

Screwing up is a great way to find out that your assumptions were wrong or that your model of the world was a little bit off. As long as you update your model and move forward with a better picture, you’re doing it right. Look for ways to test your beliefs. Never be afraid to run an experiment or to collect more data.

It helps to make predictions and anticipate nasty outcomes. Ask yourself “what would I expect to see if I’m right?” Ask yourself “what would I expect to see if I’m wrong?” Then ask yourself “what do I see?” If something totally unexpected happens, try to figure out why.

There are still some bad ways to fail. Repeating the same mistake over and over is one. Not listening to customers or peers before or after a failure is another. Never ignore the evidence; particularly when it says you’re wrong.

But what if we ALL screw up?

So if every employee is autonomously making his or her own decisions, how is that not chaos? How does Valve make sure that the company is heading in the right direction? When everyone is sharing the steering wheel, it seems natural to fear that one of us is going to veer Valve’s car off the road.

Over time, we have learned that our collective ability to meet challenges, take advantage of opportunity, and respond to threats is far greater when the responsibility for doing so is distributed as widely as possible. Namely, to every individual at the company.

We are all stewards of our long-term relationship with our customers. They watch us, sometimes very publicly, make mistakes. Sometimes they get angry with us. But because we always have their best interests at heart, there’s faith that we’re going to make things better, and that if we’ve screwed up today, it wasn’t because we were trying to take advantage of anyone.

Part 4 - Choose Your Own Adventure

Your First Six Months

You've solved the nuts-and-bolts issues. Now you're moving beyond wanting to just be productive day to day—you’re ready to help shape your future, and Valve’s. Your own professional development and Valve’s growth are both now under your control. Here are some thoughts on steering both toward success.

Roles

By now it’s obvious that roles at Valve are fluid. Traditionally at Valve, nobody has an actual title. This is by design, to remove organizational constraints. Instead we have things we call ourselves, for convenience. In particular, people who interact with others outside the company call themselves by various titles because doing so makes it easier to get their jobs done.

Inside the company, though, we all take on the role that suits the work in front of us. Everyone is a designer. Everyone can question each other’s work. Anyone can recruit someone onto his or her project. Everyone has to function as a “strategist,” which really means figuring out how to do what’s right for our customers. We all engage in analysis, measurement, predictions, evaluations.

One outward expression of these ideals is the list of credits that we put in our games—it’s simply a long list of names, sorted alphabetically. That’s it. This was intentional when we shipped Half-Life, and we’re proud to continue the tradition today.

Advancement vs. growth

Because Valve doesn’t have a traditional hierarchical structure, it can be confusing to figure out how Valve fits into your career plans. “Before Valve, I was an assistant technical second animation director in Hollywood. I had planned to be a director in five years. How am I supposed to keep moving forward here?”

Working at Valve provides an opportunity for extremely efficient and, in many cases, very accelerated, career growth. In particular, it provides an opportunity to broaden one’s skill set well outside of the narrow constraints that careers can have at most other companies.

So the “growth ladder” is tailored to you. It operates exactly as fast as you can manage to grow. You’re in charge of your track, and you can elicit help with it anytime from those around you. FYI, we usually don’t do any formalized employee “development” (course work, mentor assignment), because for senior people it’s mostly not effective. We believe that high-performance people are generally self-improving.

Most people who fit well at Valve will be better positioned after their time spent here than they could have been if they’d spent their time pretty much anywhere else.

Putting more tools in your toolbox

The most successful people at Valve are both (1) highly skilled at a broad set of things and (2) world-class experts within a more narrow discipline. (See “T-shaped” people) Because of the talent diversity here at Valve, it’s often easier to become stronger at things that aren’t your core skill set.

Engineers: code is only the beginning

If you were hired as a software engineer, you’re now surrounded by a multidisciplinary group of experts in all kinds of fields—creative, legal, financial, even psychological. Many of these people are probably sitting in the same room as you every day, so the opportunities for learning are huge. Take advantage of this fact whenever possible: the more you can learn about the mechanics, vocabulary, and analysis within other disciplines, the more valuable you become.

Non-Engineers: program or be programmed

Valve’s core competency is making software. Obviously, different disciplines are part of making our products, but we’re still an engineering-centric company. That’s because the core of the software-building process is engineering. As in, writing code. If your expertise is not in writing code, then every bit of energy you put into understanding the code-writing part of making software is to your (and Valve’s) benefit. You don’t need to become an engineer, and there’s nothing that says an engineer is more valuable than you. But broadening your awareness in a highly technical direction is never a bad thing. It’ll either increase the quality or quantity of bits you can put “into boxes,” which means affecting customers more, which means you’re valuable.

Part 6 - Epilogue

What Is Valve Not Good At?

The design of the company has some downsides. We usually think they’re worth the cost, but it’s worth noting that there are a number of things we wish we were better at:

• Helping new people find their way. We wrote this book to help, but as we said above, a book can only go so far.

• Mentoring people. Not just helping new people figure things out, but proactively helping people to grow in areas where they need help is something we’re organizationally not great at. Peer reviews help, but they can only go so far.

• Disseminating information internally.

• Finding and hiring people in completely new disciplines (e.g., economists! industrial designers!).

• Making predictions longer than a few months out.

• We miss out on hiring talented people who prefer to work within a more traditional structure. Again, this comes with the territory and isn’t something we should change, but it’s worth recognizing as a self-imposed limitation.

What Happens When All This Stuff Doesn’t Work?

Sometimes, the philosophy and methods outlined in this book don’t match perfectly with how things are going day to day. But we’re confident that even when problems persist for a while, Valve roots them out.

As you see it, are there areas of the company in which the ideals in this book are realized more fully than others? What should we do about that? Are those differences a good thing? What would you change? This handbook describes the goals we believe in. If you find yourself in a group or project that you feel isn’t meeting these goals, be an agent of change. Help bring the group around. Talk about these goals with the team and/or others.

Where Will You Take Us?

Valve will be a different company a few years from now because you are going to change it for the better. We can’t wait to see where you take us. The products, features, and experiences that you decide to create for customers are the things that will define us.

Whether it’s a new game, a feature in Steam, a way to save customers money, a painting that teaches us what’s beautiful, something that protects us from legal threats, a new typeface, an idea for how to be healthier while we work, a new hat-making tool for TF2, a spectacular animation, a new kind of test that lets us be smarter, a game controller that can tell whether you’re scared or a toy that makes four-year-olds laugh, or (more likely) something nobody’s thought of yet—we can’t wait to see what kind of future you choose to build at Valve.

His twitter is: https://twitter.com/richgel999

He didn't use a thread, so scroll down to his first tweet on July 14th to read them.

Seems like hell on earth to me and also seems corroborated by all of the glassdoor reviews I've seen.

If I recall, Portal was originally a game made by some students (Narbacular Drop). Valve liked it, so they hired those students. I think Alien Swarm had something similar. And you hear about various modders and such becoming employees.

But nowadays Valve is huge, more than ever before. Can you still do this sort of thing? Like if you make a cool game, would that really help you get a job at Valve in the way it did with the Portal students, or would even that not help you stand out much?

Asking because I had this scheme about maybe making a game, and if it blows up I could use it as a portfolio to get in with Valve. But there's so much competition now, and plenty of people have made a successful game. So maybe even having pumped out a successful product wouldn't matter.