Your next opportunity: Junior/Mid-level Embedded Software Engineer in Sydney, NSW
Job Description
Job Description \n
Junior / Mid-level Embedded Software Engineer \n
\n
Sydney | Hybrid | IoT
\n
\n
$90-130k + super
\n
\n
The Mission
\n
\n
Build the software behind a new generation of connected consumer products, from early proof of concept through to global mass production.
\n
\n
You’ll work across embedded systems, device connectivity, user interfaces and cloud-connected features, helping turn product ideas into reliable, intuitive and commercially successful hardware.
\n
\n
This is an opportunity to join a highly experienced engineering team early in your career, get exposure to the full product development lifecycle and learn from engineers who have built complex products at scale.
\n
The Challenge \n
\n
This isn’t a narrow firmware role. You’ll join a multidisciplinary product squad alongside electronics, mechanical, industrial design, quality and product development specialists, contributing to software across the complete device experience.
\n
\n
Depending on the product, that could include:
\n
\n
- \n
\nDeveloping embedded software in C and C++
\n
\nBuilding software for microcontrollers and connected devices
\n
\nContributing to React Native interfaces running on physical products
\n
\nIntegrating device, mobile and cloud components
\n
\nContributing to reusable software architectures across multiple product families
\n
\nReading schematics and debugging across hardware and software boundaries
\n
\nPrototyping quickly during concept development
\n
\nHelping mature code from early prototypes through to production-quality software
\n
\nSupporting manufacturing, validation and occasional factory engagement
\n
\nCollaborating with local teams, overseas engineering partners and remote software groups
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
The engineering lifecycle runs for roughly two to three years, taking products from an initial hypothesis through proof of concept, commercial approval, pilot builds and mass production.
\n
The Bar \n
\n
You don’t need to arrive as the finished article. We’re much more interested in strong fundamentals, evidence that you can apply them to real engineering problems and an appetite to keep learning.
\n
What you'll need \n
\n
- \n
\nA degree in Computer Science, Electrical Engineering, Mechatronics, Software Engineering or another relevant engineering discipline
\n
\nSome transferable, hands-on experience through an internship, university project, postgraduate work or early commercial experience involving firmware, embedded systems, electronics or connected hardware
\n
\nStrong programming fundamentals and practical problem-solving ability
\n
\nSome experience working with C and/or C++, whether commercially, academically or through personal projects
\n
\nA genuine interest in understanding how software and hardware interact
\n
\nThe ability to move between different problems and technical areas as a product evolves
\n
\nAn eagerness to learn, ask questions and get comfortable with unfamiliar technology
\n
\nEnough autonomy to investigate problems and make progress without needing every step mapped out
\n
\nA progressive mindset – you’re interested in better ways of doing things and willing to challenge your own thinking
\n
\nClear communication and an ability to work alongside people from different engineering disciplines
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Bonus points for \n
\n
None of these are prerequisites, but exposure to any of the following would be useful:
\n
\n
- \n
\nEmbedded systems, microcontrollers, firmware or IoT devices
\n
\nElectronics, including reading schematics or debugging hardware/software interactions
\n
\nReact, React Native or JavaScript
\n
\nPython
\n
\nMobile development
\n
\nCloud platforms or connected-device architectures
\n
\nPersonal engineering projects where you’ve built, programmed or connected a physical product
\n
\nExperience taking something beyond the classroom and making it actually work in the real world
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
We’re deliberately keeping the industry background broad. Consumer electronics experience is great, but experience from robotics, medical devices, industrial IoT, university projects, internships or other hardware-led environments can translate just as well.
\n
The Hire \n
\n
You’re likely an early-career engineer who enjoys software but wants to work closer to the hardware.
\n
\n
You might be coming straight from university or postgraduate study, have completed a strong internship or placement, or have spent your first few years working in software, embedded systems, electronics or another adjacent engineering environment.
\n
\n
You’ll probably enjoy this role if you:
\n
\n
- \n
\nPrefer building tangible products over working exclusively on digital platforms
\n
\nLike figuring out how things work rather than staying within one narrow technical lane
\n
\nAre comfortable switching context as products and priorities evolve
\n
\nAsk good questions when you don’t know the answer
\n
\nEnjoy learning from experienced engineers while still taking ownership of your own work
\n
\nCare about the full user experience, not just your individual codebase
\n
\nWant broad technical exposure while remaining hands-on
\n
\nAre excited by the idea of seeing something you helped build eventually sitting in someone’s home
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
This team values raw problem-solving ability, curiosity and potential over a perfect keyword match.
\n
The \"Why me?\" \n
\n
You’ll join an unusually experienced software group with significant principal-level capability across embedded systems, connected devices, user interfaces and cloud technologies.
\n
\n
For someone early in their career, that means genuine access to engineers who have built products at scale and an environment where you can develop across multiple layers of the stack rather than being boxed into one small area.
\n
\n
There are also several long-term career paths available:
\n
\n
- \n
\nDevelop into a deeply hands-on embedded or software engineer
\n
\nProgress toward senior and eventually principal engineering
\n
\nBuild capability across embedded, IoT, UI and cloud systems
\n
\nMove toward technical leadership, architecture or engineering management as your career develops
\n
\n
\n
\n
\n
\n
\n
The \"Why this?\" \n
\n
- \n
\nWork exclusively on new product development
\n
\nSee your software move from concept to globally manufactured hardware
\n
\nLearn directly from a highly experienced engineering team
\n
\nGet exposure to the complete product development lifecycle early in your career
\n
\nWork across embedded software, IoT, connected interfaces and physical systems
\n
\nContribute to products that combine software, electronics and mechanical engineering
\n
\nBuild reusable platforms rather than repeatedly starting from scratch
\n
\nJoin a growing, low-turnover engineering function
\n
\nAccess annual incentives and a long-term equity-style reward
\n
\nGain occasional exposure to international manufacturing operations
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
This is an opportunity to build software people can physically interact with, learn from people who have done it at scale, and get the kind of technical breadth that can be difficult to find early in your career.
\n
\n
Still reading? Get applying and let's talk.
\n