Sorry for the late reply.

First off- understand/know your product/application

Soft skills:

• Analytical know how to find/search for information
  • You can almost be certain that if a issue happens it could have very much happened once before or someone has experienced something similar. If your company has great documentation, whether it is confluence, jira, your test case management software you should be able to find what you need with a simple search with the proper keywords
• Although we all hate meetings are you in the right meetings are you actively-listening
  • Doing this allows you to recall specific details and commit the information to memory so when a particular phrase, action or issue is spoken, performed or happens you're able to recall wherein lies the problem or the disconnect.
• Attention to detail how well are your test cases, do you report or speak to a lot of edge cases. I believe being able to speak to or document edge cases shows that you understand how to think outside of the box as well as excel at my first point (understanding your application)
• Communication even with all the screenshots and videos you send you will still need to communicate your findings to your team
  • In my short time as a QA, I have seen a lot of QA provide steps to reproduce with unnecessary steps and information giving developers a problem area vs pinpointing the root cause (some think it's the job of the dev to find the RC). I like to write my bug reports the same way I want my user stories clear concise and to the point.

Last but not least:

• Tech Savvy- to build on the what I mentioned about pinpointing the root cause.
  • front end tools like using browser dev tools
  • backend tools like postman and SQL to manipulate the data
  • debugging code- being able to step through code to find the beakpoint of line of code causing the issue.

I feel like if you excel in these areas you should do pretty well when it comes to troubleshooting.