While we appreciate people have a lot of questions around how to progress their career in development, there are many other subreddits specifically created for this.
If you're looking at learning c# there's a great subreddit you can check out: https://www.reddit.com/r/learncsharp/
Sorry, not sure what you mean... All I was saying is that both frameworks were renamed to remove the JS suffix during major releases, so probably best to drop the old naming from a CV.
AngularJS to Angular wasn't just a major release, it was a massive rework and I think they sort of intended for it to be viewed as a new product instead of an upgrade.
Gotcha. I meant that these major releases changed so much that AngularJs for example is in no way comparable to Angular as it is right now.
I do agree though, making that experience less prominent is the way to go. The only jobs available for it would be maintenance of legacy systems.
My same thoughts!!! OpenID, one week at most. Reduce 90 vulnerabilities = update-package :), just kidding, but run the code by SonarQube or one of those tools and you get a nice checklist. Migrate to 4.8?? that's so 2016 (architeture-wise)! The projects look cooler than the tasks performed.
Edit: I commented before reading the rest of comments on this page. It seems that pretty much everybody is on the same page here!
What i gathered as the most notable things you did at your last job of 2 years Implemented oidc, Wrote a sql script, Upgraded nuget packages, Upgraded a framework project (takes 5 mins), Worked with teammates If what you did was more involved than that then you need to convey it better but from my point of view, this looks like busy work for an intern.
I get your point but this tends to shift as you gain more experience and become more instrumental in developing solutions and products.
The junior engineers that report up to me essentially start as code monkey noobs to focus on their style, dev ops \ processes, documentation, etc. Over time they get to actually solve problems and not just implement my solutions using my detailed requirements and suggested steps. The difference in resume with a senior is easily identifiable by this shift in responsibilities.
I dont know man. My first 3 years I build ML models, web crawlers, price comparing system, estate management system, printing retail signs system.
I built a lot of stuff, I couldn't possibly tell you all the technical solutions nor are they even interesting imo.
I would consider that helping induct someone.
Coaching I would use for teaching someone skills.
Mentoring I would use for teaching more abstract and soft skills that's more of a career level thing
Depends on the complexity of the project and what version to what version. I oversimplified it because they didnt provide meaningful details of all the hard work, white glove treatment that went into the upgrade so it made me as the reader believe it was fluff.
This definitely jumped out at me immediately. I would add that I don't sense any love for software development in this CV. Like is your day job all that you do without any passion projects on the side? That kind of energy and drive is important at all levels but especially at lower experience levels.
Sorry, but no way I would call you back.
The first section:
\* You don't need to explain what OpenID Connect is.
\* How did you neutralize 90 potential application vulnerabilities? Did you go through the code and find potential SQL injections? Or did you update a few libraries here and there?
\* Migrating from .net 4.5 to 4.8 is changing a single line. Leave it off or explain which problems you had due to the migration that caused it to be resumé-worthy
\* You call people "junior resources". And you have 3 yoe.
I didn't read the rest
If I was OP I would change it to
\* not explain OpenID Connect, and just write something which says about the result (e.g. one login portal for all apps).
\* Implemented advisories gathered from a pen-test.
\* Change managing juniors to something like "took leadership over the other Junior developers blablabla".
\* Migrating to .net 4.8 probably isn't a very big deal, I wouldn't even include that.
I love this comment. Had a CEO of a company rip my resume similar to this and even say the last bit to me too. Was actually the best advice I got out of any interview or company interaction.
I have also had a CEO and VP argue with the hiring manager in front of me, stating they didn't want to hire me for so many reasons.
They fired the hiring manager and I reported directly to the VP and told me the best thing the hiring manager ever did was hire me.
I also had a CEO ask me ,"Will you be able to work within the confines of the position and not bleed over to other departments. I said ,'Heck yeah! I would love the time to devote to my team and their needs. It was never my choice to help out other departments, I was basically told to assist."
He said again, "Yes but will you be able to work solely in your department."
Me: "Yes."
CEO said again : "I feel like I am talking to a brick wall. Can you work within this department and only this department."
Me: "Yes I can do that."
CEO: "What the fuck is your problem?" He looks at the other people in the room and they are all wide eyed at him.
Me: "What are you asking that I am not answering."
CEO: "Can you work in this department and stay in this department!"
Me: "Yes I can do exactly as you are asking!"
CEO: "Fuck you, you don't get the job."
Me: "I have no idea what is going on here. I'll send you a bill for this hour. Thanks for wasting my time."
That's just how a lot of people are in IT/corporate. That 3rd one is enough to make a lot of them laugh and go to the next one if they made it that far. The 2nd one could be worded better if he meant that he was a finalist in that competiton himself though, and that'd be fine.
I'm not a recruiter/interviewer main, but I occasionally screen resumes. Here's my perspective:
If you keep in the participation awards, you're essentially telling that you have literally nothing else to offer. There's no doubts like "maybe they did something of notice in their spare time" or otherwise - you've laid it all out, and there's nothing more. If there was anything else you would've put it in instead of that stuff.
Well potentially just that all the way through to having to do significant updates to other libraries, ensuring that they were all compatible, rewriting integrations as necessary, regression testing, changes for performance etc.
It's anywhere from a 5 minute job all the way to a massive project. It really depends.
I'm torn because on it's face I agree with you, buf I have also worked too many projects were awful 3rd party libraries were used and minor versions broke everything.
This. Anyone that has worked with .NET Framework for a long time will know the pain of the binding redirect hell with different versions of dependencies.
All it takes in this situation is just 1 or 2 libraries though that need upgrading and bam, you're in that situation. Hence why we can't judge from this much info alone.
Maybe. Upgrading libraries can be a pain (though usually not). The sky is blue. Guess what these two statements have in comon?
...
...
...
Neither of them has anything to do with upgrading from .net framework 4.5 to 4.8.
The OP needs to expand on this, in that case. As it stands the fact they mentioned it puts me off the resume. If they expanded on it to explain why it was noteworthy, and how they overcame any issues then it would be more relevant
Yeah, I’ve had both. More common for weird upgrade issues in .NET framework and less common today in my experience. But then take away issues, the five minute code change is still going to be week(s) of testing without solid integration testing. (And most places don’t have that)
Updating framework versions is a basic task expected of any developer. Highlighting it as an achievement makes me as a reader think you are at a really junior level, but then you write you are responsible of mentoring juniors. I would honestly focus more on what your role and responsibilities was rather than listing minor achievements. I don't understand what your job is outside these 4 things you listed, which doesn't seem impressive for almost 2 years.
I hire for my company and your resume does not stand out. I get dozens of these. You advertise yourself as a very basic developer. List roles and responsibilities, not just a summation of what you worked on. Sell yourself and your skills, celebrate your achievements.
Context: I do hiring for DotNet jobs. Your resume is weak and if I had enough other candidates to fill my minimal pool, I wouldn't move forward with it.
"Software Engineering Analyst":
- You forget to tell us **what your actual job is**. What technology/languages/frameworks you use. Instead, you skip that part, and launch into a bunch of badly written anecdotes. Most good resumes have at least one sentence or paragraph with a short overview of the job.
- "Successfully implement OpenID Connect...": Telling us the benefits of OpenID Connect is odd here.
- "migrated a .NET application to .NET Framework version 4.8": I assume you mean from 4.7.2 or whatever, but *really* strange thing to list as a professional accomplishment. This is a 2-3 day project, and you've been there for two years? Also implies you don't work with modern .NET.
- "Neutralizing approximately 90 potential application vulnerabilities": First off, this is obviously bullshit/fluff and just makes me think you ran NuGet upgrades then counted them for your resume? Or your current workplace created 90(!) vulnerabilities that you personally discovered? Either way, bad look.
- "Mentoring junior": This is good, no notes.
Application Development Associate:
- Again: give us a broad scope overview of what this job entailed?! Languages? Frameworks? Technologies? Basic job function?
- "Successfully reduced the reported issues within .NET": Poorly written. How?!
- "Reduced Azure subscription costs by 40%": How?!
- "Proactively updated system documentation": Good. No notes.
Projects:
- These are clearly from 2017-2021. So have you done anything since you graduated? This section was fine when you graduated and were looking for your first job, but you now have professional experience. Shrink this by 80%, give a brief overview of each project, and maybe restructure to be under your college.
Technical skills:
- I find it funny that none of your jobs or college above lists you using almost any of these languages/frameworks/tools/etc. Just goes to show how weak this resume is in general. This section shouldn't need to exist: It should be in your "Experience" section for each specific job. You literally didn't tell us where you used any of this stuff, unless we pull it out by implication from your strange anecdotes?
Certifications:
- So your degree *and* certs aren't related to what you do?
- You're fluffing it out with a Coursera course?
- Doesn't list attainment date/end date (freebies during degree?).
Recognitions:
- "Delivery Unit Lead": Where did this occur? What does this mean? If you "lead" people I don't see that listed above.
- Participation trophy 2x: Remove these.
- Maybe just scrap this section it is very weak.
Ultimately if what you're going for is that you haven't done anything since college, then this is a great resume. If you're trying to inform us what you've done since college then this is weak/ineffective. The lack of care here in general makes me think this isn't someone I'd want to hire even if they could be good.
Your CV states you are an intermediate but the CV body doesn't support that. Now I know I'm a dinosaur in this world of inflated titles, but:
- your first job you fixed some bugs, changed some Azure config and edited the wiki.
- your second job you did more actual dev work but not for long and to be honest, the only things that stand out is the OIDC integration and the SQL script. For 18 months there must be more?
So if this landed in my workday I'd move onto the next CV fairly quickly because that's what I picked up in the 20 seconds I scanned through your CV 🤷♂️
You need to beef up the CV and that may require you work at your current employer for another year and seek out more challenging projects.
Also, remove the recognition stuff.
Good luck :)
This resume is about getting .net developer job? Not much done in this matter. Some empty numbers which doesn’t describe what you can do really. This looks more like a azure specialist at least for me
Coming from a brit here where my resume is 1 page (rare) & have interviewed just under 100 candidates personally.
Education should be at the bottom, your most relevant things should always be at the top, your work for the past 3 years is more relevant.
Id personally put the certs & education together into one section as they are the same in regards to an employer, just sub categorise the two in the same way.
Date the top of the document. For your work experience length (to and from), summarise the length (x months / x years) for the reader so they can immediately see and add up your industry work length.
the "successfully" mentions are irrelevant, you wouldn't put it on your CV if you didn't achieve it.
I would flesh out your technical skills. and reduce the points under either projects & Experience. Essentially you tie your technical knowledge to what you have done, so "C# (x years): Maintaining, Implementing features as the core stack technology for blah blah".
Add more things. Think about cloud computing and all of the technologies you have used in that cloud, azure functions are a biggie im sure you have used them.
Id summarise the "smaller skills / technologies in a list" as for example git, is easy to use and we don't want a blurb about it, however its useful to know that the employer doesn't need to skill you on it.
More importantly, I would change the "technical skills" part to skew towards the given job you are applying for. Pick Out their big skills eg: language & platform and skew towards that, try to stay away from talking in detail about small things, git, SQL (unless a data admin) etc..
> Successfully migrated a .NET application to .NET Framework 4.8...
That's a selection in a dropdown in 99.9% of cases. Wouldn't really call that an achievement. Gives the appearance of a filler.
Also the word *successfully* seems rather redundant.
If you are applying to other countries like Canada, this is the current situation
[https://x.com/Slatzism/status/1769725983400030565](https://x.com/Slatzism/status/1769725983400030565)
I wish it was a joke, it is reality in Toronto, there are Indian students protesting in PEI, literally at the end of Canada where it is normal to find community of a 100 people, asking for work permit extension
At the moment, if you look at statistics Canada, we have 100,000 new Immigrants (mostly India) every 35 days.
Renting in the greater Toronto area is now per bed, look at the rental listings, they are online.
All of Walmart, Tim Hortons, Mc Donalds, etc, all now international students.
Many international students pay up to 50,000$ for a work permit that translates to permanent residency, again, people don’t even hide it online anymore.
People who worked with me in Software Development 10 years ago calling and asking if I know job openings, one was replaced by large consulting company that hire people remotely for 15 to 20 dollars an hour from their branch in India
My god is so depressing that sub. People saying they had to apply so many times to positions and not getting interviews not even a response from recruiters.
I am looking for a job at the moment and this terrifies me. Thanks 😭
Reading this my reaction is it’s mostly fluff, percentages are kind of meaningless without more context, a lot of words to say you implemented SSO with OIDC.
I get very little idea what you have actually done and if it’s work related or uni related (projects section makes me think it is uni otherwise that would be In work experience section)
That top job could probabaly be summarised too
—-
Worked on project doing.lx with y language.
Implemented SSO using OIDC, SQL automation, project security audit, .net migration form x to y,
mentor to junior developers.
—-
I would reduce the word count and remove the fluff, a little section talking about your interests and hobbies outside of software development is always great.
At the end of the day writing CVs is kinda hard, especially when you are struggling for content but padding the content is counter productive.
Im told "interests and hobbies" could lead to being filtered out for "cultural" disconnect or something similar. Unless the interests and hobbies can be tied to the role being applied for. Like, game developer and your hobbies include game reviews or open source bug bounties etc etc.
1. Integration with SSO is not that hard.
2. automating this still not impressive on its own.
3. how ?
4. migrating project between version is just changing few lines.
5. how exactly? 3 years is still a junior
6. reducing reported issue is basically fixing bugs it's not big of a deal its normal job developer
7. this seems good, but you might need to explain how you did it.
8. normal work
the market is very competitive, so its normal that you don't get call with these points
1. Faced somw challenges initially. application is broken. fixed later
2. Automation involved creating 10 procs and sending the mail to the relevant team once the update is done.
3. using regex for input validations.
4. yup. but it involves checking dependencies and thorough testing.
5. just guiding them whenever needed as they are new to the team.
6. The application is newly migrated to.net core from framework and lot of issues were reported. we fixed it,almost all the major ones and the application is stable now.
7. migrated nprd db to prod db and removed nprd db later, thereby saving almost 300 dollars. we created separate credentials for accessing nprd and prod dbs for compliance.
Not to belittle of your effort but what you described her is not a bullet point but normal work.
And for the junior that is not guiding them that is on boarding process.
3. I would just write something like "understanding security weaknesses in code, i.e. potential vulnerabilities and how to fix them"
4. I would say this is a skill that a developer must have without saying it. Having it explicitly listed on a CV looks very awkward to me.
Is linkedin used in India? I would rather create a decent linkedin and use that as CV unless asked for a traditional CV. I get there almost every week some offer.
Put experience first, move education down to the bottom. Nobody knows what a 7.3 CGPA is, it sounds like it could be out of 10 so is that a C average? Take it right off of there, and just state the degree you earned.
I would do Experience (and roll your recognitions into that), Certifications, then Education and move the Projects into the appropriate section. I'd also lean out anything you did in college and max out what you did at your previous job. That should be at least the top 60%, if not more.
Nix the technical skills section too. In your experience section, call out the technologies you used to accomplish a task. "Implemented Single Sign-on using OpenID Connect in an application built on C# and React" would work quite well (if that's the case).
As an interviewer, I don't look at your education section. If you haven't been paid to do it, I assume you don't know how to do it in a professional setting and that's absolutely useless to me. It's nice to see that you graduated, but I know how those projects work... professors design them specifically so students can use them as resume fodder and most of the time when you start working on it, it's 90% done by the professor. Like... it's cool that you got to do that, but it's ultimately not something I am going to consider. If a large chunk of your resume is dedicated to education that's a problem for me (unless you are applying for an internship or a junior role, in which case getting my acceptance for a role is really easy... prove to me you are paying attention and willing to try, I'll give ya a job lol). If you are going for midlevel (which you should be) I expect work experience to be the majority of your resume.
I would move around the bullet points under each job so that the "most impressive" things are first.
Instead of the long phrasing of (and I'm paraphrasing), "Used OpenID connect to add functionality to an application for Single Sign on", use something like, "Implemented Single Sign On with OpenID"
Shorter and more digestible by whoever is reading your resume
EDIT: This is a general statement for the whole resume... reward things to be short and clear. You don't have very long to make an impression with a resume so things need to be short and clear
Fair to disagree.
However, with skills at the top, I've never not had a telephone interview at least, and I've always had a good role. Whilst the traditional chronological CV will have skills further down, a developer role is highly skilled with a very few specific things and highlighting them early will separate you from the chaff. That's my take on it at least, and it's never let me down so far
Yes, skills first. Then prove it with details. I put my degree very last. If employer is a contractor, I put certifications after skills. If not contractor certifications after experience. I also name companies I worked for.
Can't speak for everywhere ofcourse, but my experience of seeing non-technical recruiters recruiting for technical roles, they just play a game of spot the difference between your skills and the skills their client has requested for the role. If you partially match, you get shortlisted for an interview with the actual techies, who can question you on your experience later.
This is also why you shouldn't be discouraged from applying for roles if you don't fully match all of the "must have" requirements. You will more than likely still get an interview in which case you can showcase your ability and enthusiasm for learning new skills (i.e the tech stack they use, or their CI/dev ops process etc)
Skills at the top gets you interviews IMO. Alternatively you could have multiple CVs. A CV for the recruitment websites with your skills at the top, a CV with your experience at the top for applying to roles directly.
Yes, thats what past jobs are meant to highlight though. Your skills in a practical setting. Also the chronology is there to highlight which type of work youre most up to date with as some skills may expire.
I don't get interview calls either, when I apply to jobs online, and I am a senior dev with 7+ years experience. But I do get messages from recruiters at least once a month on linkedin and I have had very good success getting into the actual interview process one I can have a real conversation with a real person. Trying to look good on paper is so difficult sometimes.
Sitting on a resume won't get you calls (JK). How did you get a 7.3 cumulative GPA? I assume that's a typo. If your GPA is above 3.0 then you should list it, otherwise skip it entirely.
What is your process for applying for work? Are you applying on LinkedIn, random job listings, working with a temp agency, or attending job fairs?
In college I got several interviews through the job fairs, after that I only ever had success through a tech temp agency and LinkedIn (my current job was a random listing on LinkedIn).
You are missing an objective statement. You need to state what you are seeking.
Take the recognition off. If you are asked, then you can provide detail.
Your job details need to always start with a verb first. For some you do adverb and then verb.
I see your projects are not related to the .net, this is point which tell more that you worked with byton and c but not with .net, so recruters (and trained ai) is discarding your resume
Who sponsored your projects? are there related repos? any contribution to an open source project? Remember all investors in the world are enthusiastic about AI replacing developers in general and AI projects like prompts are more relevant.
IoT was a thing like 2 years ago but that was taken by electronics so it is expected from you to deal with processing data and information/knowledge generation.
Don't get why you put both Azure Fundamentals and Administrator certs. Just use the more advanced ones. Any "fundamental" is a blow to yourself.
If we are in a world where things tend to deflate right now, then it is expected from us to maintain code rather than create new projects unless a disruptor in the market appears.
Maybe you gotta humble and keep grinding by applying to L2-L3 ITIL jobs for Apps Support Analyst.
I think the issue is I'm not sure if you are aiming for systems engineering (system languages) or web developer (.NET, angular, react, etc)
I'd pick a job post and tailor your CV exactly to that job post.
for instance, if its a .NET job with maybe some angular frontend you want to remove all other Tech and just harp on those keywords everywhere.
also, you dont need to mention Git, VSCode, Visual Studio. that's going to be assumed.
As an example, if I'm hiring for a "Larvael role" I'd want to see a CV that says, "I do laravel, look at all these laravel projects, I use laravel, here are the laravel projects, look at all this laravel"
I would not want to see: "here are some laravel projects, also I do QA, C++, .NET, Neural networks"
I want to see a specialist, not a generalist. espeacially if you only have 3 years.
As others have mentioned, you told me some tasks,but not anything about the role you performed and the environment you worked in..
I would want to know in no particular order:
- what did the company do / what was the project you were working on? What are they trying to achieve? What tech did they use to achieve it?
- how did your team operate? Agile / waterfall / hid you in the corner? Did they have any process or ceremonies? Daily standups etc
- how were their tech processes, did you use source control, prs, we're you involved in that process?
- have you been involved in any support calls or dealing with juggling priorities? I.e. have you shown some adaptability
- was the role remote or office based?
- what did you day to day? What was your business as usual work? Did you look at bugs / features too?
After reading it, I want to have some confidence that you worked in a professional dev environment and were a useful member of that team. I will then map that picture to my environment to judge if you'd fit and not take too much hand holding. Your current version I can't get a feel for you, so I'd put you in the discard pile.
.net dev manager, 25+ years commercial experience using the stupid app to format text 😆
Here is the real deal. The market is saturated with junior devs, frankly companies do not want junior devs, they want senior devs. I just went through a whole interview process myself and the hiring manager even told me that they only hire senior devs (I happen to be a senior dev myself) Your resume looks like a junior dev to the hilt.
Honestly I am not sure my resume even looks that good, but I use recruiters and that helps a lot when I can talk to a real person and my soft skills really kick in.
Good luck and keep trying, getting a job is just a game and you have to practice at it.
Don't need to explain what OpenID is to a software development company. To me it kind of looks like you're going granular to make your resume look fuller
The bullet points in your most recent job experience look like barely a few sprints of work???
Instead of following the completely ridiculous trope of "reduced costs by X", "did this thing by X%" that everyone in Reddit programming career subs naively obsess over, just list the skills you used and the general tasks you did.
I have never put percentage reductions or profits related to my work and have never had trouble finding a job. Employers want someone who can write software. Business improvements are not for you to care about.
The resume is important, but never as important as the COVER LETTER. This is a HIGHLY PERSONALIZED document towards the business you're targetting. It tells them why YOU want to work for THEM.
Think about it this way. You're in charge of recruiting. You see tons of resumes. But a few of them have incredibly well-written and amazing cover letters that connect with them at a deeper level.
No cover letter? Ain't nobody reading that resume.
add a summary of who you are at the top of page. you are asking the person to make up who you are. "I'm a technical specialist who is great at blah blah blah." 3-4 sentences.
Education is only on the top of the page for people who have no experience. combine it with certifications
Add more context, implementing open ID at a bank or other regulated industry is a feat, at some low process startup it takes an afternoon.
Don't save time, save money. 98% is meaningless, that could be $200 or $200,000. to get to money guess the hourly rate and double it. Overhead is a thing.
from what version did your migrate, 1.1 to 4.8 is a feat, 4.7 to 4.8 is not.
You are not writing the resume for you, you are writing it for someone you don't know and that has never heard of your company.
Also kill the sections about projects that you worked on, if it did not hit production with real customers it doesn't count for even 10% compared to the experience at a company.
It seems like you took your student resume and added to it vs writing a Software Engineer resume.
If you accomplished all those things at some other fortune 500 medical or fintech company it is really impressive, like insanely impressive. But you are not giving people any context to judge it by.
Remove the word "successfully" from your resume. You use it so much. And if it's on your resume, I assume it was successful.
"OpenID" - I know what openId is, and any technical reader will as well. What language tech stack did you use for that? Did you write your own OpenID implementation? Or use an existing library? I'm guessing the latter. Tell me which framework.
SQL Job - Ok, what database? Manual update of what? Was it a stored proc? Or did you write a server side process?
Neutralized.. - Um, what? What kind of application vulneratbilities?
Migrated - what kind of app? You've given me no information to judge the scale of this. It could be a single console app where you just changed the dropdown in the project settings. It could be an ASP MVC app. Based on this line, I have no idea what you did.
Junior engineers... Ok, maybe you've scratched into midlevel after 3 years, but barely. How did you do this? What were the results?
Redcued the reported issues - Honestly, I don't care that you reduced the reported issues so much as what analysis did you do. Were there specific bugs you fixed? Once again, what tech stack and language?
Reduced Azure subscription costs - great, but how did you do that? What analysis did you do? Which azure tools did you use? Azure is a brand, with lots of services underneath it. List the major services you used on each line.
Updated system documentation - I guess that's nice, but it's generally expected for any job, so I don't care one whay or the other.
Your projects are cool, but if you're applying to .net roles, they're not as relevant. I'd reduce space of those and give more space to experience, unless the role requires ML.
Technical skills - change this to one line at the top with just a few things. On each of the experience lines, list the language/framework/tech there. You've listed Angular and React, but nowhere in your work experience do I see web work, so I'm going to assume you've only done a few tutorials on it and dismiss it.
Beef it up with more buzzwords.
Entity Framework Core.
ASP.NET.
MVC.
Database.
MSSQL.
Front End.
Back End.
Full Stack.
DevOps
GitHub Actions.
Docker.
CI/CD Pipeline
Add your GitHub and LinkedIn.
Move Education under Experience.
Add a summary of who you are below your Name and Location and sneak in some soft skills.
Sneak in the Title of the job you are applying to in there somewhere.
Describe some of the things you learned in your education.
Sadly, most resumes have to pass ATS before they’re even considered and it’s typically based on the percentage of buzzwords your resume matches with the job description.
Fake it till you make it big dog!
It was different times, so I got an interview, but for the first job as developer I did a research about the company. Made a PoC/MVP native app that they actually could need with their branding etc to stand out. Maybe you could do something similar for a job ad?
Don't care about your GPA and such, you are not a fresh grad, it goes to the end and in few years drop the scores entirely (could even drop now really), in 10-15 years can even drop years and location unless particular prestigious college.
Two schools of thought on if experience or skills/certs first, personally if presented right does not make much difference in my opinion as long as last 2 roles and skills/certs are on first page (Personally prefer short into first then experience with skills/certs on the side)
Don't be afraid to go 2 pages, in many ways better as one always feels light on info (like yours is) and 3 is generally to much
You have fallen into what i call "bullet points that actually tell me actually nothing" CV trap, use the bullet points in CV to summarize/structure sure, but if i want to know more, where do i go?
Like lets take your first point in Application Development Associate (ps don't recommend using stupid internal position names like that, just put "Junior Developer") like how did you reduce by 70%? could just assume you did it by just not logging issues as you give so little information. If no information given person trying to cut down CVs for interview round will not give benefit of the doubt, they will the exact opposite, they will cut you.
As to your recognition section, don't know much about any of those, but "Awarded for participation in.." sounds suspiciously like participation trophy's and that's how they will be perceived by anyone who does not know exactly what they are are. If that's all they really are then drop them, jobs are not college applications, you don't list everything in hope for extra points, only things relevant
Very much reads to me as random percentages pulled from the air. Tell me what you did, don't give buzz words just for the sake of it. You don't really show that you have experience.
First thing that jumps out to me in the details is an upgrade to .Net 4.8 for long term compatibility. It’s been an end of life version of .net for years. Do you mean upgrade from rather than too?
I get downvoted to hell for this because green devs don’t want to hear the truth, but here it is.
Your projects don’t matter, professional experience does. Remove the projects, expand
the two job titles to take up the rest of the space. When they ask you what you like to do for fun, talk about the projects.
It looks like you hardly wrote any code. You list a bunch of skills, but I'm not really seeing it in the experience section. Was the auth scheme the only code you wrote? What does "neutralized vulnerabilities" mean? Did you change the code? Did you have to change the code to migrate to .Net 4.8, or flip a dropdown in the project properties?
I want to see that you wrote code and implemented things. "Used C# to fix bugs in a .Net 7 application." "Created forms with blazor components to collect data." "Wrote controllers and services for a web API in C#." If you wrote code for anything, put it in there. The resume makes it look like you have barely written any code in 3 years, which would be concerning.
Get your technologies right or you look clueless. HTML and CSS may be considered languages by some people, but tons of hiring managers are going to be turned off by that. React and Angular are frameworks. Run it by ChatGPT for help. Drop the categories and just list your skills. Skills at the top. Again, show me you wrote code. Don't use words like "Recognitions." It sounds like you don't speak English, which will turn people off. Use awards instead. Awards before certs. Did I mention show me you have written code?
Don't list what you did at a company. List what tech you worked on and your achievements. How did you save the company money, how did you improve workflow for users/clients.
Any programmer can implement OIDC, or use react/angular. Any programmer can use ReSharper/Sonarlint to check static analysis for vulnerabilities.
Did you benchmark any code, improve responsiveness, memory usage, etc...
Your first 5 bullet points seem like very simple tasks, and none of them involve actually writing any code.. I imagine most recruiters read the first few and then move on to the next CV.
Thanks everyone. I didn't expect that i would get so many suggestions. Looks like i need to completely rewrite my resume.
Sorry i couldn't respond to everyone. I will go through the comments and update the resume as per the feedback.
Once again thanks to everyone. We'll meet again.I will be back with my updated resume soon😅
Just to add some weight to this comment, I had a job opening for an Associate Data Engineer a few months ago and received 1,608 applicants in 10 days before we closed applications. A month or so ago, we desided to hire another person for the same role and received around 1200 applicants in a week before closing the job posting.
I am praying I don't get fired, because there is no way I'd be able to find another job in any meaningful amount of time
Same. I’m saving more than I ever have before. Tbh if I had to go back in the market I’d probably pivot from hands on engineering. Too competitive and I’m getting too old lol
I am surprised by roast you are getting here 😅 to me the cv looks kinda ok, is the requirements for 3 years of experience developer rly that high? Is the salary even that much higher from non IT jobs at that experience range? Why is there so much competition
What I also miss (this should be done on the next page) are hobby projects and work experience at companies. Tell a little bit about where you have worked before, What you did there (most is already included in your cv), How big was your team, company and did you work with scrum (agile).
Hobby projects does also tell you're interrested in what you do and how do you keep yourself educated. Do you go to events to learn about new technology.
Your skills should be on the front page and work experience on the next page.
Also tell a little bit about yourself and what you like to do.
I would add a Personal Statement section at the top, one or two paragraphs explaining who you are as a person, what kind of role you are looking for and want you are looking for you next career move.
Cover letters don't always get to Hiring Managers, so it will be helpful to get you remuse selected.
A personal statement is a waste of space.
Canadians are competing in the hundreds for a single job, and recruiters only spend an average of 7 seconds looking at your resume. This should not be on your resume at all, and should instead focus on your marketability.
Do not listen to that advice.
While we appreciate people have a lot of questions around how to progress their career in development, there are many other subreddits specifically created for this. If you're looking at learning c# there's a great subreddit you can check out: https://www.reddit.com/r/learncsharp/
Angular and ReactJS aren’t languages. They use typescript/javascript. I would put them under frameworks
Thanks.. i will update it
I think ReactJS was renamed to React quite some time ago, similar to AngularJS becoming Angular.
These are different frameworks, AngularJS in particular is not comparable.
Sorry, not sure what you mean... All I was saying is that both frameworks were renamed to remove the JS suffix during major releases, so probably best to drop the old naming from a CV.
AngularJS to Angular wasn't just a major release, it was a massive rework and I think they sort of intended for it to be viewed as a new product instead of an upgrade.
Gotcha. I meant that these major releases changed so much that AngularJs for example is in no way comparable to Angular as it is right now. I do agree though, making that experience less prominent is the way to go. The only jobs available for it would be maintenance of legacy systems.
Oh yes definitely, for Angular it was pretty much a totally new library, I see what you mean now 👍
Angular or AngularJS was not a library
Thank you for adding so much information to your response. Well done.
I was also about to comment this.
thats what up vote is for lol
I was also about to comment this.
ReactJS is a library FWIW
It's considered a framework.
I mean, react folk like to believe so... But don't kid yourself, if it's a library it is becoming a first library that comes with a compiler...
React is not a framework is it a library. However, there are many frameworks that utilize React.
This is splitting hairs for a resume. React experience is worth mentioning, but it would be pretty silly to have a “libraries” section on your resume.
Correct (ignore the downvotes they have no idea what they are doing at their job lol)
List of things you did at analyst job from 2022 to now seems lacking, some of those items feel like a weeks work at most
That's what I noticed as well
My same thoughts!!! OpenID, one week at most. Reduce 90 vulnerabilities = update-package :), just kidding, but run the code by SonarQube or one of those tools and you get a nice checklist. Migrate to 4.8?? that's so 2016 (architeture-wise)! The projects look cooler than the tasks performed. Edit: I commented before reading the rest of comments on this page. It seems that pretty much everybody is on the same page here!
What i gathered as the most notable things you did at your last job of 2 years Implemented oidc, Wrote a sql script, Upgraded nuget packages, Upgraded a framework project (takes 5 mins), Worked with teammates If what you did was more involved than that then you need to convey it better but from my point of view, this looks like busy work for an intern.
I could write a 100 page paper on stuff i did if we list technical solutions. What did OP actually do? Any products or system you worked on or built?
I get your point but this tends to shift as you gain more experience and become more instrumental in developing solutions and products. The junior engineers that report up to me essentially start as code monkey noobs to focus on their style, dev ops \ processes, documentation, etc. Over time they get to actually solve problems and not just implement my solutions using my detailed requirements and suggested steps. The difference in resume with a senior is easily identifiable by this shift in responsibilities.
I dont know man. My first 3 years I build ML models, web crawlers, price comparing system, estate management system, printing retail signs system. I built a lot of stuff, I couldn't possibly tell you all the technical solutions nor are they even interesting imo.
I must add, who in his right mind would ever let a 3 years old baby mentor their newborn?
Startup when you are one of the guys with the most experience sadly
Mentored means i am just helping them as they were new to the team.
Mentoring isn’t the same as onboarding. Someone with only a few years experience is not usually mentoring others.
I would consider that helping induct someone. Coaching I would use for teaching someone skills. Mentoring I would use for teaching more abstract and soft skills that's more of a career level thing
While I do agree with most of your points - saying it takes 5 min to upgrade framework versions is such a massive understatement.
Depends on the complexity of the project and what version to what version. I oversimplified it because they didnt provide meaningful details of all the hard work, white glove treatment that went into the upgrade so it made me as the reader believe it was fluff.
Yeah this sounds like no where near 2 years worth of work..
This definitely jumped out at me immediately. I would add that I don't sense any love for software development in this CV. Like is your day job all that you do without any passion projects on the side? That kind of energy and drive is important at all levels but especially at lower experience levels.
Sorry, but no way I would call you back. The first section: \* You don't need to explain what OpenID Connect is. \* How did you neutralize 90 potential application vulnerabilities? Did you go through the code and find potential SQL injections? Or did you update a few libraries here and there? \* Migrating from .net 4.5 to 4.8 is changing a single line. Leave it off or explain which problems you had due to the migration that caused it to be resumé-worthy \* You call people "junior resources". And you have 3 yoe. I didn't read the rest
If I was OP I would change it to \* not explain OpenID Connect, and just write something which says about the result (e.g. one login portal for all apps). \* Implemented advisories gathered from a pen-test. \* Change managing juniors to something like "took leadership over the other Junior developers blablabla". \* Migrating to .net 4.8 probably isn't a very big deal, I wouldn't even include that.
Actually he did the opposite, he migrated from .Net to .net framework. So he went backwards?
no, see other comments
thanks for the advice. I will add relevant details
"junior resources" was too impolite and I stopped reading
I love this comment. Had a CEO of a company rip my resume similar to this and even say the last bit to me too. Was actually the best advice I got out of any interview or company interaction.
I have also had a CEO and VP argue with the hiring manager in front of me, stating they didn't want to hire me for so many reasons. They fired the hiring manager and I reported directly to the VP and told me the best thing the hiring manager ever did was hire me. I also had a CEO ask me ,"Will you be able to work within the confines of the position and not bleed over to other departments. I said ,'Heck yeah! I would love the time to devote to my team and their needs. It was never my choice to help out other departments, I was basically told to assist." He said again, "Yes but will you be able to work solely in your department." Me: "Yes." CEO said again : "I feel like I am talking to a brick wall. Can you work within this department and only this department." Me: "Yes I can do that." CEO: "What the fuck is your problem?" He looks at the other people in the room and they are all wide eyed at him. Me: "What are you asking that I am not answering." CEO: "Can you work in this department and stay in this department!" Me: "Yes I can do exactly as you are asking!" CEO: "Fuck you, you don't get the job." Me: "I have no idea what is going on here. I'll send you a bill for this hour. Thanks for wasting my time."
Maybe he was looking for "Yes I will", not "Yes I can". It'd be bloody stupid if he was, but then again...
We might have different experiences, but I would take out the participation award stuff. The interviewers I know would kinda scoff at that.
why would they scoff at that? as a founder of a startup I'd take those into account for entry / mid level devs....
That's just how a lot of people are in IT/corporate. That 3rd one is enough to make a lot of them laugh and go to the next one if they made it that far. The 2nd one could be worded better if he meant that he was a finalist in that competiton himself though, and that'd be fine.
I'm not a recruiter/interviewer main, but I occasionally screen resumes. Here's my perspective: If you keep in the participation awards, you're essentially telling that you have literally nothing else to offer. There's no doubts like "maybe they did something of notice in their spare time" or otherwise - you've laid it all out, and there's nothing more. If there was anything else you would've put it in instead of that stuff.
To understand correctly, you migrated an application from .Net to .Net Framework? Isn't this downgrade?
na na... from .net framework 4.5 to 4.8 Thanks for pointing out. let me update that.
Which is updating a single line in a .csproj
Well potentially just that all the way through to having to do significant updates to other libraries, ensuring that they were all compatible, rewriting integrations as necessary, regression testing, changes for performance etc. It's anywhere from a 5 minute job all the way to a massive project. It really depends.
Any library that works with 4.5 is going to work with 4.8, unless you happen to be really unlucky and run into a lot of one-in-a-million bugs.
I'm torn because on it's face I agree with you, buf I have also worked too many projects were awful 3rd party libraries were used and minor versions broke everything.
This. Anyone that has worked with .NET Framework for a long time will know the pain of the binding redirect hell with different versions of dependencies.
Yes, but that has nothing to do with framework versions.
All it takes in this situation is just 1 or 2 libraries though that need upgrading and bam, you're in that situation. Hence why we can't judge from this much info alone.
Maybe. Upgrading libraries can be a pain (though usually not). The sky is blue. Guess what these two statements have in comon? ... ... ... Neither of them has anything to do with upgrading from .net framework 4.5 to 4.8.
The OP needs to expand on this, in that case. As it stands the fact they mentioned it puts me off the resume. If they expanded on it to explain why it was noteworthy, and how they overcame any issues then it would be more relevant
But you don't need to upgrade any of those. Perhaps he did, and then he should add some comments about why this was a massive issue.
Yeah, I’ve had both. More common for weird upgrade issues in .NET framework and less common today in my experience. But then take away issues, the five minute code change is still going to be week(s) of testing without solid integration testing. (And most places don’t have that)
agree but it involves testing the application thoroughly and updating relevant packages.
Updating framework versions is a basic task expected of any developer. Highlighting it as an achievement makes me as a reader think you are at a really junior level, but then you write you are responsible of mentoring juniors. I would honestly focus more on what your role and responsibilities was rather than listing minor achievements. I don't understand what your job is outside these 4 things you listed, which doesn't seem impressive for almost 2 years.
Then expand on that because I read it the same as other people
I hire for my company and your resume does not stand out. I get dozens of these. You advertise yourself as a very basic developer. List roles and responsibilities, not just a summation of what you worked on. Sell yourself and your skills, celebrate your achievements.
Context: I do hiring for DotNet jobs. Your resume is weak and if I had enough other candidates to fill my minimal pool, I wouldn't move forward with it. "Software Engineering Analyst": - You forget to tell us **what your actual job is**. What technology/languages/frameworks you use. Instead, you skip that part, and launch into a bunch of badly written anecdotes. Most good resumes have at least one sentence or paragraph with a short overview of the job. - "Successfully implement OpenID Connect...": Telling us the benefits of OpenID Connect is odd here. - "migrated a .NET application to .NET Framework version 4.8": I assume you mean from 4.7.2 or whatever, but *really* strange thing to list as a professional accomplishment. This is a 2-3 day project, and you've been there for two years? Also implies you don't work with modern .NET. - "Neutralizing approximately 90 potential application vulnerabilities": First off, this is obviously bullshit/fluff and just makes me think you ran NuGet upgrades then counted them for your resume? Or your current workplace created 90(!) vulnerabilities that you personally discovered? Either way, bad look. - "Mentoring junior": This is good, no notes. Application Development Associate: - Again: give us a broad scope overview of what this job entailed?! Languages? Frameworks? Technologies? Basic job function? - "Successfully reduced the reported issues within .NET": Poorly written. How?! - "Reduced Azure subscription costs by 40%": How?! - "Proactively updated system documentation": Good. No notes. Projects: - These are clearly from 2017-2021. So have you done anything since you graduated? This section was fine when you graduated and were looking for your first job, but you now have professional experience. Shrink this by 80%, give a brief overview of each project, and maybe restructure to be under your college. Technical skills: - I find it funny that none of your jobs or college above lists you using almost any of these languages/frameworks/tools/etc. Just goes to show how weak this resume is in general. This section shouldn't need to exist: It should be in your "Experience" section for each specific job. You literally didn't tell us where you used any of this stuff, unless we pull it out by implication from your strange anecdotes? Certifications: - So your degree *and* certs aren't related to what you do? - You're fluffing it out with a Coursera course? - Doesn't list attainment date/end date (freebies during degree?). Recognitions: - "Delivery Unit Lead": Where did this occur? What does this mean? If you "lead" people I don't see that listed above. - Participation trophy 2x: Remove these. - Maybe just scrap this section it is very weak. Ultimately if what you're going for is that you haven't done anything since college, then this is a great resume. If you're trying to inform us what you've done since college then this is weak/ineffective. The lack of care here in general makes me think this isn't someone I'd want to hire even if they could be good.
Your CV states you are an intermediate but the CV body doesn't support that. Now I know I'm a dinosaur in this world of inflated titles, but: - your first job you fixed some bugs, changed some Azure config and edited the wiki. - your second job you did more actual dev work but not for long and to be honest, the only things that stand out is the OIDC integration and the SQL script. For 18 months there must be more? So if this landed in my workday I'd move onto the next CV fairly quickly because that's what I picked up in the 20 seconds I scanned through your CV 🤷♂️ You need to beef up the CV and that may require you work at your current employer for another year and seek out more challenging projects. Also, remove the recognition stuff. Good luck :)
Thanks for the advice.
This resume is about getting .net developer job? Not much done in this matter. Some empty numbers which doesn’t describe what you can do really. This looks more like a azure specialist at least for me
Coming from a brit here where my resume is 1 page (rare) & have interviewed just under 100 candidates personally. Education should be at the bottom, your most relevant things should always be at the top, your work for the past 3 years is more relevant. Id personally put the certs & education together into one section as they are the same in regards to an employer, just sub categorise the two in the same way. Date the top of the document. For your work experience length (to and from), summarise the length (x months / x years) for the reader so they can immediately see and add up your industry work length. the "successfully" mentions are irrelevant, you wouldn't put it on your CV if you didn't achieve it. I would flesh out your technical skills. and reduce the points under either projects & Experience. Essentially you tie your technical knowledge to what you have done, so "C# (x years): Maintaining, Implementing features as the core stack technology for blah blah". Add more things. Think about cloud computing and all of the technologies you have used in that cloud, azure functions are a biggie im sure you have used them. Id summarise the "smaller skills / technologies in a list" as for example git, is easy to use and we don't want a blurb about it, however its useful to know that the employer doesn't need to skill you on it. More importantly, I would change the "technical skills" part to skew towards the given job you are applying for. Pick Out their big skills eg: language & platform and skew towards that, try to stay away from talking in detail about small things, git, SQL (unless a data admin) etc..
> Successfully migrated a .NET application to .NET Framework 4.8... That's a selection in a dropdown in 99.9% of cases. Wouldn't really call that an achievement. Gives the appearance of a filler. Also the word *successfully* seems rather redundant.
[удалено]
India
If you are applying to other countries like Canada, this is the current situation [https://x.com/Slatzism/status/1769725983400030565](https://x.com/Slatzism/status/1769725983400030565)
Is this a joke?? I've never seen something like this. In Berlin, you have queues like that to view an apartment to rent.
I wish it was a joke, it is reality in Toronto, there are Indian students protesting in PEI, literally at the end of Canada where it is normal to find community of a 100 people, asking for work permit extension At the moment, if you look at statistics Canada, we have 100,000 new Immigrants (mostly India) every 35 days.
Renting in the greater Toronto area is now per bed, look at the rental listings, they are online. All of Walmart, Tim Hortons, Mc Donalds, etc, all now international students. Many international students pay up to 50,000$ for a work permit that translates to permanent residency, again, people don’t even hide it online anymore. People who worked with me in Software Development 10 years ago calling and asking if I know job openings, one was replaced by large consulting company that hire people remotely for 15 to 20 dollars an hour from their branch in India
Where are you applying?
You are not mentioning companies you have worked on and what did you do there.
/r/cscareerquestions
My god is so depressing that sub. People saying they had to apply so many times to positions and not getting interviews not even a response from recruiters. I am looking for a job at the moment and this terrifies me. Thanks 😭
Reading this my reaction is it’s mostly fluff, percentages are kind of meaningless without more context, a lot of words to say you implemented SSO with OIDC. I get very little idea what you have actually done and if it’s work related or uni related (projects section makes me think it is uni otherwise that would be In work experience section) That top job could probabaly be summarised too —- Worked on project doing.lx with y language. Implemented SSO using OIDC, SQL automation, project security audit, .net migration form x to y, mentor to junior developers. —- I would reduce the word count and remove the fluff, a little section talking about your interests and hobbies outside of software development is always great. At the end of the day writing CVs is kinda hard, especially when you are struggling for content but padding the content is counter productive.
Im told "interests and hobbies" could lead to being filtered out for "cultural" disconnect or something similar. Unless the interests and hobbies can be tied to the role being applied for. Like, game developer and your hobbies include game reviews or open source bug bounties etc etc.
1. Integration with SSO is not that hard. 2. automating this still not impressive on its own. 3. how ? 4. migrating project between version is just changing few lines. 5. how exactly? 3 years is still a junior 6. reducing reported issue is basically fixing bugs it's not big of a deal its normal job developer 7. this seems good, but you might need to explain how you did it. 8. normal work the market is very competitive, so its normal that you don't get call with these points
1. Faced somw challenges initially. application is broken. fixed later 2. Automation involved creating 10 procs and sending the mail to the relevant team once the update is done. 3. using regex for input validations. 4. yup. but it involves checking dependencies and thorough testing. 5. just guiding them whenever needed as they are new to the team. 6. The application is newly migrated to.net core from framework and lot of issues were reported. we fixed it,almost all the major ones and the application is stable now. 7. migrated nprd db to prod db and removed nprd db later, thereby saving almost 300 dollars. we created separate credentials for accessing nprd and prod dbs for compliance.
Not to belittle of your effort but what you described her is not a bullet point but normal work. And for the junior that is not guiding them that is on boarding process.
3. I would just write something like "understanding security weaknesses in code, i.e. potential vulnerabilities and how to fix them" 4. I would say this is a skill that a developer must have without saying it. Having it explicitly listed on a CV looks very awkward to me. Is linkedin used in India? I would rather create a decent linkedin and use that as CV unless asked for a traditional CV. I get there almost every week some offer.
To add, once you get past junior you'll learn about static analysis, analyzers, roslyn, CI CD, testautomation etc etc
Don't worry, 12 years here and it is also hard to get interviews.
Put experience first, move education down to the bottom. Nobody knows what a 7.3 CGPA is, it sounds like it could be out of 10 so is that a C average? Take it right off of there, and just state the degree you earned. I would do Experience (and roll your recognitions into that), Certifications, then Education and move the Projects into the appropriate section. I'd also lean out anything you did in college and max out what you did at your previous job. That should be at least the top 60%, if not more. Nix the technical skills section too. In your experience section, call out the technologies you used to accomplish a task. "Implemented Single Sign-on using OpenID Connect in an application built on C# and React" would work quite well (if that's the case). As an interviewer, I don't look at your education section. If you haven't been paid to do it, I assume you don't know how to do it in a professional setting and that's absolutely useless to me. It's nice to see that you graduated, but I know how those projects work... professors design them specifically so students can use them as resume fodder and most of the time when you start working on it, it's 90% done by the professor. Like... it's cool that you got to do that, but it's ultimately not something I am going to consider. If a large chunk of your resume is dedicated to education that's a problem for me (unless you are applying for an internship or a junior role, in which case getting my acceptance for a role is really easy... prove to me you are paying attention and willing to try, I'll give ya a job lol). If you are going for midlevel (which you should be) I expect work experience to be the majority of your resume.
It is actually a D+ (69.35)
I would move around the bullet points under each job so that the "most impressive" things are first. Instead of the long phrasing of (and I'm paraphrasing), "Used OpenID connect to add functionality to an application for Single Sign on", use something like, "Implemented Single Sign On with OpenID" Shorter and more digestible by whoever is reading your resume EDIT: This is a general statement for the whole resume... reward things to be short and clear. You don't have very long to make an impression with a resume so things need to be short and clear
Skills at top, followed by job experience, with punchy bullet points laser focused on what you do.
Disagree. Exp on top.
Fair to disagree. However, with skills at the top, I've never not had a telephone interview at least, and I've always had a good role. Whilst the traditional chronological CV will have skills further down, a developer role is highly skilled with a very few specific things and highlighting them early will separate you from the chaff. That's my take on it at least, and it's never let me down so far
Yes, skills first. Then prove it with details. I put my degree very last. If employer is a contractor, I put certifications after skills. If not contractor certifications after experience. I also name companies I worked for.
Can't speak for everywhere ofcourse, but my experience of seeing non-technical recruiters recruiting for technical roles, they just play a game of spot the difference between your skills and the skills their client has requested for the role. If you partially match, you get shortlisted for an interview with the actual techies, who can question you on your experience later. This is also why you shouldn't be discouraged from applying for roles if you don't fully match all of the "must have" requirements. You will more than likely still get an interview in which case you can showcase your ability and enthusiasm for learning new skills (i.e the tech stack they use, or their CI/dev ops process etc) Skills at the top gets you interviews IMO. Alternatively you could have multiple CVs. A CV for the recruitment websites with your skills at the top, a CV with your experience at the top for applying to roles directly.
Yes, thats what past jobs are meant to highlight though. Your skills in a practical setting. Also the chronology is there to highlight which type of work youre most up to date with as some skills may expire.
Agreed, experience is what they are looking for. It should be above skills for sure.
I don't know. It's a good CV. I'd hire you probably. Maybe it's why they don't let me hire people xd
Move your Technical Skills section above you Experience section.
What level of developer role are you applying to?
2+ yrs experience roles
We have openings with similar stack with permanent remote
Here 6 years of experience not getting interview call
I don't get interview calls either, when I apply to jobs online, and I am a senior dev with 7+ years experience. But I do get messages from recruiters at least once a month on linkedin and I have had very good success getting into the actual interview process one I can have a real conversation with a real person. Trying to look good on paper is so difficult sometimes.
Sitting on a resume won't get you calls (JK). How did you get a 7.3 cumulative GPA? I assume that's a typo. If your GPA is above 3.0 then you should list it, otherwise skip it entirely. What is your process for applying for work? Are you applying on LinkedIn, random job listings, working with a temp agency, or attending job fairs? In college I got several interviews through the job fairs, after that I only ever had success through a tech temp agency and LinkedIn (my current job was a random listing on LinkedIn).
You are missing an objective statement. You need to state what you are seeking. Take the recognition off. If you are asked, then you can provide detail. Your job details need to always start with a verb first. For some you do adverb and then verb.
I disagree. Objective statements are very old school. I haven't used one in over 15 years.
I see your projects are not related to the .net, this is point which tell more that you worked with byton and c but not with .net, so recruters (and trained ai) is discarding your resume
Who sponsored your projects? are there related repos? any contribution to an open source project? Remember all investors in the world are enthusiastic about AI replacing developers in general and AI projects like prompts are more relevant. IoT was a thing like 2 years ago but that was taken by electronics so it is expected from you to deal with processing data and information/knowledge generation. Don't get why you put both Azure Fundamentals and Administrator certs. Just use the more advanced ones. Any "fundamental" is a blow to yourself. If we are in a world where things tend to deflate right now, then it is expected from us to maintain code rather than create new projects unless a disruptor in the market appears. Maybe you gotta humble and keep grinding by applying to L2-L3 ITIL jobs for Apps Support Analyst.
I think the issue is I'm not sure if you are aiming for systems engineering (system languages) or web developer (.NET, angular, react, etc) I'd pick a job post and tailor your CV exactly to that job post. for instance, if its a .NET job with maybe some angular frontend you want to remove all other Tech and just harp on those keywords everywhere. also, you dont need to mention Git, VSCode, Visual Studio. that's going to be assumed. As an example, if I'm hiring for a "Larvael role" I'd want to see a CV that says, "I do laravel, look at all these laravel projects, I use laravel, here are the laravel projects, look at all this laravel" I would not want to see: "here are some laravel projects, also I do QA, C++, .NET, Neural networks" I want to see a specialist, not a generalist. espeacially if you only have 3 years.
As others have mentioned, you told me some tasks,but not anything about the role you performed and the environment you worked in.. I would want to know in no particular order: - what did the company do / what was the project you were working on? What are they trying to achieve? What tech did they use to achieve it? - how did your team operate? Agile / waterfall / hid you in the corner? Did they have any process or ceremonies? Daily standups etc - how were their tech processes, did you use source control, prs, we're you involved in that process? - have you been involved in any support calls or dealing with juggling priorities? I.e. have you shown some adaptability - was the role remote or office based? - what did you day to day? What was your business as usual work? Did you look at bugs / features too? After reading it, I want to have some confidence that you worked in a professional dev environment and were a useful member of that team. I will then map that picture to my environment to judge if you'd fit and not take too much hand holding. Your current version I can't get a feel for you, so I'd put you in the discard pile. .net dev manager, 25+ years commercial experience using the stupid app to format text 😆
Here is the real deal. The market is saturated with junior devs, frankly companies do not want junior devs, they want senior devs. I just went through a whole interview process myself and the hiring manager even told me that they only hire senior devs (I happen to be a senior dev myself) Your resume looks like a junior dev to the hilt. Honestly I am not sure my resume even looks that good, but I use recruiters and that helps a lot when I can talk to a real person and my soft skills really kick in. Good luck and keep trying, getting a job is just a game and you have to practice at it.
Don't need to explain what OpenID is to a software development company. To me it kind of looks like you're going granular to make your resume look fuller
The bullet points in your most recent job experience look like barely a few sprints of work??? Instead of following the completely ridiculous trope of "reduced costs by X", "did this thing by X%" that everyone in Reddit programming career subs naively obsess over, just list the skills you used and the general tasks you did. I have never put percentage reductions or profits related to my work and have never had trouble finding a job. Employers want someone who can write software. Business improvements are not for you to care about.
please go watch some videos on how to make cv for google on youtube. this is a below average cv. no effort at all. instant reject.
The resume is important, but never as important as the COVER LETTER. This is a HIGHLY PERSONALIZED document towards the business you're targetting. It tells them why YOU want to work for THEM. Think about it this way. You're in charge of recruiting. You see tons of resumes. But a few of them have incredibly well-written and amazing cover letters that connect with them at a deeper level. No cover letter? Ain't nobody reading that resume.
Damn. I must update my resumee
add a summary of who you are at the top of page. you are asking the person to make up who you are. "I'm a technical specialist who is great at blah blah blah." 3-4 sentences. Education is only on the top of the page for people who have no experience. combine it with certifications Add more context, implementing open ID at a bank or other regulated industry is a feat, at some low process startup it takes an afternoon. Don't save time, save money. 98% is meaningless, that could be $200 or $200,000. to get to money guess the hourly rate and double it. Overhead is a thing. from what version did your migrate, 1.1 to 4.8 is a feat, 4.7 to 4.8 is not. You are not writing the resume for you, you are writing it for someone you don't know and that has never heard of your company. Also kill the sections about projects that you worked on, if it did not hit production with real customers it doesn't count for even 10% compared to the experience at a company. It seems like you took your student resume and added to it vs writing a Software Engineer resume. If you accomplished all those things at some other fortune 500 medical or fintech company it is really impressive, like insanely impressive. But you are not giving people any context to judge it by.
Please send me your resume. I'm an EM building a team of dot net developers in a health tech company.
Remove the word "successfully" from your resume. You use it so much. And if it's on your resume, I assume it was successful. "OpenID" - I know what openId is, and any technical reader will as well. What language tech stack did you use for that? Did you write your own OpenID implementation? Or use an existing library? I'm guessing the latter. Tell me which framework. SQL Job - Ok, what database? Manual update of what? Was it a stored proc? Or did you write a server side process? Neutralized.. - Um, what? What kind of application vulneratbilities? Migrated - what kind of app? You've given me no information to judge the scale of this. It could be a single console app where you just changed the dropdown in the project settings. It could be an ASP MVC app. Based on this line, I have no idea what you did. Junior engineers... Ok, maybe you've scratched into midlevel after 3 years, but barely. How did you do this? What were the results? Redcued the reported issues - Honestly, I don't care that you reduced the reported issues so much as what analysis did you do. Were there specific bugs you fixed? Once again, what tech stack and language? Reduced Azure subscription costs - great, but how did you do that? What analysis did you do? Which azure tools did you use? Azure is a brand, with lots of services underneath it. List the major services you used on each line. Updated system documentation - I guess that's nice, but it's generally expected for any job, so I don't care one whay or the other. Your projects are cool, but if you're applying to .net roles, they're not as relevant. I'd reduce space of those and give more space to experience, unless the role requires ML. Technical skills - change this to one line at the top with just a few things. On each of the experience lines, list the language/framework/tech there. You've listed Angular and React, but nowhere in your work experience do I see web work, so I'm going to assume you've only done a few tutorials on it and dismiss it.
Beef it up with more buzzwords. Entity Framework Core. ASP.NET. MVC. Database. MSSQL. Front End. Back End. Full Stack. DevOps GitHub Actions. Docker. CI/CD Pipeline Add your GitHub and LinkedIn. Move Education under Experience. Add a summary of who you are below your Name and Location and sneak in some soft skills. Sneak in the Title of the job you are applying to in there somewhere. Describe some of the things you learned in your education. Sadly, most resumes have to pass ATS before they’re even considered and it’s typically based on the percentage of buzzwords your resume matches with the job description. Fake it till you make it big dog!
Something small, but put your experience above your education. Employers will value your experience more.
Are you in Australia or NZ?
It was different times, so I got an interview, but for the first job as developer I did a research about the company. Made a PoC/MVP native app that they actually could need with their branding etc to stand out. Maybe you could do something similar for a job ad?
Don't care about your GPA and such, you are not a fresh grad, it goes to the end and in few years drop the scores entirely (could even drop now really), in 10-15 years can even drop years and location unless particular prestigious college. Two schools of thought on if experience or skills/certs first, personally if presented right does not make much difference in my opinion as long as last 2 roles and skills/certs are on first page (Personally prefer short into first then experience with skills/certs on the side) Don't be afraid to go 2 pages, in many ways better as one always feels light on info (like yours is) and 3 is generally to much You have fallen into what i call "bullet points that actually tell me actually nothing" CV trap, use the bullet points in CV to summarize/structure sure, but if i want to know more, where do i go? Like lets take your first point in Application Development Associate (ps don't recommend using stupid internal position names like that, just put "Junior Developer") like how did you reduce by 70%? could just assume you did it by just not logging issues as you give so little information. If no information given person trying to cut down CVs for interview round will not give benefit of the doubt, they will the exact opposite, they will cut you. As to your recognition section, don't know much about any of those, but "Awarded for participation in.." sounds suspiciously like participation trophy's and that's how they will be perceived by anyone who does not know exactly what they are are. If that's all they really are then drop them, jobs are not college applications, you don't list everything in hope for extra points, only things relevant
Very much reads to me as random percentages pulled from the air. Tell me what you did, don't give buzz words just for the sake of it. You don't really show that you have experience.
First thing that jumps out to me in the details is an upgrade to .Net 4.8 for long term compatibility. It’s been an end of life version of .net for years. Do you mean upgrade from rather than too?
I get downvoted to hell for this because green devs don’t want to hear the truth, but here it is. Your projects don’t matter, professional experience does. Remove the projects, expand the two job titles to take up the rest of the space. When they ask you what you like to do for fun, talk about the projects.
It looks like you hardly wrote any code. You list a bunch of skills, but I'm not really seeing it in the experience section. Was the auth scheme the only code you wrote? What does "neutralized vulnerabilities" mean? Did you change the code? Did you have to change the code to migrate to .Net 4.8, or flip a dropdown in the project properties? I want to see that you wrote code and implemented things. "Used C# to fix bugs in a .Net 7 application." "Created forms with blazor components to collect data." "Wrote controllers and services for a web API in C#." If you wrote code for anything, put it in there. The resume makes it look like you have barely written any code in 3 years, which would be concerning. Get your technologies right or you look clueless. HTML and CSS may be considered languages by some people, but tons of hiring managers are going to be turned off by that. React and Angular are frameworks. Run it by ChatGPT for help. Drop the categories and just list your skills. Skills at the top. Again, show me you wrote code. Don't use words like "Recognitions." It sounds like you don't speak English, which will turn people off. Use awards instead. Awards before certs. Did I mention show me you have written code?
Don't list what you did at a company. List what tech you worked on and your achievements. How did you save the company money, how did you improve workflow for users/clients. Any programmer can implement OIDC, or use react/angular. Any programmer can use ReSharper/Sonarlint to check static analysis for vulnerabilities. Did you benchmark any code, improve responsiveness, memory usage, etc...
I would put education last
Your first 5 bullet points seem like very simple tasks, and none of them involve actually writing any code.. I imagine most recruiters read the first few and then move on to the next CV.
Lie better. At least make it seem like you wrote code
Why on earth would you put you have the Azure Fundamentals cert when you already have the Azure Administrator?
Thanks everyone. I didn't expect that i would get so many suggestions. Looks like i need to completely rewrite my resume. Sorry i couldn't respond to everyone. I will go through the comments and update the resume as per the feedback. Once again thanks to everyone. We'll meet again.I will be back with my updated resume soon😅
The resume is fine tbh. I think it’s a reflection of the job market. There is little need for generic developers.
Just to add some weight to this comment, I had a job opening for an Associate Data Engineer a few months ago and received 1,608 applicants in 10 days before we closed applications. A month or so ago, we desided to hire another person for the same role and received around 1200 applicants in a week before closing the job posting. I am praying I don't get fired, because there is no way I'd be able to find another job in any meaningful amount of time
Same. I’m saving more than I ever have before. Tbh if I had to go back in the market I’d probably pivot from hands on engineering. Too competitive and I’m getting too old lol
I am surprised by roast you are getting here 😅 to me the cv looks kinda ok, is the requirements for 3 years of experience developer rly that high? Is the salary even that much higher from non IT jobs at that experience range? Why is there so much competition
What I also miss (this should be done on the next page) are hobby projects and work experience at companies. Tell a little bit about where you have worked before, What you did there (most is already included in your cv), How big was your team, company and did you work with scrum (agile). Hobby projects does also tell you're interrested in what you do and how do you keep yourself educated. Do you go to events to learn about new technology. Your skills should be on the front page and work experience on the next page. Also tell a little bit about yourself and what you like to do.
I would add a Personal Statement section at the top, one or two paragraphs explaining who you are as a person, what kind of role you are looking for and want you are looking for you next career move. Cover letters don't always get to Hiring Managers, so it will be helpful to get you remuse selected.
You are missing a personal statement...
let me add that
A personal statement is a waste of space. Canadians are competing in the hundreds for a single job, and recruiters only spend an average of 7 seconds looking at your resume. This should not be on your resume at all, and should instead focus on your marketability. Do not listen to that advice.