Tijmen Elseviers

I designed and developed integrations that linked Collibra with our internal systems, enhancing data management capabilities across our organization. Additionally, I provided crucial support to our Architect in crafting technical designs, ensuring seamless integration and alignment with organizational goals. Furthermore, I played a pivotal role in supporting Collibra adoption from a technical standpoint, empowering teams to leverage Collibra's full potential in optimizing data governance processes.

Used Technologies: Python, Linux, K3S

In my prior role as a Collibra Engineering specialist, where I focused on Support & Integration Design, my goal was to support the Infrastructure Engineer and Application Architect in setting up Collibra effectively. With a focus on Custom Integrations, Edge, and Technical Lineage, I played a crucial role in ensuring the smooth operation of our Collibra environment.

Furthermore, in a later stage of my tenure, I facilitated a comprehensive hand-over to a more junior colleague. This involved providing in-depth guidance on troubleshooting Edge-related issues, developing custom insights, crafting custom integrations, and understanding technical lineage within the Collibra ecosystem. Through ongoing support and mentorship, I empowered the colleague to confidently navigate and contribute to our Collibra setup, enhancing our overall data governance capabilities.

Used Technologies: Collibra, SAP BO, Java SpringBoot, Sybase IQ, DB2, Python

In my previous role as a Collibra Engineering (Support) specialist, my primary focus was on supporting technical Collibra implementations. This involved troubleshooting Jobserver issues, developing custom insights, and designing workflows to enhance data governance processes. Leveraging technologies such as Collibra, AWS (EC2, Lambda), and Snowflake, I ensured the smooth operation and optimization of our data governance infrastructure.

Additionally, as part of my responsibilities, I facilitated a seamless transition for a new, more junior colleague. I provided comprehensive hand-over sessions, sharing insights into troubleshooting techniques, custom insights development, and workflow design. I also offered ongoing support and guidance, empowering the colleague to effectively contribute to technical Collibra implementations.

Used Technologies: Collibra, AWS (EC2, Lambda, CodeDeploy, CodePipeline, CodeCommit, Fargate, EKS), Snowflake, PowerBI

In my role as a Collibra Consultant, I successfully achieved the goal of ingesting and classifying over 80 data sources within the Collibra Catalog. This involved executing Edge ingestions, troubleshooting any issues encountered along the way, and ensuring seamless data integration processes. Additionally, I focused on information classification, utilizing automation to streamline the process efficiently. Moreover, I specialized in bridging the gap between business and technical requirements through meticulous business-to-technical stitching. Leveraging Collibra and Python technologies, I optimized data management processes, contributing to enhanced organizational efficiency.

Used Technologies: Collibra, Python

As a Collibra Tech Lead specializing in Retail Data Governance, I oversaw the implementation and optimization of Collibra solutions tailored to our industry's unique needs. My responsibilities encompassed managing technical aspects, troubleshooting issues, and ensuring smooth data governance operations.

Zooming in on the migration from Jobserver to Edge deployment, I played a crucial role in planning and executing this transition. By migrating to Edge deployment, our aim was to enhance scalability and agility within our Collibra infrastructure, ensuring seamless data governance processes for our retail operations.

Used Technologies: Collibra, Linux, K3S

JBC already owned an InRiver on-premise system to manage their
product data for different external systems. After they acquired CKS
they wanted to use the InRiver iPMC version (Cloud version) with a
similar setup for them. This meant that all of the existing configuration
had to be migrated to cloud.

I was responsible for the migration of the existing extensions to the new
iPMC .NET Libraries and make sure all the differences that CKS needed
for the system were implemented. They also took this moment to
implement some new improvements for the exports.

Used Technologies: .NET, InRiver

Kruidvat already had a Stibo STEP MDM system but needed some help with future improvements and bug fixes. As part of the team my task was to find issues based on the information provided by the Kruidvat super users and fix the issues. Next to that I also worked on improvements of the existing system based on their needs and of course made sure that it was the right way to go for Kruidvat and not a short term improvement.

As a second project (05/2021) Kruidvat wanted to implement a Supplier Portal into their Stibo STEP system. New use cases were analyzed and had to be implemented into the system. My job was to implement all those requirements into the system (both technically and functionally) and make sure all edge cases were covered.

Used Technologies: Stibo STEP, JavaScript

As part of the Dille & Kamille InRiver implementation team I had to
work with the client and implement their needs in the form of InRiver
Extensions. These Extensions were written with .Net and had to
communicate with external systems through either Hotfolders or REST
API Calls.

Used Technologies: .NET, InRiver

As part of the Stibo STEP Implementation team I had to work out the strategy for their new Stibo STEP MDM system. I was part of the initial phase in which we worked out the needs of Ici Paris XL based on the already existing system Kruidvat had available. Which things could be
reused and which things had to be changed?

The next step was to create the system, my task was to implement the JavaScript business rules within the different parts of Stibo STEP. New Product workflows needed some automatization to reduce the manual tasks of the end-user, there also had to be some custom validations and transformations written in JavaScript Business Actions/Conditions to make sure the external systems could handle the outgoing data.

This project had a short pause at the start of the Corona Crisis which caused the project to be stopped between 4/2020 and 3/2021.

Used Technologies: Stibo STEP, JavaScript

As part of Nike’s new Data Governance expansion initiative I was part of a larger group of Data Governance Analysts that had to work out a new Data Governance and Data Quality way of working.

On the other hand I was part of a Data Product squad in which we had to implement these new processes and make sure everything around Data Governance and Quality was clear for the squad.

Used Technologies: Collibra

During my studies I had the Idea to create a new Craft beer platform together with a friend of mine. This grew out to us truly trying to start-up this idea and make it work. The platform consisted out of 2 big parts.

The first part was the actual community part on which users could find information about beers but also would be able to talk to a Chatbot and ask information about them. On top of that people could add their personal taste opinion of a beer and setup their own taste profile. This would be used to match people with the beers they would probably like.

The second part of the platform was to create a more innovative way for smaller craft beer breweries to sell their beers online. They would be able to create their own little shop on the platform and sell through it. This would be done by finding a fulfillment partner to which the breweries would send their beers. They would package for orders and send to the buyers.

My task was to implement the data strategy and write the recommendation system in Python. As a joined effort we both worked on the business side and tried to manage the budgets and meetings with possible clients, experts and or partner company Wingmen (Cronos).

Used Technologies: Python, Node.js Loopback, Google Cloud Platform (App Engine, Cloud Function), Oswald Chatbot