Cracking the Coding Interview: 150 Programming Questions and Solutions
As anyone working in tech will tell you, landing a job/internship can be attributed to some combination of past work, interview practice and luck.
Some good resources for interview practice are [https://toptalkedbooks.com/amzn/098478280X) , which is a must have for any technical interview prep.
To find a side project to work on, I would suggest trying to solve a small problem you have in your daily life with software. For example, maybe you want to brush your teeth for longer, or remember to do something everyday. A project like this will allow you to both write actual code, but also talk about your process with deeper understanding to interviewers.
Besides that, there are other great online resources that can help you learn more nuanced aspects of software engineering like https://egghead.io or https://doyen.app.
Don't. Do not under any circumstances say you would work for them over all other choices. There's a few reasons for this.
This isn't necessarily done on purpose, but I've seen it happen first hand too many times to count. It's almost like the "bad-boy" dilemma in dating- the guys who seem farthest away to reach are usually the most in-demand.
Instead, communicate your passion through the knowledge you have about their company. Talk about their things they've done you admire, ask them questions about how the framework they use and why (Do your research, don't say anything obvious!). If there are company github projects, read through them all. Try to get an idea of what they might be working on next and why.
In a phone interview your goal is not to get the job, just to get to the next interview. Give them what they need without sending across any red-flags. Really look closely at the job description and make sure you check each criteria. Have prepared answers for questions like: "Tell me about yourself," "Where do you see yourself in 5 years," etc.
I'd also recommend buying "Cracking the Coding Interview" if you have some time to prepare: [https://toptalkedbooks.com/amzn/098478280X)
It's extremely helpful.
Can't speak for graduate programs, but if you're applying to positions that involve coding, you'll be asked at the very least about your coding experiences, and (if you're applying to a company that actually has decent tech) be asked some technical coding questions - so basically, don't sweat the wording too much because companies will verify your experience in interviews. For applying to software development positions, I highly recommend checking out Cracking the Coding Interview , this book pretty much hits the nail on the head for everything you need to prepare for.
For reference, I was a math major and only took 2 coding courses in college (1 was required for all graduates), but I had been coding in java since 7th grade, and despite learning practically nothing new in college and getting fairly rusty, I was hired at a smallish company and do data science and software dev (currently messing around with neural nets basically just as experimentation). I put down on my resume/cv that I had 10+ years of experience in Java, was fairly proficient in C++ and Python (which was true, I had done some work in those in college and coded up some fairly large projects), and said "had experience with" a few other languages.
It can be demotivating, but don't give up, and take a look at some of your algorithm books. Or cut to the chase:
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.
I can only recommend bootcamps for 2 types of people:
But for the rest, I think you're better served biting the bullet and going back to school for an actual diploma or degree program.
For what a bootcamp provides, I think it's really expensive ($8600-9000 over 2-3 months). Ironically, the appeal of a bootcamp is also the main flaw of a bootcamp: time. For people who have no tech background (which is the main target demographic of bootcamps), you're essentially cramming all these tech concepts, languages and frameworks in 2-3 months. Are you going to retain all of this information 6 months later?
When you graduate from a bootcamp, you're competing with CS graduates, diploma students who had years to hone their skills. Give yourself an honest assessment and ask how you'll do against them?
I highly recommend going through a book called: Cracking the Coding Interview
These are the type of questions that the top companies will ask. Good luck with your pursuit!
Looking at your post and your other replies in this thread, I feel like you simply don't do that well in coding or technical interviews.
Now, I'm IT, not development, but a few people I've met swear by this book:
Buy it or find a PDF and get cracking :)
I strongly recommend Cracking the Coding Interview and The Algorithm Design Manual .