Edit - The Workplace Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2

Very much agree with this advice, and that a QA who is also a software engineer is worth their weight in gold. Alister B Scott is a good public example of a smart engineer in this mould. I would also have the OP ask themselves: do they like QA work, so long as it has a level of engineering complexity and challenge? Some programmers have the capability but just don't get the buzz from pushing a system and showing where it works, where it used to work, and where it never did.
– Adam Burke
Commented Jan 26, 2022 at 1:35
In my S&P500 corp, there are 3 different job descriptions: "Verification Engineer" (=manual QA), "Automation Engineer" and "SW Engineer" (code developer). I'm guessing that a small company won't make this further distinction.
– Jonathan
Commented Feb 1, 2022 at 11:34
It doesn't matter what you're worth, what matters is what you get paid. Being worth your weight in gold doesn't help you if the company doesn't appreciate it.
– gnasher729
Commented Mar 14, 2022 at 18:01

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »