The company is willing to pay and reward employees decently with cash and stocks. That is all.
Workload is unreasonably heavy. Management doesn't really care about the technical challenges engineers are facing, as they are under great pressure coming directly from customers who are rich enough paying billions of dollars for the AI revolution powered by NVIDIA products.
As a result, software engineers have to accommodate feature/bugfix requests from customers in very short time frames per management's direction. Long-term planning rarely exists.
This causes a huge amount of tech debt piling up quickly in just one or two generations of GPU, and from a software engineer's perspective, it is basically not sustainable to work in this manner.
This stressful working environment also creates the incentives/excuses to not help team members as you can barely finish the tasks assigned to you, which makes it even harder for everyone to be long-term productive. All in all, just all sorts of vicious cycles.
This is team-specific. We are a software team, but the most senior tech lead who oversaw most code commits didn't seem to know how to code C++, which is the single most important programming language of our software product.
Examples include:
Management should shoulder the pressure from customers and work in good faith with your engineers to develop long-term viable technical plans, which benefits all parties.
Stop playing politics and gaslighting managers/engineers with whom you don't see eye-to-eye. The very root cause for your stress is exactly the toxic culture and environment you built up in the first place.
30-minute team interview. Starting with my introduction about my most related experience, followed by very extensive and detailed questions about technical details and division of labor. Then, a free-form 10-minute basic coding question for both Py
The interview process began with a meeting with the hiring manager, followed by four technical interviews with engineers. Programming problems covered data structures, bit-wise operations, API design, and CPU optimization techniques. These were gene
MS Teams first round. Asked few questions on: * Memory management * Spin locks * Mutex * Semaphores * I2C multi-master * Clock stretching * ARM architecture * Privileges * Registers * Memory Protection Unit Then taken to the C programming section.
30-minute team interview. Starting with my introduction about my most related experience, followed by very extensive and detailed questions about technical details and division of labor. Then, a free-form 10-minute basic coding question for both Py
The interview process began with a meeting with the hiring manager, followed by four technical interviews with engineers. Programming problems covered data structures, bit-wise operations, API design, and CPU optimization techniques. These were gene
MS Teams first round. Asked few questions on: * Memory management * Spin locks * Mutex * Semaphores * I2C multi-master * Clock stretching * ARM architecture * Privileges * Registers * Memory Protection Unit Then taken to the C programming section.