I just got a Warning letter for poor performance

I joined a new company as an Associate QA engineer and almost 70% of the developers are juniors and there are no project managers and business analysts. Every time the client decides on the release date and clients directly contact developers (for more than 5 years this how they have managed projects).

And developers release on time with lots of bug without basic tests. I send lots of emails regarding this but no one replies after 4 months I got a warning letter its mention

  1. not build any QA progress
  2. client complains
  3. not tested any function

Actually all records are in gitlab and with out checking gitlab they issued a warning letter. How to tell my boss it's not my fault team leads don't care anything warn team leads

  • 3
    So if I understand correctly, you're saying that your'e being blamed for poor testing when the developers simply bypassed QA and you never got to test it? – Keith Jun 26 '19 at 13:10
  • 1
    yep but i test and add bugs in gitlab – GHOST Jun 26 '19 at 13:11
  • 1
    So you logged bugs and it got released with bugs that you found? – Keith Jun 26 '19 at 13:12
  • 1
    "they release on time but client check few days after in that gap i test " So, instead of QA being in the release pipeline, it's a parallel process? That's confusing. – Sourav Ghosh Jun 26 '19 at 13:13
  • 1
    @AndreiROM I wouldn't jump to conclusions of low effort; OP's mistakes seem like the kind that occur due to low familiarity with the language rather than laziness. – Southpaw Hare Jun 26 '19 at 15:11

When you raise the issue to your supervisor or other management, you can maximize your chances of having a productive discussion by being focused on potential solutions and avoiding blaming or complaining.

Develop a specific solution proposal and bring it to your manager. Make it clear you believe the root cause of the issues being noticed by the client is a lack of a test plan and controls around QA. Offer a suggestion of what the test plan and QA controls should look like and who is responsible for being sure they are followed.

Focusing on resolving the issues perceived by your client is probably the best way to convince your organization that the problem isn’t amongst the developers and to address the warning letter. Avoid getting defensive, blaming others, or complaining about the current situation.

Best of luck with the situation. It sounds like it could take a long time to rescue the project and even longer to help your organization see what is really going on. Being persistent and cooperative in developing a solution will be highly valued and appreciated.

  • thank you but we have 7 seniors members more than 7+ experiences but they act they are working but even they don't know how to fix simple CSS – GHOST Jun 26 '19 at 13:20
  • So the issue is the developers? What is the message you’re looking to get across to your organization’s management? – Jay Jun 26 '19 at 13:22
  • need test plan and developers should pass QA process – GHOST Jun 26 '19 at 13:23
  • 1
    Okay - apologies, I didn’t fully grasp your question. Thanks for the clarification. I’ve revised my answer. – Jay Jun 26 '19 at 13:24

You need to have it documented that your bugs were found, and ignored. Don't be afraid to speak up. If the boss doesn't accept it, you may need to go above his head. Or, I don't mean to blame you in any way, but you need to more assertively put it back on him that QA is worthless if bugs are ignored. If you got a warning letter, I'd refuse to sign it, take it to HR, or take it to his boss.

  • thank you i try to tell what exactly happen but they said do not pass ball accept its your fault :( – GHOST Jun 26 '19 at 13:21
  • 1
    @GHOST Are they saying it's your fault that devs didn't fix the bugs you found? – DaveG Jun 26 '19 at 14:43
  • @DaveG dev didn't fix any bug i found – GHOST Jun 27 '19 at 3:58
  • @GHOST does management blame YOU for development not fixing bugs? – DaveG Jun 27 '19 at 10:49
  • @DaveG exactly with out check bug report they blame me – GHOST Jun 27 '19 at 13:01

I can tell you how this works at my reasonably organised place.

As a developer, I start with a set of tasks that should be achieved for the next release. My boss has decided when the release is, and when QA needs to start testing.

I do the tasks in reasonable quality. Shortly before the date WA should start, if there are tasks not done my boss and I decide what can be left out of the release, or if the release needs to be delayed.

When I have no tasks to do (because I’ve done everything or things were moved to the next release), QA starts. WA reports bugs which become tasks for me. While QA reports bugs, I fix bugs. QA closes or reopens the bugs I fixed. If we come too close to the release date, my boss and I decide which bugs can be fixed for the next release.

The important thing: Every bug QA finds turns into a task for the devs, and the product is released when all those tasks are performed or postponed.

  • my dev team cant be like you they work 2 hrs and other 6 hrs they watch movies or playing if boss came they start act like they are working hard (most of time boss on in the office he went some where ) – GHOST Jun 27 '19 at 4:00

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .