Comment by nogridbag | Hacker News Reader

Comment by nogridbag | Hacker News Reader

Parent Full thread

Since you don't have a background in software, I would suggest specializing in the language/framework/utility of the day - something like Angular, React, etc. You will have a leg up on the vast majority of developers (the ones who don't read HN).

I work for a small startup in the NYC metro area and of course I agree with the parent post. We have a fairly terrible interviewing process. Candidates are phone screened by our non-technical manager and are usually selected for interviews based on domain experience. Nearly all of the people I'm forced to interview have the same background (bachelors in India, sole language is Java, 5-20 years experience in finance industry most coming from big banks Citigroup, BoA, etc). My interview process consists of an onsite coding problem, which is of course controversial. But when none of the people you interview have a github account (some have not even heard of github) or have any sample work, I believe it's important. The vast majority of the candidates sadly cannot create a List and populate it with integers in their language of choice.

thanks a lot for your post. input from active professionals is invaluable to me.

i've actually been working on learning angular for the past few weeks. i've stopped updating my github in that time since i'm just doing basic stuff, but once i finish some more tutorials and documentation i plan on building an angular project to display on my github. are there any particular features that would really catch your eye as someone who hires programmers?

any suggestions regarding the coding interview problem? i see http://www.amazon.com/Cracking-Coding-Interview-Programming-... recommended a lot.

If your algorithmic skills are good enough to ace the problems in that book, you can probably get a job at one of the big three software companies (Google, MS, Amazon). The vast majority of programming jobs are enterprise development work (think endless CRUD apps) that require nowhere near that level of skill.

I wouldn't worry too much about coding interview questions, especially if you're looking to just enter the profession. The most important aspects are showing a willingness to learn and an ability to think critically about problems.

Exactly. My previous comment may have been misleading. I don't think it's imperative to have a github account or a showcase of your work (it definitely would not hurt). I only have one public github project and I'm not exactly proud of it.

I normally start all of my interviews by trying to engage in a conversation about programming topics. But as most of the people I interview have little experience outside of Java and seemingly no interest in programming, the conversations are usually very brief. "I like Java." And the occasional "I have heard of something called JQuery. I may learn that."

Is Java frowned upon nowadays? I'm learning it as my first "real" language, especially for Android & Spring, however I've been playing with Javascript/JQuery and have a web/design background. I've also attempted deploying websites to AWS and CloudBees and failed deploying to Heroku multiple times. In any case, my original question still stands and what would it take for me to get a job with you if I don't have a degree and only the above projects to show you? What would you want to see in those projects and at the interview?

Java itself is not frowned upon - I'm a big Java fan. What is a big red flag, in my opinion, is when someone has multiple years of experience but is only familiar with a single language and has absolutely zero exposure to any other tools or languages. To me it shows that person has no interest in improving his/her craft. It just so happens that in the finance industry, Java is used heavily. Those who list JavaScript on their resume believe it's only purpose is for HTML form validation. I get a bit frustrated when I'm interviewing someone who has used Java exclusively for 15 years and is still making basic syntax errors, like mixing up angle and square brackets. It's not a one time occurrence, I may interview 4-5 people in a row making these same mistakes.

As to your main question, it's difficult to answer. Since we have a very small company with only a few developers, I personally am nervous hiring someone with little experience.

I recommend that book. For an entry level position, focus on the first section about data structures.

What's controversial about having a coding problem? I would assume that I'm going to write code for any position I apply to, otherwise I probably wouldn't want to work at that company. Or do the applicants just feel like you're asking an unreasonably difficult question for the amount of time provided?

In HN the general feel I've gotten for interview problems is that people prefer being given a day or two to accomplish a small coding project instead of being given a coding problem on the spot.

I agree with that approach as well, but it's probably because I consider on the spot coding problems to be nerve-wrecking.

I am looking for a new job these days. Fine if the first job you come across is ideal, and the test is OK. But its going to be frustrating if I have to dig into a lot of my personal time doing coding tests, because I want to apply for a few jobs and see what one is best.

I would rather code with the interviewer, and let him know my thought processes, and why I do things the way I do.

Reply on news.ycombinator.com