I have been following this forum for a while and I have finally gathered the courage to apply as a Quality assurance engineer under the promise route.
I have up to 3 years experience.
Here are my evidences
Letter from head of my team in my former company, we both don’t work there anymore.
Letter from an engineering lead in a company in Australia that knows my work.
Letter from Engineering lead of a company I worked with
For Mandatory Criteria
-You led the growth of a product led digital Company
Reference letter from Company A describing my work and how I led the team and how I introduced the use of automation testing in the company
Evidence of test documentation, my line of codes, Bug reports screenshot
News clipping of the product performance in the market.
Email from the company appreciating my contribution to the product and performance bonus.
-You command a high salary
Employment letter with my salary information
Performance bonus and promotion with salary increment
My previous salary history
Pay scale comparison on how it’s below average.
For OC1( Innovation)
Reference letter from Company B highlighting the introduction of new software testing technique.
A short note on why I introduced the technique to achieve better bug free product.
News clipping on the performance metrics of the product
-Screenshots of my automation code
-Test Case documentation and report
For OC3 (Impact)
-Employment letter stating me as the only QA engineer in the team
Email from the company stating increase in salary/Performance
-Reference letter from the CTO of the company which is focused on my contribution to the products in the company and it’s impact
-Growth metrics of the product (two of the products have been launched and they are doing well) and news clipping talking about the product.
Test Case documentation screenshots of some of the products I worked on.
PS: I have a little evidence of me tutoring some students but I don’t know where to fit it in because it’s not a structured program and the students are not up to 10.
You have done well to summon the courage to apply. I have seen less Quality Assurance applicants here. So, I would expect that that should make your application stand out.
Regarding the quoted segment, do you mean ABOVE average??
As I have come to find out in the latest update to the TN guide, you need at least 2 unique pieces of evidence for per criteria category i.e. you are limited on repeat evidences that you can use across the criteria. For instance, news clippings under your MC can’t be the same as those for your current OC3 as I see.
Additionally, for OC1, do you mean you came up with a new software testing technique that’s “novel” to the testing and assurance ecosystem or new only to your company? If it is the former, then we should be looking at a patent or at least, a publication (which I doubt it is). If it is the latter, I am afraid that may be considered as just simply doing what you are paid to do and not INNOVATION.
Also, you have more than 10 pieces of evidence now by my count.
I fear that most of your evidences are from “within” the organizations that you’ve worked.
I also have the feeling the your LoRs may not be considered strong (just my gut feeling) especially LoR1. Could you get one or two LoRs from an executive, e.g. CTO, CDO, CEO, Engrg Dir, instead?
To be honest, I wouldn’t so much rely on this as INNOVATION
You must - maybe you combine those that are similar and try to see if you can come up with other support documents.
Yes! All the above are suitable to the extent that they are leaders in product-led or digital tech fields themselves.
I believe OC3 is good enough as in:
Ref letter (should be somewhat detailed) + Email of salary increase
Growth metrics + news clipping
Test documentation exposé + screenshots
OC1 is pretty tough for two reasons; (i) it needs external agencies to get some form of validation e.g. media coverage, patent, publication or an external leader’s words (ii) it’s subject to the reviewer’s perception of “true” innovation. This is not to say that applying old methods to new domains cannot be considered innovation. It is just unlikely in your case since you have probably deployed conventional QA techniques in the tech space.
However, I still think that you have a good shot with what you currently have. There’s not so much more that you can add except you only repeat your increase in salary again as stated in the guide as a suitable example: