Test design craft, STLC vocabulary, defect management, and the judgement scenarios that separate testers from clickers.
Say yes if it is true, give a stage and a rough timeline without naming companies, and use it to set a decision date rather than to imply a bidding war. Inventing a process you do not have is the one answer that can end badly.
Agree the business meaning and the grain of each entity before touching field names, profile the real data to find the overloaded and sentinel values, then write a mapping where every target field has a source, a rule, a default and a decision for records that cannot be mapped.
Give the reasons in one pass so the pattern looks like a sequence of decisions rather than a habit, then name what you have changed about how you choose a role. The answer that works is a filter you can state, not a promise to stay.
Answer no, and give the non-money reason you are leaving as the evidence. If a real counteroffer arrives later, judge it against what your employer did before you threatened to leave, not against the number on the paper.
Convert the adjective into an observable: who is doing what task, under which conditions, and what result counts as a pass. Where no honest measure exists, record it as a design constraint with a named reviewer rather than leaving an unverifiable sentence in a document somebody signs.
Ask for the deadline and the reason in writing, then request a specific short extension while telling the other process you have an offer with a date. A deadline with no reason behind it is a negotiating tactic, and it is also information about the employer.