Offline on Zoom.
Very hard.
Two interviews of 1 hour each:
I think it was a first filter for a face-to-face interview, but I am not sure, because I did not pass that interview.
There is RAM that has:
A read/write control.
“1 bit per read, 1 bit per write” means there is one control signal for read and one for write. These bits are asserted on the clock pulse, together with valid data and address.
The interviewer then asks two things:
“What issues in the system may fail the correct functionality?” This means: List all possible design, timing, logical, or electrical problems that could cause the memory system not to work correctly. For example, wrong timing between clock and data, wrong use of read/write bits, address decoding errors, etc. (the exact list is up to the candidate).
“Please develop an algorithm that will find all relevant issues, pre/post silicon.” This means: Propose a test method or verification algorithm that can detect these problems:
Under Candidate coding, they give you two abstract operations that you can use in your algorithm:
write(Address, RD/RW, Write_data)read(Address, RD/RW, Read_data)These are just function “primitives”:
write(...) performs a write transaction to a specific address with some data and read/write configuration.read(...) performs a read transaction from a specific address and returns the data, using the RD/RW configuration.The following metrics were computed from 2 interview experiences for the Google Verification Engineer role in Tel Aviv-Yafo.
Google's interview process for their Verification Engineer roles in Tel Aviv-Yafo is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Google's Verification Engineer interview process in Tel Aviv-Yafo.