Any one have the idea about the short list the good QA CV and identify the QA applicants.
This can be automate or manual testing . Can i get the tips for this activity.
4 Likes
What I like most about resumes is LONG resumes. People often think a 1 page resume is the thing to do. But I totally disagree. I very much like a longer resume even if itâs 20 pages.
What I look for in a resume is peoples skills, methodologies and technology that theyâve used in a project as well as a small summary of the project itself and what the company is about. I want to see peoples challenges and realizations in their resumes. When I read the resume, I want to feel how proud they are of their work experience there.
A nice addon would be to see their goals/ambitions in their resume. Normally I always ask this in interviews BUT if they have it on their resume, for me, it only makes it more clear of what the person wants and it shows ambition and that theyâve thought about it.
4 Likes
This is the different perspective now days single page CVs most of people using
1 Like
Yea for sure! I work as a consultant for a company and I often do smaller projects also. If I have to list them all on 1 page with all my skills and technologies used⌠: / Itâs going to be written in Font Size 5 
1 Like
I donât think we can answer this question without more context. Youâre asking for a short list of âgood QA CVâ - we would need to know the role being applied for to comment.
As for CVâs generally, in my opinion a CV is just merely a âdeclarationâ of where youâve been and what youâve done. It should be brief, and only contain stuff that you believe to be relevant to the job youâre applying for. It should be enough to get you through the âfilterâ of other job applicants, and you should be prepared to talk about anything on that CV.
A good CV should be accompanied by a cover note.
Anyone can put anything on a CV, but the cover note is where you bring it all to life. Your cover note is what you should use to explain how youâve worked, what interesting or challenging projects youâve been on. What inspiring people you worked with and what practical skills you learned on the way. You should be prepared to be able to talk about - at length - whatâs on your cover note and it should of course again be geared towards the job your applying for.
2 Likes
I disagree with this to be honest, if a person has done X or Y on a project, itâs good to shine because a company might say we need A or B but in fact they could really use X or Y but they just donât know about it 
Itâs nice to see peoples skills imho
3 Likes
Regarding A good cover note i will agree with this some times we will get 50 CVs per day so filtering the CV based on cover note
1 Like
Tips for a good CV
- it is concise (1 or 2 pages at most)
- it includes only up-to-date info about technologies and skills. Not that tool that the candidate used 10 years ago for a few times
- each job description has a clear definition of what candidates have actually done at the job, not what were his or her daily tasks. Done here - means that there are achievements with more or less clear measurements
- if candidate has it - a link to Github or Youtube with the recording of talks
2 Likes
Some skills are not always appropriate to list on a CV when youâre applying for a job⌠it really depends on how you want to present yourself to that place.
What I didnât say is that your CV should also have links to any professional sites youâre on - such as Linkedin, or your own website / blog or even your git profile⌠and this is where you showcase ALL your skills.
3 Likes
From the companyâs point of view they should have thought ahead of time what skills and behaviours are important for the role. Then this info is summarised in the job advert (in the form of a job spec and/or person spec).
So a good CV is one that makes it easy for the reader to see that youâre a good match for the required skills and behaviours. Just matching them isnât enough - you need to make it easy for the reader to see this.
Thereâs a bit of an art to this - just throwing more words at the problem might backfire, because the reader might give up before getting to the good stuff. What do you think is most important to the reader? Make the words for that really easy to read - towards the top of the CV, etc.
Some things might be just a matter of âI know Xâ, but much of the time youâll need to provide evidence. So, not just âI can testâ or âI worked as a tester on team X for this date rangeâ but âI was a tester on the data integration team. I advised developers on how to improve their automated testing, which brought test run times down from 45 minutes to 14 minutes with no loss of quality. Through conversations with product owners I found potentially costly bugs before implementationâŚâ
This is sometimes expressed as what â so what? The âwhatâ is a bit of information; the âso what?â is why itâs important. What = âI worked as a tester on team X for this date rangeâ. Why is this important? Because I helped the developers, found bugs etc.
If you point to things outside your CV / job history that help then do so. Other people have mentioned this - things like a GitHub repo, blog etc. Also any hobbies or volunteering etc. you do - if they provide evidence of things that are valuable to the role, then include them and make it clear how they are relevant.
Because of all this ^^^ a good CV is often customised for each application. As a job applicant it can help to have a document that has a library of all the bits you could include in a CV, and you pull from that for each job application.
2 Likes
I will vehemently (but respectfully) disagree. Iâve personally never seen a resume longer than 2-3 pages that wasnât chock full of unhelpful âfillerâ and repetition.
Thatâs totally fine, I think it differs from country to country also. Here in Belgium there are many test/qa consultants who do 3-6-9-12months projects with different clients (sometimes multiple at the same time), so itâs all we see here.
Itâs defo not a filler since itâs just a listing of peoples experience.
Iâve looked at hundreds of CVâs in the last few years, and for me, too many words or pages are noise. I like facts based, bullet pointed lists of the roles youâve had for how long, with what technologies, team structures and responsibilities. And honestly, I donât like tailored CVâs, send me your LinkedIn. I want to know the whole person, not the person you think I want to see. A cover note is fine, but not necessary.
But, my hiring process makes this all very easy. Candidates take an online ability test as step one, if they pass I take a look at the CV to make sure the basics are there and have a 30 min unstructured phone chat with the person. The CV is a useful conversation starter for the individual to tell me about their roles.
So really, I think that as a hiring manager, you have to decide what is a good CV for you. My perfect CV is going to be very different @kristofâs, but thatâs fine. Life would be dull if we were all the same 
Probably easier to identify a list of red flags with a CV starting with Comic Sans⌠
2 Likes
Same! My resume is what it is. Iâm not gonna put key words from the job app into my resume either.
My LinkedIn profile is pretty bland though. So resume it is
Yea totally fine, I do believe it depends from person to person and company to company and country to country.
Iâm a consultant and if you are hiring a consultant with only 1 or 2 projects. It doesnât stand out to me, more as in âhe doesnât have much experience in different environmentsâ.
But as you said, totally fine and context dependent!
Amen
1 Like
I wrote about this in Hiring a Software Tester, an Analysis and will be doing another publication on the subject soon.
The short answer is it depends. The only way for you @kayu to understand good CVs and applicants is for you to try it yourself, learn and optimize. It will very much depend on your context and who / what you are hiring for.
In the article I published, I work in a startup environment with mostly modern testing practices. We were product based, not project based. I also got a lot of applicants. Given those constraints, I need resumes that are easy to understand. That means long resumes are too confusing and donât make it to the interview stage.
Some people must like long resumes, I see them a lot with contractors and/or people working for contracting companies. To me thatâs all fluff and doesnât tell a good testing story about what youâve done.
1 Like
I like it when people offer links to their other works: LinkedIn, GitHub, blog, etc. That provides a much more complete or well rounded view of who they are. Iâll take the time to glance at those things in addition to the resume.
I actually given candidates an initial / step one âscreen emailâ with some questions. What is the ability test you give them them?
Yes give analyses give more inside i think it depend on our requirement we have to shortlist the CVs
things like a GitHub repo, blog etc. Also any hobbies or volunteering etc. you do - if they provide evidence of things that are valuable to the role,
This would be valuable screening mechanism , We are using on this
I thought weâd got away from the covering letters, especially with applications using websites and linkedIn more and more. The tailored CV doing some of the work the letter would have done.
3 Likes
Some job postings may not require them. It also might be different if youâre working with a recruiter for your next role, as they will be able to convey your personality and motivationsâŚ
âŚbut otherwise just a CV on its own, does not tell your story like a targeted cover note can - hiring decision makers donât have time to trawl through professional social media sites for candidates - they want to know why youâre applying and what makes you tick.
1 Like