You can summarize all your past math experience into one line item and keep it under experience or remove all of it from under experience and mention in your goal/mission you were a math teacher for the last decade looking to switch careers.
You will be then left with lots of space which is good as you can expand on your projects
Structure your Projects as Experience
Give them a timeframe in which you did them, provide yourself a title eg. Full Stack Developer.
React Considerations
React is in demand and is the easiet way to enter the web-dev industry full time at good pay. I do consider React a dead-end in terms of career and salary progression but you need to get in somewhere with good pay its where I'd suggest to start.
I would suggest you to create a varation of your resume where you are a "React Frontend Developer". The problem with React is that it highly varies in terms of configuration which makes it hard for companies to hire juniors because they are never trained on that variation. If you can show you can work with any technical pairings you be overwhelmed with full time jobs offers.
So you would need to demostrate you can:
React + Typescript + Redux
React + No Redux + ES6
React + Rails + Webpacker
React + Laravel + Webpack
Showing lots of variation, and in a short time you could take on the label as Senior React Developer. Put a large emphasis on how fast you can get started on any project without being hand-held and you'll be in good shape.
Full Stack Considerations
The majority of startups use Relational Databases and a common growing pain is perfomance of queries which means that they eventually have to start writing raw queries. Demostrating you can write raw complex queries both in MySQL and Postgres (and I would suggest an emphasis on the latter) is a clear signal you are experienced.
MongoDB has its uses but as primary database it is a mistake. Many startups eventually figure that out when they run into growing pains and make the switch to relational. MongoDB is the mark of an inexperienced developer. Why do so many juniors use MongoDB? Bad online tutorials and no real-experiece at succesfull startup to know better. When NodeJS became a thing MongoDB was the fad database at the time. The first NodeJS frameworks only had MongoDB adapaters and there were a wave of tutorials using MongoDB which is the cause of this problem.
DEV.to Contributor
My number one recommendation is open-source contributions and the best project to do so is DEV.to itself which is open-source. If you can knock out a few medium size tickets on DEV.to in a timely manner than I would consider you hireable. I talk to recruiters and the number one thing they say to me that their clients want to see is open-source contributions.
Thanks for all your feedback and follow up. I think I'll definitely be condensing my past experience so I can expand on the current projects I have going on and focus more on that.
Structure your Projects as Experience
Give them a timeframe in which you did them, provide yourself a title eg. Full Stack Developer.
I greatly disagree. If those projects did not hold you accountable like a job does, you do not pretend they are such to inflate things. You'll have background checks wanting to know who your manger was at this "Github" thing or reference requests for how you manged time and requirements on what was a hobby project. Be true to what happened -- if it was a project, keep it listed as such in its own section. I'd only consider projects experience if it happened while at work with formal expectations for how it would get done.
Not suggesting he passes them off as working at Github. I have small windows of time to contribute comments on DEV.to so I would hope readers would give me the benefit the doubt.
For personal projects, timelines help you understand how fresh and how long work has been invested in a project
Providing a title can help understand the role in the project.
If the goal says he's switching careers and working on multiple open-source projects to showcase his self-learned experience there is no deception here and in-honest it's not hard to infer they are hobby projects. The github project links are a dead give away.
Initially misread it -- yeah, having things formatted consistently would absolutely help the readability of this (though I more noticed education seemed copy-pasted from an old resume). I thought the advice was to consolidate things into one section, which my corporate work has shown that would be a nightmare.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Condense the math experience
You can summarize all your past math experience into one line item and keep it under experience or remove all of it from under experience and mention in your goal/mission you were a math teacher for the last decade looking to switch careers.
You will be then left with lots of space which is good as you can expand on your projects
Structure your Projects as Experience
Give them a timeframe in which you did them, provide yourself a title eg. Full Stack Developer.
React Considerations
React is in demand and is the easiet way to enter the web-dev industry full time at good pay. I do consider React a dead-end in terms of career and salary progression but you need to get in somewhere with good pay its where I'd suggest to start.
I would suggest you to create a varation of your resume where you are a "React Frontend Developer". The problem with React is that it highly varies in terms of configuration which makes it hard for companies to hire juniors because they are never trained on that variation. If you can show you can work with any technical pairings you be overwhelmed with full time jobs offers.
So you would need to demostrate you can:
React + Typescript + Redux
React + No Redux + ES6
React + Rails + Webpacker
React + Laravel + Webpack
Showing lots of variation, and in a short time you could take on the label as Senior React Developer. Put a large emphasis on how fast you can get started on any project without being hand-held and you'll be in good shape.
Full Stack Considerations
The majority of startups use Relational Databases and a common growing pain is perfomance of queries which means that they eventually have to start writing raw queries. Demostrating you can write raw complex queries both in MySQL and Postgres (and I would suggest an emphasis on the latter) is a clear signal you are experienced.
MongoDB has its uses but as primary database it is a mistake. Many startups eventually figure that out when they run into growing pains and make the switch to relational. MongoDB is the mark of an inexperienced developer. Why do so many juniors use MongoDB? Bad online tutorials and no real-experiece at succesfull startup to know better. When NodeJS became a thing MongoDB was the fad database at the time. The first NodeJS frameworks only had MongoDB adapaters and there were a wave of tutorials using MongoDB which is the cause of this problem.
DEV.to Contributor
My number one recommendation is open-source contributions and the best project to do so is DEV.to itself which is open-source. If you can knock out a few medium size tickets on DEV.to in a timely manner than I would consider you hireable. I talk to recruiters and the number one thing they say to me that their clients want to see is open-source contributions.
Thanks for all your feedback and follow up. I think I'll definitely be condensing my past experience so I can expand on the current projects I have going on and focus more on that.
I greatly disagree. If those projects did not hold you accountable like a job does, you do not pretend they are such to inflate things. You'll have background checks wanting to know who your manger was at this "Github" thing or reference requests for how you manged time and requirements on what was a hobby project. Be true to what happened -- if it was a project, keep it listed as such in its own section. I'd only consider projects experience if it happened while at work with formal expectations for how it would get done.
Not suggesting he passes them off as working at Github. I have small windows of time to contribute comments on DEV.to so I would hope readers would give me the benefit the doubt.
For personal projects, timelines help you understand how fresh and how long work has been invested in a project
Providing a title can help understand the role in the project.
If the goal says he's switching careers and working on multiple open-source projects to showcase his self-learned experience there is no deception here and in-honest it's not hard to infer they are hobby projects. The github project links are a dead give away.
Initially misread it -- yeah, having things formatted consistently would absolutely help the readability of this (though I more noticed education seemed copy-pasted from an old resume). I thought the advice was to consolidate things into one section, which my corporate work has shown that would be a nightmare.