<?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[Stories by Anna J McDougall on Medium]]></title>
        <description><![CDATA[Stories by Anna J McDougall on Medium]]></description>
        <link>https://medium.com/@annajmcdougall?source=rss-51f15275ef3a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ltEetjseu8P5FkStAIBdNw.png</url>
            <title>Stories by Anna J McDougall on Medium</title>
            <link>https://medium.com/@annajmcdougall?source=rss-51f15275ef3a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:21:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@annajmcdougall/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is an Engineering Audit Like?]]></title>
            <link>https://annajmcdougall.medium.com/what-is-an-engineering-audit-like-dc2e09719efd?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc2e09719efd</guid>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[audit]]></category>
            <category><![CDATA[iso-13485-standard]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 20:21:35 GMT</pubDate>
            <atom:updated>2025-08-18T20:21:35.285Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is an Engineering Audit Like? An ISO 13485 Medical Device Engineering QMS Case Study</h3><figure><img alt="A title slide with a dramatic yellow background. In the foreground, we see a cut-out photo of Anna making a quizzical face to camera, with badly superimposed clipart of a green hat and thick green glasses overlaid on her. Text reads “what is it like? ENGINEERING AUDIT” followed by a green magnifying glass. The text below reads: “An ISO 13485 Medical Device Engineering QMS Case Study”." src="https://cdn-images-1.medium.com/max/1024/1*40gM5OvXtNKMLvuYF6UcrQ.png" /><figcaption>I think I found my new look.</figcaption></figure><p>If there’s one thing that gets me fired up, it’s a good ol’-fashioned audit!</p><p>… Said nobody ever.</p><p>Sadly, audits are a part of the business world that tend not to be fun.</p><p>However, they also serve an important purpose, and are part of the transition from the “fun team lead” style of management into the “business leader” role is coming to grips with the unsexy stuff.</p><p>As part of my role at HelloBetter, I was tasked with leading engineering compliance and reporting for ISO 13485, an internationally recognised standard for Quality Management Systems (QMS) specifically for medical device manufacturers, within the broader context of the EU Medical Device Regulation (MDR).</p><p>For those who aren’t familiar with what an audit of this kind involves, the simple version is this:</p><ol><li>Certain requirements exist as part of the standard, not just about how to effectively create and maintain software, but also how to document that compliance.</li><li>This documentation is referred to as the Quality Management System (QMS), which as the name implies serves as documentation for <em>how</em> you maintain quality as per the ISO.</li><li>The ISO isn’t only about software, but software is part of “Lifecycle Management”, tracking how a medical device (in this case) goes from design and development to distribution and surveillance.</li><li>A company required to meet the ISO should therefore create <em>and follow</em> a system that ticks all the boxes for things like patient safety, risk management, and any additional regulatory hurdles.</li><li>Typically once a year, an auditor is hired to enter the company and review the documentation alongside representatives from the company who guide them through the QMS.</li><li>Additionally, individuals (like me!) are pulled from different parts of the company to talk through their processes and documentation, and to show any examples that may be relevant.</li></ol><h3>My Experience with Engineering Compliance for ISO 13485</h3><p>This was my first audit, and I took the role very seriously. Alongside our compliance officers, I was tasked with reviewing and editing several QMS documents that were either outdated or needed more detail.</p><p>In order to ensure that we were producing accurate documentation, this process lasted several months and included pulling in engineers from throughout the organisation.</p><p>Some examples of what we needed to document included:</p><ul><li>Branching conventions</li><li>Coding style guide</li><li>Evaluation of risk for libraries/packages (Software of Unknown Provenance or SOUPs)</li><li>Quality assurance and testing processes</li><li>Traceability</li></ul><p>Two of these were areas that I hadn’t explored much before, and which proved to teach me a lot about ISO 13485 and EU Medical Device Regulation generally.</p><h4>Evaluation of SOUPs</h4><p>As an engineer at previous companies, my experience with external packages and libraries I wanted to use was really rather simple. It went like this:</p><blockquote><strong>npm install</strong></blockquote><p>That was it.</p><p>However, during my time at HelloBetter I was exposed to a much more strictly regulated software landscape. Here, it wasn’t as simple as just installing and using the package you need. Instead, attention needs to be paid to where this package comes from, whether it is actively maintained, and what level of risk comes with its inclusion in your code.</p><figure><img alt="A black-and-white comic with a picture of stacking blocks piled up very high. In the centre is one big base block balancing precariously on a small thin block. The block tower as a whole is labelled “All Modern Digital Infrastructure” and the tiny block is labelled “A project some random person in Nebraska has been thanklessly maintaining since 2003”" src="https://cdn-images-1.medium.com/max/385/0*1WIBXt35CJwoTtYS.png" /><figcaption>Image courtesy of <a href="https://xkcd.com/2347/">xkcd</a>: Dependency</figcaption></figure><p>To understand this risk, engineers and/or Engineering Managers need to pay attention not just to the node warnings at runtime, but also to the ongoing balance between software <em>benefit</em> and patient <em>risk. </em>In other words, is the convenience and ease of using this package worth the potential downside (e.g. hacking attempts, data leaks, full app breakdowns)?</p><p>For the sake of the audit, companies need to be able to demonstrate:</p><ol><li>Who has the responsibility for evaluating this benefit/risk balance?</li><li>When or how often is that balance revisited/reevaluated?</li><li>What procedures are in place for any sudden vulnerabilities discovered in SOUPs?</li><li>Where are the SOUPs themselves documented?</li></ol><p>Combined, these questions must be answerable in documentation and as a realistic part of the software development process.</p><h3>Traceability</h3><p>The other main theme is traceability. Let’s go back to what I said earlier about the role of software in ISO 13485 relating to “Device Lifecycle”. If we take the goal of the audit as being an evaluation of the entire process of a device, and we acknowledge software as part of that process, then the core question becomes this:</p><p><em>How can we see the device changes occur, from conception through to execution?</em></p><p>For ISO and medical devices in Europe generally, this means tracking software features both via software (e.g. Jira or other task-tracking tooling) and also via consistent software versioning.</p><p>On this last point, you don’t need to guess at how to structure your versioning, because there are also guidelines on how to make these numbers. Specifically, the UDI (Unique Device Identifier).</p><p>Luckily for me, implementing the new UDI requirements was part of my team’s responsibilities, meaning I’m now very familiar with the requirements.</p><p>In short, you need to be able to identify:</p><ul><li>Unique Device Identifier or UDI-DI: the static number for a specific device</li><li>Product Identifier or UDI-PI: a dynamic identifier which changes with any code or course content change</li></ul><p>In the case of physical devices, you can actually see this information displayed as a barcode. For example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/0*wxOkg_RlgU3iFey6.jpg" /></figure><p>In our case, we are a software product, so our structure is a bit different.</p><p>We pulled BitBucket build versions to automatically update our UDI-PI and combined those with our UDI-DI for each course, and the mobile version numbers. Taken together with proper branching conventions and when synced with Jira, you could trace every ticket right through to the exact build both for development and user support.</p><p>Importantly for the auditors, this process allows them to trace exactly when and how any change is pushed to production, completely independently of any potential human documentation errors.</p><h3>The Audit Itself</h3><p>Naturally, I can’t go into too much detail about how the audit itself ran. I can say that it is a very thorough and slow process. Certainly there was a lot of sitting around and a lot of waiting.</p><p>When needed, we would answer questions regarding the requirements, and then show evidence that we were meeting those requirements. Whenever there were points of confusion or clarification was needed, I would answer to the best of my ability. If more detail was needed, we would call in one of our relevant engineers (e.g. for security or quality assurance) to dive deeper.</p><h4>Tips for Audit Preparation</h4><p>Some things which helped me to prepare were:</p><ol><li>A ‘Documentation Taskforce’ made up of volunteer engineers, where we went through all existing QMS and working instructions for engineering.</li><li>Preparing a spreadsheet of each ISO 13485 topic relevant to engineering, including a link to the documentation and 2–3 links to relevant, recent examples.</li><li>Ensuring that all senior/lead developers were aware of the audit and kept their calendars clear in case we needed to invite them into the meeting for clarification.</li></ol><p>More importantly than all of the above, is having an organisation-specific person or people who are highly competent and good at explaining what is needed for each of us representing our departments. In our case, this was the expert work of <a href="https://www.linkedin.com/in/dr-victor-stephani/">Dr Victor Stephani</a> and <a href="https://www.linkedin.com/in/esther-blum-33383b220/">Esther Blum</a>. Without them, I would have been in the dark about the expectations and preparation required, and I cannot thank them enough for being my guides into the weird and wonderful world of audits!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc2e09719efd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Autistic Employees Need Forethought, Not Fixing]]></title>
            <link>https://annajmcdougall.medium.com/autistic-employees-need-forethought-not-fixing-3c814e93e1db?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c814e93e1db</guid>
            <category><![CDATA[autism]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 07:06:01 GMT</pubDate>
            <atom:updated>2025-08-04T07:06:01.253Z</atom:updated>
            <content:encoded><![CDATA[<p>Rethinking communication, expectations, and team norms can create a better workplace for autistic employees… and everyone else, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91vOntZMrfhmrUdluo2d1Q.png" /></figure><p>A few days before drafting this, I read a <a href="https://www.linkedin.com/feed/update/urn:li:activity:7352961533758373888/">LinkedIn post</a> by <a href="https://www.linkedin.com/in/elliemidds/">Ellie Middleton</a> about assumptions that often get made about her as an autistic person.</p><p>They were:</p><blockquote>1. I’m being “difficult” when I want things done a certain way or need information in advance.</blockquote><blockquote>2. I’m challenging your authority when I ask “why?”</blockquote><blockquote>3. I’m rude because I communicate directly.</blockquote><blockquote>4. I’m cold or unapproachable (my face is neutral most of the time).</blockquote><blockquote>5. I need more alone time to decompress, so I don’t get lonely/need support from people around me.</blockquote><p>As a neurotypical manager (well… there’s a chance of undiagnosed ADHD in there but let’s just ignore that for now), this naturally leads me to think about my own behaviour, and how I can make the workplace a better place for my autistic employees.</p><p>To take it one step further, I like to think about ‘The Curbcut Effect’, which is the effect wherein improving accessibility tends to make things better for everyone.</p><p>It’s best illustrated by this simple graphic from <a href="https://sketchplanations.com/the-curb-cut-effect">Sketchplanations</a>:</p><figure><img alt="The curb-cut effect: A range of people of all ages next to a crossing, road, and park show how the curb cut design on the sidewalk benefits everyone; for example not just wheelchair users but also prams/pushchairs, bicycles, suitcases, walking sticks, etc. The text reads “When we design for disabilities, we make things better for everyone”." src="https://cdn-images-1.medium.com/max/1024/0*_6kg5ZtL9TliDat5" /></figure><p><strong>So let’s break it down according to each of these five assumptions, and see what we as leaders can offer.</strong></p><h4>1. Needing Information in Advance</h4><p>Include information on a meeting’s agenda in advance, along with any documentation that would be helpful. Additionally, when getting to know your employees, ask if they have specific ways they like things done. You can’t always do things exactly how everyone prefers, but at least you can be aware and do your best to adapt so that your team members can do their best work.<br>Additionally, I’ve heard of a “communication profile” being made about each employee, where they specify how they like to be addressed, how they prefer communication (e.g. email for this, Slack for that, phone call for the other thing). I haven’t personally tried this, but I do try to ask these kinds of questions in early 1-on-1s.</p><h4>2. Employees Asking ‘Why?’</h4><p>When someone asks “Why?”, view it as an opportunity to demonstrate transparency and ownership. If you’ve made a decision for a specific reason, clarify that. The employee might disagree, but short of confidentiality reasons, there’s no purpose to hiding the ‘why’ of your decisions. Take it one step further by involving the team more in decision making and by documenting your decisions, so that people can see how you derived at your decision, and the tradeoffs you know are taking place.</p><h4>3. Super Directness</h4><p>Direct communication is a gift. Sometimes it can hurt, or come off as rude, but it’s your job as a manager to know your people and their intentions. You can also say directly “Are you saying that because you disagree? Or are you saying that because you want clarification?” or something similar. Remember that you can also express your own communication desires, for example by saying “I’m happy to answer your questions, but do you mind if we do a quick debrief of the week first before we jump in?”.</p><h4>4. Neutral Facial Expressions</h4><p>Similarly to 3, try not to assume intent. If someone looks neutral or even pissed off, you can just say to them “I’m having trouble reading your expression right now. What are you thinking?” and let them tell you (or get back to you later if they need time to process).</p><h4>5. Needing Alone Time</h4><p>Leave space (both physical and time-wise) at team events, half- or full-day workshops, etc. for people to disappear, and try to avoid making comments like “Where did you go?” or “I haven’t seen you for a while”. Start with the assumption that people need alone time, and then if they want to be sociable during those breaks then that’s fine too; rather than starting from the assumption that people will be sociable.</p><p>Furthermore, as Ellie outlined in her post: don’t make assumptions about those who use this time to be alone. Many people know me as a massive extrovert, but I often spend many hours alone playing logic puzzles or writing to recharge my batteries. Similarly, autistic employees who want alone time aren’t less sociable, or less interested in friendship or support.</p><h3>Conclusion</h3><p>None of the above is revolutionary, but all of it is based around a single facet: <strong>Do not assume you know what someone is thinking, feeling, or needing</strong>.</p><p>Provide the space to be adaptable, to answer questions honestly and transparently, and to give your employees room to think and respond in their own, unique ways. If you do that, then just like the Curb Cut Effect, you will find that all of your employees benefit.</p><p>—</p><p>If you find this post useful, I’d appreciate your support by sharing it around, or by <a href="http://www.linkedin.com/in/annajmcdougall">following me on LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c814e93e1db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain Less, Align More: Explaining tech to non-technical stakeholders]]></title>
            <link>https://annajmcdougall.medium.com/explain-less-align-more-e72c6a692b23?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e72c6a692b23</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Tue, 22 Jul 2025 16:33:29 GMT</pubDate>
            <atom:updated>2025-07-23T14:03:01.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5YmqpAHwWCNc3lsNIzfJFg.png" /></figure><h3>Introduction</h3><p>A few months ago, I was invited to speak on behalf of the women’s tech organization AnitaB at a Deutsche Bank event. The topic was <em>“Communication Strategies for Overcoming Stakeholder Resistance to Digital Transformation.”</em></p><p>It might sound a bit like buzzword salad, but it’s actually a crucial skill for technologists, especially in cultures where change is often met with resistance. Anyone working in German digitalisation will recognise the familiar phrase: <em>“It’s always been done that way.”</em></p><p>Unfortunately, just before the event, I came down with Norovirus (which, by the way, I do not recommend) and had to withdraw from the talk.</p><p>While a blogpost can never replace the energy of a live presentation, I wanted to share some of the key takeaways here. You can also access the slides of the presentation I prepared <a href="https://www.linkedin.com/posts/annajmcdougall_communication-strategies-for-digital-transformation-activity-7323234786024509440-BJCS?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAAN0lzoBQ09RKxBgjiKHcLFXruqBzcgDprQ">here</a>.</p><figure><img alt="Meme image of a woman looking exasperated and rolling her eyes with the text: “The look on your customer’s face after being inundated with tech jargon and geek speak”" src="https://cdn-images-1.medium.com/max/547/0*-m9HszowTW5MHndR.jpg" /></figure><h3>Main Takeaways</h3><h4><strong>Speak their language</strong></h4><p>Are they in business, marketing, or finance? Rather than jumping into technical jargon, take time to consider which terms and concepts they’re likely familiar with. And if you’re not sure, ask.</p><p>For example: “If I say ‘microservices’, is that familiar enough for you to explain back to me, or would you rather I go over it?” or even don’t ask and default to “Unless anyone objects, I’m going to do a quick refresher on what a microservice is”.</p><p><strong>An important note here is not to ask questions where people default to a false yes.</strong></p><p>For example, you want to avoid “You get that, right?” or “That’s familiar to you already, I assume?”. Asking these questions makes it hard for any individual to lose face and voluntarily say “Actually no, I’m the person who has no clue about this”.</p><p>Establishing expectations also helps: the stakeholders might be asking more about budget or people than about the details of the technical implementation at all! Your refresher on microservices might be totally out of place is you don’t establish early that that’s what the conversation is actually about. My tip here is to start simple, and work your way to more complex information.</p><figure><img alt="A screenshot of some speech bubbles indicating a conversation between two people. Person 1: “What would we need to get this project off the ground?”; Person 2: “A message queueing backend using RabbitMQ combined with Elasticsearch and of course a gateway API should get us the basic infrastructure needed to support a responsive microfrontend”; Person 1: “So… a team?”" src="https://cdn-images-1.medium.com/max/689/1*cBYmtPguwNpZEzR1c2k8Ww.png" /></figure><h4><strong>Cater to the lowest level in the room</strong></h4><p>This approach ensures that nobody is left behind.</p><p>If your room is full of 10 senior engineers and 1 product manager with no technical background, you cater to the product manager unless they have <em>explicitly</em> told you not to. Those with more experience will benefit from a refresher and will also (hopefully) learn about non-technical communication by listening to how you explain your concepts.</p><p>You might also be surprised by how many engineers have significant gaps in their technical knowledge, be it because of the passage of time, changing technologies, or a different area of technical expertise.</p><h4><strong>Focus on collaboration and co-creation</strong></h4><p>The goal is not just to pitch a solution but to understand the pain points of their current systems and create a shared vocabulary around a solution.</p><p>It is easy to walk into these kinds of conversations with an idea (or maybe even a full proposal) of the implementation you want. Even if that’s the case, wait to first get more details about what already exists.</p><p>If everything matches your expectations or assumptions, then BOOM you have an amazing proposal/idea ready to go. If, however, you have managed to make an incorrect assumption, or you realise mid-conversation that your solution is not ideal for their needs, then you still have time to pivot.</p><p><strong>On the flip side, you may not be used to non-technical stakeholders even wanting technical details. </strong>If it so happens that they <em>do </em>want to dive deeper, take the opportunity to “teach and not preach” by bringing them on board with what you’re proposing as you would in a classroom. Let them see <em>why </em>what you’re proposing is good, rather than just having to trust you.</p><figure><img alt="Speech bubbles indicating a conversation. Person 1: “I don’t understand what an API is. Why do we need to build one?”; Person 2: “Don’t worry about it, just know that it has to happen”; Person 1 (thought bubble): “OK but I’m paying for it…”" src="https://cdn-images-1.medium.com/max/684/1*BSoAGHp20pj4FbHnjrvK6A.png" /></figure><h4><strong>Be direct about resistance</strong></h4><p>When someone resists, they’re revealing the boundaries of the negotiation or underlying business priorities.</p><p>If the concern is delivery time, suggest a smaller or more focused solution. If the concern is cost, offer a simpler alternative or extended timeline. For usability concerns, suggest extra sessions with a designer or more user testing.</p><p>The key here is to communicate options.</p><h4><strong>Practice active listening</strong></h4><p>This is <em>by far</em> the most common mistake I see technical people making when trying to communicate to non-technical people: they miss the moment when the audience tunes out.</p><p>Breaking down solutions and going over technical ooptions can spark productive conversations even with the least tech-savvy person out there, but be prepared to cut short your explanations if you notice your audience disengaging.</p><p>Here, I’ve found it helpful to be very direct about it: “I feel like I’m losing you a bit here, should I back up a bit and you can tell me where it doesn’t make sense?”.</p><p>Alternatively, try something like: “OK I can see I’m losing you, why don’t I try explaining it in just one sentence” and follow up with a simpler metaphor. Speaking of which…</p><h4><strong>Use metaphors</strong></h4><p><strong>Bridges, factories, post offices, architecture, and housing construction have all been metaphors I have used for explaining software engineering concepts to non-technical stakeholders.</strong></p><p>If you’re working with someone from a bank, try using a bank account analogy or even a physical bank analogy (e.g. messages in a queue being like cheques). If you’re working with people in automotive, then factories or even physical cars can work (e.g. frontend is the ergonomics, design and paintwork, backend is the engine)</p><h4><strong>Incorporate storytelling</strong></h4><p>Where possible, use stories to illustrate processes. This is particularly useful for explaining concepts like Git versioning or sprint planning.</p><p>For example, explaining a hypothetical scenario about a team trying to share code without version control, using a metaphor like sharing a word document over and over again via email, vs using Google docs.</p><h4><strong>Be their resource</strong></h4><p>Regardless of whether stakeholders accept your recommendations, offer to be available as a resource. Remember that this isn’t just an opportunity for <em>right now</em>, it’s also an opportunity for the future.</p><p>Even if they don’t select your solution, you can become the technologist they know they can turn to for the next project, for due diligence, or for auditing support.</p><p>By showing that you know how to communicate technical problems and solutions in a clear, understandable way, you are building trust that can come in handy later.</p><h3>Conclusion</h3><p>Many of the above strategies will help you in gaining support for your technical solutions, be it as a consultant, a senior/principal engineer, or a CTO talking to a board. I’d even go one step further and say that many of the above steps, especially in terms of speaking to the lowest level in the room and using metaphors, will also help you in conference presentations, meetups, panel discussions, and more.</p><p>I hope you find this post useful and that you will lend me your clicks to follow me on <a href="https://www.linkedin.com/in/annajmcdougall/">LinkedIn</a>. I also do public speaking and workshops, but then you have to pay me. LinkedIn is free.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e72c6a692b23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Time to Be the Bad Guy]]></title>
            <link>https://annajmcdougall.medium.com/its-time-to-be-the-bad-guy-76d14e8f64db?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/76d14e8f64db</guid>
            <category><![CDATA[leadership-team]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <category><![CDATA[management-skills]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 12:20:24 GMT</pubDate>
            <atom:updated>2025-06-25T12:20:24.151Z</atom:updated>
            <content:encoded><![CDATA[<p>An Engineering Manager’s Guide to Taking Ownership by Taking Heat</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZO-8NvX_dUzMPBgG51ARw.png" /><figcaption>Title Image: a vibrant yellow background with a picture of Anna smiling, with two red devil-horns superimposed on top. Title text reads: “It’s time to be the BAD GUY. An Engineering Manager’s Guide to Taking Ownership by Taking Heat”</figcaption></figure><h3>Introduction</h3><p>At my first project management job, I was given the nickname “Mad Dog”.<em>*</em></p><p>Any time new sales reps would join the company, the existing reps would try to scare them by telling them “Oh shit, you’re on Mad Dog’s project”.</p><p>The joke, of course, is that I’m a big ol’ ray of sunshine: After a few days of being scared to encounter Mad Dog, those reps would meet me and realise they weren’t going to have a problem with some hard-ass micromanager.</p><p>The same is still true today, but I’ve also come to realise that there are some benefits to being Mad Dog. Sometimes, the best way to help your team is to lean into being the bad guy.</p><p>In this post, I’ll cover some situations where it’s good to be bad, and why being the bad guy is a core management skill.</p><p><em>* The nickname came about due to my name’s similarity to a famous football player (</em><a href="https://en.wikipedia.org/wiki/Adam_MacDougall"><em>Adam “Mad Dog” MacDougall</em></a><em>). Say “Anna McDougall” and “Adam MacDougall” ten times and you’ll hear it.</em></p><h3>Leadership means stepping out of the team</h3><p>As you move up the engineering leadership chain, from EM to Director to VP to CTO, you become less and less a part of the development teams. This sense of social isolation often drives leaders to try their best to be buddy-buddy with developers, to attempt to completely eradicate any sense of hierarchy, and to improve psychological safety.</p><p>In general, this is a great idea.</p><p>As a leader, you <em>do </em>need people to know that you’re just human. You <em>should</em> have people trust you with their real thoughts. You <em>must</em> enable a culture where failure and feedback are freely given and learned from.</p><p>But…</p><p>You are also the one who has to take the heat from above, and sometimes you have to be the bad guy <em>to</em> the team when it comes to responsibilities and work expectations.</p><p>By moving from engineer to team lead or engineering manager, you move from taking and executing tickets to a far more world where you have to balance the needs of the engineers, stakeholders, product and the business.</p><p><strong>You have to deliver hard feedback, push the team on goals they may resist, and sometimes say no when it would be easier to say yes or be vague.</strong></p><p>By far one of the biggest struggles I’ve seen new managers deal with, is not being able to separate themselves from the team. Although you should create a level of safety and friendliness that enables free exchange of ideas, you also have a different job to execute. You are not an engineer any more, and your priorities need to shift with that changed role.</p><p>To give new managers an idea of how this looks, here are some sentences I’ve had to say in my leadership roles over the past 5 years:</p><ul><li>“I know that’s what you want, but <strong>it’s not going to happen</strong>.”</li><li>“In the end, <strong>that’s the job</strong>. I know it’s not fun, but it’s what the business needs right now.”</li><li>“<strong>Like it or not</strong>, that’s the impression you’ve given them”</li><li>“If I had a task like that to give you, I would. But<strong> it just won’t be an option</strong> for at least a few months.”</li><li>“If that’s the direction you want your career to take, <strong>it won’t happen here</strong> at this company.”</li></ul><h3>Don’t provide false hope</h3><p>All of the above example sentences are similar in that they acknowledge what the developer thinks/wants/believes, but gives them a quick and crisp answer that is clear. This directness is a blessing.</p><p><strong>Most disappointment, resentment, and frustration comes about when expectation doesn’t match reality.</strong></p><p>If you know a certain goal, opinion, or option is just not going to happen, you should never try to cushion it in terms of “maybe” or “let’s see”, because people will pin their hopes on that. Being clear that you don’t expect it, or you can’t offer it, helps people to understand where they’re at.</p><p>Similarly, if a developer is complaining about their work expectations/tasks, you can absolutely empathise, but at the end of the day: that’s their job. They can complain all they want, but at some point they need to buckle down and do it.</p><p><strong>As a very optimistic, smiley person, it has been crucial for me to learn to not always make people feel good.</strong></p><p>Sometimes, the work just sucks: be it because of some uninspiring feature, a nasty bug, a lot of testing/documentation work, or colleagues you just don’t click with. None of that changes the fact that the work needs to get done, and it’s my job to make sure it does.</p><p><strong>Empathise, but don’t make promises to change something that is a reality of the job. </strong>What you’ll often find is that, over time, by being the bad guy and being upfront about these things, <em>you are actually building trust</em>.</p><p>It feels bad in the moment, especially if you’re used to being part of the team or being eternally optimistic, but what it does is show the developers that you’re serious, direct, and will tell them the truth. You won’t just say nice things to be nice, or give them false hope when it’s not going to happen: they can take you at your word.</p><p>Then, when good stuff is on the horizon, compliments roll in, or you say something <em>is</em> possible, there will be a lot more excitement and buy-in.</p><h3>Actively taking the blame</h3><p>For those of you already feeling sad that you can’t just be part of the team and enjoy the experience, I have some good news for you… Being unafraid of the “bad guy” title can also give you options to help the engineers.</p><p>Here, it’s about being ready to take ownership of the team, their priorities, and your decisions.</p><p>Let me again provide some examples:</p><ul><li>“You shouldn’t be spending your time on that, and if Sarah has a problem with it <strong>he can come to me.</strong>”</li><li>“No no, don’t let them rope you into that. Do it the way you want to, and then <strong>just tell them it’s me being a hard-ass</strong> and making you do it.”</li><li>“Our priority right now has to be Initiative X. If anyone tries to get you to work on anything else, you tell them it’s out of your hands and <strong>just blame me</strong>.”</li></ul><p>You are the one expected to stand between the team and the pressure coming from outside. When stakeholders are upset or deadlines are tight, you are <em>and should be </em>the one taking the heat.</p><p>This process should not be accidental, but <em>purposeful</em>. You know the engineers are going to get pushback on something, so you prepare for it by giving them an out.</p><p><strong>At this point, “Just blame me” should basically be printed on my tombstone.</strong></p><p>When you say, “Tell them I am making you do it this way,” you give them cover. You protect them from cross-team or cross-company conflict and let them focus on their work. You allow them to treat you as the hard-ass so they can keep their heads down.</p><p>This is part of being a shield for the team and is a valuable part of building trust and accountability in your role. In the end, you need to own your decisions, and doing so in this very public, social way is beneficial both to your engineers (they don’t need to come up with their own justifications) and to you (you get to show that you back your own decisions).</p><h3>Why this helps the team</h3><p>Being the bad guy does not erode trust. It builds it.</p><p>The team knows you are willing to carry the weight and make hard calls. They can trust you to tell them the truth and to look out for the bigger picture so they can focus on their work.</p><p>By giving them truth directly, even when it’s hard to hear, you let them know that your positive moments aren’t false or designed to mislead or please them.</p><p>By being the shield and actively taking the heat from any pushback, you are showing the team that you are willing to defend them and to put your own reputation on the line for the decisions you make and for what the team delivers.</p><p>So, dear manager, it’s time…</p><p><strong>It’s time to be the bad guy.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76d14e8f64db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter]]></title>
            <link>https://annajmcdougall.medium.com/from-epa-2-6-to-3-0-healthcare-data-integration-for-electronic-patient-records-at-hellobetter-f60a7e63c0f5?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f60a7e63c0f5</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[germany]]></category>
            <category><![CDATA[healthtech]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[electronic-patient-record]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Tue, 20 May 2025 09:27:30 GMT</pubDate>
            <atom:updated>2025-06-06T14:31:20.183Z</atom:updated>
            <content:encoded><![CDATA[<h3>From ePA 2.6 to 3.0: A Technical Journey in Healthcare Data Integration for Electronic Patient Records</h3><h4>…so far</h4><figure><img alt="A purple background with white header text reading “ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter”. A picture of hands typing is seen next to a graphic from the blog post visualising the connection architecture. In yellow some text says “…SO FAR!”" src="https://cdn-images-1.medium.com/max/1024/1*0s7FaP_HqegOjvZ3nKOOMA.png" /></figure><p>Germany has a bad reputation for digitalisation, so the government’s push to implement an electronic patient record (“elektronische Patientenakte” or ePA) for its citizens and residents is a step in the right direction.</p><p>As an official digital health application (“digitale Gesundheitsapplikation” or “DiGA”), we are obligated to shift to the ePA 3.0 implementation. The government rollout has been plagued with technical difficulties and delays, but we’re now at a point where we have completed our implementation successfully, pending BfArm approval.</p><p>In this post, I want to cover the exact steps we and had to take to achieve this. I want to thank <strong>Senior Product Manager</strong> <strong>Tanja Lembcke</strong> and <strong>Senior Backend Engineer Chaythanya Sivakumar</strong> for their contributions to this piece.</p><h3>The Challenge: Connecting Patient Data Across Systems</h3><p>The electronic patient record (ePA) and HealthID integration project had a clear mission: we wanted to give our patients the ability to log into the HelloBetter platform using their HealthID (which they access through their insurance company) and export their HelloBetter data into their ePA.</p><p>A successful implementation would mean that both doctors and patients can electronically access therapeutic data whenever they need it. To make this happen for the patient data at HelloBetter, we partnered with two key players: RISE for ePA system access and <a href="https://azuma.health/de/">Azuma</a> for HealthID system access.</p><p>Our journey began in 2024 when our backend team laid the groundwork for ePA 2.6, setting up the pipeline and data export in our staging environment. We successfully implemented both PDF and XML document writing capabilities, along with the frontend and backend integrations for HealthID login.</p><h3>How It All Works: The Architectural Side</h3><h4>HealthID Authentication</h4><p>The first piece of the puzzle is connecting to and authorising the user’s HealthID. This part of the system has remained stable and continues to work smoothly.</p><p>When a user wants to log in, they select “Log in with HealthID” in our platform, which takes them to their health insurance app. After logging in and authorising the necessary data sharing, they bounce back to HelloBetter, and we receive their user attributes from the IDP Federation.</p><figure><img alt="A diagram showing the 4 steps for user login with HealthID: Selecting the login, authorising via their health insurer, receiving user attributes, and then returning to the DiGA for login." src="https://cdn-images-1.medium.com/max/1024/0*61b-crXgReD_e_o1" /><figcaption>A diagram of the user login flow via HealthID</figcaption></figure><h4>The ePA Connection: Then and Now</h4><p>In the ePA version 2.6 implementation, our setup required a physical card terminal located in our Berlin office that used a specialised (dummy) health insurance card to access the RISE connector. The system involved complex authentication processes and careful data formatting to ensure successful transmission. The connection flow was more direct compared to 3.0: once authenticated through the card terminal and connector (both provided by RISE), we could begin the data upload process.</p><figure><img alt="A diagram showing the ePA 2.6 connection: the user authorises the DiGA to transfer data; once data upload is triggered the backend connects to the ePA module and card terminal which updates the data set." src="https://cdn-images-1.medium.com/max/1024/0*PDUBhPLYY-bMPVDC" /><figcaption>Data flow for ePA 2.6</figcaption></figure><p>Version 3.0 introduced additional security layers through the trusted execution environment (“Vertrauenswürdige Ausführungsumgebung” or “VAU”) in connection with the identity provider (“Identitätsprovider” or “IDP”) service.</p><p>The new process follows these steps:</p><ol><li>We use the card terminal for initial VAU channel authorisation.</li><li>The VAU channel has a chat with the IDP service to authenticate itself.</li><li>The IDP service sends us a code.</li><li>We ping that code back to the VAU to confirm our authentication.</li><li>The VAU responds with another code giving us the all-clear.</li><li>Only then can we start sending data through the VAU to the ePA system.</li></ol><figure><img alt="A diagram of the steps outlined above in the article, showing the authorisation code flow between the ePA Client, VAU, and IDP Service." src="https://cdn-images-1.medium.com/max/1024/0*vy3oX9yGE92S8uob" /><figcaption>Data flow for ePA 3.0</figcaption></figure><h3>Technical Implementation Details</h3><p><em>Contributed by Chaythanya Sivakumar, Senior Backend Engineer</em></p><h4>VAU Channel Setup and Authentication</h4><p>In our application, we leverage the Gematik VAU library (GitHub — gematik/lib-vau) to implement the initial key negotiation process and obtain the VAU-CID.</p><p>The VAU authentication process involves two key steps:</p><ol><li>Initial Channel Setup: The VAU handshake process establishes the secure communication channel.</li><li>User Authentication via IDP Service: Once the channel is established, we authenticate it using the IDP service to receive a VAU-NP (VAU-Nutzerpseudonym), which is required for all subsequent communications.</li></ol><h4>Document Upload Specifications</h4><p>The system has strict requirements for document formats and verification:</p><p>Supported Document Formats:</p><ul><li>application/pdf (PDF/A only) — .pdf</li><li>text/plain — .txt</li><li>application/fhir+xml — .xml</li><li>application/json — .json</li></ul><p>PDF/A Compliance: Due to security concerns around executable code, only specific PDF/A formats are accepted:</p><ul><li>PDF/A-1a</li><li>PDF/A-1b</li><li>PDF/A-2a</li><li>PDF/A-2u</li><li>PDF/A-2b</li></ul><h4>Implementation Architecture</h4><p>Our data upload process follows these key steps:</p><ol><li>PHR Service Port Configuration</li><li>Configure CXF client with custom transport and security settings</li></ol><ul><li>Apply MTOM (Message Transmission Optimisation Mechanism) for efficient binary data transmission</li><li>Set HTTP client policies</li></ul><p>3. Header Creation: Generate headers with required clientSystemId, mandantId, and workplaceId</p><p>4. SOAP Message Handling</p><ul><li>Utilize the diga-epa-lib to create ProvideAndRegisterDocumentSetRequestType SOAP responses</li><li>Implement SOAP interceptors for outgoing message encryption</li><li>Use CxfVauReadSoapInterceptor for response decryption</li></ul><h3>Technical Evolution and Solutions</h3><p>During the transition, we encountered and resolved several technical challenges. The most significant were connecting to the VAU itself; and once that was established the difficulty became adapting to new data formatting requirements.</p><p>While version 2.6 utilised a specific library for formatting PDF and XML data, version 3.0 required us to construct SOAP requests manually according to the <a href="https://mio.kbv.de/display/DIGA1X1X0">DiGA MIO standard</a>.</p><p>Unfortunately, the DiGA MIO website is not so easy to get answers out of, and requires meticulous combing to ensure that you not only send all the required fields, but that the fields of your own data are formed to the exact namings and conventions that it stipulates.</p><p>Notably, the official site is also not available in English. Normally this would be expected of German bureaucracy, but it’s a known reality that a huge proportion of software engineers in Germany are English-speaking. This means that many teams, not just ours, will be battling the confusing documentation and the German language at the same time.</p><p>Our engineering team successfully implemented these changes, ensuring our data formatting aligned with the new specifications and field requirements despite the above challenges.</p><p>Throughout the process, we also received invaluable support from Stefan Pratsch and Jonas Brüstel at Significo, who had already completed a successful ePA 3.0 migration themselves. They shared their firsthand experience with us, providing an overview of the various steps involved in the process and introducing us to several libraries and tools that had proven useful for their own migration. Their guidance was especially helpful during a technical huddle focused on formulating the IDP payload, where they walked us through their custom solution and clarified some of the more challenging aspects of this step.</p><h3>Looking Ahead in the Regulatory Landscape</h3><p>The Federal Institute for Drugs and Medical Devices (BfArm) plays a crucial role in overseeing digital health applications in Germany. As a regulatory body, they must approve any significant changes to medical devices or digital health applications to ensure patient safety and system integrity.</p><p>This means that although we consider our implementation to be “Done” in the Jira sense, the feature itself exists behind a feature flag which is only selectively enabled in our staging environment.</p><p>Submitting to BfArm means sending an explanation of our implementation, complete with screen recordings and logs demonstrating succesful writing of data to the ePA systems. It remains to be seen whether they will approve our implementation, but we and other DiGAs remain patient to see if our interpretation of their system has been accurate.</p><h3>Banding Together as DiGA Providers</h3><p>My team and I have had to talk to several other DiGA providers to get this system working. Everywhere we go, the responses and stories are almost identical to our own.</p><ul><li>A lot of information and companies purporting to have solutions</li><li>Very few actual examples of it happening</li></ul><p>Without naming names, I’d like to thank all of the individuals and companies who have helped us to navigate this system.</p><p>I am also yet again reminded of the pure <em>skill </em>of good technical writing, and I hope only that the German government will invest in multi-language, clear API documentation in future, that prioritises clarity and simplicity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f60a7e63c0f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EM/PM Relationships Aren’t About Luck: 5 Tips for Product/Tech]]></title>
            <link>https://annajmcdougall.medium.com/em-pm-relationships-arent-about-luck-5-tips-for-product-tech-617c9a257135?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/617c9a257135</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[product-engineering]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Tue, 13 May 2025 14:53:24 GMT</pubDate>
            <atom:updated>2025-05-13T15:12:57.224Z</atom:updated>
            <content:encoded><![CDATA[<h3>EM/PM Relationships Aren’t About Luck: 5 Tips for Product/Tech Teams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FzXGG2xnrER4n7rDYOptAQ.png" /><figcaption>Header image: purple background with the text “EM/PM Relationships Aren’t About Luck. 5 Tips for Product/Tech Teams :)” and a photo of Anna and Tanja together.</figcaption></figure><h3>Introduction</h3><p>As my probation period at HelloBetter was coming to an end, my team’s Senior Product Manager <a href="https://www.linkedin.com/in/lembcketanja/">Tanja Lembcke</a> remarked, “It’s great working with an EM who cares so much about product.”</p><p>I could easily have said the same back to her, because it’s just as valuable working with a PM who cares deeply about technology, something at which she truly excels.</p><p>Together, we’ve become a strong team. Much of that relationship has developed naturally, but I’ve also noticed a few intentional practices that have helped us along the way. I want to share them here for all the product managers, engineering managers, and whoever else happens to like reading my sporadic blog posts.</p><p>In the end, Tanja and I didn’t just “luck out” working together. There are some tried-and-true strategies we <em>both </em>employ to make the most out of our work and get the results we need.</p><p><em>If you prefer LinkedIn, you can view the short-form version of this post as a summary and carousel </em><a href="https://www.linkedin.com/posts/annajmcdougall_effective-engineering-product-relationships-activity-7321255434122653696-B0Ru?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAAN0lzoBQ09RKxBgjiKHcLFXruqBzcgDprQ"><em>here</em></a><em>.</em></p><h3>Tip 1: Purposefully be the intersection of business, team, and product</h3><p>As a Team Lead or Engineering Manager, it’s important to operate at the intersection of business goals, the engineering team, and product. This means not only using the product but also critiquing it, asking thoughtful questions, and continually returning to the core “Why.”</p><p>It is all too easy to sit back and just wait for features to drop in your lap, estimate them, deliver them, and then dust off your hands with a “job well done” attitude that allows you to add a nice dot-point to your CV about value creation.</p><p>What is much harder, is to actually focus on quality: that hard-to-measure, hard-to-prove value that is constantly competing with your time.</p><p>For EMs, we tend to see the word “quality” and jump to the concept of code quality, or architectural quality, or latency, or memory management. But I want to challenge you to also think about quality in terms of this question:</p><p><strong>How much value am I, personally, delivering to our product?</strong></p><p>This means challenging assumptions that your PM makes, seeing opportunities from your team’s expertise (we are rarely using the full capabilities of our team members), but also personally taking ownership of quality improvements that sit awkwardly between tech and product.</p><p>A key example here is compliance.Most recently, I took on the initiative to deliver what’s called a “UDI-PI” version identifier for our product to improve compliance with ISO 13485. This has provided a great opportunity for me to drive our business forward meaningfully while acting as a ‘translator’ between the different parts of the business.</p><p>Compliance is often in the ‘grey zone’ between product and tech, and it has the following added benefits to your career:</p><ol><li>It is mission-critical to product success, especially if it’s part of legislation, auditing, or certification.</li><li>Nobody wants to do it.</li></ol><p>In <a href="https://www.amazon.com/You-Belong-Tech-Programming-Knowledge/dp/3982435811">my book <em>You Belong in Tech</em></a>, I make the argument that junior engineers can get ahead by specialising in the “unloved” parts of engineering (documentation and testing, specifically) to give them the upper hand in a job search or in career development.</p><p>Similarly, I would argue that compliance (including security) is the perfect intersection of product, tech, business, and the team for EMs and PMs to form a strong bond and move forward quality metrics in a way that is meaningful to their company.</p><h3>Tip 2: PMs should insist on clear explanations of value… and EMs should insist that PMs insist on it</h3><p>As a Product Owner or Product Manager, it’s crucial to require clear explanations of the value behind technical initiatives. Pushing engineers or the EM to walk through exactly what’s happening (and why) helps avoid relying on technical jargon and ensures everything is explained in understandable terms.</p><p>To hark back to my work with Tanja: part of what I enjoy is seeing her really comprehend technical explanations that the engineers give. Sometimes they explain things too vaguely, and sometimes far too specifically.</p><p><strong>The stereotype of incommunicable engineers lingers on for a reason: as with any technical or scientific profession, developers tend to underestimate the base level of knowledge that a casual, non-technical audience has.</strong></p><p>Of course, EMs can take some initiative here and also offer explanations to the PM. That’s all fine and good I guess…</p><p>BUT (you knew it was coming!) I think what is more productive is having the PM and the engineer figure it out together, and to encourage the PM to ask directly in group settings.</p><p>Not only does this help improve the PMs connection to the rest of the team, but it also means other engineers who might not have understood the explanation the first time have a chance to ‘get it’ the second time around.</p><p>Additionally, the engineer also has a chance to receive immediate feedback that their explanation was insufficient for a non-engineer, which is far more powerful than hearing it days or weeks later in a one-on-one.</p><h3>Tip 3: Build in space for technical initiatives</h3><p>No tech stack is perfect, and no codebase lasts forever. Packages evolve, browsers and devices change, user needs shift, and business priorities move.</p><p>While structured planning is essential, it’s just as important to leave significant space , at least 20 percent , for technical initiatives, even after accounting for bug fixes.</p><p>What this means in practical terms is that EMs and PMs need to be on the same page as to the importance of tech initiatives, but also in terms of sprint planning (if you’re working in sprints) or epic planning (if you’re working across quarters, for example).</p><p>My general rule of thumb is 70% product initiatives, 20% technical initiatives, and 10% bugs. How this is divided amongst the engineers, the sprints, the quarters, the year, etc. is totally up to you and your team.</p><p><strong>Do you disagree or have a different system for creating balance? I’d love to hear about it in the comments!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NLNDKCLGGe0OAXT26JWwKA.png" /><figcaption>An image of torn paper with a quote: My general rule of thumb is 70% product initiatives, 20% technical initiatives, and 10% bugs. — Anna J McDougall</figcaption></figure><h3>Tip 4: Keep timing and priorities in constant conversation</h3><p>Priorities can change rapidly, especially in industries like healthcare and digital therapeutics, where regulatory requirements or market opportunities can shift overnight. Weekly conversations to review what’s coming up, what’s planned, what’s changing, and what needs to be adjusted are vital, not just for personal goals but for aligning with the broader objectives of the company.</p><p>Tanja and I catch up every week for half an hour. In a good week with only one leading priority, these meetings can be quite short or quite casual. However, as soon as the team is more full or the initiatives start piling up, we often find we need more time or additional meetings.</p><p>This is because we are ruthless on prioritisation.</p><p>Furthermore, in standups after we run through any upcoming release topics, triage issues, etc. I will end with “Is anyone unclear on their priorities?”. My QA Engineer and my senior engineers are often working on multiple topics simultaneously, and this one question has saved us many times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G8S9s9cd9Mk1mSd-5rlGkA.png" /><figcaption>A quote box over a background of a forest. The quote reads: I will end standups with “Is anyone unclear on their priorities?”. This one question has saved us many times.</figcaption></figure><h3>Tip 5: Be upfront about what you don’t know</h3><p>If you and your EM/PM have the feeling of needing to pretend to know everything with each other, then the partnership isn’t as strong as it could be.</p><p>Being willing to reveal gaps and bridge them together leads to healthier collaboration and faster team progress.</p><p>For example, if my PM uses an acronym I don’t know, I really have three options before continuing the conversation:</p><ol><li>Google it quickly.</li><li>Ask her.</li><li>Nod and say “Mmm, yeah”.</li></ol><p>Too many people choose option 3 because they are lazy, or because their EM/PM uses <em>too many</em> terms they don’t know and they don’t want to interrupt all the time.</p><p>The next group chooses option 1 because it allows them to follow the conversation without seeming ignorant.</p><p>But I would argue that 100% of people, 100% of the time, should choose option 2: even if it is annoying; even if it is breaking the flow of conversation; and even if other meeting attendees are rolling their eyes.</p><p><strong>Why?</strong> Let me give a non-exhaustive list:</p><ol><li>You’re probably not the only one confused, so asking helps others in the room to also learn.</li><li>Your EM/PM will learn that they’re not explaining it clearly.</li><li>You don’t lose track of the conversation thread because you’re trying to multitask: the meeting stops and waits for you.</li><li>You might learn more nuance/detail about how it applies to your company/industry by opening up a conversation around it than by just looking up a definition.</li><li>You model vulnerability which will help your EM/PM to do the same in future (hence applying all of the other benefits outlined above to them and you as well): in other words, you establish psychological safety.</li></ol><h3>Closing Reflections</h3><p>As you can see, there are some common threads to how I view a productive working relationship between Engineering Managers and Product Managers.</p><p>They rotate around:</p><ol><li>Understanding what and why</li><li>Giving space for the code to breathe and grow</li><li>Pushing for clear prioritisation</li></ol><p>If you can challenge yourself to take these three things seriously, then the above 5 tips should naturally fall into place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=617c9a257135" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Can’t Outrun AI in Tech Interviews, So We Designed Around It]]></title>
            <link>https://annajmcdougall.medium.com/you-cant-outrun-ai-in-tech-interviews-so-we-designed-around-it-018ae0ac4ddd?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/018ae0ac4ddd</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[technical-interview]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 19:08:54 GMT</pubDate>
            <atom:updated>2025-04-22T10:11:25.337Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8mclzdpcwg75Vm4D_cjilA.png" /></figure><h3>Building the McDougall Method at HelloBetter: A Fairer, More Modern Approach to Technical Interviews</h3><p>As someone obsessed with tech careers, business growth, and engineering management, I am constantly coming up against the boogey-man of technical interviews.</p><p>In many ways, tech companies are stuck in the thinking of 20–30 years ago: white boards, algorithms, logic puzzles, and tasks that rotated around an in-person interview space.</p><p>We’re in a new era, where 99% of engineering interviews are done virtually and the candidate’s workspace is uncontrollable by the interviewing team.</p><p>We need to adapt to this, not by simply porting previous methods across to an online platform, but by fundamentally rethinking the skills we expect 21st century software engineers to have.</p><p>Naturally, opinions about <em>what is wrong with technical interviews</em> are prevalent both from employers and (potential) employees.</p><p>For example, <a href="https://leetcode.com/">leetcode</a>-style assessments have long been derided as being a bad test of abilities.</p><p>“Instead,” opponents argue, “you should use take-home tests or projects that the candidate can explain back to you”.</p><p>Ah, but you see, not everyone can afford to let their evenings and weekends disappear into these take-home tests or side projects.</p><p>Due to this inconveniently linear construct called “time”, more experienced engineers start having or caring for families, adopting pets, or (lord forbid) doing sports and hobbies. It’s also no big secret that the majority of housework and care duties still tend to be shouldered by women.</p><p>To put your best foot forward as a candidate, you will create the best possible solution, no matter how many hiring managers tell you to “only spend 2–3 hours on a solution”. Therefore, take-home or “own project” technical interviews tend to put older candidates and women candidates at a disadvantage.</p><p>One other problem popping up nowadays is the prevalence of AI tools for engineers to pass technical interviews, ranging from manually entering prompts into ChatGPT (now a bit old-school), all the way through to having someone else take the technical round for you and have your face artificially plastered onto theirs.</p><p>Going back to take-home tests for a moment, these are all but obsolete in the age of AI, in large part because all the solutions seem to be eerily similar to each other… 👀</p><p>So what do you do when…</p><ul><li>Leetcode tests aren’t a good indication of the work itself.</li><li>Take-homes will favour those with more free time.</li><li>Asking freestyle technical questions lends itself to cheating with AI.</li></ul><p>Here, I share our own journey at Berlin mental health DTx startup <a href="https://hellobetter.de/">HelloBetter</a> in transforming our technical interview round into a solution that not only mirrors the real work, but doesn’t require an unreasonable amount of candidate time.</p><p><strong>I don’t believe there is a perfect solution yet to the challenge of assessing technical skill in an engineering candidate, however I do think this is the best solution I know of so far in terms of balancing realistic expectations, useful insights, and equitable testing conditions.</strong></p><h3>Background</h3><p>In November 2024, we began overseeing changes to our hiring process by, firstly defining what our current issues were.</p><p>Most of these will probably seem familiar to you, O reader who has tried hiring engineers:</p><ol><li>An interview process with too many steps.</li><li>Long time-to-hire.</li><li>Not discovering crucial information about a candidate until late in the process (e.g. they want to move vertically or horizontally within a year)</li><li>Candidates using AI to cheat or misrepresent their abilities.</li><li>A technical interview round that feels more like a memory test.</li><li>Engineers’ time being taken up by interviewing candidates the hiring manager doesn’t want</li><li>Engineers who are confused when they recommend against a candidate in an interview round, but that candidate gets hired anyway, or vice versa.</li></ol><h3>Non-Technical Hiring Changes</h3><p>Firstly, let’s look at the solutions we implemented that <em>aren’t </em>related to the technical interview:</p><ul><li>Introduced a short questionnaire in the application form to screen out some common misalignments on goals, salary, etc. (Though it should be noted that all HelloBetter IC salary bands are <a href="https://handbook.hellobetter.de/compensation-benefits/salary-bands">publicly available</a>)</li><li>Moved the technical round to <em>after</em> the hiring manager round.</li><li>Combined our two final, half-hour interview rounds — the “Team Interview” and the “Founder Interview” — into one hour-long slot, to reduce delays from scheduling.</li><li>I offered more of my time and willingness, for example to interview multiple candidates per day or back-to-back.</li></ul><p>For our most recent hire, I made a point to stay in close contact with our recruiter, sharing at least 1–2 slack messages every day to stay on top of the process, candidates, and next steps. We further had a half-hour sync meeting every week.</p><p>Most of the changes above were done in a collaboration between the Engineering Managers and Recruitment. I volunteered to take on the challenge of defining changes to the technical interview, in large part because I had a clear vision of how it could be done better.</p><h3>Technical Interview Round: Workshop Phase</h3><p>I wanted to ensure this was something involving all of engineering. Since the engineers are the ones conducting the technical interview round, it made sense to have them drive the ideation and narrowing of precise structure, based around my criteria.</p><p>In Slack, I asked for volunteers to assist me, and got 6 takers. By chance, they managed to neatly divide into two engineers each for mobile, web frontend, and backend.</p><p>The engineers in question were <a href="https://www.linkedin.com/in/juliaero/">Julia Ero</a>, <a href="https://www.linkedin.com/in/mohamed-elmoazin-54b465165/">Mohamed Gaber Elmoazin</a>, <a href="https://www.linkedin.com/in/andrewlapin/">Andrei Lapin</a>, <a href="https://www.linkedin.com/in/caio-quinta-80b6a2b5/">Caio Quinta</a>, <a href="https://www.linkedin.com/in/euclides-r-s-junior/">Euclides dos Reis Silva Junior</a>, and <a href="https://www.linkedin.com/in/chaythanya-sivakumar/">Chaythanya Sivakumar</a>.</p><p>I set up a Miro board and defined the goals/guidelines for what we wanted the technical round to achieve. In two sessions of about 1hr each, I guided the engineers through questions and discussions about their own experiences both as candidates and as interviewers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*GCSBO4OJdGQ1k_m56zdOTQ.png" /><figcaption>A screenshot of part of our Miro board for the workshop</figcaption></figure><p>As you can see in the image, I provided a few guiding principles:</p><ol><li>The goal of the interview is to provide the hiring manager with an idea of the technical abilities and level of the candidate, <em>not </em>to pass or fail that candidate.</li><li>Create an interview structure that can work across disciplines (i.e. backend and frontend interviews shouldn’t be wildly different)</li><li>The candidate should feel supported and welcome.</li><li>The process should be as close as possible to the actual work they will do, rather than on purely abstract concepts.</li><li>The end result should allow us to assess the candidate’s analytical capabilities, programming ability, understanding of programming principles, and “code communication” skills.</li></ol><p>In the first session, we covered the engineers’ own experiences. The goal here was to ground their ideas in lived experience, and to ensure that their framing began from the candidates’ perspective. Each person was given their own post-it to fill out, and after each section I would summarise what points seemed to be most common or agreed-upon.</p><p>From there, we devised the basic structure with a timeline of approximately 75–90 minutes total.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*lXCUXVo7TAhzQ-wnt8rNcw.png" /><figcaption>A fair, memeable assessment of the current gap between technical interviews and the jobs for which they’re assessing.</figcaption></figure><h3>Introducing the McDougall Method</h3><p>In this 90-minute interview structure, we assess the abilities of the candidate in a real-world scenario which prioritises a fair process for the candidate with the pragmatic reality of a technical assessment.</p><p>The structure can be broken down into four phases:</p><ol><li>Introduction to the candidate and a brief overview of their technical history (10–15 minutes)</li><li>Pair programming session (30–45 minutes)</li><li>Reflection/follow-up questions (15 minutes)</li><li>Candidate questions and wrap-up (10 minutes)</li></ol><p>Separating each of these stages out, we had a combined brainstorming of what questions we could ask for each stage, and for Step 2 (Pair Programming), how we could best achieve the goals laid out above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*j-7BaDR-f3isiKud4M1B1Q.png" /><figcaption>Shared brainstorming for each phase of the interview</figcaption></figure><p>Each of these phases is important and serves a crucial purpose. Let’s look at each in turn.</p><h4><strong>A quick note on naming…</strong></h4><p>The term “McDougall Method” is my own label for the framework I led, developed and documented to address these technical interview challenges. I chose the name it’s more convenient than saying “our new technical interview method” or “HelloBetter’s updated technical interview round structure” on repeat.</p><p>However, like most things EMs take credit for, it was not actually a solo effort, and is thanks to the input of the six engineers mentioned above, as well as thanks to HelloBetter CTO Amit Gupta, and fellow EMs Leonardo Couto and Garance Vallat — who provided me with the freedom to drive this initiative.</p><h3>Phase 1: Candidate Introduction and Technical Background</h3><p>This phase is pretty common, but nevertheless it’s important to understand <em>why </em>this phase exists in most technical interviews, rather than jumping straight into a coding exercise or a quiz. This stage only includes two engineers, to avoid the candidate being overwhelmed but also to avoid any potential individual bias playing too big of a role.</p><p>In short, we want the candidates to feel as relaxed as possible. We will <em>never</em> have fully relaxed candidates in this situation, but if there’s any way for us to reduce stress, we know that will lead to better performance. The brain does not operate at its best when it’s in fight-or-flight mode.</p><p>Here, we smile, introduce ourselves, make a bit of small talk about our roles at the company and maybe even a fun fact about ourselves.</p><p>We then give the candidate an opportunity to introduce themselves with the same basic questions they face in most interview stages, which should provide some ‘easy wins’ for them:</p><ul><li>Tell us about yourself</li><li>Tell us about your recent work history</li><li>What excites you about the role?</li></ul><p>…and so on.</p><p>We explicitly don’t want this stage to go on too long, again because of stress.</p><p><strong>Every candidate enters the technical round knowing they will be assessed, so too much small talk is delaying the bit they fear the most.</strong></p><p>As such, we want <em>enough </em>introductory conversation to ‘grease the wheel’, but not so much that they start getting jittery about when the hard part will actually start. For us, we set this limit at about 10–15 minutes.</p><h4>Evaluation Criteria</h4><p>For this section, we keep things pretty light and non-critical, asking only “Could the candidate clearly express their technical background/expertise?”. This phase is mostly about psychological safety and building rapport, so comple criteria or feedback is not essential here.</p><h3><strong>Phase 2: Pair Programming</strong></h3><p>This is probably the part of the post you came here to read, so let’s dive into it.</p><p>Firstly, I earlier stipulated that the coding portion of the interview should mimic the real job as closely as possible. For that, we required three things:</p><ol><li>A codebase similar to our own: same tech stack, same naming conventions, same structure, etc.</li><li>Problems similar to ones we really fix.</li><li>A setup allowing the same flexibility and freedom of a real engineer.</li></ol><p><strong>The core of the McDougall Method is a 40-minute technical pair programming assessment providing a dummy codebase mirroring a section of your production code, complete with incomplete functions, faulty implementation, and failing tests.</strong></p><p>The candidate is sent read-only access to the repository one hour before the interview, to allow them to look over it and get a feel for the code, how it’s structured, etc. However they should not actively implement anything in that hour.</p><p>Once in the interview, the candidate pairs with <em>one </em>of the interviewing engineers, and together they work out how to solve (potentially) five problems of increasing difficulty.</p><h4>The “Problem” of AI</h4><p>“But Anna!” I hear you cry from behind your screen, “This doesn’t solve the problem of cheating with AI! They could have another screen, or another device, and be using AI to solve the problems!”</p><p>Well, we’ve managed to overcome this challenge by welcoming our new robot overlords, because<strong> the McDougall Method explicitly allows AI tools to be used</strong>.</p><p>That’s right. The candidate shares their screen, and is told (both in earlier communication and in the interview itself) that they can use Google, Stack Overflow, GPT, Copilot, Cursor, whatever they want. Most importantly, they can ask any questions they like of the interviewers, <em>and should</em>.</p><p><strong>In the age of AI, what we want to assess in technical interviews is not how many facts or algorithms an engineer can memorise, but <em>how</em> they work, and if they understand what they create in the process.</strong></p><p><strong>If we accept that we want our engineers to use AI tools for productivity increases, then we have to view AI use as a skill. If our technical interview rounds are for assessing technical skill, then AI use <em>must therefore be allowed</em>.</strong></p><h4>Dos and Don’ts for the Codebase</h4><p>In the last few days, I’ve posted about the McDougall Method across several related posts on LinkedIn, and have had some misunderstandings pop up.</p><p>As such, I want to take a small pause here to cover some Dos and Don’ts for this phase.</p><p><strong>Do:</strong></p><ul><li>Create a private repository they can clone locally and easily install and run.</li><li>Use a small section of code either taken from your production codebase or mirroring it closely.</li><li>Build in several levels of difficulty, for example in frontend you would start with a small styling change and build up to a complex, verbose function requiring full refactoring.</li></ul><p><strong>Don’t:</strong></p><ul><li>Use your actual production code.</li><li>Use candidates to complete real tickets (that is free labour and not cool).</li><li>Include any secrets or API Keys.</li><li>Forget to send the repository one hour beforehand.</li></ul><p>On this last point, <strong>GitHub does not yet offer the feature of scheduling repository access</strong>. My hope is that this post and the ensuing avalanche of teams switching to the McDougall Method might inspire them to offer it as an option. At present, the only way to do this is to schedule a reminder for yourself (or one of the interviewing engineers) one hour before the interview.</p><h4>Technical Grading of the Exercises</h4><p>I mention above that we use five different ‘levels’ of problem for each codebase, for example a styling change as Level 1 and a full functional refactor at Level 5.</p><p>These levels should roughly correspond with a technical grading for the candidate. I include here some examples based on React as a framework:</p><ul><li>Level 1: Intern or fresh junior (e.g. small styling change)</li><li>Level 2: Junior or low-level mid (e.g. onClick event not triggering the correct response)</li><li>Level 3: Mid-level ability (e.g. efficiently and accurately populating components from an API response)</li><li>Level 4: High-mid to low-senior ability (e.g. handling complex state management and/or re-rendering errors)</li><li>Level 5: Senior+ ability (e.g. full refactoring of complex verbose functions and/or inefficient component architecture)</li></ul><p>Why? Because again, our goal here is not to see who our ‘best’ candidate is, but to see if the level we’re hiring into matches the candidate. This can also potentially avoid situations where a candidate under-levels themselves (again statistically more likely to occur with women), and ensures that we accurately determine what role to hire them into, which in turn assures fair pay, and lower mid- to long-term turnover.</p><ul><li>When hiring for juniors, you would start at Level 1.</li><li>When hiring for mid-level engineers, you would start at Level 2.</li><li>When hiring for senior engineers, you would start at Level 3.</li></ul><h4>Why 40 minutes?</h4><p>Put simply, because it’s enough time.</p><p>You aren’t going to get much more insight on a candidate that you haven’t gotten in 40 minutes of pair programming with them.</p><p>In truth, our final guidelines indicate a minimum of 30 and a maximum of 45, but 40-minutes seems to be the sweet spot.</p><h4>Assessment Criteria</h4><p>I’ve already indicated that coding ability and effective information sourcing (e.g. asking the colleague questions, using Google/AI, etc.) is the main goal of this round. However, also being assessed is their ability to communicate their ideas about <em>how </em>they’re solving the problem.</p><p>Here we ask the interviewing engineers to answer four questions:</p><ul><li>How many tests did the candidate solve?</li><li>What was the average quality of the solutions they completed? (1–5 scale)</li><li>Could the candidate clearly communicate their decisions or approach?</li><li>What level would you estimate the candidate to be at?</li></ul><p>We also give a free text area where they can go into more detail, for example about the tools used, any major errors or points of confusion, etc.</p><p>As much as I enjoy the structure of the first three questions, the free text box is usually where the most valuable information pops up, for example:</p><ul><li>Candidates who spot errors in the code which were not on purpose (oops!)</li><li>Candidates who can’t explain how the results they get from AI/Google/etc work</li><li>Candidates who are unable to talk through their thought process</li></ul><p>After that, we move into the next phase which is directly related to the pair programming task.</p><h3>Phase 3: Reflection / Follow-up Questions</h3><p>Almost as important as the pair programming session itself are the questions the team asks afterwards.</p><p>In a traditional technical interview round, the coding exercise itself is supposed to reveal the technical knowledge of the candidate. In the McDougall Method, the pair programming session is more about assessing <em>how they work.</em></p><p>In Phase 3, the team has the job of asking questions allowing the candidate to display how well they <em>understand</em> what they implemented.</p><p>As you can see, this phase itself has two steps.</p><h4><strong>Reflection</strong></h4><p>Firstly, we allow the candidate to reflect on how they feel. We know nerves are on edge, tensions are high, and candidates almost never perform at their best in an interview. So, let’s give them a chance to say so.</p><p>The first question every interviewing engineer should be asking before anything else in Phase 3 is:</p><p><em>How did you feel about that exercise?</em></p><p>This is an open question which allows them to explain their emotions, worries, fears; or even what they’re proud of. From there, questions around what they would have liked to do differently, or what other tasks they would have liked to do, can arise.</p><h4><strong>Follow-On Questions</strong></h4><p>After this initial reflection, follow-on questions should be next. These revolve around <em>why</em> they chose a certain approach, what pitfalls might occur, how certain implementations would/could scale or be maintained; or perhaps questions about naming conventions, readability, or memory management.</p><p>In our latest round of interviews, it was here where good “implementers” had their knowledge gaps revealed. This is <em>not necessarily a bad thing for the candidate</em> because, as stated earlier, it is the hiring manager’s prerogative to match the candidate to the role.</p><p>For example, if you’re hiring a junior or a lower mid-level candidate, then you won’t expect many deep answers here, but knowing the limits of your hire will help with forming a development plan for their first year in the company.</p><p><strong>In short, rather than assessing the core of their knowledge during<em> </em>the coding exercise in Phase 2, we allow the candidate to focus on <em>pure implementation</em>, and then go deeper in Phase 3.</strong></p><p><strong>Note: </strong>This is the section in which the engineers require the most EM guidance in terms of accurately defining the expected level of analysis/understanding. I will be keeping an eye on this in future hiring rounds, and offer some more concrete guidance for allowing a deeper dive here in future blog posts.</p><h4>Assessment Criteria</h4><p>Due to how much this section can change, we opted to keep one question about candidate openness to feedback, but again mainly relying on a free text summary for the interviewers to describe their approach, strengths, weaknesses, etc.</p><h3>Phase 4: Candidate Questions and Wrap-Up</h3><p>I don’t have much unique insight to add here, but I would say this is a crucial step to any interview. Some guidelines I provided the engineers were:</p><ul><li>Open the floor to the candidate for questions</li><li>When you think they’re done asking questions, <em>ask one more time </em>if there’s anything else they want to know</li><li>Explain the next steps (e.g. “We’ll pass our feedback to Anna and she will be in touch within the next few days”)</li><li>End with a smile and thank the candidate for their time</li></ul><h4>Assessment Criteria</h4><p>As with Phase 1, we keep the asessment criteria for text information about what questions they asked and any final notes.</p><h3>Final Feedback</h3><p>In addition to the fields and questions outlined above, our HR software <a href="https://www.personio.com/">Personio</a> offers a “Negative”, “Neutral”, and “Positive” option for every candidate.</p><p>Our instructions for this final rating are as follows:</p><ul><li>“Positive” should reflect an overall good experience with the candidate, <em>not</em> that you think they are technically suitable.</li><li>“Neutral” should be if the candidate was polite, but that perhaps it was awkward or lacking cohesion, consistency, or decent communication ability.</li><li><strong>Only leave a “Negative” if there is a serious cultural or interpersonal clash</strong> e.g. sexism, racism, aggression, cheating, etc. Do not select ‘Negative’ if you think they’re lower level than the position advertised.</li></ul><p>In short, the final rating should act as a way to give us a ‘vibe check’. Personally, being aware of some of the issues around cultural evaluations particularly for neurodivergent candidates, I would accept any candidate with Neutral or Positive if the other criteria are met.</p><h4>Overall Evaluation Field</h4><p>The last field is an open text field where each interviewing engineer can summarise their thoughts. In both our Confluence documentation and in the training sessions I give the engineers, I emphasise the need to note both strengths and weaknesses in this field. In the case of someone who really can’t complete the exercises or is totally underqualified, I would also expect the engineers to outline that here.</p><h3>Outcomes of the McDougall Method</h3><p>Narrowing down our earlier list to the three challenges we can address with the technical round, we can see the results clearly:</p><h4>Long time-to-hire</h4><p>All of the changes taken above led to our “Days to Fill” metric being 30% of its usual in our latest hiring round. Naturally, this time equals money. This metric was influenced by the streamlined interview process, the close work with our recruiter, and the engineers being trained to submit predictable, standardised evaluations.</p><p>In addition to the hours saved by moving the interview process along quickly, we also save time and mental energy from the context-switching of having to keep candidates in an overly-long pipeline: this goes both for the hiring manager and the interviewing engineers.</p><h4><strong>Candidates using AI to cheat or misrepresent their abilities</strong></h4><p>Although this is still technically possible, the separation of the coding phase from the analytical phase makes it harder to use AI. Questions are based around feelings, hypotheticals, and preferences, many of which have no right or wrong answer.</p><p>The ability to openly use AI during the pair programming exercise removes the element of ‘shame’ from using it as a tool.</p><h4><strong>A technical interview round that feels more like a memory test</strong></h4><p>As a candidate, the McDougall Method requires zero memorisation or cramming of factoids. Instead, practical programming fundamentals become key. If you’ve worked as a mid-level candidate at a company for the last three years, you will likely be levelled as a mid-level candidate with the McDougall Method, regardless of how recently you inverted a binary tree, how many JavaScript concatenation quirks you can recite, or how many HTTP status codes you can memorise.</p><h4><strong>Engineers who are confused when they recommend against a candidate in an interview round, but that candidate gets hired anyway, or vice versa</strong></h4><p>The emphasis of this method is on levelling candidates and determining their strengths and weaknesses, NOT on giving them a pass/fail grade based on the interviewing engineers’ assumptions.</p><p>A candidate could be technically strong, but the cultural tradeoff might not be worth it when compared to a more technically-flawed candidate who is an excellent team player.</p><p>Furthermore, within the method itself there is space for a difference between those who are <em>implementers</em> and those who are <em>knowledge-havers</em>. We all have a balance of both, and the structure allows us to see who is strong where, and what areas still need to built up — crucial to building a development plan for a new-starter.</p><p><strong>In the end, it’s the hiring manager’s job to balance these considerations, and the McDougall Method gives ample opportunity for interviewing engineers to provide their feedback and build an accurate picture of a candidate’s technical abilities for that manager to weigh.</strong></p><h4>Future Action Points</h4><p>There are still some ways to improve this method:</p><ol><li>More clearly define the technical criteria for Phase 3: since this is highly dependent on the role, it is hard to devise concrete questions in a standardised format here</li><li>More precise assessment criteria for Phase 3: as per the above, I think the variability in this phase means that we need to be open to more individualised assessment criteria here.</li></ol><p>These two points lead me to believe that a new framework for the devising and assessment of this phase is required. For example, through some sort of question matrix or pre-hiring questionnaire to assess the relative importance of different technical insight areas and levels of knowledge per position.</p><h3>Documentation and Training</h3><p>After developing this method, I created detailed documentation for the engineers before also guiding a training session for those who I knew would soon be interviewing candidates.</p><ul><li>A Confluence documentation detailing the method similar to the details in this post</li><li>A position-specific doc outlining the expectations for that precise role and how it related to the process</li></ul><p>In the 90-minute training session, I not only covered all of the information you have read above, but also had each engineer practice their intros and outros for the interview, providing a few prompts and feedback on how to provide a friendly atmosphere.</p><h3>Call to Action</h3><p>Let’s keep things simple. My call to action is this…</p><p>Try it.</p><p>Take it to your EMs, or your team, and talk about it. What are the pros and cons? What might be missed?</p><p>If this resonates, share it with your team. I’m especially keen to hear what you’d differently, whether here in the comments or on <a href="http://www.linkedin.com/in/annajmcdougall">LinkedIn</a>, where I regularly post about engineering management, tech careers, and my own observations about the industry and healthtech in particular.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=018ae0ac4ddd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Support Junior Developers: Ten Crucial Tips for Seniors and Leads]]></title>
            <link>https://annajmcdougall.medium.com/how-to-support-junior-developers-ten-crucial-tips-for-seniors-and-leads-6cb7fb5925bd?source=rss-51f15275ef3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cb7fb5925bd</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[senior-developer]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[junior-developer]]></category>
            <dc:creator><![CDATA[Anna J McDougall]]></dc:creator>
            <pubDate>Sun, 13 Jun 2021 20:15:51 GMT</pubDate>
            <atom:updated>2021-06-14T06:27:46.231Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*A08xedzYnQq8ZYcEiMhj2A.png" /></figure><h3>Introduction</h3><p>I am in a unique position right now: I am a Junior Software Engineer filling in for a Tech Lead for two weeks, covering two internal projects filled with other juniors, trainees, and interns. This means that I am both a junior and acting as a guide for juniors at the same time.</p><p>This isn’t the first time I’ve played this ‘double role’: when I was completing my year-long training in web development, I was both a student and a class tutor: learning and teaching at the same time. There is a lot to be said for this: namely, that teaching helps you learn as well.</p><p>Additionally, this unique position allows me to provide insight on how best to support junior developers with the advantage of both perspectives: that of the junior, and that of the supporter.</p><p>All that said, let’s talk about ten things you can start doing to better support your juniors today. <strong>Spoiler alert:</strong> a lot of it comes down to communication!</p><blockquote><a href="http://www.twitter.com/annajmcdougall">Follow Me on Twitter @AnnaJMcDougall</a></blockquote><h3>1. Define expectations and timelines</h3><p>It can be extremely disorienting to enter not only a new workplace but also a new industry. If you are in charge of guiding the path of a junior, it is your job to explain to them <em>as early as possible</em> what that path will be, what is expected of them, and what kind of timeline they’ll be working with.</p><blockquote>“For the first month or so, you and I will be working closely to have you trained up in Java for the backend, including testing and basic microservices. There is no set timeline for this, but once you feel you’re ready to move on, we’ll then look into Docker and other containerisation technologies. The goal is that by about six months into your time with us, you’ll be comfortable and confident coding the backend for bigger projects.”</blockquote><p>Alternatively, you could speak more broadly:</p><blockquote>“As a junior, we really want you to focus on learning and asking as many questions as possible. You’ll have a chance to explore a lot of different technologies, and after around a year we can talk more about which you’d like to specialise in.”</blockquote><p>It is also important to speak directly about what you expect (or don’t expect) from them:</p><blockquote>“Our expectations in your first few months is that you get to the point of being able to solve a few tickets, but we don’t expect you to be an expert or to complete them without any assistance.”</blockquote><p>By having these conversations, the journey of their first year won’t seem quite so daunting: this kind of structure can provide a better sense of security. This allows them to have some soft goals to work towards, but also gives them an understanding that they are not expected to be an expert.</p><h3>2. Emphasise trust</h3><p>A lot of juniors will be entering the industry straight out of some sort of study situation, be it a bootcamp or a degree or self-study at home. As a generalisation: the younger or newer to the workplace a junior tends to be, the more they will tend to try to impress you and not tread on any toes. This is <em>not a good thing</em>: you want honesty and you want to know exactly where they stand with the technology.</p><p>Often juniors are so caught up in trying to impress you, <a href="https://blog.annamcdougall.com/impostor-syndrome-the-biggest-enemy-to-your-progress-is-your-ego-ckdejvtg700062xs16154g181">since they’re often suffering from Impostor Syndrome and trying to prove themselves</a>, that it will be hard for you to get an honest assessment of their skills and abilities, and any attempt you make to do that directly could embarrass them.</p><p>Instead, try to build a relationship of trust.</p><p>For example, when I first began I told my Unit Lead that I had a dentist appointment on that Friday and I wanted to know if that was “OK”. His response was perfect:</p><blockquote>“I’m not here to micromanage you. I trust you to handle your own schedule and complete your hours as you see fit.”</blockquote><p>Additionally, you need to be transparent about not knowing things, and to talk about it openly with your juniors. One trainee asked me about the difference between casting and parsing, and my response was:</p><blockquote>“Great question! I think I know, but let me check so I don’t feed you false information.”</blockquote><p>This models the kind of behaviour you want to see: honest conversations about what we do and don’t know, and an openness to being wrong and checking for the latest info.</p><h3>3. Provide choices</h3><p>Very often, a company or team will have a structured onboarding process. This is usually a great idea, but there has to be wiggle room for individual responses. Where possible, try to find small ways where you can provide options. Give optional ‘bonus assignments’, provide multiple tracks of specialisation, or offer for the junior to come into meetings they wouldn’t normally be in so they can see how things run.</p><p>Early on in my time at Novatec, I was invited into a few meetings with the Software Reliability Engineering team in our Spanish office. I barely said two sentences, but getting to see how different teams worked together was highly valuable for me, and I felt special being invited.</p><p>Now, as an Acting Tech Lead, I’ve offered opportunities for trainees and students to work with me on topics, or to sit in on workshops that are too advanced for them (for a half-hour or so), so they can get a taste of what is to come. Nobody *has* to do these things: they are offered up as choices for additional involvement/observation/learning, and the junior is free to take it or leave it.</p><p>From your perspective, this is also a good way to see what opportunities interest individual juniors, and what opportunities don’t. This can only help you further personalise your interactions, and perhaps also flag early which areas could be their future specialisation.</p><h3>4. Avoid Minimisers: “Easy”, “Simple”, “Basic”, and “Obviously”</h3><p>This is one of the most important but most difficult habits to break. In my team, we work with a lot of trainees with little or no programming experience.</p><p>- How do you think this person will feel if I talk about how “easy” HTML and CSS are and then they get stuck learning Flexbox? <br>- What about when they ask me how to turn a string into an integer and I say “Well obviously you need to parse it” and they don’t know what parsing means?<br>- What if I tell them to try some “simple exercises” and they get stuck only 5mins into trying?</p><p>As someone with a bit more experience, it’s easy to forget how hard things are at the beginning, and how much of a change in thinking programming often requires. Things that are easy, simple, and obvious to you are not necessarily that way for a junior.</p><p><em>Your goal might be to make concepts seem less intimidating, but what the junior hears is “you’re supposed to know this and you’re ignorant if you don’t”</em>. Remember Impostor Syndrome? A lot of juniors are also career changers, and when they have it implied that something is obvious that they don’t know, it can trigger a broader fear of not belonging.</p><p>That, in turn, means they’re less likely to ask the follow up questions they should ask:</p><p>- “Flexbox seems to be holding up my progress, do you have any good resources on it?”<br>- “Sorry, what does parsing mean?”<br>- “I’m stuck on the first exercise, can you help?”</p><h3>5. Avoid solving problems for them</h3><p>Let’s say, though, that they <em>do </em>ask the right questions; They <em>do </em>ask for help. What comes next? Presumably, like any good mentor, you’re ready and willing to help them solve it. Wonderful!</p><p>If you’re in a position to guide a junior, then you most likely are a problem solver, and your instinct will be to solve their problem as quickly and easily as possible.</p><p>Unfortunately, that instinct is not the right approach. You need to give them enough resources to solve the problem, without actually solving it for them.</p><p>For many beginner issues, the problem will be not knowing the correct terminology to Google: in this case, the answer could be as simple as saying “Try looking up information on CORS”.</p><p>But let’s say they have the information, and still don’t know how to proceed. The next question should be “What have you already tried?”. This achieves two things: it ensures they’ve actually tried to solve it themselves (which helps promote initiative); but it also gives you an idea of how they’re thinking about the problem and its solution.</p><p>In short, try to ask leading questions or make suggestions for future research, rather than just saying “Oh that’s easy just use a loop”.</p><h3>6. Ask questions</h3><p>It’s not just the junior who should be asking questions, it’s you as well. Asking questions allows the junior to repeat and articulate concepts that may otherwise be unclear or not totally solidified in their minds.</p><p>Try some of these:</p><p>- “What kind of problems do you anticipate for this ticket?”<br>- “What kind of tests will we need to write?”<br>- “What should happen if a user enters text instead of a number?”<br>- “Do you think we should use an integer or a double here?”</p><p>This step is particularly important for juniors and trainees who<em> aren’t</em> asking a lot of questions themselves. These kinds of points allow you to gauge where a junior is at in terms of their knowledge, which means you can better tailor your responses to their level. If they can answer the fourth question clearly, but can’t answer the second question, then you know they have decent programmatic knowledge but less testing knowledge. This is good information and means you can help them with finding appropriate resources.</p><h3>7. Review tickets with “Why?”</h3><p>Your junior has completed a ticket and/or has asked you to review their code, terrific! One great piece of advice I received recently from my own Technical Lead, is to always ask “Why” in these scenarios.</p><p>This is especially the case if, like me, you’re still new to the project yourself. Even if not, trying to understand the perspective of your junior is always worth the extra time it takes to ask more probing questions.</p><p>If someone has solved something in a way that would never occur to you, this is especially important to ask, as it avoids you perhaps jumping to the conclusion that it is just wrong. Sometimes the fresh eyes of juniors can bring things to our attention that are new or different, and taking the time to understand that perspective could actually help you improve your codebase.</p><p>In addition to that, asking ‘Why’ might also highlight misconceptions the junior has about the codebase itself, which in turn could help you with refactoring or making the flow of information cleaner. After all, we want human-readable code that is as simple to follow as possible.</p><h3>8. Give regular feedback</h3><p>One of the hardest things to do as a senior is to give honest, regular feedback. Let me teach you a simple strategy for doing so, called the “compliment sandwich”.</p><p>- Lead with a compliment<br>- Insert some constructive criticism<br>- End with a compliment</p><p>Here’s an example of a compliment sandwich:</p><blockquote>“I wanted to share with you some general feedback about your progress, since you’ve now completed your first week. <strong>Overall I’m really happy with how many questions you’ve been asking</strong>: it’s clear you’re really engaging with what you have to learn and are being honest about your progress. I got a comment or two from coworkers that <strong>sometimes you interrupt them in group discussions</strong>, so ideally that’s something you could work on for next time. Other comments I received said that <strong>your sense of humour is really refreshing</strong> during routine meetings, though, which I know is greatly appreciated by all of us!”</blockquote><p>This gets the point across: “people are noticing when you interrupt, and it’s a behaviour which isn’t good for the team”. However, it’s also not making it into a bigger deal than it needs to be, and the junior won’t come out of the engagement thinking that everyone hates them, which is naturally a concern of someone new to any type of group.</p><p>The other benefit to this type of feedback is that it leaves room for a different approach when something more serious <em>does </em>happen. If someone is yelling at teammates, for example, or making discriminatory “jokes”, you can pull them aside and be far more direct, and they will know that it is serious because THERE IS NO SANDWICH.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*69BPNDnIP9BslvJYrzUVjQ.jpeg" /></figure><h3>9. Go beyond technical conversations</h3><p>Sometimes you see a junior lose the wind in their sails. They look deflated and defeated, and are not being their usual selves. This is the time to enter “Mentor Mode” and shoot them a quick message or have a quick chat with them: “Hey, you don’t seem quite yourself today. What’s going on?”. If they make it clear it’s not to do with work, then you need to also make it clear that that’s OK: “No worries, you can still tell me about it.”</p><p>I have been on both sides of this conversation. Both times, I have come out feeling closer to the other person and it has built trust between us. It feels good to know that someone is noticing when I’m down, and that I’m not bound by what is considered typically professional when something is impacting my work. Similarly, knowing what is happening in the personal lives of others, especially when it is serious and impactful, means that we won’t rush to make judgments about their work performance or personalities.</p><p>You might also find that someone is dealing with typical issues such as impostor syndrome. In these scenarios, it’s a good idea to share your own experiences, how you felt when you started your first tech job, etc. Knowing that you understand, or at the very least acknowledge, the impact of these feelings can lead to even further trust and helps establish a solid working relationship.</p><p>Of course, if the issues are beyond the scope of your abilities to handle or support, there is also nothing wrong with saying so: “I am here if you need someone to talk to, but I’m not a professional and this sounds like something you need to discuss with someone who knows more about it”. Definitely don’t give unsolicited medical advice for medical issues (e.g. depression, anxiety, phobias, etc.).</p><h3>10. Ask for regular feedback</h3><p>Last but not least, remember that the flow of information should never just be one-way. None of us are perfect, and we all mess up. Similarly, we all have skills we can work on. If you’re new to guiding juniors, take the time when giving them feedback to ask them “Is there any way I can support you better?” or “Have you got any feedback for me from our time together?”.</p><p>Try not to phrase a request for feedback as a statement, such as: “I hope you’ve found our time together useful”. This begs for a compliment and does not provide an open environment for honest critique.</p><p>Better still, if there are a few members of the team who you know tend to brutally honest or lack a filter, then it’s worth shooting them a message and saying “If you have or hear any feedback on me, good or bad, I’d love to know”. This again builds trust, but you also know that if word starts going around ‘on the grapevine’, you’ll hear about it.</p><p>Although of course, you have to be ready to hear negative feedback, just like when you were a junior yourself. Honest critique, even when constructive, can still hurt; but it is essential not only to your own progress, but to that of the future juniors you take under your wing.</p><h3>Conclusion</h3><p>Build trust, have an open ear, and be ready to read between the lines. Nurture your leadership of juniors and their progress will not only reward your company, but your soul. You can probably recall someone who lifted you up and gave you faith in yourself in your early days. Be that for someone else and you can change their lives, even if only for 20–40 hours per week.</p><p>You got this.</p><blockquote><a href="http://www.twitter.com/annajmcdougall">Follow Me on Twitter @AnnaJMcDougall</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cb7fb5925bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>