Quality Engineering: Software must work. Each person is responsible for their area.

Layers of quality control:

Best Practices. Check the link below to code with best practices. We won’t repeat these things while you code. So make sure you pay attention to it.
.Net Coding Best Practices

[Required] If you are a .NET developer working on Visual Studio. Please enable the Spell Checker extension to avoid any spelling mistakes in the code. https://devblogs.microsoft.com/visualstudio/visual-studio-spell-checker-preview-now-available/#:~:text=The%20spell%20checker%20can%20be,main%20toolbar%20in%20Visual%20Studio

Defensive coding. Check the below course for the same.

• https://medium.com/c-sharp-programming/defensive-programming-in-c-best-practices-and-examples-f1edeb676e97

Peer Reviews (The PR reviewer is responsible. Your job is to not let code go in by default. Be mean.) https://dev.to/nirajkvinit/pr-code-review-best-practices-5363

Automated Testing (Unit, Integration, Cypress/Selenium),
https://app.pluralsight.com/library/courses/creating-automated-browser-tests-selenium-c-sharp/table-of-contents

Runtime Asserts (If something should not happen, it should assert/break) (Sentry / Rollbar)

Independent Manual QA (Backup. If they find mistakes, you have an issue.)

• When there is a break in the system, an SEV review document must be written.

Quality Testing: As a QA engineer, you should be testing the system end to end and try to break it. That should be your goal.

Do positive and negative testing: If something is confusing to report to the team with suggestions.

• Make proper test cases for each project

Automated testing is needed
https://app.pluralsight.com/library/courses/creating-automated-browser-tests-selenium-c-sharp/table-of-contents