The most comprehensive bank Interview Answer Review tooling available online.

So i can take one 2:1 multiplexer and 2:1 mux have 2 inputs, one output and one select line so i can connect one of the variable to select line and another will connect to input 1 and input zero is grounded

property check_setup_hold;

  logic clk, rst;

  logic data, data_en;  // Input data and its enable signal

  @(posedge clk)

  disable iff (rst) 

  $rose(data_en) |-> 

      ##[Setup_Time:Setup_Time] data_stable  ##1 

      data_stable throughout $fell(data_en) ##[Hold_Time:Hold_Time]; 

endproperty 

sequence data_stable;

  (data == 1'b0) || (data == 1'b1); 

endsequence

assert property (check_setup_hold(clk, rst, data, data_en));

Situation:

Success can be measured in different ways depending on the context—whether it’s a project milestone, team collaboration, or personal growth. For me, success is about achieving the intended goal while creating a lasting impact, whether that means delivering high-quality verification, improving efficiency, or mentoring others to grow.

Task:

One example that defines my success criteria was when I was responsible for closing the verification of a complex IP. The challenge was that I had limited resources—a team of mostly junior and mid-level engineers—and tight timelines. Success in this scenario wasn’t just about delivering verification but also ensuring that my team could ramp up and work independently.

Action:

To achieve this, I:

• Developed structured onboarding materials to accelerate the team's understanding of the testbench.
• Strategized task distribution to ensure each engineer had ownership of a small but impactful portion of the verification process.
• Created a collaborative debugging process, where team members could efficiently troubleshoot and escalate issues.
• Ensured verification coverage met the expected metrics while identifying and fixing key testbench gaps.

Result:

We successfully completed verification on time, identified critical testbench bugs, and delivered a well-documented framework that continues to benefit future teams. To me, this was a success because:

1. The technical objective (verification sign-off) was achieved.
2. The team grew and became self-sufficient, reducing dependency on senior engineers.
3. The long-term impact was positive, as the documentation and processes set up are still in use.

To solve this detector, essentially you would need a finite state machine. first you need to draw the state diagram of the transition while detecting the sequence. Then in verilog, you need to implement the case statement.