Excellent offices, good cafe, good pay, decent work-life balance, and interesting problems to solve, if you can get to do them.
Extreme (and largely useless) secrecy makes it difficult to get anything done. The "Apple way" of doing things is by plucking some people from separate teams that specialize in something and sort of mushing them together as a virtual team. This has its advantages and disadvantages. Advantage: those teams can really deeply specialize in a narrow sub-field, and as such deliver insights and results that generalists can't deliver. You can see this in Apple products every day. Disadvantage: this works only on the hardware side. On the software side, I would much rather have teams of capable generalists working on products, but with the ability (and requirement) to reach out to specialists when needed. That would work way better than the "Apple way" works today.
Consider seriously reorganizing the way you work on software, especially on AI software.
Consider allowing the internal use of AI coding and code review aids.
I'm a believer in Apple, and seeing how the sausage is made there only bolstered my beliefs. There are lots of people there who really care. It'd be a shame if Apple permanently fell off the wagon, which it might if it doesn't adapt.
An engineer called me for a 1-hour coding round for a Java position. The interview started with some basic questions. Then, the interviewer kept asking about: * Networking internals * File system internals * Network packet details * Protocol detai
The questions were easy. They were general questions that anyone with this background could handle. The interview was conducted in a teleconference style. It started with an introduction of past work history. After that, we went into technical quest
A recruiter contacted me and scheduled a 30-minute interview. I was told it would be behavioral and technical if needed, but mine was a completely technical round. It was a deep dive into LLMs, with questions on: * Example prompts for given use cas
An engineer called me for a 1-hour coding round for a Java position. The interview started with some basic questions. Then, the interviewer kept asking about: * Networking internals * File system internals * Network packet details * Protocol detai
The questions were easy. They were general questions that anyone with this background could handle. The interview was conducted in a teleconference style. It started with an introduction of past work history. After that, we went into technical quest
A recruiter contacted me and scheduled a 30-minute interview. I was told it would be behavioral and technical if needed, but mine was a completely technical round. It was a deep dive into LLMs, with questions on: * Example prompts for given use cas