Tips, thoughts [as a hiring manager]:<p>1. Build a professional CV. The current one (CV_Late2022.pdf), with a black background, bright colored links, no useful information, it's off-putting and looks amateurish. I found your "real" one (CV_Mid2022_Frozen.pdf), not sure why it's an additional click away. Take the "frozen" one, and turn it into a good-looking professional one. Just put something like "2022-present Career break" at the end.<p>2. You probably should do lots of practice interviews [in english]. Get feedback on how you're doing. If you want to get a job, this is probably the highest leverage activity (other than fixing the CV), _not_ messing around with functional programming and Blender.<p>3. Pick some open source projects and try to contribute. If/once you're successful, put it on your CV.<p>Less important:<p>4. Make a showcase site that looks good. The website as-is looks like something on Geocities from the 90s, amateurish like the CV. Only show things that tell a good story. Also know that the showcase site is not that important, eg. recruiters don't look at it, hiring managers _maybe_ will see it.<p>5. You always mention the ACM membership, but it doesn't mean anything. It's just a membership, not a qualification/accomplishment.<p>6. Consider not having a big picture of yourself everywhere. Are you trying to get hired based on your looks, or your competence?<p>-<p>Note on asthetics, since some people mention it in comments:<p>A. I personally strongly believe that asthetics matter, because asthetics are a big part of Engineering in general, Software Engineering in particular.<p>B. If the person can't follow some sort of reasonable cultural style guide in your 1-page CV, will they follow coding style guides at work?<p>C. Eg. if somebody doesn't bother to align paragraphs, leaves commas hanging, uses inconsistent spacing, has typos, etc, ON THEIR 1-PAGE CV, THE MOST IMPORTANT DOCUMENT FOR GETTING A JOB, then.. Will they indent their code? Will they follow style guidelines? Will they use good names without typos for variables and functions and classes? Will they write good comments and commit messages?<p>D. Having reviewed 1000s of CVs and done 100s of interviews, the above correlations exist. And picking CVs and interviews are about looking for signals.<p>-<p>Obviously I'm just one hiring manager in about a pool of a million (or more), my opinion is not universal, no reason to get too worked up about it!