[seaknoll]

Practice algorithms and read about software design in your spare time. Apply to tons of companies, be prepared to be rejected from almost all of them, and to be asked questions that you have no intelligent answer to. Remember what they asked you, learn the problems you got wrong, and repeat. It may be brutal and embarrassing at times but if you keep at it you will eventually get a job. The only thing I can say about maintaining any sense of morale is to take some pride in the fact that you’re pushing yourself, and that tons of people have had the same shitty interviewing experience but gotten through it and realized it was 1000% worth the pain.

[bad_interivewee]

the leetcode/algo question stuff is mentioned here on HN alot but I've never gotten to the point where a test was actually offered to me. will start practicing though and hopefully an opportunity pops up.

[smus]

If you're not getting calls, it's your resume that is bad. That either means the format, or the content. Seems to me the only change to the content that you can make is working on and advertising well written open source personal projects that your interviewers can see, or contributing to large open source projects.

[seaknoll]

In that case, you might want to have a friend/acquaintance with a job like what you want to review your resume and give you feedback on that and a first round-style interview. If you don’t know anyone who can, read over resumes on linkedin, and pay close attention to the language used, and to the extent that it’s relevant to your work try to mirror it. Try to be direct and confident about what you know/don’t know during the interview, and try to at least learn how to talk about technologies that touch what you’re more expert in.