Behavioural Questions
1️⃣ “Tell us about a time you disagreed with a supervisor.” Situation: On a previous project, my supervisor wanted to release a feature quickly without full regression testing. Task: My responsibility was to ensure the release would not introduce production defects. Action: I respectfully shared my concerns, backed them with data from past incidents, and proposed a compromise—running a focused regression on high-risk modules instead of full testing. Result: We delayed the release by one day, avoided a potential production issue, and the supervisor later appreciated the risk-based approach. 👉 Key signal: Professional disagreement + data + teamwork 2️⃣ “Describe a time you had to solve a problem you didn’t immediately know the answer to.” Situation: During integration testing, an API intermittently failed with inconsistent error messages. Task: I needed to identify the root cause and ensure system stability before deployment. Action: I reviewed logs, reproduced the issue in a lower environment, collaborated with developers, and researched similar issues. I isolated the problem to a timeout configuration mismatch. Result: After fixing the configuration, the failures stopped, and the system passed integration testing. 👉 Key signal: Problem-solving + learning mindset 3️⃣ “How do you handle multi-tasking and competing priorities?” Situation: In one role, I was supporting testing, handling production issues, and assisting developers simultaneously. Task: I had to make sure critical issues were addressed without missing deadlines. Action: I prioritized tasks based on business impact, used a task-tracking system, communicated timelines clearly, and focused on high-risk items first. Result: All critical issues were resolved on time, and stakeholders were satisfied with the transparency and delivery. 👉 Key signal: Organization + calm under pressure 4️⃣ “Why do you want to work for the Commonwealth / PSP?” (This is motivation + values, not strict STAR—but structured works) ...