Electrical Engineering Technology degree
Study across electrical and electronic systems, power, renewable energy, control, programming and applied design.
Electrical Engineering Technology graduate and Engineers Australia Graduate Member seeking a first professional engineering opportunity. I bring hands on experience in electronics assembly, embedded systems, electrical projects, programming, testing and technical fault diagnosis, together with current professional experience supporting business critical technology.
The combination is broader than a typical graduate profile. It includes degree level electrical engineering study, earlier electrical trade focused education, electronics production experience and several years of professional technical troubleshooting.
Study across electrical and electronic systems, power, renewable energy, control, programming and applied design.
PCB assembly, soldering, calibration, sensor integration, circuit testing and electronic fault finding.
Arduino, C++, Python, MATLAB, IoT, ultrasonic sensing and programmed control behaviour.
Current work across Windows, SQL, TCP IP networking, hardware, EFTPOS, printers and connected devices.
The part of engineering I enjoy most is where physical hardware, sensing and software have to work together as one system. I like taking an uncertain fault, breaking it into smaller questions and testing each assumption until the cause becomes clear. That is the same thinking I bring to electronics projects and to the live technical systems I support professionally.
My formal education combines degree level electrical engineering study with earlier electrical technology training, professional engineering membership and practical site safety credentials.
Degree level study across electrical and electronic systems, power, renewable energy, control systems, programming, testing and applied engineering design.
These projects are important to me because they were not only exercises in making something work. Each one started with a problem I found interesting, then required me to combine electrical systems, electronics, programming, mechanical ideas and testing into a complete working prototype.
I wanted to work on a project where electronics could solve a practical human problem rather than simply operate as a demonstration circuit. A traditional walking stick gives a blind person information only after the stick physically touches an object. I was interested in whether a simple embedded system could provide an earlier warning and give the user more time to react before making contact with a person, wall or obstacle.
That made the project interesting to me because the electronics had to become part of the user's interaction with the environment. The important question was not only whether a sensor could detect an object, but whether the information could be turned into feedback that was useful without requiring the user to look at a screen.
Develop an assistive walking stick that could electronically detect nearby obstacles and warn the user through vibration and an audible beeper before the user physically contacted the obstacle with the stick.
The first design decision was that the warning could not depend on a visual interface. The person using the stick needed to understand that something was nearby while still concentrating on walking. This led to the use of tactile vibration as the primary feedback method and a beeper as a secondary warning.
An Arduino Uno was used because it provided a straightforward way to connect multiple sensor inputs and control the warning outputs in one embedded system. It became the decision making part of the prototype. The Arduino continuously read the sensing hardware, interpreted the proximity information and selected the appropriate feedback state.
The prototype used proximity and infrared sensing to look at the environment ahead of the stick. The purpose of using electronic sensing was to detect an object before the end of the stick physically reached it. Sensor placement therefore mattered because the sensing area needed to represent the path immediately in front of the user rather than pointing too far away from the direction of travel.
The Arduino program repeatedly checked the sensor readings and compared them against the warning logic. When the system detected that a person or object was close enough to create a collision risk, the controller changed the output state. This separated the project into three clear functions: sensing, decision making and user feedback.
A vibration motor was selected because the user could feel the warning directly through the stick. This avoided depending entirely on sound, which could be difficult to notice in a noisy environment. The beeper was added as a second warning method so the system had both tactile and audible feedback.
The sensing hardware needed to face the direction of travel while the Arduino and wiring needed to remain protected and out of the way of the user. The wiring was routed so it did not interfere with the normal use of the stick, and the feedback device was positioned where vibration could be transferred effectively to the user's hand.
After individual components were operating, the important test was whether the whole system behaved sensibly as an obstacle approached. The prototype was tested against nearby people and objects at different positions and distances while checking that the warning occurred before the user would normally make contact with the object using the stick.
Testing helped identify where sensor positioning, warning behaviour and wiring arrangement could be improved. The goal was to avoid a system that constantly warned the user when there was no immediate risk while still giving enough notice when an obstacle was genuinely close.
The way information is presented to the user matters just as much as detecting the obstacle. The project made me think about engineering from the user's perspective rather than only from the circuit perspective.
I would record detection distance, false warnings and response consistency across more obstacle types, then use that data to tune the warning logic and sensor placement more systematically.
Arduino Uno programming, proximity sensing, infrared sensing, assistive technology design, embedded control, tactile feedback, audible warning systems, low voltage wiring, sensor placement, system integration and prototype testing.
After working on the walking stick, I wanted to take the same general idea of detecting an obstacle before physical contact and apply it to a different user problem. A reversing vehicle has the same basic challenge: the driver needs to know that an obstacle is getting close before the vehicle reaches it.
The difference was that a driver can use visual information. That allowed me to change the interface completely. Instead of vibration being the main output, I wanted the system to calculate proximity and show the remaining distance on a screen so the user could see how much space remained before reaching a wall or object.
Build a reversing assistance prototype that measured the distance to a wall or obstacle and displayed the remaining proximity to the driver before contact occurred.
The project began with the same basic principle as the walking stick: sense an obstacle before contact occurs. The main engineering change was the interface. A vehicle reversing system could provide more detailed information because the driver was able to look at a display.
The proximity sensor monitored the area behind the simulated vehicle and produced information that changed as the prototype moved closer to a wall or fixed object. The controller repeatedly sampled this information so the displayed value could update as the distance changed.
The controller processed the sensor input and converted it into a proximity value that could be understood by the driver. This was important because raw sensor information is not useful by itself. The program had to turn the measurement into something meaningful on the display.
The calculated distance was displayed visually so the driver could see the remaining space before the vehicle reached the obstacle. This made the system more informative than a simple warning light because the user could watch the distance reduce during reversing.
The program also divided the measured range into warning conditions so the user could quickly understand when the vehicle was moving from a safe distance toward a more critical distance. The warning behaviour and displayed reading worked together rather than acting as separate features.
The prototype was moved toward a known fixed object while the screen was monitored. The purpose of the test was to confirm that the displayed distance changed in the correct direction and that the warning state became more urgent as the remaining space reduced.
The system was adjusted so the information was easy to interpret without distracting the user. The main lesson was that a good reversing aid needs both measurement and communication. Detecting the wall is only part of the problem; the system also needs to tell the driver clearly what that measurement means.
The walking stick and reversing sensor shared a similar sensing idea, but the output interface had to change because the user and operating environment were different.
I would compare displayed distance against measured physical distance across a larger test range and record the error at each point to create a clearer calibration profile.
Proximity sensing, distance measurement, embedded programming, display interfacing, user feedback design, warning logic, sensor integration, low voltage electronics and functional testing.
I was interested in the idea that energy we normally ignore could still be captured and used. People create mechanical energy every time they walk, so I wanted to see whether that repeated pressure could be converted into electrical power and then stored instead of disappearing as wasted movement.
What made the project especially interesting to me was that it was not only a generation problem. The raw output from the piezoelectric elements was not immediately suitable for charging a battery. The project therefore became a small power electronics system involving mechanical design, rectification, voltage conversion, charge control and storage.
Generate electrical energy from foot pressure using piezoelectric crystals, condition the changing electrical output and store the recovered energy in a battery.
The main prototype used two wooden plates with a spring like mechanism between them. The upper plate moved when a person stepped on it, applying force to the energy harvesting elements, while the spring action allowed the plate to return after the pressure was removed.
Piezoelectric crystals were installed so the movement of the upper plate placed mechanical stress on them. When pressure was applied, the elements produced an electrical output. Using several elements allowed the project to demonstrate energy generation across repeated footsteps rather than relying on a single element.
The piezoelectric output needed to be conditioned before it could be treated like a useful charging source. A rectifier circuit was used so the electrical output was converted into a consistent polarity for the following stages. This was the first step in turning an irregular generated signal into usable stored energy.
Footsteps do not produce exactly the same electrical output every time. A buck boost stage was therefore included so the voltage could be conditioned toward the level needed by the charging system even when the generated input changed.
The conditioned electrical output was passed to a charge controller before reaching the battery. This created a proper charging path rather than trying to connect the changing piezoelectric output directly to storage. The full electrical chain became generation, rectification, voltage conversion, charge control and battery storage.
Testing was carried out across the electrical path rather than only checking the battery at the end. The generated output was checked after pressure was applied, then the behaviour of the rectifier, buck boost circuit and charge controller was checked as the energy moved through the system.
After building the larger platform, I wanted to see whether the same concept could be made portable. I built a smaller version using the same basic piezoelectric generation and power conditioning idea and mounted the generating elements onto my shoes.
The output was connected through the same general circuit concept so the energy generated while walking could be used to charge a power bank. The experiment worked in the sense that electrical energy was generated and the power bank could receive charge, but the amount of power produced was very low.
That result was useful because it demonstrated the difference between proving that a concept works and proving that it is practical. A person can generate measurable electrical energy while walking, but the available power from a small wearable piezoelectric system is limited. It would take a large number of steps and significant time to make a meaningful contribution to a normal power bank.
I liked that the smaller version gave me a real limitation rather than a perfect classroom result. It showed me that engineering is also about asking whether a working idea produces enough useful output to justify the design.
The project successfully produced and stored energy, but the shoe mounted experiment made the low power limitation much more obvious and gave me a better understanding of energy density and practical system efficiency.
I would log voltage, current and accumulated energy across a known number of steps, then compare the mechanical input and stored electrical energy to quantify efficiency and identify where the greatest losses occur.
Piezoelectric energy harvesting, mechanical design, rectification, buck boost conversion, battery charging, charge control, low voltage measurement, power electronics, portable prototyping and practical evaluation of system limitations.
This was the project where I wanted to combine the most parts of my engineering study into one system. Instead of building one generator or one controller, I wanted to explore a bigger question: could a house continue generating useful electrical energy if the weather changed and one renewable source became weak?
That led to the idea of a miniature off grid house using several energy sources together. Solar could work well in bright conditions, hydro could use available water or rainfall, wind could contribute when conditions were suitable, and the footstep system could recover a small amount of energy from normal human movement. The Raspberry Pi IoT layer then provided monitoring and control so the house was not only generating energy but also using it intelligently.
Build a miniature house that demonstrated how multiple renewable energy sources, automatic solar tracking, electrical storage, IoT monitoring and load control could work together as an off grid energy concept across changing weather conditions.
The concept started from the limitation that no single renewable source is available at full output all the time. A fixed solar panel depends on sunlight, wind generation depends on wind, and hydro depends on available water. The house therefore used several generation ideas so one source could contribute when another was weak.
The miniature house used a drainage based hydro generation idea. Water could come from a lake style source or from rainfall collected through the drainage system. Before the water reached the storage tank, it was directed through a wheel or turbine mechanism so the moving water could contribute electrical generation.
I liked this part because it treated drainage water as something that could potentially perform useful work before being stored. The same rainwater that would normally be directed away from the house became part of the energy system.
Rather than mounting the solar panel in a fixed position, the panel was placed on a rotating mechanism. Light dependent resistors were positioned so the system could compare light intensity from different directions.
The purpose was to make the model respond to the location of the strongest light source and keep the solar panel pointed toward the brightest available area rather than assuming the best angle would remain constant.
The LDR values were read by an Arduino Uno. The program compared the light levels and determined which direction contained the stronger light. A servo motor then rotated the solar panel toward that direction.
This created a closed feedback loop: the sensors measured light, the Arduino made the decision, the servo moved the panel, and the sensors were read again to continue adjusting the position.
A wind generation element was included as another weather dependent source. The idea was that conditions which reduced solar performance might still provide wind, allowing the overall house concept to draw from a different form of renewable energy.
The footstep generation work was incorporated into the smart house concept as an additional small scale source. This allowed human movement around the house to be represented as another opportunity to recover energy, even though the amount of power from this method was much smaller than the primary generation methods.
The model included electrical loads such as lighting and other miniature household equipment. These loads made it possible to demonstrate the complete idea of generation, monitoring and consumption rather than only showing isolated power sources.
A Raspberry Pi was used as the IoT monitoring and control layer. It provided a way to monitor power generation and control lights and electrical equipment inside the miniature house. This connected the electrical energy system to software based monitoring and control.
The most important part of the project was not any one generator. The goal was to demonstrate how several imperfect energy sources could be combined so the house had more options under different weather scenarios. The project became an exercise in system integration rather than only individual circuit design.
The project showed me that generation, control, sensing, storage and loads all affect one another. A strong individual subsystem does not automatically create a strong complete system.
I would add formal energy logging for each source, track generation over time and build a clearer power management strategy that decided when energy should be stored, used immediately or prioritised for specific loads.
Renewable energy integration, solar tracking, LDR sensing, Arduino Uno programming, servo control, hydro generation concepts, wind generation, piezoelectric energy harvesting, Raspberry Pi IoT, electrical wiring, load control, embedded systems and whole system integration.
My work history shows progression from electronics assembly and practical workshop environments into customer service, professional IT support and business critical technical systems.
Skills are grouped into four predictable categories so they can be scanned quickly rather than presented as one long keyword list.
Open to graduate and entry level opportunities where electrical engineering, electronics, embedded systems, testing, automation, field work or technical IT experience can add value.