What our day-to-day activities will look like (based on the kind of validation issues we face in project today):
Check completeness of CI/CD (continuous integration/deployment) build activities,
collab with IT and maintain the lab infra – this will slowly be transferred from existing team to the new person.
example, check if data from boards-database matches with actual data and Lauterbach/Reset device is unique to this device.
Slowly start developing Jenkins pipelines, enhance existing infra config and ultimately, become one-point contact for all release-related integration activities.
Over the course, train to understand embedded code so you can get familiar with project code to provide improvements related to CI/CD activities (releases, quality, release scripts etc)
Requirements
Mandatory skills:
Medium level embedded C with debugging knowledge (gdb, Lauterbach or equivalent debuggers); pointers, memory understanding are a must
Python scripting knowledge – ability to develop small features in oops concepts, debug issues in .py scripts of current framework, idea on python processes.
Basic understanding on DevOps workflow – SCM, CI build systems
1. Jenkins can be trained from DevOps team
2. knowledge on git basics, PR and CI/CD workflow – needed.
Good to have skills:
Basic networking knowledge (ARP, DHCP, what is static/dynamic IP, MAC, firewall aso); no in-depth knowledge is needed, just the basic concepts
Strong problem solving ability and independent work-oriented preferred (be confident in setting up new hardware, know ESD regulations etc)
Very good analytical thinking to solve first seen issues, especially debugging
