This period has included active development work as before, but also saw me take a more central role in various team efforts. Firstly, I took the lead on a technical integration between us and a potential partner. This involved discussions with their technical teams, as well as the design of adaptations and new features that we needed to add in order to integrate with their OAuth system and other API's. I also performed a significant amount of the development(Elixir and Phoenix), devops(terraform) and documentation(confluence) work needed for this project.Secondly, I took a central role in the design and development of a new multi-tenant on-boarding platform, that is closely coupled with our existing pub/sub system and provided OpenID support for one of our partners. Some of the more noteworthy contributions were; integration with aws services using aws instance roles, adaptations to existing API wrappers(for both aws and internal API's) and the design and development of an extensible state machine that allowed each tenant to customize their multi-step registration up flows.Thirdly, I helped to mentor a new team member. This included explaining various aspects of Elixir, the Phoenix framework and our existing systems, as well as other team specific approaches and practices.

I was a member of a small team who actively developed on and maintained, using Elixir and the Phoenix framework, a system which allows HealthQ to securely and reliably integrate with their partners. The core of the work involved the development and maintenance of a pub/sub message hub, that coordinates messages, in such a way, that subscription subjects remains anonymous. This requires extensive use of GenServer pipelines, executing in parallel. Hashing is used in several ways to distribute the load between different pipelines as well as different Erlang nodes.To support the functionality of the core project, several interfaces were also developed. These included a secure REST API, a third party authentication service, a phoenix based UI with extensive use of phoenix channels and Javascript. To help our clients(both internal and external) to integrate with the hub, we also built an extensible client library using Elixir, Tesla and customisable Tesla middleware. An aws RDS based PostgreSQL instance is used for the persistence of information.In all of the mentioned systems, I have contributed significantly, not only in code, but also with architectural suggestions, and their implementations. Several of the suggestions lead to great improvements in the overall functionality, scalability and maintainability of the relevant systems.In addition to this, I also took the lead on several adhoc projects. The most significant of these is the building of a free standing web app. The app allowed us to sign up pilot users, helped them to provide consent for participation in the pilot, allowed them to fill in questionnaires, and allowed us to correspond with them via email. The UI required a significant amount of custom html and css work, as well as live DOM manipulation using javascript. The backend, built with Elixir and Phoenix, required integration with aws IAM, Cognito and S3.

This period consisted mainly of getting the NL Sports Android app production ready, this included optimisations, testing, debugging and later Google Play Store deployment. I also contributed significantly to the improvement of the backend API. The mentioned improvements consisted both of active development and feedback, the latter of which I gave from my perspective as a mobile developer. Finally I contributed to the web-interface, especially by providing some insight into data visualisation techniques.Some of the tasks in the mobile work can be seen below:- Fabric-Beta and Google Play Store deployment- Push notifications using Firebase messaging service.- Crashlytics based issue identification.- Developing generic, dynamic and reusable UI components- Modularisation of code.- Significant usage of RxJava based reactive programming within the app. - Italian localisation- Performance optimisation using Android layout inspector, as well as GPU and CPU profiling tools.- Significant contribution to the design of the API, as well as help debugging the API from the client side.- Development of a live-data architecture using database change listeners,- Database migration in Realm.- Data manipulation on background threads using IntentService and BroadcastReceivers.Below are links to the official Next Level website, and the app on the Google Playstore.

In this position I assisted the development team with the continuous improvement of POC software for one of our prospective clients. My main projects during this time were as follows: - Setting up back-end resources as well as web/UI components for new product features. This included Mongo and Influx database components and ORM data objects. The API components on the front-end and back-end were also included. I got significant exposure to the Groovy and Java programming languages, the Spring and Spring boot frameworks and the Gradle and Maven build tools.- Debugging and testing of my own and other product features using tools such as POSTMAN and kibana.- The development of an Android app to serve as a mobile interface for the existing system. For this I utilized RxJava and retrofit to build web-calls, Android schedulers to decouple the UI from the background work and a realm database for persisting data. I also built the UI complete with custom view containers, adapters and reusable fragments. Tools used included among others Stetho and Android Studio.

In this position, I act as a product development engineer on GRW's refrigerated trailers. The position is multi-faceted in that it entails management and technical tasks relating both production and research activities. Competing products and new technologies are researched, and concepts generated for application on new models/iterations of these trailers.These concepts are developed into production-ready BOM's and drawings with the assistance of draftsmen. This happens in the context of a fast paced production environment, which also requires continuous time-management and planning, both for myself and the draftsmen that assist me.Some interesting tasks included:- Layout planning for modular designs.- Planning and communicating packing strategies for international shipping from suppliers.- Management of CE certification for a shipping frame that was developed in-house.- Prototyping, and collaboration with the "product validation and verification" team.- Assistance in the development of jigs for manufacturing.- Liaising with local and international suppliers.- Collaboration with the designers on other product-lines when designing/using shared sub-systems.- Activities related to compliance with various regulations.

The position entails design and manufacturing support for the production of truck trailers and the modular systems used during the assembly process. The designed modules ensure that the end-product matches the clients' specifications. The process involves the generation and detailing of design concepts, drafting and management of drawing packages, as well as BOM management using PTC windchill and our own in-house MRP software. In collaboration with other departments, all designs are assessed and continuously improved by decreasing its' cost and weight, while improving the ease with which it is manufactured.

Junior design engineering post with a large variety of tasks. These included the design and implementation of measurement systems and devices, 3D modelling and draft work, FEA analysis on Pro-mechanica as well as Abaqus. Other projects during this period included the assembly of electrical equipment, analysis and reporting on the volatile solid contents in the incoming and effluent streams of a bio-digester and the programming of a CNC milling machine to produce the flow-nozzles that I had designed.