Live data from Hacker News

Getting a job in software development: A Reddit discussion round-up

reddit.com

1–10 of 50 posts

Re: Getting a job in software development: A Reddit discussion round-up

#2
Most of the questions and answers seem aimed at college seniors planning for Google-style Big O cross examination.

For experienced developers it's a bit simpler: build a portfolio, craft a cashflow-oriented elevator pitch, build a network, and plan ahead for a bit of buzzword compliance in your desired niche as needed.

Re: Getting a job in software development: A Reddit discussion round-up

#3
This seems... really simple. Basic algorithms, data structures, and theory that I learned in second-year comp sci.

Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. Knowing this stuff doesn't mean you can program for shit (see: academic coding horror). Best to build a portfolio as dpritchett said, with a few "lessons I learned from experience when working on this project" anecdotes ready to go.

That's just personal experience though, and I competed in the ICPC during my university career so I never worry about the problem solving questions.

Re: Getting a job in software development: A Reddit discussion round-up

#4
post #3

This seems... really simple. Basic algorithms, data structures, and theory that I learned in second-year comp sci. Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. Knowing this stuff doesn't mean you can program for shit (see: academic coding horror). Best to build a portfolio as dpritchett said, with a few "lessons I learned from experience when working on this project" ane…

[deleted]

Re: Getting a job in software development: A Reddit discussion round-up

#5
post #3

This seems... really simple. Basic algorithms, data structures, and theory that I learned in second-year comp sci. Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. Knowing this stuff doesn't mean you can program for shit (see: academic coding horror). Best to build a portfolio as dpritchett said, with a few "lessons I learned from experience when working on this project" ane…

Tech firms seem to love these kinds of questions all the time. Almost every interview I've had has had them.

Re: Getting a job in software development: A Reddit discussion round-up

#6
post #3

This seems... really simple. Basic algorithms, data structures, and theory that I learned in second-year comp sci. Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. Knowing this stuff doesn't mean you can program for shit (see: academic coding horror). Best to build a portfolio as dpritchett said, with a few "lessons I learned from experience when working on this project" ane…

Knowledge on these subjects is easy to pick up, taking you a few days of study at the most.

I doubt you can pick up a solid understanding of just the first 15 or so chapters of CLRS in a few months, let alone days.

Re: Getting a job in software development: A Reddit discussion round-up

#7
post #5
post #3

This seems... really simple. Basic algorithms, data structures, and theory that I learned in second-year comp sci. Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. Knowing this stuff doesn't mean you can program for shit (see: academic coding horror). Best to build a portfolio as dpritchett said, with a few "lessons I learned from experience when working on this project" ane…

Tech firms seem to love these kinds of questions all the time. Almost every interview I've had has had them.

It's how they get around labor laws.

Re: Getting a job in software development: A Reddit discussion round-up

#8
post #3

This seems... really simple. Basic algorithms, data structures, and theory that I learned in second-year comp sci. Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. Knowing this stuff doesn't mean you can program for shit (see: academic coding horror). Best to build a portfolio as dpritchett said, with a few "lessons I learned from experience when working on this project" ane…

Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. I doubt you can pick up a solid understanding of just the first 15 or so chapters of CLRS in a few months, let alone days.

Coming from a pure math background, I find CLRS to be very easy to read. YMMV based on prior experience, but it's not at all unreasonable to learn the basics in a week or two if you're studying it full-time.

Re: Getting a job in software development: A Reddit discussion round-up

#9
post #3

This seems... really simple. Basic algorithms, data structures, and theory that I learned in second-year comp sci. Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. Knowing this stuff doesn't mean you can program for shit (see: academic coding horror). Best to build a portfolio as dpritchett said, with a few "lessons I learned from experience when working on this project" ane…

Knowledge on these subjects is easy to pick up, taking you a few days of study at the most. I doubt you can pick up a solid understanding of just the first 15 or so chapters of CLRS in a few months, let alone days.

You could learn it well enough to answer interview questions on it. I have my copy of CLRS here and none of the first 15 chapters are exceptionally dense.

Re: Getting a job in software development: A Reddit discussion round-up

#10
post #7
post #5

Earlier quoted context omitted.

Tech firms seem to love these kinds of questions all the time. Almost every interview I've had has had them.

It's how they get around labor laws.

I don't understand; can you elaborate on that?
Post reply on HN