Are you the enthusiastic, talented Biomedical engineering and/or Mechatronics engineering we’re looking for?
You will be joining the Innovation Team in the Oral Healthcare R&D department at Philips Drachten. This is an impactful, multi-disciplinary team of experienced and passionate professionals who collaborate with internal and external teams worldwide. You will have the opportunity to work on an important tool for validating innovative brushing technology concepts to improve consumers' oral health.
Description of assignment
The assignment consists of the following parts:
- Design requirements, specifications, and constraints for the test tool are crucial for its successful development and implementation. These elements ensure that the tool meets the intended purpose, performs as expected, and integrates seamlessly with existing systems. **Design Requirements** outline the high-level goals and functionalities the test tool must achieve. They are often user-centric and focus on what the tool needs to *do*. * **Functional Requirements:** * **Test Execution:** The tool must be able to execute predefined test cases (e.g., automated scripts, manual steps). * **Test Data Management:** It should support the creation, management, and application of test data. This includes data generation, masking, and provisioning. * **Result Recording & Reporting:** The tool must accurately record test execution results (pass, fail, error messages, timings) and generate comprehensive reports. * **Defect Tracking Integration:** Seamless integration with defect tracking systems (e.g., Jira, Bugzilla) for logging and managing defects found during testing. * **Configuration Management:** Ability to manage different test environments, configurations, and versions of the system under test. * **User & Role Management:** Support for different user roles with varying levels of access and permissions. * **Test Planning & Organization:** Features to organize and categorize test cases, test suites, and test cycles. * **Real-time Monitoring:** (Optional, depending on the tool's scope) Display of test execution progress and status in real-time. * **Audit Trails:** Recording of all actions performed within the tool for traceability and compliance. * **Non-Functional Requirements:** These focus on the quality attributes of the tool itself. * **Performance:** The tool should execute tests efficiently and without introducing significant overhead. Reporting generation should be timely. * **Reliability:** The tool should be stable and not crash or produce inaccurate results. * **Usability:** The user interface should be intuitive and easy to navigate for testers of varying skill levels. * **Scalability:** The tool should be able to handle an increasing number of test cases, users, and test runs without performance degradation. * **Maintainability:** The tool's code should be well-structured and easy to update, debug, and extend. * **Security:** The tool must protect sensitive test data and user credentials. Access control mechanisms should be robust. * **Compatibility:** The tool should be compatible with the target operating systems, browsers, and development environments. * **Interoperability:** The tool should be able to integrate with other tools in the development and testing ecosystem (CI/CD tools, repositories, etc.). **Specifications** are detailed descriptions of *how* the design requirements will be met. They translate the "what" into a more concrete "how," providing specific technical details. * **Technical Specifications:** * **Architecture:** Description of the tool's overall architecture (e.g., client-server, web-based, microservices). * **Technology Stack:** Specific programming languages, frameworks, databases, and libraries to be used. * **API Definitions:** Detailed specifications for any APIs that the tool will expose or consume for integration. * **Database Schema:** Design of the database structure for storing test cases, results, user data, etc. * **User Interface Design:** Wireframes, mockups, and style guides for the user interface. * **Data Formats:** Specification of data formats for imports, exports, and communication between components. * **Error Handling Mechanisms:** Detailed design for how errors will be detected, logged, and reported. * **Security Protocols:** Specifications for authentication, authorization, and data encryption methods. * **Integration Protocols:** Specific protocols and methods for integrating with third-party tools (e.g., REST APIs, SOAP, message queues). **Constraints** are limitations or restrictions that must be adhered to during the design and development process. These can be imposed by external factors, existing systems, or organizational policies. * **Resource Constraints:** * **Budget:** The total allocated budget for the development and maintenance of the tool. * **Timeline:** The deadline for the delivery of the tool or its specific versions. * **Personnel:** Availability and skillsets of the development and testing teams. * **Hardware/Infrastructure:** Existing hardware or cloud infrastructure limitations. * **Technical Constraints:** * **Existing Technology Stack:** The tool may need to be built using or integrate with an organization's established technology stack. * **Compatibility Requirements:** Must be compatible with specific versions of operating systems, browsers, or backend systems. * **Performance Benchmarks:** Specific performance targets that the tool must achieve. * **Security Policies:** Adherence to organizational security standards and regulations. * **Licensing Restrictions:** Limitations imposed by third-party software licenses used within the tool. * **Organizational Constraints:** * **Organizational Standards & Guidelines:** Compliance with internal coding standards, documentation policies, and architectural guidelines. * **Integration with Existing Tools:** The tool might be constrained by the capabilities or limitations of existing enterprise tools. * **Regulatory Compliance:** Adherence to industry-specific regulations (e.g., GDPR, HIPAA) if applicable to the data handled. * **Change Management Processes:** The tool's development and deployment must follow established change management procedures. By clearly defining these requirements, specifications, and constraints, stakeholders can ensure that the test tool is developed with a clear vision, meets all necessary criteria, and is implemented effectively within the given limitations.
- Based on a standard laboratory x, y, z robot, create control software for it to mimic several brushing methods. This also includes design of a suitable UI.
- Create an extension for the robot that allows control of the brushing forces applied.
- Add a camera system that evaluates brushing results.
Main required technical skills:
- Robotics, including dynamics and control theory
- Programming, preferably in Python
- CAD design for creating additional components
- Hardware and software design for controlling additional components, e.g., for Arduino boards
- Sensors and actuators
- UI design
- Vision algorithms
The exact assignment(s) can be further discussed and defined by the student in collaboration with our team. You are in the lead!
Please note that this subject is confidential and requires signing NDA-like contracts. Presentations may need to be adapted if they are required to be presented to a general audience.
We are looking for:
Master/Bachelor internship student pursuing Biomedical engineering, Mechanical engineering, or Robotics, who will work on the project for at least 5 months.
To succeed in this role, you have the following skills and experience:
- Affinity with robotics and the biomedical and consumer fields.
- Programming, preferably in Python
- Professional skills in English (written and verbal).
- Team player, passionate about results and people.
- Hands-on mentality and result driven.
- Likes to create test tools and devices based on robotics.
- A solid background in the above-mentioned subjects.
- Students open to learn a lot of new competences, like technical subjects, research, development, consumer research, international cooperation in a large-scale company etc.
- Able to work mainly on site (Drachten) for at least 3-4 days per week.
You will be part of:
In Drachten you'll find one of the largest innovation sites of Philips globally. With over 2000 colleagues from over 35 different nationalities, it's an inspiring environment for you as a young talented intern. At Philips Drachten some of the best consumer product developers in the world work together to create innovative products with excellent end-user experience.
Philips Drachten could be the start of your promising career, with lots of opportunities to develop yourself locally or internationally in different sectors of our company. At Philips you work for an employer whose activities have a major positive impact on people all over the world. You also get:
- Opportunity to strengthen your capabilities and knowledge.
- Dedicated substantial support and guidance from an experienced supervisor and support from several professionals and departments.
- You will receive an internship allowance.
- Within Philips you get the opportunity to expand your professional network.
Contact
Peter Bremer, M.Sc.El.Eng.
Advanced Systems and Predevelopment Engineer, Connected Architecture, AI and Optics
Innovation Team Oral HealthCare, Drachten
Building HA-B 03
Oliemolenstraat 5, 9203 ZN Drachten, The Netherlands
Tel: +31 6 51 66 48 92 Email: peter.bremer@philips.com
We are looking forward to receiving your a CV and a motivational letter containing your ambition as you see it now, for at least the coming 3 -5 years.
Published: May 21, 2026