4 ms·
I would focus more on the complexity of each project in your portfolio rather than the quantity. If you have been maintaining a single app for a while, especial
by throwntoday 5y ago
I would focus more on the complexity of each project in your portfolio rather than the quantity. If you have been maintaining a single app for a while, especially one used by others, it looks better than a dozen weekend projects IMO. Ideally projects should be related to the position you are applying for, but having a variety of things can demonstrate an ability to adapt.
As far as interviewing, since you are self taught I would make sure your CS fundamentals are solid as a lot of companies are using leetcode/hackerrank problems as a filter. Dynamic programming, data structures, time/space complexity, algorithms. If you grind enough problems you should have a good understanding of these things but it's important to be able to explain them too, at least in an interview.
You can join any number of CS dev communities and you'll hear the same thing. Getting your first job at least is a massive grind, just keep applying non-stop, don't get discouraged. And DONT burn yourself out in a single day by applying for 100 jobs thinking it will help. Best of luck to you.
- jobhdez 5y agoThanks. Is a linear algebra system complex? I’ve written some systems that compute linear algebra operations.
- ShamelessC 5y ago> I would make sure your CS fundamentals are solid as a lot of companies are using leetcode/hackerrank problems as a filter. Is this a thing in silicon valley or something? I've never seen this done in practice and would hate it if I had to do this in an interview. Mostly because it doesn't seem like it tells you how good of a programmer someone is, but how much they cared to study for your job interview (how desperate) they are. I have to say, I mostly disagree with the notion that CS skills are deeply important for a first job. That isn't to say that they aren't important more broadly, but I actually had a very wrong idea about programming due to my comp sci major. My first job (internship) I had to learn some tough lessons about pair programming, code review, clean code, messy code, _overly_ clean code, unit testing, etc. Almost none of my computer science skills were useful. That didn't come until about 8 years later in my career.