#WhereAreTheLowLevelCrewAt
#LowLevelCrew
#AssemblyEngineers
#LowLevelProgramming
#EmbeddedEngineers
👋 Hey there tech enthusiasts! If you’ve ever found yourself wondering where all the low level crew are hiding, then you’ve come to the right place. In a world of high level developers and cloud hosting, it’s easy to overlook the essential work being done by low level C and assembly engineers. In this article, we’re going to dive into the world of low level programming and shine a light on the often overlooked but critical role of these unsung heroes.
## The Hidden Army of Low Level Engineers
When we talk about low level crew, we’re referring to the skilled programmers who work at the bare metal level, dealing with intricate details of system architecture, hardware interfaces, and memory management. These engineers are responsible for programming everything from aircraft guidance computers to your coffee machine. While their work may not always be as visible as that of high level developers, it is crucial for the functioning of countless everyday devices and systems.
### Examples of Low Level Programming in Action
– Aircraft guidance and control systems
– Medical devices
– Automotive systems
– Industrial manufacturing equipment
– Consumer electronics
## The Outsourcing Conundrum
You might be wondering why you rarely hear about low level crew or see job postings for these roles. The truth is, many companies do outsource this type of programming work, which can make it seem like these engineers are a rare breed. However, the reality is that they are an essential part of the tech ecosystem, quietly working behind the scenes to ensure the smooth operation of a wide range of systems and devices.
### The Role of Outsourcing in Low Level Programming
– Many companies outsource low level programming to specialist firms
– Outsourcing can make it challenging to identify and connect with low level engineers
– Despite outsourcing, there is a significant demand for low level programming talent
## Shining a Light on Driver Developers
One specific group of low level engineers that deserves some recognition is driver developers. These are the engineers who write the software that allows operating systems to communicate with hardware devices. For example, driver developers at companies like Nvidia play a crucial role in ensuring that graphics cards and other hardware components work seamlessly with a variety of software applications.
### The Vital Work of Driver Developers
– Writing device drivers to facilitate communication between hardware and software
– Optimizing performance and functionality of hardware components
– Defining standards and protocols for device interactions
## Connecting with the Low Level Crew
If you’re interested in connecting with the low level crew, there are a few avenues you can explore to engage with this community and expand your knowledge of low level programming.
### Networking with Low Level Engineers
– Join online forums and communities dedicated to low level programming
– Attend industry events and meetups that focus on embedded systems and low level development
– Reach out to companies that specialize in low level programming to learn more about the field
### Exploring Low Level Programming Languages
– Learn about programming languages commonly used in low level development, such as C and assembly
– Explore resources and tutorials that delve into the intricacies of low level programming
– Consider taking courses or workshops that focus specifically on low level programming techniques
By shedding light on the vital work of low level crew, we hope to inspire a greater appreciation for the essential role they play in the tech industry. From writing firmware for medical devices to creating drivers for cutting-edge hardware, the impact of low level engineers is far-reaching and indispensable.
So, the next time you power up your gaming console or use a sophisticated piece of machinery, take a moment to appreciate the intricate programming work that makes it all possible – courtesy of the low level crew! Let’s give a round of applause to these unsung heroes of the tech world.👏
Don’t hesitate to reach out to us if you want to learn more about low level programming or connect with the low level crew. We’re here to help you uncover the fascinating world of low level engineering!
Yes, they are called electrical engineers. The problem is that for every application requiring low-level code there are a thousand requiring higher level code. I know a few ECE people working as web developers for that reason. You need to be *very* good to get those coveted low-level jobs.
I was an embedded software engineer for about 12 years. It typically doesn’t pay as well – the demand isn’t the same. As a principal embedded engineer, I was making less than I could make as a senior software engineer doing cloud/backend work.
I’m a firmware team lead, and have worked in embedded ever since I graduated from college. Like you imply, there is a large breadth of embedded positions. I’ve never seen or heard of a company worth their salt successfully outsource their entire project.
An easy way to get your foot in the door would be to start at a defense contractor. Your sanity may be tested, but most large defense contractors will hire any dev with a degree and a pulse.
Our jobs aren’t glamourous and we don’t get “day in the life” vids on tiktok about us so people forget we exist
I met a ton when I worked at GE. They definitely still exist and I don’t think they outsourced it at all either compared with other software roles.
We don’t talk to outsiders
God, I wish I could escape the hellscape of web development and do shit that’s actually innovative like embedded tech.
I’m a low-*life*, if that counts?
Embedded linux and bare-metal dev checking in (C / C++14/17/23)
See flair.
Not sure about the complaints about low pay, I make on par as other software engineers, probably above par. The trick is to not work for hardware companies, but work for software companies needing hardware 🙂
malware analysis, exploit dev, vuln discovery gang wya
I like my job very much. Even before I graduated I decided I was gonna go into networking, so I work in Linux user space network drivers for fpgas and virtual devices, a lot of software defined networking stuff. All in C/C++ and lots of python.
I got a 90% raise by moving to cloud work lol
These people formed a high proportion of the sw dev population prior to the arrival of the web app explosion.
They are still around ‘tho.
Look up ’embedded’, ‘firmware’, ‘tools developer’, ‘driver developer’ etc.
FWIW in the UK the average age of these engineers, from what I have seen, is around 50 .. with some still working in their 70s.
Many/most come from the era where you made your own radio systems, computer boards etc. They bear the scars of soldering iron burns, not spilled *latte* burns.
It’s something like ~10% of developers are embedded/firmware. So there simply being less of us is part of it. I’d be willing to bet that the average age is also higher than other sub fields, and this sub tends to be younger on average.
Low level crew are at anything government affiliated.
Contracted employees too, basically anyone that has a CAC or needs a clearance for their job.
I’m a rendering engineer in the game industry. I love it, I get to wade around arm-deep in low-level code. I get to seriously think about stuff like cache locality and sometimes I find disassembled bytecode easier to analyze than the original code.
If it takes ten microseconds to run, I will eventually end up taking a look at it to see if I can make it faster.
It’s *fun*.
> nearly every job on every job board (apart from the occasional stray embedded engineer advert) is a high level dev
Are you looking for the right keywords? There are a lot of job postings on LinkedIn for embedded engineers. Even more so if you’re open to working in the defense industry.
a lot of engineering positions in telecom use c/c++ like at nokia, ericcson, qualcomm, broadcom, etc.
Many hats guy here, I work on devices w/ screens (think like infotainment systems) for a small company. Everything from kernel dev & drivers to GUI apps that go on the devices. Hoping that eventually I’ll wind up at a computer design company like ASUS/HP or working on core smartphone / laptop tech eventually, but the nature of the specialization is that I have to be in person and it’s just not a good time to move to a different place (i.e., austin/NYC/Cali) to pursue those companies.
I’ve worked in defense, aerospace, and consumer electronics, and I can tell you that pretty much none of the first two are outsourced. Consumer electronics have outsourced firmware “sometimes”, it just depends on the company.
I try to keep up with what the general CS grad vibe is by reading through here. But not a lot of advice & input from the firmware & low level development career is also applicable to the cloud engineering / systems infrastructure field. I.e., I found that the layoffs from big tech didn’t affect my circle of colleagues at all, as most are in defense & aerospace. And no job I’ve applied to outside of Google has ever used Leetcode as a screening tool.
I’m an embedded firmware engineer working for a company you know. Fewer jobs, lower pay, but still pretty damn good pay in absolute terms relative to non-tech folks.
I appreciate that my tech stack doesn’t change every 6 months, and it’s one of the reasons I’ve stayed away from web dev despite the lower demand.
>Everyone on here…is a high level dev, building websites or data pipelines hosted on the cloud and alike.
Maybe it seems like from your perspective after reading a few specific threads, but I’m pretty sure ~90% of the people on this sub have only 0-1 years of experience, or are just LOOKING to enter the field.
The barrier of entry is super high and it’s harder to teach an entry level person embedded software. There’s a lot that goes into it. A breadth of knowledge that you need to succeed. A lot of people think we don’t exist and we don’t but, we do super interesting work. It’s also a giant pain the ass, stuff is on fire, etc most of time. Just setting up a testing environment takes forever because it’s hard to replicate.