They use a poll of applications. It is not about very specific positions with expiring posts; it is not dynamic, unlike in the case of other companies.

If you apply to several job openings and are called for an interview, they won't give you the specific number of the job opening.

In most cases, you need to have some experience with CUDA. To increase your chances of getting a job offer, you need to know linked lists very well. We used collabedit.com for the interview. It's like a chat but for coding. I received the following question on the collabedit screen:

// There is a chunk of memory in the kernel address space represented by kernelResource and an API exists to clear it. An IOCTL path exists to take a request from user-mode and, using O/S services, eventually dispatches to API_ZeroResource. From a security perspective, what concerns do you have with this implementation? How would you fix them?

// // KERNEL // BYTE kernelResource[10] = {0};

int API_ZeroResource( in_params *pParams ) { if (pParams->offset + pParams->length > sizeof(kernelResource)) return ERR_INVALID_LIMIT;

memset(kernelResource + pParams->offset, 0, pParams->length);

return 0;

}

// // USER //

void ZeroResource() { in_params params = { ??? };

// an ioctl path exists to call API_ZeroResource
ioctl( CMD_ZeroResource, &params );

}