Frequently used answers :)

UI developer - I think API is not working
Backend developer - Front end is not sending the request correctly
Tester - Testing! Testing!
UI/UX - As per android/ios standards...
QA - Let me check one more time
PM - Let us have another meeting and get on the same page
Dev-Ops - It's very complicated you know
CTO - We're working on a next-gen solution
Founder - Let us build something that no one has built, something similar to what google...facebook...

Cridits: My EX-CPO

Hahah, Nice one :D

Tester and qa - different things?

@R2-D2 Can't amount to human error enough.

@netikras Yes. Are they frequently different people? sadly no. are those different skillsets? definitely. Testing is usually quite technical, if you do it well it's a well set up scientific experiment that allows you to set up your null hypothesis (shits fucked up) and enrich it with data until you can make a rather certain statement about the hypothesis being true. Extra points if your hypothesis is precise enough to actually allow for a diagnosis of why shits fucked up.

QA usually deals with processes and the question why they produce errors. It's much closer to the realm of management. Finding systemic flaws in communication, fighting for time to write unit tests, tackling bullshit requirements like maximum estimates on features and so on.

Then of course there are your 0815 "Testers" who just click around on an application and wouldn't recognize a risk assessment if it'd bite their failed developer asses. Those are neither QA or testers, those are a waste of salary.

@Godisalie thanks. I was under impression that testers fall under the QA umbrella as they are asserting product's quality. And you cannot assure smth if you have no means to verify [test]. I guess my assumption was wrong then?

Also.. Qa fights for unittests timem do they also write them?

And is that the theory or the setup where you work?

TIA