5 ms·

> Location: Austin, Texas. Meh... Where are the remote jobs? I bet if you open an office in Oregon (where there's tons of Intel Open Source people) you'll find

> Location: Austin, Texas. Meh... Where are the remote jobs? I bet if you open an office in Oregon (where there's tons of Intel Open Source people) you'll find a lot of candidates. Or, you know, act like the old times of 2020 and hire remote employees?

xkeysc0re 6y ago
Not to mention Linux itself being developed remotely
bgorman 6y ago
If you are developing low-level device drivers, it is nice to be close to the hardware engineers.
- com2kid 6y ago
  People don't realize how quickly hardware iterates and how many modifications and changes are made on site in the lab. Or just how often development hardware self-bricks and needs to be recovered. Doing hardware work remotely is a lot slower. Possible, but slower. Edit: Or how there is that one person who is really good at assembly and if you can walk down and ask them a question it'll save you a couple hours (days) of debugging. And then there is that one person who is really good with an oscilloscope and while in theory you shouldn't need to have decode messages by sight from waveforms, well, this one person can and it sure is useful time to time....
  - raverbashing 6y ago
    You're right for prototype HW. For things that are "working" already it's usually not needed
  - dyingkneepad 6y ago
    This is not my experience. Driver developers don't use oscilloscopes. Changing HW once the first prototype is done is expensive and it takes a lot of time for you to get the second iteration. Or you flip a bit in the driver to disable the new broken feature. Most of the driver development happens before the physical hardware even exists. Everything is virtual.
    - com2kid 6y ago
      > Changing HW once the first prototype is done is expensive and it takes a lot of time for you to get the second iteration. Sure, but minor fixes soldered in place aren't uncommon. My experience is with firmware for embedded and consumer electronics, maybe video cards are sufficiently complex that none of the things I saw are even possible! Lots of issues resolving power states, clock trees, monitoring buses, docs from suppliers were always subtly wrong, power management chips never quite worked how they were supposed to, things like that.
- dyingkneepad 6y ago
  I do happen to work writing low-level device drivers, and I do work remotely. The hardware engineers are always one click away from me. I can give them access to my machine with another click on the machine reservation system. It is very much possible and viable to have everything remote.
cat199 6y ago
> Meh... Where are the remote jobs? would guess since this is AMD and low level Linux, there may be a good deal of interfacing with physical hardware, in addition to any other preferences they might have
AareyBaba 6y ago
Don't let the stated location stop you from applying. 3rd party HR software and outdated pre-pandemic rules force hiring managers to state a location even if they are willing to hire to work from any location.
- dyingkneepad 6y ago
  They could write in the description that remote is a possibility...

xkeysc0re 6y ago

Not to mention Linux itself being developed remotely

bgorman 6y ago

If you are developing low-level device drivers, it is nice to be close to the hardware engineers.

com2kid 6y ago
People don't realize how quickly hardware iterates and how many modifications and changes are made on site in the lab. Or just how often development hardware self-bricks and needs to be recovered. Doing hardware work remotely is a lot slower. Possible, but slower. Edit: Or how there is that one person who is really good at assembly and if you can walk down and ask them a question it'll save you a couple hours (days) of debugging. And then there is that one person who is really good with an oscilloscope and while in theory you shouldn't need to have decode messages by sight from waveforms, well, this one person can and it sure is useful time to time....
- raverbashing 6y ago
  You're right for prototype HW. For things that are "working" already it's usually not needed
- dyingkneepad 6y ago
  This is not my experience. Driver developers don't use oscilloscopes. Changing HW once the first prototype is done is expensive and it takes a lot of time for you to get the second iteration. Or you flip a bit in the driver to disable the new broken feature. Most of the driver development happens before the physical hardware even exists. Everything is virtual.
  - com2kid 6y ago
    > Changing HW once the first prototype is done is expensive and it takes a lot of time for you to get the second iteration. Sure, but minor fixes soldered in place aren't uncommon. My experience is with firmware for embedded and consumer electronics, maybe video cards are sufficiently complex that none of the things I saw are even possible! Lots of issues resolving power states, clock trees, monitoring buses, docs from suppliers were always subtly wrong, power management chips never quite worked how they were supposed to, things like that.
dyingkneepad 6y ago
I do happen to work writing low-level device drivers, and I do work remotely. The hardware engineers are always one click away from me. I can give them access to my machine with another click on the machine reservation system. It is very much possible and viable to have everything remote.

cat199 6y ago

> Meh... Where are the remote jobs? would guess since this is AMD and low level Linux, there may be a good deal of interfacing with physical hardware, in addition to any other preferences they might have

AareyBaba 6y ago

Don't let the stated location stop you from applying. 3rd party HR software and outdated pre-pandemic rules force hiring managers to state a location even if they are willing to hire to work from any location.

dyingkneepad 6y ago
They could write in the description that remote is a possibility...