{"id":6083,"date":"2026-07-04T14:48:33","date_gmt":"2026-07-04T14:48:33","guid":{"rendered":"https:\/\/dalelane.co.uk\/blog\/?p=6083"},"modified":"2026-07-04T16:11:23","modified_gmt":"2026-07-04T16:11:23","slug":"i-have-a-new-job","status":"publish","type":"post","link":"https:\/\/dalelane.co.uk\/blog\/?p=6083","title":{"rendered":"I have a new job!"},"content":{"rendered":"<p><strong>In April, I wrote an <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=6027\">outline of my career<\/a>. That post is already out of date, because I have a new job to add to the list.<\/strong><\/p>\n<p>I&#8217;m joining <a href=\"https:\/\/confluent.io\"><strong>Confluent<\/strong><\/a>  as a <strong>Principal Software Engineer<\/strong> working on <strong>Confluent Platform for Apache Flink<\/strong>. <\/p>\n<p>I won&#8217;t try and describe what &#8220;Confluent Platform for Flink&#8221; is here. Partly because I&#8217;m sure I&#8217;ll have plenty to say about it in coming months. Mostly because I&#8217;ve got a lot to learn and anything I say today will almost certainly be incomplete or inaccurate in ways I&#8217;ll find embarrassing once I know more. In the meantime, <a href=\"https:\/\/www.confluent.io\/product\/confluent-platform\/\">the product page<\/a> or <a href=\"https:\/\/docs.confluent.io\/cp-flink\/current\/\">the docs site<\/a> are the best places to go if you&#8217;re curious.<\/p>\n<p>But that won&#8217;t stop me speculating about what this all means for me.<\/p>\n<p><!--more--><\/p>\n<h3>What stays the same?<\/h3>\n<p><strong>I still work for IBM.<\/strong> With <a href=\"https:\/\/newsroom.ibm.com\/2026-03-17-ibm-completes-acquisition-of-confluent,-making-real-time-data-the-engine-of-enterprise-ai-and-agents\">IBM&#8217;s acquisition of Confluent<\/a> now complete, Confluent is an IBM company. Although it doesn&#8217;t entirely feel like it, this is an internal move. <\/p>\n<p><strong>I&#8217;m in the same technology space.<\/strong> The product I&#8217;ll be working on is about helping companies run Apache Flink on self-managed and on-premise Kubernetes clusters, to process streams of events on Apache Kafka topics. If you keep to that high a level and squint a bit, a lot of the technology there is <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=5906\">the same stuff I&#8217;ve been working on<\/a>.<\/p>\n<h3>What changes?<\/h3>\n<p><strong>I&#8217;ll be more focused and more hands-on.<\/strong> My <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=6027\">role in Event Automation<\/a> was technical leadership across a portfolio of related products: Event Streams (our Kafka distribution), Event Endpoint Management (our event governance product and the Kafka gateway we invented to enable it), Event Processing (our Flink distribution and <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=5304\">tooling<\/a>), and an event streaming capability in <a href=\"https:\/\/www.ibm.com\/products\/webmethods-hybrid-integration\">IBM webMethods Hybrid Integration<\/a>. I was responsible for products spanning both on-prem Kubernetes and on-cloud <a href=\"https:\/\/www.ibm.com\/think\/topics\/ipaas\">iPaaS<\/a>. <\/p>\n<p>In other words, it was about breadth. My opportunities for coding were prototyping new ideas for future features and doing bits specifically related to customer projects I supported. I&#8217;m still working out exactly what my new role in Confluent will involve, but I know it&#8217;ll be more hands-on and focused on a narrower scope. I&#8217;m looking forward to this. I&#8217;ll be a proper developer again. I&#8217;ve spent too much time in meetings over the last year. <\/p>\n<p><strong>I&#8217;ll be working in a remote-first distributed team.<\/strong> I <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=6027\">haven&#8217;t worked in a remote-first team since 2016<\/a>. I&#8217;ve enjoyed the norm of collaborating with my team in person, pairing at the same screen or standing around the same whiteboard. There have been occasions since then where I haven&#8217;t been able to (most obviously, the pandemic), and I didn&#8217;t enjoy them. I&#8217;m nervous about this, and will make an effort to avoid feeling isolated again. <\/p>\n<p>First decision on this is that I&#8217;m going to keep going into <a href=\"https:\/\/en.wikipedia.org\/wiki\/IBM_Hursley\">the office at IBM Hursley<\/a>, even though I don&#8217;t have any work reason to. <\/p>\n<p><strong>I&#8217;ll be working on an established product.<\/strong> For <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=6027\">every software product I&#8217;ve worked on since 2008<\/a>, I&#8217;ve been around since day one and was a part of launching it. Confluent Platform for Apache Flink <a href=\"https:\/\/www.confluent.io\/blog\/introducing-confluent-platform-7-8\/#flink-generally-available\">launched in December 2024<\/a>. <\/p>\n<p>In practice, this probably is a smaller difference than it feels like &#8211; there are always existing technologies to learn. For example, although I was a part of launching IBM&#8217;s Event Streams, it was based on Apache Kafka which was an established technology. But still&#8230; most of my career has been building and launching new products, so it feels weird to be the new guy on something already out there. <\/p>\n<h3>Why now?<\/h3>\n<p>So&#8230; exciting times! <\/p>\n<p>The <a href=\"https:\/\/www.ibm.com\/docs\/en\/announcements\/withdrawl-event-automation\">withdrawal of Event Automation<\/a> <sup>[1]<\/sup> was obviously the catalyst for me needing some sort of change, but&#8230; I was overdue a change. My three-and-a-half years in Event Automation was the <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=6027\">longest I&#8217;ve ever spent doing the same role<\/a>. <\/p>\n<p>(<em>Technically, I was in IBM MQ for 3 years 10 months, but that was a graduate rotation thing moving each year between different teams across Development, Test, and Level 3 Support roles, so that didn&#8217;t feel like the same job for the whole time<\/em>). <\/p>\n<p>With my attention-deficit tendencies, I think I was overdue switching things up to do something a little different! <\/p>\n<p>.<\/p>\n<p><\/p>\n<hr \/>\n<p><sup>[1]<\/sup> &#8211; <em>yes, the typo in that URL makes me itch<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In April, I wrote an outline of my career. That post is already out of date, because I have a new job to add to the list. I&#8217;m joining Confluent as a Principal Software Engineer working on Confluent Platform for Apache Flink. I won&#8217;t try and describe what &#8220;Confluent Platform for Flink&#8221; is here. Partly [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[255],"class_list":["post-6083","post","type-post","status-publish","format-standard","hentry","category-ibm","tag-career"],"_links":{"self":[{"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/posts\/6083","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6083"}],"version-history":[{"count":16,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/posts\/6083\/revisions"}],"predecessor-version":[{"id":6099,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/posts\/6083\/revisions\/6099"}],"wp:attachment":[{"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6083"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6083"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6083"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}