{"id":6027,"date":"2026-04-26T13:06:01","date_gmt":"2026-04-26T13:06:01","guid":{"rendered":"https:\/\/dalelane.co.uk\/blog\/?p=6027"},"modified":"2026-04-26T13:07:53","modified_gmt":"2026-04-26T13:07:53","slug":"22-years-at-ibm","status":"publish","type":"post","link":"https:\/\/dalelane.co.uk\/blog\/?p=6027","title":{"rendered":"22 years at IBM"},"content":{"rendered":"<p>Looking back at my career so far, and what this could mean for what comes next&#8230;<\/p>\n<p><!--more--><\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: August 2003<\/strong> &#8211; June 2007<br \/>\n<strong>title: Associate Software Engineer<\/strong><br \/>\n<strong>roles:<\/strong> Development, System Test, Level 3 Service<br \/>\n<strong>product: IBM MQ<\/strong><br \/>\n<strong><em>then WebSphere MQ<\/em><\/strong>\n<\/div>\n<p>I did a few different jobs across a few years &#8211; rotating through Development, Test, and Level 3 Service teams. I learned a lot, about middleware and the role of messaging in enterprise architectures, and more importantly about what software development at scale with high standards looks like.   <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: June 2007<\/strong> &#8211; August 2008<br \/>\n<strong>title: Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Level 3 Service<br \/>\n<strong>product: IBM Business Automation Workflow<\/strong><br \/>\n<strong><em>then WebSphere Process Server<\/em><\/strong>\n<\/div>\n<p>Another Level 3 Service role, another chance to quickly understand and implement fixes in production enterprise software. But this time in a new product space (business process management), and on a new platform (z\/OS mainframes).   <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: August 2008<\/strong> &#8211; June 2011<br \/>\n<strong>title: Software Engineer<\/strong><br \/>\n<strong>team: IBM Research<\/strong><br \/>\n<strong><em>then Emerging Technology Services<\/em><\/strong>\n<\/div>\n<p>A client-facing role &#8211; helping clients to understand and adopt emerging technologies. My projects spanned a wide range of technology areas, including IoT and sensors, web 2.0 and social, mobile apps, and AI and ML. This was sometimes through presentations and workshops, but often through building demos and proofs-of-concept. <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: April 2011<\/strong> &#8211; April 2012<br \/>\n<strong>title: Senior Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Developer<br \/>\n<strong>product: IBM Watson<\/strong><br \/>\n<strong><em>transitioning research project<\/em><\/strong>\n<\/div>\n<p>In February 2011, the Watson research project was demonstrated on a US TV gameshow. For a year following this, the code was adopted by a small team of developers to take the research breakthrough, and commercialize it through working aspects like scalability, performance, security, and manageability.   <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: April 2012<\/strong> &#8211; December 2014<br \/>\n<strong>title: Senior Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Developer<br \/>\n<strong>product: IBM Watson<\/strong><br \/>\n<strong><em>then IBM Watson Group<\/em><\/strong>\n<\/div>\n<p>The Watson platform derived from the Research breakthrough project was applied in large-scale projects in industries such as healthcare and financial services. I was responsible for the tooling used to develop and deliver the projects, with a focus on accuracy analysis for a large-scale complex machine learning system. <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: January 2015<\/strong> &#8211; December 2016<br \/>\n<strong>title: Staff Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Lead Developer<br \/>\n<strong>product: IBM watsonx<\/strong><br \/>\n<strong><em>then IBM Watson Developer Cloud<\/em><\/strong>\n<\/div>\n<p>The Watson strategy shifted from a small number of large-scale dedicated clusters used by AI\/ML experts on long-term specific projects, to providing reusable cloud services for developers without an AI\/ML background to quickly create diverse projects. I worked on the creation of several new multi-tenant AI cloud services and the developer tooling to access them. <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: January 2017<\/strong> &#8211; December 2017<br \/>\n<strong>title: Staff Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Lead Developer<br \/>\n<strong>product: IBM Event Endpoint Management<\/strong><br \/>\n<strong><em>then Managed Event Streams<\/em><\/strong>\n<\/div>\n<p>I worked on developing an idea for a new software offering (bringing the discipline of API management to event streaming protocols like MQ, MQTT, and Kafka) and prototyping the new technologies needed to enable it (leading to the creation of a first-of-a-kind Kafka-protocol aware Event Gateway).<\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: January 2018<\/strong> &#8211; July 2021<br \/>\n<strong>title: Staff Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Technical Lead (2018-2020), Architect (2020-2021)<br \/>\n<strong>product: IBM Event Streams<\/strong>\n<\/div>\n<p>Event Streams was Apache Kafka, with additional supporting components for running, managing, and monitoring it in Kubernetes clusters, and a focus on design and user experience. <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: January 2021<\/strong> &#8211; July 2021<br \/>\n<strong>title: Staff Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Architect<br \/>\n<strong>product: IBM Event Endpoint Management<\/strong>\n<\/div>\n<p>We revived and released the \u201cManaged Event Streams\u201d prototype project that I\u2019d worked on in 2017 (which we\u2019d paused to build and launch Event Streams). This was a new type of product, enabling clients to use Kafka in new and different ways. <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: August 2021<\/strong> &#8211; January 2023<br \/>\n<strong>title: Staff Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Platform Engineer<br \/>\n<strong>team: IBM Client Engineering<\/strong><br \/>\n<strong><em>then Technology Garage<\/em><\/strong>\n<\/div>\n<p>I worked with our clients to rapidly prototype and validate solutions using IBM technologies. In addition to building a wide range of Minimum Viable Products (MVPs) solutions for UK companies in a variety of industries, I also learned how IBM brings products to market and approaches sales, which I\u2019d not seen working in product development.   <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>when: January 2023<\/strong> &#8211; now (April 2026)<br \/>\n<strong>title: Principal Software Engineer<\/strong><br \/>\n<strong>role:<\/strong> Chief Architect<br \/>\n<strong>product: IBM Event Automation<\/strong>\n<\/div>\n<p>I returned to Kafka, taking technical responsibility for the Event Streams and Event Endpoint Management products that I\u2019d worked on before, and adding Event Processing to the set. Event Processing is an event stream processing platform based on Apache Flink, together with a business-user-friendly low-code event stream processing authoring tool.  <\/p>\n<div style=\"font-size: 1.1em; border-top: thin black solid; padding-top: 0.5em;\">\n<strong>next?<\/strong>\n<\/div>\n<p>And that brings us to now. <\/p>\n<p>This isn\u2019t meant to be a implied announcement that I have a plan for what comes next. (And I\u2019ve written similar posts before <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=291\">in 2008<\/a>, <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=2870\">in 2013<\/a>, and <a href=\"https:\/\/dalelane.co.uk\/blog\/?p=4458\">in 2021<\/a>.)<\/p>\n<p>But, I have been in my current role for a few years now, which my history suggests is a long time for me. It is a good time to reflect about what might come next. <\/p>\n<p>I\u2019d like to get back into AI\/ML again &#8211; I miss my Watson days. Plus I watch more than a few AI projects today with frustration as they make many of the same mistakes that we made a decade or more ago. <\/p>\n<p>I think there is more interesting work to do in the Kafka world &#8211; it\u2019s not as widely adopted it could be. And Flink is only just getting started. <\/p>\n<p>I\u2019d like to go back to being more hands-on as a developer again &#8211; agentic coding tools are changing the game for the role of a technical leader. I\u2019m excited about how this could improve the job of a \u201cChief Architect\u201d. <\/p>\n<p>But who knows what\u2019s next? I\u2019ve never been great at long-term career planning, and instead just looked for opportunities to build new things and solve new problems. Some of the most fun I&#8217;ve had came from jumping to something new outside of my comfort zone. \u00af_(&#x30C4;)_\/\u00af<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Looking back at my career so far, and what this could mean for what comes next&#8230;<\/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-6027","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\/6027","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=6027"}],"version-history":[{"count":8,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/posts\/6027\/revisions"}],"predecessor-version":[{"id":6036,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=\/wp\/v2\/posts\/6027\/revisions\/6036"}],"wp:attachment":[{"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6027"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6027"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dalelane.co.uk\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6027"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}