Here is another example entry from my mammoth engineering experience record for the PEO. This was my first job in the field in which I had obtained my Master’s degree (Biomedical Engineering) and the company developed QA hardware and software for the medical physicists and radiation oncologists.
Nothing too special here. One of my supervisors was a P.Eng., so that helps.
|Company||Acme Medical Products|
|Supervisor||(A P. Eng.)
|P. Eng reference (colleague)||(A former colleague, who was a P. Eng.)
License: 123456789 (PEO)
|Responsibilities||Developed software applications for the control of quality assurance devices in the field of radiotherapy oncology. The majority of work focused on a product line of description of specific product I spent most of my time developing.|
2.2.1 Application of Theory
Note the active language, as suggested by PEO. Try to write your summaries as “I designed… “, “I tested…”, etc. so that it is abundantly clear that you, and no one else, performed these tasks.
|Analysis||The motor controller for the product had ethernet connectivity, which had previously only been used through a direct connection. I assessed, by developing a programming language prototype, the feasibility of controlling the device over local area network (LAN), which became a major feature of the software upgrade.|
|Design and Synthesis||I was responsible for the entire design and development of the new version of the software application. This included motor control of the product, visualization of the active simulation, and the generation, management, and editing of product-specific patient data.|
|Testing Methods||I developed, documented, and executed a regression test plan for the software application that covered all features, functionality, and use cases, in order to ensure that the software functioned as specified.|
|Implementation Methods||I designed and tested the software to comply with CSA standards such that operation ceased in a safe manner if the communication between the device and software was interrupted.|
2.2.2 Practical Experience
The “significance of time” section can be a challenging one and, as you can see below, I had to a reach a little bit in this case.
|Function of components as part of the larger system||The software was designed and tested to function on a number of operating systems (Windows XP, Vista, 7) and to be able to control the product over a direct or LAN connection.|
|Limitations of practical engineering and related human systems in achieving desired goals||The motion motor used in the product was limited in the maximum accelerations and velocities that it could achieve. The software was designed to accordingly limit both generated and measured patient data from exceeding these physical limits.|
|The significance of time in the engineering process||The previous versions of the software was developed in an older technology (C++ MFC), which, as the customer's operating systems were being upgraded due to newer versions becoming available, caused a degraded user experience. I transitioned our software to the Microsoft .NET Framework, which ensured portability across the majority of our users Windows-based platforms and a more consistent user experience.|
|Knowledge and understanding of codes, standards, regulations and laws that govern applicable engineering activities||I was required to understand the CSA standards for our product and what functionality the software required to comply with them.|
2.2.3 Management of Engineering
This is an example of how, even at a job where someone is not a “manager” or directly supervising anyone, you can still be exposed to management-related activities.
|Planning||Led a full review of the initial version of the software (to be replaced) with all product stakeholders. Requirements for the features and performance of the next version of software were established.|
|Scheduling||I was responsible for the software development schedule, including estimation of internal development tasks, managing external dependencies (e.g. motor controller firmware development), and keeping management informed on changes in the product release date.|
|Supervision||I implemented a web-based software code review system and gave a technical presentation to introduce development team to this process improvement.|
2.2.4 Communication Skills
|Preparing written work||I wrote detailed test reports and release notes for all product software. I also provided technical input to written marketing material for several products.|
|Oral Reports or Presentations||I performed internal demonstrations of software to the management team.|
|Presentations to General Public||N/A|
2.2.5 Social Implications of Engineering
One benefit of working in the medical sector is that the social implications are fairly direct and not difficult to articulate.
|The value of benefits of engineering work to the public||Products such as the MyProduct and its control software help to assure that radiation therapy systems are functioning as expected, which benefits cancer patients.|
|The safeguards in place to protect the employees and the public and mitigate adverse impacts||The product is a quality assurance device and provides medical physicists with the means to test the product-specific aspects of their radiation therapy systems. Radiation therapy quality assurance helps to ensure that cancer patients receive the proper dosage of radiation, delivered to the correct anatomical location. Lack of quality assurance in radiation therapy leading to disastrous results have been well documented (e.g. Therac 25 case study).|
|The relationship between engineering activity and the public at large||N/A|
|The significant role of regulatory agencies on the practice of engineering||The American Association of Physicists in Medicine (AAPM) published a task group report (TG-53) containing recommendations for clinical radiotherapy treatment planning. The recommendations in the report included rigorous testing of the systems involved, establishing a need for products such as the MyProduct.|