Software Engineer: Inventory Management System for Valeo
- Period
- Dec 2022 – Sep 2023 · 10 mos
- Organisation
Artillence Kft.- Role
- Software developer and design engineer
- Location
- Artillence Kft.Németvölgyi út 87/A, 1124 Budapest, Hungary
- Posted
Designed, managed and developed an enterprise inventory management system for Valeo Automotive's offices in Budapest, Erlangen, Giza, Cergy and other sites. I led requirements analysis, Python development, CI/CD, testing and validation, documentation and customer coordination.
- Built from scratch for a multinational automotive supplier
- Co-designed the CI/CD process, from code to deployment and monitoring
- Coordinated with Valeo stakeholders across several international offices
Artillence is a small Hungarian consultancy and software vendor that works for Valeo Automotive, among others. Valeo needed an internal inventory management system for its offices in Budapest, Erlangen, Giza, Cergy and other locations. I designed, managed, developed and coordinated that project, and with the team I built it from scratch. The work ran alongside my MSc, and from April to June 2023 it also counted as the programme's 240-hour professional internship.
Responsibilities
The role was half engineering and half management.
Engineering
- Research, analysis and evaluation of requirements for the inventory application and the operating systems it had to run on.
- Software design and development in Python.
- Co-designing and building the CI/CD process, covering the whole cycle from code to deployment and monitoring.
- Evaluating the hardware–software interface together with the engineers on site.
- Developing and overseeing testing and validation protocols.
- Assessing, refining and documenting maintenance procedures for the operating systems, communication environments and application software involved.
Management
- Managing the programming work and the development of the documentation.
- Ongoing dialogue with Valeo about development and maintenance, with stakeholders spread across several countries.
What I took away
This was where I learned that most project risk sits between the requirements and the code: in assumptions nobody wrote down, in environments that differ from site to site, and in what "done" means to different stakeholders. I now bring that perspective to teaching software engineering and to supervising student projects.