by calebjosue on 5/3/24, 3:02 AM with 92 comments
I have had all sort of experiences in my job search:
Sometimes I pass the interviews but companies goes with other candidates. I have failed some interviews too (Unable to solve the problem on the given amount of minutes by the interviewer). I have taken two take-home projects, ghosted. In my last interview after elaborating about my experience they told me: We have just been told the vacancy is no more. Also, I have been noticing that Spring have become synonym of Java (Most of the time when I apply for a Java Developer job they ask about Spring), I can grasp it on the job.
I need to refresh some Algorithms knowledge, I have devoted sometime learning Scala for example, and a little bit of Haskell.
I firmly believe I can help with something in a Software oriented company, even data wrangling or any other task nobody else likes to do.
Here's my website: https://calebjosue.gigalixirapp.com (Take a look at the lifelong learning section)
I am located in Mexico, so I am willing to do remote. And... (Please don't hate me for this [I know this put pressure on other country's citizens]) I don't charge that much.
P.S. I can't help thinking one of my biggest mistakes have been being too idealistic. Or neglecting reality, e.g. I have devoted these two past days entirely to Blender in order to produce a little sorta short-film. But any step I was thinking I shall study some Algorithms. But I really wanted to finish this Blender project, once down, I hardly will spend more than half an hour to it (Exception on the weekends of course).
Be the visionaries Steve Jobs have in mind when he said he was looking for a long-term relationship: _We will build great things on the next decade_ (IIRC)
I accept I've failed on focusing in a simple thing to build deep knowledge of a given computer science area. If you allow me to play the victim card: I am in need to buy some medicines for my skin condition. (Yes, I know you are not a charity but believe, I truly believe I can help you with something).
by kristopolous on 5/3/24, 5:47 AM
I know that's stupid but it's also real.
Use something simple like linktree and go way deeper on your blogposts if you want to use that. When I'm in a hiring manager role, I'm looking for works that express depth and competency.
Really, if I can find say, 100 or so lines of competently written code, I'm interested. As far as what that means, take https://js1k.com/ and click on any of them and go to the demo details. I just picked a random one: https://js1k.com/2019-x/details/4167 ... I see that code and I think "well this person seems to know what they're doing, it's worth a phone call".
Or let's take https://allrgb.com/ ... any one of them take pretty decent understanding and coding to do (here's a random one: https://allrgb.com/random-triangles) Make one, do a writeup on it, release the code and present that.
Another tactic: Any large software project. Let's take Libreoffice. Bugs from the last 7 days: https://bugs.documentfoundation.org/buglist.cgi?chfield=%5BB... ... or the 1000 open tickets on wireshark: https://gitlab.com/wireshark/wireshark/-/issues start fixing them. There's plenty of work to do.
If your work is good, the jobs will actually come to you. Most companies are desperate for good, motivated, easy to work with engineers.
by com2kid on 5/3/24, 5:02 AM
If you are applying for a senior Java role in a Spring shop, they'll be expecting you to already know Spring. The easiest way is to write some projects in Spring!
That is it, right there. If you can show off a nice professional website written in Spring (try to find a designer buddy who is also out of work and needs a portfolio piece!), and a link to the GH repo for the same site, you'll possibly skip a large portion of the interview process, or at least be put in the front of the line.
by jacob_rezi on 5/3/24, 5:43 AM
by Maro on 5/3/24, 6:15 AM
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.
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.
3. Pick some open source projects and try to contribute. If/once you're successful, put it on your CV.
Less important:
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.
5. You always mention the ACM membership, but it doesn't mean anything. It's just a membership, not a qualification/accomplishment.
6. Consider not having a big picture of yourself everywhere. Are you trying to get hired based on your looks, or your competence?
-
Note on asthetics, since some people mention it in comments:
A. I personally strongly believe that asthetics matter, because asthetics are a big part of Engineering in general, Software Engineering in particular.
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?
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?
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.
-
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!
by dwebs9 on 5/3/24, 6:01 AM
I've typically had pretty good success landing jobs and a lot of the time, it doesn't come down to the technical skills, but what I like to call 'the vibe check'.
Obviously, having the right experience is important, but I typically focus on a few things that might be missed:
- Analysing the business and understanding their brand and culture so you can speak their language during the interview - Showing interest in their broader business goals - When explaining technical challenges you've faced, describing how you took those learnings away and applied them to a problem you faced in the future
Not hard tips, but after doing this I definitely got more job offers.
(p.s. If the resume is lacking, just pay a professional to make one for you).
by Kwpolska on 5/3/24, 6:01 AM
by stoperaticless on 5/3/24, 5:54 AM
> Sometimes I pass the interviews but companies goes with other candidates. I have failed some interviews too (Unable to solve the problem on the given amount of minutes by the interviewer).
Reminder: during interview, you are checked not only for technical excellence. How you communicate and deal with difficult questions matters a lot. (Maybe even more)
Also as others have mentioned, if it’s spring position, knowing spring is mandatory. (2 years seems like a plenty of times to make something with spring)
Last but not least, your linked web page has link to CV, after opening it it became clear to me that you are looking for junior position, only couple of entries about training. (Then eventually I noticed the link to PDF; please understand how this confusion on my side is not beneficial to you; also nitpick regarding PDF, it lists “completed trainig required by the company”. It does not seem relevant to next employer unless its clear what the training was about)
by steve1977 on 5/3/24, 6:32 AM
There are a couple of things I noticed when looking at your website and CV. You seem to have many interests and ideas. Maybe too many. This might be ok on a personal level, however on a professional level this is only good if you can actually follow through on those interests. Otherwise it might give the impression of a lack of focus more than anything else.
For example, you mention Swift as area of expertise and an iOS Developer nanodegree. Yet I don't see a single iOS app you made. You mention Cloud Developer using Azure, yet I don't see any demo or portfolio projects.
On the CV of 2022, you mention AWS Certified Cloud Practitioner (Coming soon). But I don't see this certification.
Now, don't get me wrong - I don't think you need to have all of this. But then there is no use in mentioning it. Show what you actually have.
In your blog, you mention something like this: "Explain the protected access modifier in Java, probably using Blender"
This could actually be very interesting and something unique! But don't talk about it beforehand - do it, then show it!
Don't put your TODO list on the Internet. Put your DONE list on the Internet.
Hope this has some value :)
by tarxvf on 5/3/24, 5:50 AM
I don't think your current website and current resume show off your employment history at all, and if you're applying to places with the new ultra minimalist resume I could see that being an issue. It might also be worthwhile to update your links and listed emails on your resume, website, and github so that they all point to your current website and contact info.
My friends and I have been part of the layoffs - SWE and SRE work. Everyone is job hunting and hiring seems to be way down. I know my most recent company had a hiring freeze for the last year and a half across most business units, but they still had job postings the entire time. That might be very common. And it seems like most places want the exact right applicant for their tech stack. Unfortunately this is the nature of remote work - there probably is someone with exactly the right expertise applying.
It's rough out there, but keep at it. Good luck!
by jurschreuder on 5/3/24, 6:30 AM
This is like? Want me to build your house: I've taken a masonry course online.
Show me at least 4 walls that you've built and if your specialty is walls and these are your demo walls they better be state of the art, all best practices, explain why you used which technique for which wall.
by JPKab on 5/3/24, 6:12 AM
by xeornet on 5/3/24, 5:49 AM
We have such a reliance on hoping someone will give us a consistent, hourly rate rather than going it alone and doing something yourself. It's not easy - but you stop relying on others.
by Hock88sdx on 5/3/24, 7:29 AM
by heldrida on 5/3/24, 7:56 AM
You seem like an humble person, in todays age the job market is very aggressive, there are many self titled senior devs with 3 years of experience and a lot of people who aren’t honest about their experience. My suggestion is to work on your CV to represent you better!
Nothing wrong doing other things, it’s actually important! I used to work in Blender since early 2000’s, I had the original book and always been a fan of Ton Roosendaal. I’ve been developing since Pascal and Action Script, or LAMP days, and still pushing work with any technology I find revelant. And that doesn’t stop me from time to time, to do creative work. I’ve done 9 music videos, for a punk rock project (Portuguese) in the last year. Including 8 pixel art, stop motion and 2d/traditional animation. I push a lot of work daily as a developer, including helping colleagues, mentoring people etc—literally product engineering/full stack, write the spec, prototype, devops, backend, front end, design, if necessary motion graphics, etc and always document everything.
It’s all a matter of empathy, so make sure you work on that CV and Portfolio. Make sure it represents you better!
I haven’t updated my site for a very long time now but hope it inspires you https://punkbit.com
Good luck!
by Mawr on 5/3/24, 11:38 AM
Saying you can learn it on the job is a meaningless statement if you have nothing to back it up with. They will not just take you on your word. You need to get ahead of their expectations and learn Spring.
> I need to refresh some Algorithms knowledge, I have devoted sometime learning Scala for example, and a little bit of Haskell.
Brushing up on algorithms can't hurt, but those languages have nothing to do with that. They will not help you with your goal of landing a job at all.
> I firmly believe I can help with something in a Software oriented company, even data wrangling or any other task nobody else likes to do.
Don't ever bring that line of thinking to any sort of an interview. Preferably don't even think in that way at all. Coming off as a beggar is the worst thing you can do.
> https://calebjosue.gigalixirapp.com/
First impression: the design is straight from the early 2000's. The first impression is all it takes, so you're getting disqualified immediately by anyone who opens your website.
Make a proper modern project that showcases your skills. An e-commerce website is generally a good choice, a copy of Amazon basically. User authentication, payments, nice repo on github with CI, all the best pracices, etc. Spend ~3 months on it and link to it directly from your CV.
by TechDebtDevin on 5/3/24, 5:39 AM
by chefkd on 5/3/24, 4:19 AM
by fendy3002 on 5/3/24, 6:41 AM
* outside of technical tests, the chance for you to be hired is 100% lies on presentation and communication (soft) skills. Confidence is a must, don't show any sign of desperation
* don't mention any past companies or blame them explicitly, for anything hiring or work-experience related. Keep it vague, maybe just say that you're unlucky or the market just isn't aligned
* talk about your skills, achievements or portfolio more, less about your opinion. Don't talk about weakness at all, and when asked prepare an answer that is positive, like "sometimes I aim for higher quality that development took a little longer"
* don't mention lower rate / cheap, that'll be perceived as lower quality. Do a market research and specify a rate if asked. Or just mention that your rate is "competitive" rather than "lower"
Sure the post is different than interview, so those points above are more like general guidance.
by theogravity on 5/3/24, 5:12 AM
Not if you ever get said job.
If that's what's in-demand, then spend time learning it with the time you have.
by MrDresden on 5/3/24, 6:22 AM
- Where is your resume? If it is on your webpage I sure couldn't find it. Make it more prominent.
- If you want to work in software development, you need to have demonstrable skill at doing so (at least to the junior level). Code more and show off what you have done.
- Try to reign in the overly verbose way you communicate in (i.e long rambling posts with too much unrelevant information). This may come off as harsh, but it can pay off knowing when and how to communicate to different groups of people. (Suggest checking out 'bottom-line, up-front' or 'BLUF')
I agree with many of the other points already made by others so won't duplicate them.
Good luck!
by Deluded on 5/3/24, 6:49 PM
by atoav on 5/3/24, 6:14 AM
1. The person needs to be reliable, I need to be able to depend on them, they need to be able (within reason) to think for themselves and solve problems in a good, none-convoluted, well documented and future-proof way.
2. The person needs to be able to learn for themselves and master a topic. That doesn't mean this is a school test, sometimes the solution is: "Boss we would be stupid if we built this ourselves, there is this great open source project I found"
3. The person needs to be able to communicate clearly and honestly.
Notice how most of these aren't related to the programming at all? They are more about how you conduct yourself and what people can see in you.
My advice to you would be to work on one or two "bigger" projects to which you can point when you are sitting across in the interview. If you are clever and pursuing different topics is your driver, choose something where you can apply all of those skills. Maybe you find something that would involve Blender and Spring? Blender has a python API so you can remote control many things. The most important part is however that you get those projects to a good state.
The reason such projects are a good thing is because it would show me that you are able to organize yourself, you can get things done, you manage to combine your skills etc. and above all: Solving problems motivates you.
And even if you had those projects and you sit across and talk to me like all of that bores you I am not sure I'd give you a chance.
by work_a on 5/3/24, 6:01 AM
by ayende on 5/3/24, 6:58 AM
Given a two years gap, you should invest the time and effort in learning whatever it is the market is seeing demand in.
Consider the employer's perspective. Given two equivalent candidates, where one of them know Spring, but the other needs a month or so to learn it. They'll go with the one that already knows that.
That attitude of I can learn on the job is likely hurting your prospects.
The CV in the website is also really bare bones. Basically, nothing relevant there. The old one appears to at least show the employment history.
The website link from GitHub is erroring. The website you linked looks bad, Geocities bad.
The GitHub profile itself is really bare bones. The first non-forked repository I saw was literally hello world (hidden by many layers).
by overtomanu on 5/3/24, 7:24 AM
Otherwise, just learning spring boot, assuming some things happen "by magic" will take fewer hours.
by work_a on 5/3/24, 6:00 AM
by morgante on 5/3/24, 5:32 AM
by zo1 on 5/3/24, 6:07 AM
Also, wtf does Steve Jobs have to do with this? It's non-sensical and out of place. I hope you don't go off on such tangents in your interviews.
by calebjosue on 5/4/24, 10:39 PM
by jongjong on 5/3/24, 6:31 AM
I haven't been able to find a job in over a year in spite of a stellar resume. Also I write a fair bit online anonymously.
Most of these tech people are control freaks so they probably snoop in on their employees with all kinds of special tools using text analysis.
by mikhael28 on 5/3/24, 1:04 PM
by emacsen on 5/3/24, 6:53 AM
I also want to mention that aside from hiring for my team, I've also previously worked with paid interns from Google Summer of Code, both in the mentorship and the selection process.
I'm not someone in a large company, so that made the process of hiring somewhat more open, but if someone send me your website or sent me your CV, I must admit that I don't think I would take it very seriously.
There are generally three things that I look for in a candidate:
1. Is this candidate already familiar with what I need them to do, or would this be a stretch of their skills?
Having the exact experience I need, with the exact tools, etc. is nice but not always necessary or the deciding factor.
2. Does this candidate have credentials that demonstrate their ability to do the job. This might be experience, a degree, of contributing to a FLOSS project in a notable way.
3. Do I think this person will be someone I want to work with?
This is very "fluffy" but demonstrations of both professionalism, and also good communication are key here, as well as harder to measure things like attitude.
Your resume links to a much better resume. The first resume on your website lacks anything "interesting" and if someone sent it, I'd simply pass.
The frozen resume is better, but still quite challenged. Drop the huge logos; they don't impress and they feel "scammy" to me.
I also think that there's some challenges with your English. For example "Backed by 10+ years of experience in the Software Industry." is off. It's not quite gramatically correct, or to be more precise, this gives off scammy vibes. :(
It's not a problem in isolation to have people whose native language isn't English, if you're aiming at an English speaking audience, your resume should be better- spelling, grammar and "culture"-wise.
Then in some of these jobs, describe what you did in a way that's more compelling. For example "Software Development internal to this State institution."
That tells me nothing about the work. Even if it's something boring, you could say "Developed a web based application to manage employee payroll."
My experience has been that when presented with a lack of detail, it equates to a lack of knowledge or participation, which is why I pass over such resumes.
I agree with other posters and suggest you get some coaching in this, both in the resume and perhaps in the interview process.
by Jomus on 5/3/24, 6:40 AM
by dvrp on 5/3/24, 5:54 AM
reflect on what you want, it’s definitely not a programming skill issue
by itake on 5/3/24, 5:38 AM
1/ For coding interviews, you should be solving 4-6 leetcode problems per day which should take about 5-6 hours). The remaining 3 hours of bandwidth should be spent learning system design.
2/ If the jobs are you applying for learn Spring, go build a few apps on your own in Spring. Your github profile doesn't have much coding activity.
3/ your profile photos in github and your website aren't centered.
4/ I would remove the donate button on your website. it doesn't signal that you're a successful programmer. If you truly need to have a donation button, write more explaining why people should donate to you.