New answers tagged interview
1
I think you're really asking two questions:
what salary should I ask for
will testing be a good career path for me
I'll attempt to share a bit on both of these:
1) I was in a similar position a couple fo years ago and the way I decided to go about it was I figured out what my monthy expenses were, the sort of bare minimum I could sustain myself ...
6
US Interviews broadly consist of two approaches:
1) Test the applicant. Test their knowledge. Push them on algorithms. Test CS fundamentals. See if the candidate can defend themselves when pushed. See if a candidate can think clearly during the interview. This is used for over 90% of interviews (even at the manager level). This sort of interview is ...
2
First of all, let us assume my skills and experiences more or less match the position I'm applying for. That means that if for example, job postings are looking someone with "skill A" I don't possess and have not even heard of are of the table.
Second, I look through my CV and try to systemize what have I done and what have I learned at previous jobs.
...
10
There are many factors that come up when interviewing someone, the main things an interviewer would be looking for would depend on many factors like the role, experience, team size, Job description etc;
Some of the most generic things that an interviewer would be looking for are:
How passionate is the candidate about the quality and the overall quality ...
4
When I prepare for interview I'm trying to structure nearly everything I know. All the technologies, methodologies, all my experience and achievements. The good way to do so is to use mind mapping tools.
This technique allows to make an overview of your career and decide what could be important for the job you're trying to apply and what could be not.
...
0
First understand that there is no software in this world with zero defects when comes to production.
Stop worrying about yourself or team that bug went to the production.
Find what kind of impact did the bug done in the production.
Do a clear root cause analysis.
If the bug impacted huge, check whether you need to role back the release to previous one.
check ...
0
Bugs are found in prod all the time. Especially when the time to market becomes a race and the focus of testing lies on the little time given rather than the application. So as testers we need to leave our ego on the door and do our best with the tools and circumstances we're given.
First, understand that testers don't own bugs, so don't take it personally. ...
1
I am surprised to read that everyone is talking about tester/QA missing the test case. Most of the time, its the requirement issue. I have done the research and even the data backs it up, around 30% of the time, it's either a missing requirement or ambiguous requirement and many times, developers don't even ask questions before implementing it.
Consider QA ...
Top 50 recent answers are included
