37 lines
1.7 KiB
Markdown
37 lines
1.7 KiB
Markdown
|
||
# Current Job
|
||
|
||
My job title is **Test Software Specialist** with the official qualifier **Test and Testability Expert**, in an leading european defense company.
|
||
|
||
I have been working in this company for nearly 10 years and climb from software developer contractor to this position.
|
||
|
||
|
||
# Job Key points
|
||
- Designing the company TE(Test Equipment) SW Platform so it fit:
|
||
- Needs of 200 developers (in 4 site / 2 countries), 20-50 new TE every year
|
||
- Requirements of 3 (main) usages: UUT development / production and maintenance
|
||
- Both for intern usage and external-customers delivery
|
||
- From small system (1 bay, to test a simple card) to big one (a complete warehouse, to test a full system)
|
||
- A given version might be used for 20+ years
|
||
- TE are both an execution and development platform
|
||
- Helping people to use this platform:
|
||
- Documentation / Training
|
||
- Dedicated support in TE integration
|
||
- Design & Develop Test SW template projects to correctly use this platform
|
||
- Support on Project & Team management
|
||
- Interface with projects:
|
||
- Quotations / Planning
|
||
- Feature survey or requests
|
||
- Some important part I have dedicated responsibility:
|
||
- Companie's TE self-test generic software
|
||
- Critical libraries
|
||
- Improving working methods
|
||
- Implement CI/CD pipeline for Test SW (and later the SW platform itself)
|
||
- With the specific constraints of this application:
|
||
- For Test SW there is almost always hardware involved
|
||
- For the Platform itself it’s a system-level test, which add more limitation
|
||
- Improve reuse and coworking
|
||
- Making SW catalog and libraries requirements
|
||
- Defining methods at any stage of the process, including at non-software ones
|
||
- Technology watch (ATML, uServices approach.)
|