<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[mainframe-careers - Medium]]></title>
        <description><![CDATA[Stories and advice for a bright career in mainframe. - Medium]]></description>
        <link>https://medium.com/mainframe-careers?source=rss----d23f4ae387dc---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>mainframe-careers - Medium</title>
            <link>https://medium.com/mainframe-careers?source=rss----d23f4ae387dc---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:02:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/mainframe-careers" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From 3270 to Intuitive GUI: My Summer as a Next-Gen Mainframer]]></title>
            <link>https://medium.com/mainframe-careers/from-3270-to-intuitive-gui-my-summer-as-a-next-gen-mainframer-a314b8ab16bb?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/a314b8ab16bb</guid>
            <category><![CDATA[mainframe-modernization]]></category>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Ritthikha Ragavan]]></dc:creator>
            <pubDate>Tue, 26 Aug 2025 21:56:32 GMT</pubDate>
            <atom:updated>2025-08-26T21:56:25.742Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Mission: Simplifying Mainframe Security</h3><p>This summer, I had the incredible opportunity to work at Broadcom’s Lisle office as a Next-Gen Mainframer in UX Research. Building on an academic foundation in Cognitive Science focusing on Psychology/HCI and AI from UT Dallas and prior UX research experiences in distributed environments, I was eager to dive into the unique challenges and immense potential of the mainframe world. From day one, the warm welcome and collaborative spirit of the Broadcom team, including UX colleagues, set the stage for an immersive and impactful twelve-week journey.</p><p>The mission this summer? To contribute to making the mainframe experience intuitive for next-gen mainframers. This was the vision echoed by one of our UX team members I had a 1:1 with during my first weeks in the role: ‘make mainframe usable for mom.’ This vision reflects the current overall initiative in UX — modernizing the mainframe experience. This is crucial, as the most experienced users will soon reach a well-deserved retirement, and to enable the next generation of mainframers in our customer organizations to seamlessly continue using the products they’re familiar with. Currently, this involves simplifying traditional mainframe interactions and transforming them into a modern, GUI-based, user-friendly experience.</p><p>My primary focus was on the Security Insights (SI) platform, a web-based tool designed to help mainframe security professionals and auditors analyze access controls and identify potential security risks. Its core purpose is to empower customers to gather data for compliance reports, a critical function in the face of ever-increasing regulatory and audit demands. The challenge was significant but achievable. Currently, mainframe compliance reporting methods are inefficient, requiring security professionals to recall complex 3270 commands. Many banking customers have resorted to manual workarounds due to the lack of an easy-to-use solution for comparing granular security entitlements.</p><p>Mainframe Security Administrators need to quickly replicate user permissions when there are organizational changes, allowing new personnel to perform their roles, such as approving loans. For this error-prone process involving thousands of settings and privileges on the mainframe, auditors need to verify compliance by comparing specific security entitlements to ensure the appropriate permissions are given. As senior mainframe users retire, new mainframers may lack awareness of necessary commands and prefer a more user-friendly solution. The existing process involves auditors requesting direct screenshots of live 3270 command entries, indicating distrust in non-native software reports. Overcoming this trust barrier is key to our solution’s adoption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6W97-JWsphcbHW4M.png" /><figcaption><em>As-Is: The 3270 Command Challenge — User forgot the comparison command</em></figcaption></figure><h3>Project: Driving UX for Security Insights</h3><p>Working alongside fellow researchers (Matthew Mills and Ryleigh Quinn), designer (Jim Lofton), and product team (Chip Mason and Thomas Melzer), I led the usability testing effort for the early-stage GUI-based interface designs for 3 key features for SI:</p><ol><li><strong>Runtime Comparison: </strong>Comparing security permissions at an account/user level at run-time.</li><li><strong>Full Report Delta: </strong>A broader report-level comparison to track changes over time.</li><li><strong>Scheduler: </strong>An in-built automation for report scheduling.</li></ol><p>Who were we building for? Our primary target persona was the Mainframe Security Professional, tasked with managing granular permissions and fulfilling audit requests by providing security comparison reports to auditors to verify compliance. Understanding their roles and specific pain points was crucial.</p><p>Our UX Designer Jim Lofton developed a prototype — a functional representation of the interface — to conduct usability testing with representative end-users. This prototype allowed us to simulate key functionalities, such as visually identifying modified, removed, or added items in a Full Report Comparison, or showing side-by-side attributes in a Runtime Comparison, testing initially for the Top Secret External Security Manager (ESM) environment. Our methodology was rigorous: We conducted usability testing with three internal security Subject Matter Experts (SMEs) in one-hour sessions. To ensure our research truly delivered actionable insights, I followed a two-step analysis process:</p><ol><li><strong>Initial Debriefs:</strong> Immediately after each session, I held quick discussions with our research team (and designer Jim) to capture fresh observations and spot early trends.</li><li><strong>Affinity Mapping Workshop: </strong>Then, I organized an affinity mapping workshop for our UX team to systematically organize the hundreds of individual observations into overarching themes. This collaborative approach built consensus and directly translated raw user feedback into actionable insights.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sL2c5kCGNq-iKukG.png" /><figcaption><em>Collaborative Affinity Mapping</em></figcaption></figure><h3>Uncovering Critical Insights &amp; Tangible Impact</h3><p>Our testing yielded 13 actionable insights, categorized by severity (5 High, 2 Medium, 6 Low). The direct impact of our work was clear: 38% of these insights were taken forward by the product team, resulting in 4 updated Rally items and, crucially, a saved development effort.</p><p>Our most significant high-impact findings included:</p><ul><li><strong>Prove Report Integrity — Chain of Custody:</strong> Auditors expressed significant distrust in non-native GUI reports, preferring live 3270 commands due to concerns about data alteration. This reinforced the critical need for verifiable evidence within SI to build robust audit credibility. In the short term, we have implemented a checksum (a digital fingerprint) as a temporary fix. However, this insight directly validated our architecture team’s plans for a backend “provenance solution,” a more permanent solution currently on our backlog.</li><li><strong>Trust the Data Source — Data Freshness: </strong>Users need confidence in data freshness, especially given that SI leverages periodic data loads from the CIA database, which are not real-time. Ensuring the “last refreshed” timestamp is prominent and transparent allows us to manage expectations and build trust.</li><li><strong>Provide the “Why.” Not Just the “What”</strong>: Auditors are looking for “security intelligence” — the context and reasons behind security issues, not just lists of entitlements. This validated our long-term product vision: integrating data from our security products (CEM, Cleanup, and TAMz) into SI to provide a holistic view of the security posture, a goal already on our roadmap.</li><li><strong>Strategic Insight on the Scheduler: </strong>We found that users have a strong reliance on existing external mainframe workload automation tools (like ESP and CA7) for report scheduling. This crucial insight allowed us to strategically put the in-built scheduler feature on hold, saving significant development resources and allowing the team to prioritize the other critical features, Runtime and Delta comparisons, for which design mock-ups have already been updated.</li></ul><p><strong>Findings Discussion:</strong> I involved design and the product team in a findings discussion after testing for direct comments and alignment. Directly hearing from users about their pain points, like “Need to show auditors data hasn’t been altered” and “Auditors don’t trust non-native software,” and involving the stakeholders from the start resulted in the 4 updated Rally tickets for product implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uFQV2yFIPVqbYIe7.png" /><figcaption><em>Findings Excel Document</em></figcaption></figure><h3>Beyond the Project: A Broader Learning Experience</h3><p>My summer at Broadcom was about much more than just a single assigned project. It was a broad learning experience, as I contributed not only to the Security Insights platform but also took the initiative to work on the usability testing for the Watchtower Network product, as well as a broader Security Value Stream customer research initiative to make the most of the experience. I made efforts to collaborate closely with my fellow researchers, refining testing scripts and engaging directly with SMEs and customers on numerous calls. Attending the virtual MTE for SI was a highlight, furthering my product understanding.</p><p>I valued the connected company culture, actively participating in team lunches, summer worker interlocks, and new hire roundtables. The mentorship from fellow researchers Matthew Mills and Ryleigh Quinn, as well as designer Jim Lofton, was invaluable. I proactively sought numerous sessions with Jim to clarify my extensive running list of questions about the product and the nuanced mainframe security domain. This, coupled with the constant support from manager Ruchi Saxena and our broader UI/UX team and leadership, reflected Broadcom’s supportive culture as I successfully navigated to complete the mission. Throughout this process, I made an effort to connect with many team members, both internally and outside my core team, documenting their suggestions from each interaction.</p><p>The opportunity to work in the niche mainframe space has been uniquely fulfilling. It offered fascinating insights into distinct research considerations and challenges compared to distributed environments, such as participant recruitment. I am grateful for this experience and will undoubtedly take forward the lessons learned, skills acquired, and connections made. Thank you, Broadcom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CKkijsmiYR3DGHFf.jpeg" /><figcaption><em>New Hire Roundtable: In Lisle</em></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a314b8ab16bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/from-3270-to-intuitive-gui-my-summer-as-a-next-gen-mainframer-a314b8ab16bb">From 3270 to Intuitive GUI: My Summer as a Next-Gen Mainframer</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mainframe DevOps: My Summer in Broadcom’s Gen Team]]></title>
            <link>https://medium.com/mainframe-careers/mainframe-devops-my-summer-in-broadcoms-gen-team-dd96d46cf9bd?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd96d46cf9bd</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[broadcom]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Saishravan Muthukrishnan]]></dc:creator>
            <pubDate>Fri, 22 Aug 2025 21:44:05 GMT</pubDate>
            <atom:updated>2025-08-22T21:44:05.150Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-PpZS280ZKvUc0R-ysswUQ.jpeg" /></figure><p>This summer, I had the opportunity to join the <a href="https://www.broadcom.com/products/mainframe/application-development-testing-devops/gen">Gen Product team</a> within Broadcom’s Mainframe Software Division as a summer Next-Gen Mainframer. Gen is a tool that provides a unified environment for developing and maintaining large-scale applications across multiple platforms.</p><p>During my time here, I worked on modernizing Gen’s application deployment process by building a command-line utility called <em>gendeploycli</em>. This tool automates the deployment of Gen applications in containerized environments — equipping Gen to make another step forward in the modern DevOps adoption journey. Through this project, I gained experience with the Go programming language, collaborated with seasoned engineers, and developed a deeper understanding of how automation can improve business processes.</p><h3>What is Gen?</h3><p>Gen is a powerful, model-driven development tool used to build enterprise applications. Developers create applications using abstract models, which are then used to generate code that can run across multiple platforms, from mainframes to Windows and Linux servers.</p><p>Applications built with Gen are modular — broken into smaller “load modules,” each representing a piece of functionality. This modular design makes Gen flexible and adaptable to different technical requirements and platforms.</p><p>Gen has long been a cornerstone in mission-critical infrastructure. But as the tech landscape evolves, so must Gen.</p><p>That’s where my summer project comes in.</p><h3>The Project: Building gendeploycli</h3><p>The goal of my project was to streamline the development, deployment, and testing of Gen applications using containers. Traditionally, configuring and deploying Gen applications is a manual and often time-consuming process — especially for complex, multi-component systems.</p><p><em>gendeploycli </em>simplifies this by offering an automated command-line interface for managing deployments quickly and consistently.</p><h3>A Quick Primer on Containers</h3><p>Containers are lightweight, portable environments that bundle an application with everything it needs to run — code, runtime, libraries, and configuration. This ensures that the app behaves the same whether it’s running on a developer’s laptop, a staging server, or in production.</p><p>Think of containers as portable boxes that hold your entire app environment.</p><h3>Key benefits of containers include:</h3><ul><li><strong>Portability</strong>: Run anywhere — on local machines, servers, or in the cloud</li><li><strong>Isolation</strong>: Each container runs independently, reducing conflicts</li><li><strong>Speed</strong>: Containers are lightweight and fast, perfect for CI/CD workflows</li></ul><h3>Popular container tools used in modern DevOps:</h3><ul><li><strong>Docker</strong>: The most widely used container engine</li><li><strong>Podman</strong>: A daemonless alternative to Docker (used in my project)</li><li><strong>Kubernetes</strong>: A platform for orchestrating and scaling containers across clusters</li></ul><h3>What Does gendeploycli Do?</h3><p>At its core, gendeploycli automates the creation and configuration of database and application containers for Gen applications.</p><p>Example Command:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sV1GYp6seMtFSrYT-Jk0oA.png" /></figure><p>To give monitoring capabilities within the Gen application containers, I integrated <a href="https://github.com/google/cadvisor">cAvisor </a>directly into gendeploycli as a platform option. cAdvisor (Container Advisor) is an open-source monitoring tool developed by Google that provides real-time metrics and resource usage statistics for containerized applications. It collects detailed information on CPU, memory, disk, and network usage per container, and presents this data through an accessible web interface or APIs</p><h3>Here’s a sample usage:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*o-t07jX32_PWXMwfd6ObZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/0*mQ9aM858We9gIZ7s" /></figure><h3>Benefits of cAdvisor Integration:</h3><ul><li><strong>Real-Time Resource Tracking</strong>: Monitor how each container utilizes system resources</li><li><strong>Performance Tuning</strong>: Identify and fix inefficient modules or misconfigured containers</li><li><strong>Faster Troubleshooting</strong>: Quickly locate performance bottlenecks or system resource issues</li><li>Adding cAdvisor support allows teams to detect issues early and optimize applications before deployment.</li></ul><h3>What I Learned</h3><p>This summer has been one of the most valuable learning experiences of my academic and professional journey. It was my first time working with the Go language and containerization tools. Learning both simultaneously — while applying them to a legacy system like Gen — was challenging but incredibly rewarding.</p><p>I learned the ins and outs of Gen: how to build applications, configure load modules, and bridge legacy components with new technologies like containers. Navigating between old and new technologies forced me to think critically and problem-solve creatively.</p><p>Perhaps most impactful was working closely with the Gen team. I had real conversations with developers, listened to their challenges, and built tooling to solve actual problems. It showed me that great software starts with listening, asking the right questions, and understanding the user.</p><p>The team at Broadcom was incredibly supportive. Whether I was debugging a container issue or exploring Gen internals, there was always someone willing to help. I learned from engineers who modeled patience, precision, and professionalism.</p><p>I’m deeply grateful for my time at Broadcom. The experience allowed me to apply what I’ve learned, explore new technologies, and contribute meaningfully to a product used in real-world enterprise environments.</p><p>I walk away more confident, skilled, and inspired — not just because of the code I wrote, but because of the people I worked with and the lessons I learned along the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd96d46cf9bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/mainframe-devops-my-summer-in-broadcoms-gen-team-dd96d46cf9bd">Mainframe DevOps: My Summer in Broadcom’s Gen Team</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2024 MOE Summer Mentorship: I am part of a community!]]></title>
            <link>https://medium.com/mainframe-careers/2024-moe-summer-mentorship-i-am-part-of-a-community-aa1efd9e6f6f?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/aa1efd9e6f6f</guid>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[lfx-mentorship]]></category>
            <dc:creator><![CDATA[Maryblessing O.]]></dc:creator>
            <pubDate>Thu, 29 Aug 2024 22:23:51 GMT</pubDate>
            <atom:updated>2024-08-29T22:23:51.441Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I talk about:</p><ul><li>What I learned during my mentorship program</li><li>What I did as a mentee</li><li>My next move</li></ul><p>I think am naturally not a technical person, because, if I was, why did I fail twice at mobile development? 😆 But that’s a story for another day!</p><p>Anyway, today I’m excited to share my experience as a summer mentee on the Mainframe Open Education (MOE) Project. When I first heard about it, I was intrigued by the team’s goals. I applied for the mentorship program to learn more about mainframes, which was <em>alien</em> to me until one of my many searches led me to realize that <a href="https://open-mainframe-project.gitbook.io/mainframe-open-education-project/chapter-1-what-is-a-mainframe-today">mainframes have been a part of my daily life</a> without knowing it 🤯</p><p>Like anyone else, I joined the team with a lot to learn. My mentors were patient and understanding, giving me time to adjust before jumping on tasks. I took that opportunity to feed my curiosity about mainframes.</p><p>I gradually started completing tasks, one at a time. One of the most challenging assignments was when I was asked to speak at the student user group. I thought it was nice but what could I possibly say…? However, the questions I received during the session helped me reflect on my motivations for joining the project. You can watch the recap <a href="https://youtu.be/MlWGQrmwfJ0?si=HaorHSp9BlvRnORb">here on YouTube</a>.</p><p>I’ve previously written about my journey into the LFX Mentorship Program, including an overview of MOE and its parent project <a href="https://medium.com/@UkDev/mid-internship-progress-report-mainframe-open-education-project-58cd933b8568">here</a>. You should catch up with it before we continue!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*6h4AMrYcvnExRHLHFg9bxA.png" /><figcaption>mainframe-open-education-logo</figcaption></figure><h4>My mentorship goal</h4><blockquote>Increasing awareness of the Mainframe Open Education program within the mainframe community and outside, reviewing content, and providing feedback and new ideas on what else our project can do to attract those who consume and contribute.</blockquote><p>As someone with a background in community management, I believe that strong communities are essential for the success of tech-driven solutions. That’s why I like the MOE project’s focus, which is on open-sourcing mainframe learning roadmaps and fostering community knowledge transfer.</p><p>Each task I’ve worked on has been an opportunity to go deeper into the world of mainframes. To complete these tasks effectively, I had to explore different aspects of mainframe technology and its community, which was incredibly fun.</p><h4><strong>What I learned?</strong></h4><p>Contributing to the MOE project is like stepping on my feet in a deep ocean. I initially had limited knowledge of mainframes, but I quickly realized their significance in my everyday life. This discovery made my involvement in the project even more exciting as I deepened my understanding of mainframes through my research. There was always something new and fascinating to learn.</p><p>While I’m not always a disciplined writer, the opportunity to educate others about mainframes and the MOE project rekindled my passion for writing. I went through several drafts before finalizing the article. <em>lol, jokes.</em></p><p>Patience isn’t my strongest virtue, so reviewing our GitBook and webpage was a challenge. However, I understood the importance of gathering feedback for our community resources and approached the task with focus. The review process was actually quite enjoyable as I learned a lot along the way. <em>cool for real!</em></p><h4><strong>What I did?</strong></h4><p>I wrote about what I achieved in the first half of my mentorship and you can read all about it <a href="https://medium.com/@UkDev/mid-internship-progress-report-mainframe-open-education-project-58cd933b8568">here</a>.</p><p>I want to highlight one particular achievement: organizing a meetup at a university in Nigeria.</p><p>When I first thought of it, I didn’t think it was possible. I’ve never really organised something for myself (except that one time I organised a home party with close friends at mine and events I organised for organisations). Also, the school year was over, so I anticipated low attendance. Despite these challenges, I decided to proceed with the event. I booked a venue, contacted a vendor for snacks, and created a registration form. I have the cool folks at the Open Source Community Africa OAU (OSCA OAU) and <a href="https://www.linkedin.com/company/sca-oau/">She Code Africa OAU</a> (SCA OAU) to thank.</p><p>The meetup was a success, with 10 out of 15 people in attendance. It was a great outcome, considering my initial concerns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8esAwUGzEBOhMlMeCOyd-Q.png" /><figcaption>MOE Campus Meetup Highlight</figcaption></figure><p>During the meetup, we discussed mainframes, open source, and how students can contribute to the MOE Project. We reviewed Chapter 1 of our GitBook, and three students sent a more comprehensive review after the meetup. It was so lovely to witness their initial curiosity about mainframes turn into excitement and a desire to join our Slack community.</p><p>I got this message from an attendee and I was impressed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ft-BLURkRSMr7R1SGPslaA.png" /><figcaption>Message from an attendee at the meetup</figcaption></figure><p><strong>What’s next for me?</strong></p><p>I have a saying: Everything ends, no matter how good our intentions are. My time as an LFX Mentee has concluded, but my journey with the MOE Project core team is just beginning. I’m committed to carrying forward the project’s vision and continuing to contribute to this incredible community and <em>movement</em>.</p><p>The MOE Project is more than just a project; it’s a movement to open-source mainframe resources. It’s such incredible and important work we’re doing and the future is so bright!</p><p>I look forward to us (as a community) adding more content to the GitBook, organizing additional meetups to raise awareness and forge partnerships with other mainframe-focused communities.</p><p><strong><em>In conclusion…</em></strong></p><p>A big shoutout to everyone contributing to our vision, one piece of content at a time. Thanks to the MOE core team members for their hard work behind the scenes.</p><p>I’d also like to express my sincere gratitude to my mentors, <a href="https://www.linkedin.com/in/johnlovett/">J.J.</a> and <a href="https://www.linkedin.com/in/lauren-valenti-a1a577/">Lauren</a>, for their exceptional support and guidance. I’ll miss our weekly mentor-mentee calls, which were always a chilled and productive time.</p><p>If you’ve made it this far, thank you! Please consider contributing to our <a href="https://open-mainframe-project.gitbook.io/mainframe-open-education-project/">Gitbook</a>. You can find information on how to get started in <a href="https://open-mainframe-project.gitbook.io/mainframe-open-education-project/welcome-learn-and-contribute-to-moe/contributor-log-in">this section</a>.</p><p>sayonara 👋🏾</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa1efd9e6f6f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/2024-moe-summer-mentorship-i-am-part-of-a-community-aa1efd9e6f6f">2024 MOE Summer Mentorship: I am part of a community!</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2024 Summer of Learning- Mainframe Observability]]></title>
            <link>https://medium.com/mainframe-careers/2024-summer-of-learning-mainframe-observability-72826cf99d8c?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/72826cf99d8c</guid>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Vikram Iyengar]]></dc:creator>
            <pubDate>Fri, 16 Aug 2024 14:02:45 GMT</pubDate>
            <atom:updated>2024-08-16T14:08:32.750Z</atom:updated>
            <content:encoded><![CDATA[<p>Throughout this summer, I began my journey as a Next Generation Mainframer at Broadcom. In late May, I walked into the office and was introduced to the team and the environment at their Durham facility, before diving into the main project I would be working on. Over the course of 12 weeks, I have gained a wealth of new technical and personal skills. I want to take this chance to explain what I have been able to work on this summer, and also share the experiences that have made my time here so memorable and valuable.</p><h3>The Task and Solution</h3><p>I worked with my fellow Next-Gen Mainframer, Win Geigerman, on a project that involved improving a component on Broadcom’s Watchtower platform. Watchtower is an observability platform for mainframe users, giving them a more user-friendly interface to address different mainframe features. Our task was to implement smart features within a component in Watchtower to further enhance the user experience when executing specific mainframe commands.</p><p>We made use of a variety of tools and applications in order to implement our developments. Initially, we had to create the foundation for our project, which meant getting familiar with SpringBoot to setup and create the Java backend and our RESTful API. The biggest portion I worked on involved the UI, allowing me to make use of Broadcom’s Precision UI library. Through a combination of React, Typescript, SCSS and Precision components, I was able to implement and polish a lot of new visual features on our application.</p><p>We also made use of JSoup and ANTLR as well. In order to accurately provide specific commands to the users, we scraped z/OS documentation and ran it through a grammar we created, tokenizing our inputs. These tokens were parsed and finally stored in a database using PostgreSQL, where information about the commands would be retrieved with our API to display relevant information to the user. Our entire application was built, tested, and deployed through a DevOps pipeline using Jenkins.</p><p>Ultimately we were able to develop a lot of new features that enhanced the overall experience on this component in WatchTower, achieving our goal of improving user accessibility for less experienced mainframe users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zoxr4ATKO4CcItIfRgJDYQ.jpeg" /><figcaption>WatchTower Platform for Mainframe AIOPs</figcaption></figure><h3>A Lasting Experience</h3><p>This project taught me a lot of new technical skills, and gave me better insights on the mainframe itself. One particular moment came from a meeting I had with a highly experienced Product Owner who offered me a new perspective on the mainframe. He told me just how integral the mainframe is in everyday transactions, with it being the technological hub behind different banks, airlines, and other large scale operations. What really stuck with me was when he said that if the mainframe goes down, the world goes down. A lot of everyday digitally based activities that we all do would be rendered unavailable if it went down. Hearing this really opened my eyes to the enormous value the mainframe provides to not just large-scale businesses, but to individuals like you and myself. Being able to work on an application that directly interfaces with something of this caliber has been both a humbling and amazing experience.</p><p>Beyond the technical knowledge I have gained, there were a lot of moments at Broadcom which have contributed to my overall growth as a person. One thing that really stands out for me, was realizing the importance of not only communicating my accomplishments, but my struggles as well.</p><p>As I began working on this project, I quickly encountered an obstacle which hindered my progress, making it very challenging to determine the next steps. My frustration with not being able to resolve this issue initially caused me to avoid addressing it. However, through meetings with my team and with other mentors in the office, I further realized just how vital communication about everything is — whether it be about something good or bad — when it comes to a team project.</p><p>Openly sharing the issue that I was struggling with proved to be the best course of action. We discussed the problem in my approach and quickly came up with a new way to address it. I realized that when you are working in a team environment, effective communication is one of the most critical paths to success, and I have found that my communication skills have grown every single day here.</p><p>I was so fortunate to be part of this program and to have such a great team around me. The environment here at Broadcom felt welcoming from day one. It always felt like I could talk to anyone in the office, whether it be a question regarding a story I am working on, or just in regards to life and career advice. Everyone wanted to help and make sure that I felt comfortable during my time here. I am very privileged to have spent my summer here, and I look forward to seeing what’s in store for the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72826cf99d8c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/2024-summer-of-learning-mainframe-observability-72826cf99d8c">2024 Summer of Learning- Mainframe Observability</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2024 Summer of Learning — Developing Zowe Python SDK for The Open Mainframe Project]]></title>
            <link>https://medium.com/mainframe-careers/2024-summer-of-learning-developing-zowe-python-sdk-for-the-open-mainframe-project-900f087e82c5?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/900f087e82c5</guid>
            <dc:creator><![CDATA[Peizhao Mei]]></dc:creator>
            <pubDate>Sun, 11 Aug 2024 16:53:27 GMT</pubDate>
            <atom:updated>2024-08-11T16:53:27.597Z</atom:updated>
            <content:encoded><![CDATA[<h3>2024 Summer of Learning — Developing Zowe Python SDK for The Open Mainframe Project</h3><p>As an undergraduate student, I have longed to use theoretical knowledge in a practical setting, especially working for industry and making contributions to the community. This summer, I was fortunate enough to have the opportunity to be part of the Next Generation Mainframer Program, working side by side with the Zowe team at the Broadcom, Pittsburgh office. It was an exceptionally valuable and wonderful experience that I will cherish forever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iel71CpFCxPvGhUGMZJeAA.jpeg" /></figure><h3>Mainframe and Zowe</h3><p>A mainframe is a powerful, large computer system used primarily by large organizations for critical applications, bulk data processing, and large-scale transaction processing. This type of system has been introduced for a long time, and many efforts were put in order to keep the mainframe evolved and relevant.</p><figure><img alt="An example of how mainframe is visualized" src="https://cdn-images-1.medium.com/max/1024/1*w1wMv1b6u-f4lSxe2kO4EQ.png" /><figcaption>An example of how mainframe is visualized</figcaption></figure><p>With that being said, <a href="https://www.zowe.org/">Zowe</a>, a project sponsored by Broadcom (and many other companies), is an open mainframe project that aims to build an integrated and extensible open-source framework for z/OS and offer modern interfaces to interact with z/OS. To achieve its goal and provide wider support, Zowe contains a core set of applications out of the box in combination with the APIs and OS capabilities future applications will depend on.</p><p>My journey started with the Python SDK, which belongs to the Zowe project. <a href="https://github.com/zowe/zowe-client-python-sdk">The Zowe Client Python SDK</a>, is a set of Python packages designed to allow programmatic interactions with z/OS REST API interfaces with minimal effort. It allows programmers to create powerful scripts/applications that can interact with z/OS components in Python.</p><h3>My Team</h3><p>From my experience, the Zowe team is an inclusive, respectful, friendly, and inspiring team. The work environment is flexible and supportive, and the content improves my ability greatly. On my first day of arrival, I was warmly welcomed by my team. I received a full tour around our office, and that was super considerate and enlightening especially for a new guy. Activities were held from time to time to enhance our belongness. For example, there was an icebreaker for the whole office during my first week, where many new employees and Next-Gen Mainframers introduced themselves and senior employees shared their stories at Broadcom. Also impressive were the food contests. We had a donut contest between multiple local donut shops, and the whole office was invited to vote for their favorite. My team also held a cereal contest where twelve different cereals competed for the champion. I was glad that my favorite won the title.</p><h3>My work</h3><p>My responsibility during the summer was to maintain the Python SDK and implement new functionalities based on the team’s conception and feedback. Usually, I would be assigned to certain issues that the team prioritized, but I was also free to pick up issues under my considerations. My mentors would not interfere with my style of work, and they always gave me more support than I needed. I was grateful for that because it gave me more freedom to solve problems, and I was more prepared for independent work in the future. My mentors would review my code and give me valuable feedback in a decent and timely manner. I was also grateful for that, given that they had their own work at the same time. With their help, I was able to refactor the whole structure of the Python SDK, added a few enhancements including a logger class, and fixed several severe bugs. I also developed a <a href="https://github.com/zowe/zowe-client-samples">sample SDK</a> for the Python SDK. I felt that my work was truly valued and respected, and I took great pride in what I accomplished.</p><figure><img alt="Code Snippet of the Sample SDK" src="https://cdn-images-1.medium.com/max/1024/1*ahP0OXDaSJa01NxMWOFXEg.png" /><figcaption>Code Snippet of the Sample SDK</figcaption></figure><h3>Summary</h3><p>Overall, I am fortunate and grateful that my first step in the industry started with the Zowe team and Broadcom. The team showed me a great combination of professionalism and team spirit. I will cherish this summer forever, and my experience will keep me going in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=900f087e82c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/2024-summer-of-learning-developing-zowe-python-sdk-for-the-open-mainframe-project-900f087e82c5">2024 Summer of Learning — Developing Zowe Python SDK for The Open Mainframe Project</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2024 Summer of Learning — Streamlining QA Automation and Diagnostic Reporting]]></title>
            <link>https://medium.com/mainframe-careers/2024-summer-of-learning-streamlining-qa-automation-and-diagnostic-reporting-cb769ae011d5?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/cb769ae011d5</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[mainframe-modernization]]></category>
            <category><![CDATA[reporting-tool]]></category>
            <dc:creator><![CDATA[Dominick Dellecave]]></dc:creator>
            <pubDate>Fri, 09 Aug 2024 14:09:24 GMT</pubDate>
            <atom:updated>2024-08-09T14:09:24.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>2024 Summer of Learning — Streamlining QA Automation and Diagnostic Reporting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rIL7LJ1zkqVCqWctg44NcQ.png" /></figure><p>This past summer, I had the privilege of getting to learn and grow through Broadcom’s Next Generation Mainframer program. This program not only allowed for me to explore a plethora of new technical areas and the tools associated with them, but it also further advanced my larger professional skill set by allowing me to to work amongst and across large teams within the organization. With the vast amount of experience I gained this summer, there were a number of projects I got to dive headfirst into and make an instant impact on. However, perhaps none were more significant to my team than my work to comprehensively overhaul and streamline the Quality Assurance (QA) regression test suite and its corresponding reporting mechanisms.</p><h3>The Challenge</h3><p>When I initially arrived at Broadcom, I was quickly introduced to the QA team for the OPS/MVS product, which is a critical event management and automation tool for mainframe systems. I was told that the challenge of streamlining their automated test suite and improving its reporting mechanisms was something that had always been a high priority. After hearing the issue and realizing the importance of further modernizing the test suite, I got to work on breaking down the problem and fully grasping what I was up against. From my initial diagnosis, the QA team was faced with three main issues.</p><p>Firstly, their many Python test scripts were running as “freestyle” jobs within an internal deployment of Jenkins, an automation server that supports many CI/CD initiatives. Jenkins is a well-known, well-respected tool in the industry, however, by using freestyle jobs the team wasn’t able to take advantage of much of the fantastic functionality and features that the server provides to its users. Another issue with these freestyle jobs was that, while they all did identical runtime setup (environment variable initialization, package installation, etc.), each of them only ran a singular test script. This, compounded by the fact that the team had over 100 of these jobs running nightly, means there was a large, unnecessary cost of overhead taking place when considering time and processing resources.</p><p>The second issue I found was on the diagnostic side of the system. Their reporting mechanism was simple: each time a job ran, if that run failed for any reason, the logging output of the job would be emailed to the team. Although it is simple, diagnosing an issue quickly became a laborious task for the QA team, especially when some major issue cropped up, bringing down many tests at once. The team relayed that they were unhappy with this process, as it was not unusual to be flooded with emails, requiring them to sift through them and painstakingly dig into the output for each failing test to determine what the issue was, the severity of the problem, and who/what might’ve caused that issue.</p><p>Finally, the last issue I was tasked with was automating additional REXX tests that were previously driven manually. These tests relied on hardcoded values in an Excel spreadsheet, which was not tracked through a Source Code Management (SCM) tool like GitHub, making it labor intensive to run and update.</p><h3>My Solution</h3><p>The first issue I tackled was the conversion of the Jenkins freestyle jobs into Jenkins pipelines. Leveraging Infrastructure as Code (IaC) principles, I wrote the pipeline structure utilizing the programming language Groovy Script, which allowed for these pipelines to be fully-customizable, stage-based procedures that were version-controlled. By employing these IaC principles, I was also able to parameterize many common values that had previously been hard-coded into the freestyle jobs. For example, if the team wanted to update the Python version for testing, rather than changing the value in every single job as it had been before, we could now simply change one property value through the Jenkins UI, which is then dynamically distributed to the pipelines at runtime:</p><figure><img alt="The place in the Jenkins UI where you can change these dynamically distributed properties. They reside in the folder containing all the jobs you wish to have access to them." src="https://cdn-images-1.medium.com/max/1024/1*YgmJgsxdgwM-Oe-ZLdySFQ.png" /><figcaption>Using the “Folder Properties Plugin” for Jenkins, you can dynamically distribute values to your jobs at runtime.</figcaption></figure><p>These pipelines solve the issue of the costly repetitive setup that freestyle jobs suffer from, performing setup once and then using that environment for the remainder of the pipeline. In our case, I worked closely with the QA team to logically group tests into various pipelines by category of product functionality they were testing.</p><p>Jenkins is also great about providing visual pipeline representations/reporting out of the box. Simply clicking on a pipeline within the Jenkins UI pulls up this “stage view”:</p><figure><img alt="A picture containing the “stage view”, which shows each build of a pipeline segmented into its different stages. Lots of information is surfaced on this screen." src="https://cdn-images-1.medium.com/max/1024/1*B2VwT918YKcv7kGe9Peisw.png" /><figcaption>By clicking on a pipeline in the Jenkins UI, you are automatically brought to this stage view.</figcaption></figure><p>Each row is a specific run/”build” of the pipeline, while the columns are the stages present within the pipeline. Lots of valuable information is surfaced on this screen, such as whether the run passed or failed (the red box on the left means they failed), the stage names, the average runtime for each stage, the actual stage runtime for a build, and whether a stage passed (green), failed (yellow), or was skipped (gray) due to disablement. By clicking on a certain stage for a run (often one that failed), Jenkins also automatically surfaces a pop-up to the screen that holds an excerpt of the test’s output, containing whatever error was found:</p><figure><img alt="The excerpt of a stage’s console output holding the error that occurred." src="https://cdn-images-1.medium.com/max/1024/1*kYg8AcM-fvosSDJ9AM4NvQ.png" /><figcaption>This excerpt of the stage console output can show you exactly where the error occured in a process.</figcaption></figure><p>The ability to disable certain tests was something the QA team strongly pushed for, in case a certain test needed maintenance or was corrupting files that could affect other tests. Once again, I implemented this feature so that our team can simply change one value within the Jenkins UI to disable a test of our choosing. This also works for the test suite as a whole, in case all the pipelines must be disabled at once.</p><p>For even more visual reporting power than just this out-of-the-box feature, I set up a real time monitoring dashboard utilizing the Jenkins Build Monitor View plugin:</p><figure><img alt="A monitoring dashboard for Jenkins jobs that provides real-time updates and information at a glance." src="https://cdn-images-1.medium.com/max/1024/1*FxqbK1pEDR7wBqGsbcCskg.png" /><figcaption>This dashboard is a great triage tool that improves the inital diagnostic process of our team.</figcaption></figure><p>This screen is a tremendous improvement over the process of sifting through emails, and provides additional information that helps us to diagnose key aspects of an issue. Each box is clickable, bringing one directly to a pipeline’s corresponding stage view as shown above and, on top of seeing the pass/fail/disabled status of each pipeline, valuable insights are front and center, such as how many builds have failed in a row, certain identified problems which we can tell Jenkins to search for in failing builds, and, if someone made a change to the code immediately preceding the fail, the name of the committer that might be responsible:</p><figure><img alt="An excerpt from the monitoring dashboard that shows who committed changes right before the pipeline broke, and how many builds failed since that change." src="https://cdn-images-1.medium.com/max/1024/1*fNlQyWo_Zh9Y6bPL6Ff4pg.png" /><figcaption>Providing the name of the person who might be responsible for breaking the test(s) allows us to quickly know who to follow-up with on the issue.</figcaption></figure><p>While I left in the email reports from failing pipelines as a backup, these more modern, visual reporting mechanisms have already revolutionized the way the QA engineers approach diagnosing a failure in our test suite.</p><p>The last reform I made to the QA system here was to fully automate the manual portion of our test suite. To bring these tests up to speed with the rest of the suite, I wrote various Python scripts to automate the Excel-to-CSV conversion necessary for testing, as well as a larger test driver program. I also refactored the old codebase to be more robust, readable, and maintainable, by allowing engineers to pass various parameters into the program at runtime, rather than manually hardcoding values into the code itself. Lastly, I again broke down the tests logically into functional groups with my team and implemented a pipeline to automate the nightly schedule, as well as to exploit all of the features I already mentioned above. All of the files necessary to this portion of the test suite were now also stored alongside our various other tests, version-controlled in Git/GitHub. This automation took a large time burden off our QA team that the manual process required, freeing them up to work on higher priority matters.</p><p>All in all, I took 133 freestyle jobs, plus all of the manual tests, and slimmed them down into 37 logically grouped pipelines, all while improving upon the reporting mechanisms and maintenance of the test suite.</p><h3>A Look Back</h3><p>Making a positive, lasting impact in any way I can is an important driving force in my life, and my time at Broadcom this summer has allowed me to do just that. My project allowed me to make an immediate impact on the productivity of the QA team here and on the reliability of our testing as a whole. Furthermore, I accomplished all this while also making diagnostics and maintenance of the test suite easier, improving the day-to-day experience of our QA engineering team.</p><p>While this post highlights my main project from this past summer, I also had the opportunity to engage in a variety of other activities that have enriched my learning and growth. My time at Broadcom has truly provided me with a wealth of new knowledge and experiences across various tools and disciplines. I can’t express enough how grateful I am to my team, others in my office, and to the company as a whole for this opportunity, knowing that I have been primed for my future career.</p><p>This summer may have passed in the blink of an eye, but its impact will surely be lasting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb769ae011d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/2024-summer-of-learning-streamlining-qa-automation-and-diagnostic-reporting-cb769ae011d5">2024 Summer of Learning — Streamlining QA Automation and Diagnostic Reporting</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2024 Summer of Learning -Integrating AI with User Experience Research]]></title>
            <link>https://medium.com/mainframe-careers/2024-summer-of-learning-integrating-ai-with-user-experience-research-348a89b85627?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/348a89b85627</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <dc:creator><![CDATA[Saskia]]></dc:creator>
            <pubDate>Fri, 09 Aug 2024 14:05:50 GMT</pubDate>
            <atom:updated>2024-08-09T14:05:49.929Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This summer, I worked as a User Experience (UX) Research intern with the Mainframe Software Division of Broadcom. As the first-ever Research intern on the Mainframe UX team, it was an exciting opportunity to learn from and contribute to the talented UX team behind the software for some of the most impactful systems in the world.</em></p><p><em>During my internship, I focused on a project titled “Smartly Integrate AI with UX Research,” which aimed to explore how artificial intelligence can enhance the UX process within Broadcom. Additionally, I worked closely with a Principal UX researcher on the Precision Design System, conducting a large-scale UX research project on the documentation site of the design system that is used across almost all Mainframe products. In this article, I will share my journey and findings from my 12-week internship experience with Broadcom.</em></p><h3>Transitioning from Consumer to Enterprise UX Research</h3><p>From a UX internship at a mobile app startup to a product internship at a B2B professional development services company, my previous work experiences focused on researching and designing products for individual consumers. As I transitioned from consumer-facing products to enterprise software, I found that the UX process required a deeper understanding of complex workflows, stakeholder needs, and organizational goals.</p><p>Enterprise software products on Mainframe computers are designed for the internal operations of companies, governments, universities, hospitals, industrial plants, transit terminals, etc. They are built to ensure smooth organizational operations by providing vital information, critical communications, and essential processes that help workers perform their jobs. The specific functions that need to be done using the Mainframe can be very specialized, presenting challenges for the UX team tasked with modernizing complex systems.</p><p>The stakes in Mainframe software UX design are high — decisions can impact millions or billions of dollars in potential waste or savings. Additionally, the scale of data that needs to be processed or monitored is unprecedented, with thousands or even hundreds of thousands of objects requiring numerous actions by users across multiple geographies.</p><h3>Experiencing the Power of Team Collaboration in UX</h3><p>At Broadcom, I also learned the power of collaboration among designers and researchers, rather than working as a solo contributor.</p><p>In many previous projects, I had to wear multiple hats — UX researcher, UX designer, project manager, and UI developer. While this approach works for small, independent projects, it often shortchanges the UX process and doesn’t leverage the unique strengths of a dedicated UX team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DhPa0l5VH_v-DMMyzVzWiA.jpeg" /><figcaption>The large UX team at Broadcom encouraged feedback and collaboration.</figcaption></figure><p>During my internship, I observed researchers and designers from different value streams and products come together to solve problems collaboratively. Participating in large design critiques and reviews, where the entire team evaluates design solutions, was fascinating. I observed how researchers and designers from various products cycled through designs and gradually refined solutions to problems, and it motivated me to reach out to coworkers for feedback.</p><h3>Investigating AI’s Role in UX Research</h3><p>On the first day of my internship, I was assigned to a project called “Smartly Integrate AI with UX Research.” Although the current landscape is characterized by significant push towards artificial intelligence, I recognized that it would be premature to assume that AI was the most suitable solution. Instead, I chose to prioritize an in-depth analysis of the underlying problems and challenges, rather than rushing to apply AI as a potential fix.</p><p>I spent the first two weeks conducting informal stakeholder interviews with over a dozen people from the UX team to investigate the pain points in the UX process. Speaking with designers, researchers, and managers about their workflows not only provided insights into the UX process at Broadcom, but it also offered a valuable perspective on the career paths and approaches of others in the field.</p><p>Identified challenges included difficulties in finding participants and understanding user contexts, as well as communication gaps in the UX research process that were significantly hindering the workflow. It was this last point in particular, where I saw an opportunity for improvement using AI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iU4xqmQlYAq6ZcMf" /><figcaption>As-is diagram showing the pain points in the UX research process.</figcaption></figure><p>Researchers and designers often work on complex systems and analyze vast amounts of unstructured data, but managers and stakeholders can sometimes struggle to keep track of ongoing activities. Much meeting time is spent explaining context and updating others on the work being done, rather than optimizing time for feedback or exchanging new ideas.</p><p>I saw this as an opportunity to experiment with AI tools for summarization and rapid analysis to streamline the research process and enhance collaboration within the UX team.</p><h3>Shifting UX Research from Reactive to Proactive with AI</h3><p>Before discussing my implementation of AI as a summarization tool in the UX research process, it is important to understand why “AI in UX Research” matters. AI in UX research isn’t just about adopting the newest tools; it represents a shift from a reactive to a proactive design philosophy.</p><p>Traditionally, UX has focused on designing products that react to user cues. UX research investigates what users will do when they commit certain tasks, but with AI the goal is to design products that understand and execute the desired outcome. This paradigm shift of AI — from reactive to proactive software products — is pushing the field of UX design as well as UX research. While Mainframe software itself operates within a reactive paradigm based in methodical progression of tasks, its internal tools can benefit from this new proactive approach.</p><p>Research summaries should be generated before leadership requests them, creating seamless lines of communication. Analysis and code tagging should be dynamic, creating a foundation of insights for UX researchers to build off of. AI tooling should help UX researchers see one step ahead–that is the future of AI in UX.</p><h3>Practical Applications and Challenges of AI in UX Research</h3><p>When considering use cases for AI in UX research, AI’s strengths lie in coding, tagging to categorize similar findings, sorting through patterns, and leveraging extensive data sets. For my project, I focused on using these capabilities to create executive summaries from unstructured data gathered during user sessions.</p><p>Using LM Studio, a framework designed to deploy large language models on local machines, I experimented with various open-source models from Hugging Face by configuring prompts, temperatures, configuration files, and GPU settings. I tested the accuracy of the AI configurations by using raw, unstructured qualitative data from previous usability studies as inputs and comparing the summary output with what was produced by the researcher at the time.</p><p>In this iterative process of testing different models and configurations against a number of datasets, I created an “AI UX research assistant” that was able to produce executive summaries that had a high accuracy against executive summaries produced by researchers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9gFHftuEbMLiTCxD" /><figcaption>Executive summary produced from unstructured notes on a past UX study from 2023.</figcaption></figure><h3>Case Study: Testing AI on Design System Documentation Research Study</h3><p>To evaluate whether the AI improved the UX research process, I applied my findings from the experiments to a research project I conducted in collaboration with a Principal UX researcher at Broadcom.</p><p>The project focused on the documentation website for the Precision Design system, used by almost all Mainframe Software products. This involved creating a research plan and session guide, working with a designer on alternative designs, conducting interviews and usability testing, analyzing notes, and summarizing findings into an executive summary.</p><p>During this process, an obstacle was keeping the Principal UX researcher updated about each of the usability interviews she was unable to attend. With over ten user sessions and many tasks, it was challenging to balance my own note-taking with producing executive summaries for each session.</p><p>By feeding my notes and transcripts into LM Studio, I produced accurate and concise summaries in seconds — transforming communication between me and the stakeholders on this project.</p><h3>Challenges and Future Directions</h3><p>While I succeeded in generating AI summaries from my notes, I still encountered challenges. I found that while my notes were easily understood by the AI and produced reliable summaries and findings, summarizing from raw transcripts faced token limitations and often lacked the context needed to produce useful summaries.</p><p>Additionally, while the model handled notes in various document types and writing styles from different researchers, the phrase “garbage in, garbage out” proved true for working with AI. Notes that use a lot of shorthand or lack detail are not always “readable”, sometimes resulting in summaries that do not accurately reflect what happened during the session. AI cannot compensate for incomplete note-taking, which remains a human problem that technology cannot solve.</p><p>Ultimately, further research needs to be conducted to evaluate how AI tooling fits into the workflow of a larger team. Specifically, it is crucial that there are established channels of communication for this technology to be effective in improving workflows.</p><p>While challenges and limitations exist, I firmly believe that incorporating AI has the potential to greatly enhance UX research, particularly with respect to proactively generating summaries and readouts for leadership. In the future, I would be really interested to see how the same technology can be used for other areas of UX research, such as coding and thematic analysis.</p><p>Thank you to Broadcom for an incredible learning experience and for the opportunity to push the limits of UX research.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=348a89b85627" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/2024-summer-of-learning-integrating-ai-with-user-experience-research-348a89b85627">2024 Summer of Learning -Integrating AI with User Experience Research</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[1 Weekly Hour That Transformed My Career to Success]]></title>
            <link>https://medium.com/mainframe-careers/1-weekly-hour-that-transformed-my-career-to-success-7ea51ad87d50?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/7ea51ad87d50</guid>
            <category><![CDATA[success]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Shiva Saberi]]></dc:creator>
            <pubDate>Tue, 12 Mar 2024 17:47:09 GMT</pubDate>
            <atom:updated>2024-03-12T17:47:09.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-I2-t9opu_ZmpocQcNIbA.jpeg" /><figcaption><a href="https://www.linkedin.com/posts/malakeh-saberi-shiva_community-activity-7074489431902015489-OsLD?utm_source=share&amp;utm_medium=member_desktop">Me &amp; The Broadcom Mainframe Software Division’s SVP, MTE Conference-Opening Keynote, Plano, TX</a></figcaption></figure><p>I was in the plane flying from Montreal, QC to Plano, TX. I was sitting by the window, watching the clouds, and imagining my trip; not only to Texas but my rewarding career journey to becoming a mainframer.</p><p>A hot Texas summer day; I was invited to the city of Plano where I had the honor to be one of the speakers at the Broadcom Mainframe Technical Exchange (MTE) conference. Not just any general session — the opening keynote, “Going Bigger Together!” While checking in, I was thrilled to discover a very important person. She made me feel so wanted; the energy around me was electric. With a sweet welcoming smile, she said, “Shiva! It has been a year since we first met. How wonderful to have you here.” It was her! <em>My beloved MENTOR.</em></p><p>For telling you why I was very delighted to meet her in person in Texas, I open up a story that acted <em>as a trigger for our mentor-mentee relationship</em>.</p><h3>One Year Before My Trip to MTE, Texas…</h3><p>By then, I had been working at a Canadian governmental agency as a Mainframe Software Developer &amp; IDMS Analyst for two years. My early morning work day recipe was this: Exercising for 15 minutes, enjoying a cup of English tea with some honey inside, and having a focus minute to myself before looking at my calendar to prepare for my day at work.</p><p>My job was feeding me with joy because I never finished a day without learning things about the mainframe. What pleased me the most was our productive teamwork projects. I also had a mentor whose expertise in high level technical mainframe systems transactions support was excellent. He was guiding me from A to Z; our central system “architectural analysis” to “zOS ” mainframe environment. I was loving my job and everything about it. It was great up until the last organizational update, which seemed to limit my career growth opportunities considerably. I had to plan for a job change. I knew my career goals. The reasons I had for making a change were also clear to me, but still I was uncertain about changing my job.</p><p>Switching my job could involve a variety of changes in my professional life, not limited to only changing companies. As a young professional, I successfully had passed all those interviews that ultimately led to me working for the government. It was hard to ignore that I had a highly secure position, especially post-Covid with many lay-offs going on. I couldn’t easily go work somewhere else<em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Lg_6jELT_20zNVWN.jpg" /><figcaption>Image credit: <a href="https://www.constructionexec.com/article/mentoring-can-provide-contractors-with-sustainable-benefits">Mentoring Can Provide Contractors With Sustainable Benefits</a></figcaption></figure><blockquote><em>I felt like I needed a hand to help me step up and expand my growth. Stepping beyond my comfort zone was essential for my career progression and personal development. The ideal was to talk with an expert. </em>How about my program mentor at work? <em>Not that I could not ask for his advice. I was uncomfortable having a conversation with him about “</em>the future of my job<em>”.</em></blockquote><p>What I did next was take some time off work, book a flight, and headed to the SHARE conference in Columbus, OH.</p><h4>Why Go to SHARE, Columbus, OH?</h4><p>Its name said it all! SHARE was an event with plenty of chances to meet with the mainframe community. It gave me and other mainframers access to the latest enterprise IT news and software product highlights on emerging technologies. I attended a number of technical sessions and engaged in knowledge exchange with subject matter experts. Not to forget that I had lots of fun during lunch &amp; learn gatherings!</p><p>Not only did showing up at SHARE support me in building up my skillset, but it also gave me more clarity on what my next job could look like.</p><h4>A Short Talk with Big Impact at SHARE…</h4><p>I took the chance to talk with two successful women, the Directors of Mainframe Software Programs at Broadcom. I was following their news on LinkedIn because I was fan of their path. “As I was detailing my job, I discussed my next career move and its potential for advancement. I also shared my uncertainty about finalizing my plan. They exchanged looks and then asked, ‘Do you have a mentor?’ I replied, ‘Yes, I do have a mentor in my organization who offers me great insight into mainframe technology.’ ‘Not just a technical mentor,’ they responded with a smile. ‘You also need someone who can show you the other side — a person to talk with and help mentor you from a career perspective.’”</p><p>After making sure that our contact info is up-to-date, they said that I’ll be contacted by someone who may be available for taking me as her mentee. Guess what? I already knew her from our “<em>Women in Mainframe Circle</em>” that was holding virtual meetings every last Friday of the month. Woohoo! Another advantage of being engaged in the mainframe community!</p><blockquote>“Not just a technical mentor. You also need somebody who can show you the other side — a person to talk with and help mentor you from a career perspective”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ajV8aB6O1RbTLwN9" /><figcaption><a href="https://www.linkedin.com/posts/malakeh-saberi-shiva_takingyourbusinesstomach10-topgun-vitalityprogram-activity-6967890819236175874--PuU?utm_source=share&amp;utm_medium=member_desktop">The selfie we took at SHARE, Columbus, OH.</a></figcaption></figure><p>That night in the hotel all I thought was about “<em>the other side</em>”. It had never been brought to my attention that I could have different mentors at the same time to guide my decisions and form my plans in the right direction. Indeed, to the other side.</p><h4>One Step Toward The Other Side…</h4><p>A few days after SHARE Ohio, I got an email from my new mentor. She was happy that I attended SHARE and continued her eagerness to meet with me and talk further about my career goals as well as any current challenges or opportunities. She was a Technical Customer Events Program Manager in the Broadcom Mainframe Software Division. She asked for my next month availabilities as she was currently managing a big event in Prague. “Let me know what you are hoping to achieve from these meetings and we can chat about how to best move forward,” She added. With respect for her time, I followed up promptly and thoughtfully followed her instruction. She was making herself available for me while leading a big technical event. That meant a lot to me.</p><p><strong>1 Weekly Hour That Bounced Me To The Other Side…</strong></p><p>The experience with my new mentor was an eye opener. In our calls, I was describing my achievements or any challenges I had, so she was able to visualize the state I was in and advised me on how to improve. I worked with her very efficiently. For instance, I ensured thorough preparation for our meetings by dedicating an hour each week to documenting my goals and expectations in a notebook titled ‘Shiva’s Career Perspective.’ This practice helped me prioritize objectives and set clear intentions before our discussions.</p><p>I remember once I had the word ‘Feedback’ in my notebook. It was to share with her that the top managers admired my performance for reducing the timing of our Database Management Systems Optimization project by half. She first congratulated me, then offered a helpful tip: “You could create a folder for gathering all those accomplishments or positive feedback, emails and letters from any of your coworkers. This way, you can easily access them later when updating your resume or preparing for an interview.”</p><p>Additionally, there were some general conversations we had about how I was feeling at work, which I couldn’t have with my best friend or program mentor at work. That made her mentorship more special to me. Her perspective addressed directly my needs, helping me make informed decisions and level up my personal development.</p><p>For almost a year, we were having virtual calls. Finally an opportunity came to meet her in person. Now you could guess why I was very excited when my flight landed in Texas.</p><h3>The Success Coming Out Of The MTE, Plano, TX…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*HM1K1WKKE0nhrFLv" /><figcaption><a href="https://www.linkedin.com/posts/malakeh-saberi-shiva_community-activity-7073783477476679680-Lv42?utm_source=share&amp;utm_medium=member_desktop">Broadcom welcoming me for attending MTE Texas</a></figcaption></figure><p>What I remember the most about my mentors is how these people I had in my life made me feel. It was everything, even more important than the advice and guidance they provided. I felt included, cared for and valued — that’s the things that lasts. This is what stays with me always.</p><p>As I said, my new mentor was a Technical Customer Events Program Manager in the Broadcom Software Division. She and her team were leading a great Mainframe Technical Exchange event in Plano.</p><blockquote>She came to me on the other side of the big desk. I hugged her tightly. “Are you ready for the Opening session tomorrow?” she asked. “Ready but nervous!” I answered. She said that everything’s going to be perfect just try to be yourself and engage the audience by sharing your story. I thanked her again for all her support and came back to my room to prepare for tomorrow…</blockquote><p>Thanks to her mentoring, I was better prepared for career growth opportunities at Broadcom MTE Plano compared to SHARE Columbus. I successfully expanded my network according to my planned criteria, minimized potential risks, and maintained clarity about my direction. While many more steps lay ahead on my journey to “<em>the other side”, </em>our mentor-mentee relationship helped me navigate through my career path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*lWnW9_hTHbiQfsx3" /><figcaption><a href="https://www.linkedin.com/feed/update/urn:li:activity:7074489431902015489?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7074489431902015489%2C7074887971979567104%29&amp;dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287074887971979567104%2Curn%3Ali%3Aactivity%3A7074489431902015489%29">My mentor and me in MTE, Plano, TX.</a></figcaption></figure><p>Finally, it was time to sit with the Broadcom Mainframe Software Division’s SVP. True to <em>my mentor</em>’s foresight, my energy and enthusiasm overpowered my stress, enabling me to engage the audience effectively and deliver my message with clarity. Following the Opening Keynote Session- “Mainframe Going Bigger Together”, I received a lot of positive feedback validating my thoughts and further energizing my journey towards career success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ea51ad87d50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/1-weekly-hour-that-transformed-my-career-to-success-7ea51ad87d50">1 Weekly Hour That Transformed My Career to Success</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Programming the Mainframe in 2024]]></title>
            <link>https://medium.com/mainframe-careers/programming-the-mainframe-in-2024-6746c3641b2b?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/6746c3641b2b</guid>
            <category><![CDATA[2024]]></category>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[mainframe]]></category>
            <dc:creator><![CDATA[Boris Petkov]]></dc:creator>
            <pubDate>Fri, 09 Feb 2024 20:34:20 GMT</pubDate>
            <atom:updated>2024-02-09T20:34:19.933Z</atom:updated>
            <content:encoded><![CDATA[<h4>What It Takes to Be a Mainframe Programmer in 2024</h4><h3>Introduction</h3><p>Traditionally, mainframe programming has been associated with seasoned professionals who have spent decades honing their skills. However, the demographic of mainframe programmers is undergoing a transformation. A new generation of technologists is emerging, empowered by a plethora of newly developed innovative tooling, bringing fresh perspectives, diverse skill sets and capabilities to the mainframe arena.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*OO8Mr6361DJjy99Q" /></figure><p>Mainframes, sometimes perceived as isolated and stagnant, have proven time and again their resilience by adapting to modern challenges and environments. These robust computing machines are the lifeblood of industries such as finance, healthcare, retail, and telecommunications, handling vast amounts of data with unparalleled reliability and security. Mainframes are run by programmers, and this is what it takes to be one of them in 2024.</p><h3>Mainframe Engineer</h3><p>Colloquially named just a “mainframer”, the term refers to an individual who specializes in working with mainframe computing environments. Mainframers can be programmers, system administrators or hardware installation and maintenance specialists and their expertise may range from knowing programming languages such as Assembler and COBOL to configuring and administering the operating systems and their features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gOmg1RC4Kn_AmGRu.jpg" /></figure><p>In 2024 the mainframe is part of a bigger enterprise computing infrastructure, so beside the traditional system programming and software development, a mainframe engineer can specialize in other areas such as Hybrid Cloud or DevOps engineering and architecture. Mainframe APIs enable complex business integrations, external orchestration, and reporting tools whose designs evolve into holistic solutions. Today’s mainframers are the specialists that make those integrations possible, they are the driving force that continues the evolution of the platform.</p><h3>Mainframe Programming Languages</h3><p>By far the most popular programming language for the mainframe platform is COBOL (Common Business-Oriented Language). Although being one of the oldest, it is still widely used for coding business, finance and administrative systems and applications. COBOL <a href="https://www.thestack.technology/cobol-in-daily-use/">arguably</a> holds a record amount of lines of code in production and is still growing. Its popularity may be because its syntax is so explicit and close to spoken English.</p><p>The most performance efficient way to program the mainframe is to use Assembler. This low-level programming language is specific for the architecture of the particular microprocessor and enables direct control over the hardware, high-efficiency and close integration with the machine architecture. Many programs originally written in Assembler are still maintained and developed to enable critical system and business operations.</p><p>PL/I (Programming Language One) is a versatile programming language developed for scientific, engineering and business applications. The language was created as a response to the limitations of the existing programming languages at that time. Its original intention was to make it a more general-purpose language, capable of handling multiple use cases of different nature. Regardless of being considered one of the fundamental development tools for the platform, it remained less popular and in the shadow of its big brother — COBOL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*WcxzqjC5ZX1rOBl4lyh3FA.jpeg" /></figure><p>In the present, mainframes come integrated with several compilers, interpreters and runtime environments such as C/C++, Java, Rexx, Node, Python among many others. New applications and automations are usually implemented using one of those, nevertheless, the mainframe programmer of today would still be expected to have a good grasp on the classics too.</p><h3>Mainframe Development Environment</h3><p>Traditionally, the mainframe platform offers a set of tools, and environments tailored to the unique requirements of these powerful computing systems, TSO (Time Sharing Option), SDSF (System Display and Search Facility) and ISPF (Interactive System Productivity Facility) being the most prominent ones. Those three, together with some other console user interfaces, are commonly called “the green screen” and are an essential part of the evolution and present of the platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z3ytjXEvUAArWO20.png" /></figure><p>Being character-based programs displayed on a character-oriented terminal emulators, they often intimidate new enthusiast that are eager to become proficient with the platform. Until today, a proficient mainframe system programmer must know how to interface with the platform by using TSO, SDSF or ISPF. However, for today’s mainframe software developer, this is no longer the first they need to learn and for some it may not be necessary at all. Instead, VS Code, or less commonly known as Visual Studio Code, is becoming the IDE (Integrated Development Environment) of choice for the mainframe as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*_FuojMlT7u-fJYjHG8s0Vg.png" /></figure><p>This is how VS Code’s extensions marketplace looks like if one searches for the “mainframe” keyword there. An impressive number of specialized extensions from a variety of vendors and volunteers appear, providing a remarkable variety of options for one to choose when setting up their IDE. For a developer with experience in programming for distributed platforms, this would feel very familiar and a natural first step in their journey towards the secrets of the mainframe.</p><h3>Conclusion</h3><p>The landscape of mainframe programming in 2024 reflects a dynamic shift propelled by a new generation of technologists and the relentless adaptability of mainframes systems. Traditionally associated with seasoned professionals, mainframe programming now welcomes a diverse cohort armed with innovative tools and fresh perspectives. The resilience of mainframes is evident in their sustained relevance across vital industries. While traditional languages like COBOL and Assembler remain integral, today mainframes natively support powerful programming languages such as C/C++, Java, and Python. The development environment, once dominated by character-based interfaces, has evolved with the rising prominence of VS Code, symbolizing a departure from the good old “green screen”.</p><p>In 2024, a mainframe engineer, or “mainframer”, encompasses a broader skill set, extending beyond traditional programming to include expertise in Cloud, DevOps, software engineering and architecture. The mainframe’s role in the larger enterprise computing infrastructure emphasizes the importance of these specialists in driving the ongoing evolution of this powerful computing platform. As the mainframe continues to adapt, so do the professionals who contribute to its resilience and evolution, shaping the future of mainframe programming.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6746c3641b2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/programming-the-mainframe-in-2024-6746c3641b2b">Programming the Mainframe in 2024</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Q&A — Product Owner skills]]></title>
            <link>https://medium.com/mainframe-careers/q-a-product-owner-skills-95118f351658?source=rss----d23f4ae387dc---4</link>
            <guid isPermaLink="false">https://medium.com/p/95118f351658</guid>
            <category><![CDATA[broadcom]]></category>
            <category><![CDATA[maiframe]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Kim Peelman]]></dc:creator>
            <pubDate>Fri, 08 Dec 2023 20:01:56 GMT</pubDate>
            <atom:updated>2023-12-11T21:17:14.680Z</atom:updated>
            <content:encoded><![CDATA[<h3>Q&amp;A — Product Owner skills</h3><p>One way Broadcom Software contributes to our community is by mentoring college students. This blog is the result of those conversations.</p><blockquote>Question from: <a href="https://www.linkedin.com/in/gelila-getu/">Gelila Getu</a>, student, Marist College</blockquote><p>I’m currently in my third year of college and I’m eager to enhance my skills to increase my chances of landing an internship. Which specific skills are highly valued by your company, especially in the role of Product Owner?</p><blockquote>Answered by <a href="https://www.linkedin.com/in/kimberly-peelman-17853738/">Kim Peelman</a>, Product Owner, Broadcom’s Mainframe Software Division</blockquote><h4>Communication skills are key. That comes with the ability to:</h4><ul><li>Facilitate and mediate conversations by empathizing with others and finding solutions that suit people with different needs.</li><li>Make decisions that don’t make everyone happy, and having difficult conversations to address that disappointment.</li><li>Organize your thoughts and share a simple message that is relatable to all your stakeholders.</li></ul><h4>It’s important that you have the ability to <strong>prioritize</strong>. This helps ensure your team is able to deliver rather than being distracted.</h4><ul><li>You will always have more work to do than resources to accomplish it all.</li><li>You will always have new requests coming in at any given time.</li></ul><p>With clear priorities, you can have productive conversations with stakeholders so they understand why something needs to wait or something needs to be handled immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nh1kO-7lXqLh7sTdgBUm_A.jpeg" /></figure><h4>Lastly, something that many people don’t consider is the ability to influence others without having official authority.</h4><ul><li>Product Owners manage a backlog, not people, yet the core of their responsibility is to work with people to accomplish a goal.</li><li>To influence without authority you have to build relationships and earn people’s respect so they listen to you even though you aren’t their “boss”.</li><li>Having a high emotional intelligence helps. It’s human nature to ask “what’s in it for me”. When you understand the needs of each of your stakeholders, you can help everyone work towards the same goal even if they each have different reasons or ways of getting there.</li></ul><h3>Preparing for the Interview</h3><p>When you’re interviewing, if you don’t already have some of these skills, it still looks very good if you say what skills you want to strengthen. Employers are happy to know what you’re good at, but they have even more respect when you are self-aware and eager to improve. I’ve been a Product Owner over 10 years and I’m still learning.</p><h3>Bonus Tip</h3><p>Being skilled with PowerPoint and Excel is also important. There are lots of free training resources available online, as well as some paid courses. Personally, I learn the most with practical real-world experience.</p><blockquote>Gain hands-on experience by creating projects for yourself. For example, join a fantasy hockey league, use Excel to analyze player stats, compare it to the league’s points system, and create a PowerPoint presentation to suggest a plan for the draft, season strategy, and getting to playoffs.</blockquote><p>Everyone says they know how to use Microsoft Office tools, so these won’t make you stand out at first. But these tools are assets to you, and you want to be proficient at using them. You will be better at analyzing data and communicating a plan.</p><h3>Conclusion</h3><p>By definition, a Product Owner manages a backlog, but in practice, a Product Owner connects people. To be successful, you need premium communication skills, high emotional intelligence, and the ability to prioritize in an ecosystem that is constantly changing. Find tools to help you analyze information, stay organized, and share insights. Enjoy being a life-long-learner, because the fun is in the challenge!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95118f351658" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mainframe-careers/q-a-product-owner-skills-95118f351658">Q&amp;A — Product Owner skills</a> was originally published in <a href="https://medium.com/mainframe-careers">mainframe-careers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>