The 'technologies' will be replaced by their respective icons.
The 'technologies' will be replaced by their respective icons.
Why? I have no idea what the icon for some of those are and I'm sure others may not as well.
I meant like this:
Ah - okay I wouldn't call that "replaced" - the icons were "added to" the names. I thought you meant the icons would be there instead of the name.
Apologies for the wrong word usage.
This change would also be bad for anything that scans for keywords, which includes most applicant tracking software.
I'd change
This assumes that OP actually meant git...
I fear they may have had no idea what the distinction between git and GitHub is and intended to say GitHub.
Thought it was a good opportunity to potentionally learn something new. Seems to have worked out.
Changed, but why Git but not GitHub for version control:
Because "Git" is the technology. GitHub is just one site that works with it.
I see, I thought Git and GitHub are not one and the same.
There's plenty of git forges that aren't GitHub. Git itself has nothing to do with central servers and can theoretically be used in a completely decentralized manner.
Understood.
At college some guys were self hosting a git server for a project but it went down. We resorted to a USB stick that acted as remote and was passed around. That was awesome to see, for about a day...
Lol. Git itself can act as a server over the git protocol. Might have been easier 🤪
Also if you go with git instead of github you should use git's icon
Agreed, here you go:
Speaking from experience, in the past year, I've used 3 different hosting providers for git repositories at work. Only one of them is GitHub. It's good to keep your options open - git isn't locked to any particular provider, after all.
What other options are popular in the market?
I've used GitLab and Azure DevOps professionally, but there are a lot of services out there which host Git repositories. GitLab can also be self-hosted which is nice. They all fundamentally work the same though from my experience - code viewer, issue tracker, pull requests, some way of doing CI/CD, and various collaborative and documentation features (wikis, discussion areas, permission management, etc).
It may be good to understand also where the separation lies between features that are part of Git vs those which are part of the service you're using (like GitHub). For example, branches are Git, while pull requests and wikis are GitHub.
Just remove the fullstack part. If there are any senior developers going through the CVs, that's an immediate red flag.
Why? The "stack" has grown so large, that when a dev claims to be fullstack, you know he either doesn't understand enough to know he cannot be a fullstack developer, or he does, and isn't really good at anything, because there's just too much to know these days.
Here you go, I hope to reach to the Senior Developer's level one day:
The second column seems clunky to me. I know what everything in column 1 is for. Column 2 seems redundant or filler. For a keyword search or something like an ATS having those things mentioned is probably helpful. Though, for an ATS you should be optimizing for that separately.
Right now the About Me page doesn't tell me anything that I won't find out on the Resume and My Projects pages. I would get annoyed at having a wasted click for no new information, and it tells me that you're just putting stuff on a page for filler. Maybe consider combing the About Me and Contact Me pages.
On the about me, you may want to add a portrait and some biographical information. Nothing too personal. The stuff you would like to share an icebreaker in an interview. It's a good way to provide a conversation starter, "Hey, I saw on your page that you like kitties and hiking. I like kitties and hiking." I had my HVAC serviced last week, and the company sent me a text with a photo of the tech and some general biographical info on it. Apparently the guy likes going to the gym and spending time with his family. I don't know why I needed to know that, but now I do. Humans are social animals, and a lot of humans like that kind of stuff. The portrait doesn't have to be anything professionally done. Any decent phone has a portrait mode. Just look nice and use a clean background. Don't use the webcam on your monitor with your unmade bed in the background.
Also, this page tells me you are more of a back end person. Someone more front end would be a little more creative on the graphical design. This looks like a default template. That's fine if that's the message you want to convey. That's what my stuff looks like. I mostly do data engineering and present those data in an interactive dashboard with some manipulation and filters. In that situation having a boring and generic looking dashboard is desirable. My users prefer that since they are really there for the data and controls, and anything extra would be a distraction. If you want to convey that you are more front end focused you need a less tabular layout and more visual candy.
I understand what you're saying, but I designed my website to be short and sweet, something that can be skimmed through and move on.
Maybe consider combing the About Me and Contact Me pages.
Can you expound?
For a keyword search or something like an ATS having those things mentioned is probably helpful. Though, for an ATS you should be optimizing for that separately.
I asked ChatGPT to make an ATS friendly change to the About Me section. Is this what you mean, and can it be beautified with the ability for the ATS to go through it
I think we need to take a step back and add some context. Every company will have their own hiring process, but they are mostly the same. Where I work it goes like this.
During this entire process the only people that are going to look at your website are the hiring manager, stake holders, and peers. That is only if they are feeling motived to do additional research on you after having looked at your application and resume. Your application and resume should have already told them that you know the technologies you listed. This means that the user is not rewarded with any additional information. What was the point of me seeing this page? As one of those people interviewing you the only thing this page actually tells me is that you know how to put words on page with a template. That template should be custom and look amazing.
Jeff Geerling’s website is a good example for content. The design isn’t something I would expect from a front end developer, which he is not.
https://www.jeffgeerling.com/ https://www.jeffgeerling.com/about
Nowhere does he have a list of icons of technologies used. You learn that he knows how to use git by the link to his GitHub profile. He doesn’t have a dedicated contact page. The only thing that is really needed is mention an email address on the about page and links to socials. It’s almost like he shows us his skills instead of telling us about them.
I see so make the website look like a resume, genius.
I disagree about humans reading these... As someone who has to read resumes while hiring, I'd rather see this than the word-soup I often get. It gives me an idea of what you're best at, and I can figure out that you'd also be able to learn/do similar things.
I'd suggest rewording the mongoDb line to emphasize familiarity with NoSQL and call out mongoDb as a specific technology in the family. Also, if you have actual RDBMS experience please don't omit that, it's something we weight a lot more than just mongo/redis/memcached.
Where should I put that information? I am trying to keep the 'About Me' as to not write a long story about my personal life, I'll leave that to the interviewer.
I'd love for someone more experienced to chime in, but on first glance the classification of JavaScript/Typescript as backend strikes me as weird.
That may just be because the team I work with uses a React/Typescript/Java/Postgres stack and we specifically classify the Typescript as part of the Frontend. Maybe it's different in different companies?
I'm sure that a Typescript backend could work perfectly fine, it's just semantics 🤷
You don't classify a language, you write what language you used for the task. I'm guessing you're using Java for backend, and TS only for react?
Yup, exactly! So a calculation-only module that doesn't have a frontend would never have any TS Code in my case.
The classification of language -> task makes sense! I'm thinking of the weird college courses that wanted Java frontends lol
But how would you generalize that for a resume? Say you've used C# both for making backends and making frontends in separate projects. Would any sort of classification make sense in that case?
But how would you generalize that for a resume?
I separate languages and tools/frameworks (not a dev CV so take with a grain of salt). No clue about the c# world, but for js I'd do something like:
Languages: js, TS
Frameworks: express, react, etc.
The key is to hit all of the required keywords, machines and HR don't know anything else. If a developer looks at your résumé they'll know that you wrote both ends.
Ubuntu font? Good font
I'm using Ubuntu, so it chose Ubuntu font as the default, and the font doesn't look bad at all. I may stick with it.
I would overload the first portion of your resume with as many keywords related to the stacks you’re familiar with
what 'keywords' should I fill it with.
Do not do this, but if you are, be sure to include Excel, Word, Windows, Outlook, and TCP/IP. Adding TCP/IP lets them know you're a real technical person.
Most automated scoring of a resume compares your resume to the job posting you're applying for. The closer the match the higher the score. You should be tuning your resume for each job and while using the same words and phrases in the job posting.
Maybe this can be included in Other Skills. Thanks for the advice.
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
