say something like "i'm lookin for something in the region of x to y but want to find out more about the position first"

* What to make u a good tester?
* What's passion make u to become a tester?
* Is it important to share ur knowledge with ur peers?
* From ur perspective， how to maintenance/handle the relationship in a team
* What's different between function test and a UAT test
* What's different between Web testing / data base testing
* Is customer always right?
* If customer said there's a bug, but u can't reproduce it,how to proven they are wrong?
* What's important in a bug report?
* If there's a requirement, how will you start testing?
* Have u even in a situation where there's no req/spec before testing?
* In what situation u might bypass the testing procedure (documentation ) ?


---they arent always right
but you have to explain to the customer

--if you cant reproduce than you may not have enough or the correct information to do so
you need to speak to the customer and ensure the environment is the same or the customer provides you with some evidence.

We created FPPS, the payment stuff was originally part of the one large system.

The network was another Service, but William and i wanted to break it up into more smaller services

It's easier to test smaller components, and reduces the complexity. Also each service can be optimized, upgraded, maintained seperatly, rather than having just one big application