Ask HN: Advice for a newly grad, avoiding an intellectual rut.

I'm a CS graduate with 10 years in the field.<p>I've worked at 3 different companies and, compared to college coursework and projects, not a single one of these jobs has been intellectually stimulating for me. In fact, my first task at my first job was to document Java code created by foreign contractors. Most of the code was get/set functions for member variables. Nevertheless, there have been projects that I relished, but they have been few and far between.<p>Most of the work you do in college is individual work. It's completely the opposite in the working world. You have to work on a team of people, and your focus is building a product, not learning new things. This is not to say that you won't learn, but that aspect comes in a distant second to creating a working piece of software, on a schedule, that meets a business need.<p>My advice on keeping your intellectual needs met: do your brainy stuff outside of work. Work is not your muse; it's not your professor. Work pays the bills so you can live how you want outside of work.<p>At two jobs I was actually singled out and mocked for doing "advanced" things that had immediate positive effects on the business. Superiors and coworkers can feel threatened by a brainiac. Politicking isn't limited to the Beltway. These companies weren't exactly tech giants, but you'd probably find this situation is possible at any company. So being street smart is also a requirement. Don't showboat unnecessarily.<p>If you find a company that interests you, use your alumni association to find people who work there. Get in touch with them and ask them questions about what they do, what they like about the company, and what they don't like. Do some networking and research the work environment before you send a resume. It's very difficult to gauge a company from a job interview since it's a stressful situation and you're focused on presenting yourself as the ideal candidate.<p>Also consider jobs that aren't primarily tech-oriented, but permit you to use technology to do your job better. At a former company there was a sales guy who knew programming fairly well and he used it to streamline his processes. He was able to handle more clients more efficiently and he got promoted quickly. If there's something non-technical that you absolutely love, then taking a related job and applying tech to it might lead to interesting results.<p>As for start-ups vs. small companies vs. giants. It all depends on what you're comfortable with. Start-ups are risky but the atmosphere is generally pretty fun and they are often more open to using new technology and unorthodox methods. As companies get larger, the bureaucracy sets in and things become more about following a process than finding something that works. I'd recommend joining a start-up to any CS graduate, but do it before you settle down in life.

<i>"there seem to be a lot of crap jobs out there, lots of people looking for experts in Java or .NET."</i><p>Choice of language has little to do with whether or not the job will be intellectually challenging or whether the company will provide opportunities for you to grow your skills. There are a lot crap jobs in Java and .NET because there a just a lot of jobs in those languages in general. So unless you are keen on using a specific language I would try to be as language/tool agnostic as possible. As to how you detect whether a job will foster your intellectual growth, try asking some questions along those lines in your interviews. For example:<p>"How far do you feel you have come in terms of your skills compared to when you first started working here?"<p>"What was the most challenging thing you have gotten to work on here?"<p>As far as trying to convince employers that you can pick up whatever they are using, my experience has been that employers asking for X years of experience in Y are not likely to be convinced and the likely-hood of changing their minds is probably proportional to the number of years they are asking for. So look for employers emphasizing fundamental skills over particular technologies because they already get it and it won't really be a question.

&#62;<i>"Maybe I'm being too harsh on myself, but its hard to be proud of my work when every 30 minutes I have to lookup an example or reference of some part of an API, and then modify it for my purposes"</i><p>The time to invent something new is when it will take ten weeks to complete your project using existing technology or five weeks using new technology and it will take two weeks to develop the new technology.*<p>The wheel has already been invented, so there's no point in building your own hexagonal version - focus instead on what is important: shipping.<p>* Credit to Neil Stephenson

IMHO if you can work with a startup that is using technology you find interesting, that would be the best thing - you'd get a lot more breadth of experience and you'd have more of a chance to play with newer stuff. If you do join a big company, like you mentioned, make sure it isn't one of those Java shops where you wouldn't learn anything. I think that's a perfectly legitimate thing to ask in an interview - what kind of technology you would have the opportunity to work with.

<a href="http://card.io" rel="nofollow">http://card.io</a>, which seems like a <i>really</i> cool company, is hiring: <a href="https://gist.github.com/821454/" rel="nofollow">https://gist.github.com/821454/</a>. I'm guessing the Java and C skills would be useful considering that 1) they're building SDKs for Android and 2) they're doing heavy duty image processing.<p>Good luck!

You bring it to the job, not the other way around.

Consider grad school. I didn't regret it :)