I mean, Macrumors could have at least posted the most relevant information.
Apple is currently looking for experienced programmers with detailed knowledge of the RISC-V Instruction Set Architecture (ISA) and Arm's Neon vector ISA for its Vector and Numerics Group (VaNG) within its Core Operating Systems group. Apple's VaNG is responsible for developing and improving various embedded subsystems running on iOS, macOS, watchOS, and tvOS.
This is interesting because without this piece of information I would have thought Apple is trying to save pennies in those embedded ARM cores ( not the the ones used in CPU ) such as U1, W1 etc. But this is being specific to VaNG. And RISC-V is certainly a great fit for this use case with their Vector extension instructions. ( If you want to understand this I recommend searching for SIMD and Vector ) It will be interesting to see how all these fits together.
The embedded ARM cores aren't always 100% Apple ones. Apple licenses work from other folks for embedded jobs. If those other folks are starting to switch over to using RISC-V then Apple would need to cover that if they want to do highly custom drivers/interfaces to those targets.
RISC-V in DSP and signal processing isn't getting deep traction because of the "vector machine" approach in the RISC-V standard set. There is also flexibility to put in specific instructions for narrow DSP problems into the implementation.
If Apple is picking 3rd party embedded implementations because they are cheaper because that 3rd party can sell their solution at a lower cost and still make a profit.... then it hasn't particularly escaped Apple chasing pennies via cheaper component costs. Especially, where Apple is the major external force pushing for downward pricing on the components.
There was lots of low level 'dot the i's and cross the t's' work that Intel pragmatically did for Apple because coasted on EFI/UEFI/BIOS boot and baseline driver design already written to interface from x86. If Apple is substantively changing how to talk to the devices then they'll need their own team to help replace that baseline driver work.
P.S. there are lots of embedded chips that have "someone else's cores " embedded inside somewhat anonymosly. CEVA cores are in most of Intel, Samsung, MediaTeks modems.
"..Of the latter, there’s only Qualcomm and most recently HiSilicon (the in-house modem IP
introduced in the K960), whereas most other major players over the last couple of years have used CEVA IP. Samsung, Intel, MediaTek, and ..."
www.anandtech.com
Maybe Apple is kicking CEVA out after they acquired Intel's implementations, but is almost certainly going to cost them substantive time to market. But the notion of Apple kicking every embedded 'CPU' core out of every chip soldered to or licensed from integration into an Apple product with an Apple deisgned from scratch CPU core is loopy and probably totally unnecessary.
Apple is going to have to have some folks on staff to deal with cores that they don't do themselves. Can't be a 'down to the metal" systems provider and ignore everyone else's stuff at the same time.