Lee D.

Looks like I'm first! SnapLogic Integration / Data Engineer Experience: Several years of hands-on SnapLogic experience, designing and supporting integration/data pipelines, extraction frameworks, API integrations and AWS-based data workflows. Strong experience across pipeline design, transformations/mapping, orchestration and integration architecture. Keen developer of internal accelerators and reusable solutions. At Arriva, I have developed automated solutions for operational processes including MyDrive safety and Route Association, involving multiple data extracts, transformations and API integrations. I have also developed pipelines supporting a monitoring and failure-management solution, reducing the need for manual monitoring and incident raising. Looking for: Permanent roles — SnapLogic Developer / Integration Engineer / Data Engineer, ideally at mid-to-senior level. Also interested in opportunities with a path towards integration and solution architecture. Location: North East England, UK (GMT/BST) — open to remote/hybrid opportunities, with flexibility to travel. Looking for a role where I can continue working extensively with SnapLogic while expanding further into API integration, data engineering, cloud technologies and architecture. I’m particularly interested in opportunities where I can develop into a broader architectural role. Open to learning new technologies and taking on new challenges. www.linkedin.com/in/leeduffy88 Happy to set up any time to discuss anything further. Thanks fo reading.

Whats the best way to achieve a "binary union"? I have a router om the back of a file reader, and need to convert the file type depending on what the source to target configuration is. currently looking at a direct mapping where source/target are the same, and only excel/csv to parquet, but I dont want 2 file writer snaps, so want to union direct and parquet outputs to the file writer.

I’m using multiple logging branches in a SnapLogic pipeline (for example pipeline_start, pipeline_end, and extraction) which are later combined using a Union Snap. { "logging": { "pipeline_start": { "status": "started" } } } { "logging": { "pipeline_end": { "status": "success" } } } { "logging": { "extraction": { "status": "success" } } } After Union, these remain as separate documents, but I want to combine them into a single payload with the key "logging" { "logging": { "pipeline_start": { "status": "started" }, "pipeline_end": { "status": "success" }, "extraction": { "status": "success" } } } I need a clean way (preferably simple Mapper expression) to merge all logging objects into one structured object, ideally an expression that could be dynamic.