joshj19
Impossible Aerospace is a venture-backed startup with the goal of reducing the environmental impact of commercial aviation by electrifying air transport. Our first product is the US-1, an enterprise quadrotor drone with a 2-hour flight time.
We are hiring embedded software engineers to work on multiple projects including flight control, motor control, radios, cameras, battery management systems, etc. Multiple different target platforms, including bare-metal on ARM, RTOS on ARM, and embedded Linux.
We are also hiring web and mobile developers to build out new applications for remote operations of aircraft.
Hiring hardware engineers to build out many different avionics systems.
Design and production of our product is in-house at our headquarters in Santa Clara. Current engineering team is about 15 engineers from aerospace (SpaceX and others), automotive (Tesla and others), and consumer electronics backgrounds.
Positions available at the entry, senior, and team-lead levels.
Interested? Apply here: https://jobs.lever.co/impossible
Or email our Director of Engineering your resume: josh [at] impossible.aero
http://elinux.org/RPi_Low-level_peripherals
It provides some information on how to interface with the GPIO pins with a multitude of programming languages. Granted it may not be an absolute beginner guide, it still has a lot of useful information. If I can find another guide I'll comment back here.
I'd also want to echo something that the other reply to your comment mentioned, which is that you should seriously consider starting with an Arduino if you want to do some lower-level programming/interfacing with hardware. From my personal experience, there's a little more documentation on that sort of thing with Arduino than the Raspberry Pi. Additionally, the Raspberry Pi's GPIO pins are not fault tolerant, which means you could damage your Pi if you wire up your hardware improperly. If I remember correctly, Arduinos typically have some voltage fault tolerance (at least there are variants which do), and even if you fry the actual microcontroller chip on the board, it can be removed and replaced for a couple of dollars. Once you've got some experience on an Arduino board, then I'd recommend doing some of the low-level stuff on the Raspberry Pi.