Skip to main content

Meta QA Engineer Interview Questions

Review this list of 5 Meta QA Engineer interview questions and answers verified by hiring managers and candidates.
  • Meta logoAsked at Meta 
    +38

    "def is_palindrome(s: str) -> bool: new = '' for a in s: if a.isalpha() or a.isdigit(): new += a.lower() return (new == new[::-1]) debug your code below print(is_palindrome('abcba')) `"

    Anonymous Roadrunner - "def is_palindrome(s: str) -> bool: new = '' for a in s: if a.isalpha() or a.isdigit(): new += a.lower() return (new == new[::-1]) debug your code below print(is_palindrome('abcba')) `"See full answer

    QA Engineer
    Data Structures & Algorithms
    +4 more
  • +7

    "In my time at Snapp! I was in charge of communicating the product backlog to our CEO. We had a shared Jira board that he had access to and I made specifically for him. One day he saw me in the office and said he doesn’t know anything about our backlog and that’s because I failed to communicate with him. I got upset at first because of the fact that I made the dashboard exclusively for him. But I tried to ask questions to understand his point of view in depth. He then mentioned he doesn't have t"

    Ra R. - "In my time at Snapp! I was in charge of communicating the product backlog to our CEO. We had a shared Jira board that he had access to and I made specifically for him. One day he saw me in the office and said he doesn’t know anything about our backlog and that’s because I failed to communicate with him. I got upset at first because of the fact that I made the dashboard exclusively for him. But I tried to ask questions to understand his point of view in depth. He then mentioned he doesn't have t"See full answer

    QA Engineer
    Behavioral
    +9 more
  • "Described a scenario where I joined an established project as an EM Typical medium sized team - 6 devs, 2 testers, PO, PM (part time) Scrum master (very hands off) The product was well established and already being used by circa 30000 single country based users for the companies own products (personal banking capabilities) We were due to go live with a BIG change about 2 months after I joined - this change meant a user could manage multiple personal banking accounts from the 1 interface. We w"

    Hans - "Described a scenario where I joined an established project as an EM Typical medium sized team - 6 devs, 2 testers, PO, PM (part time) Scrum master (very hands off) The product was well established and already being used by circa 30000 single country based users for the companies own products (personal banking capabilities) We were due to go live with a BIG change about 2 months after I joined - this change meant a user could manage multiple personal banking accounts from the 1 interface. We w"See full answer

    QA Engineer
    Behavioral
    +1 more
  • +2

    "Situation: Was given negative feedback about an aspect of my communications. The person said it made them worried because of the brevity and the format of some messages. (Their worry was that a longer negative message was coming) Task(s): Reflected on feedback about my communication style. Acknowledged the point. Assumed best intentions on the part of the person giving the feedback Saw things from the other person's point of view Action(s): In private - Apologised to the person wh"

    Hans - "Situation: Was given negative feedback about an aspect of my communications. The person said it made them worried because of the brevity and the format of some messages. (Their worry was that a longer negative message was coming) Task(s): Reflected on feedback about my communication style. Acknowledged the point. Assumed best intentions on the part of the person giving the feedback Saw things from the other person's point of view Action(s): In private - Apologised to the person wh"See full answer

    QA Engineer
    Behavioral
    +2 more
  • "Described a bug I found on an app designed for a specific make of tablet. In this sequence I described: The app the bug was found in The priority and severity of the bug That it was a regression to an existing working piece of functionality The hardware and the firmware on the device the bug occurred on The steps that led to me finding the bug and how it manifested itself Talked about how we debugged from the point of view of: Code Component Deployed application Comparison to"

    Hans - "Described a bug I found on an app designed for a specific make of tablet. In this sequence I described: The app the bug was found in The priority and severity of the bug That it was a regression to an existing working piece of functionality The hardware and the firmware on the device the bug occurred on The steps that led to me finding the bug and how it manifested itself Talked about how we debugged from the point of view of: Code Component Deployed application Comparison to"See full answer

    QA Engineer
    Analytical
    +1 more
  • 🧠 Want an expert answer to a question? Saving questions lets us know what content to make next.

Showing 1-5 of 5