<?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 Pat Kua on Medium]]></title>
        <description><![CDATA[Stories by Pat Kua on Medium]]></description>
        <link>https://medium.com/@patkua?source=rss-4ef627af4a72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bP1XF6xQ9mN2NaH8.jpg</url>
            <title>Stories by Pat Kua on Medium</title>
            <link>https://medium.com/@patkua?source=rss-4ef627af4a72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:48:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@patkua/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[Moving on from N26]]></title>
            <link>https://medium.com/@patkua/moving-on-from-n26-675eff16c2b8?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/675eff16c2b8</guid>
            <category><![CDATA[n26]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Fri, 27 Dec 2019 13:17:31 GMT</pubDate>
            <atom:updated>2019-12-27T14:22:52.188Z</atom:updated>
            <content:encoded><![CDATA[<p>More than a couple of years ago, I started on the journey as a “shake-up” CTO at N26. I often describe the role at the time as, “Shaking the snow globe.” The patterns of an early stage start up would no longer scale, and the company needed someone to help guide the transition. I was very honoured to guide the tech team through hypergrowth, and helping us transition from “start up” to the “scale up” stage of a company. Flash forward to today, and I’m happy to say we achieved that (and more).</p><p>I’m happy to say that the tech team is significantly more robust, and I leave knowing it’s in a much healthier state than what it was.</p><blockquote><em>“Every new beginning comes from some other beginning’s end”</em></blockquote><blockquote><em>- Semisonic</em></blockquote><p>There are, of course, always many areas to continue to improve on. I’m happy that we have grown and hired many strong technical leaders who will continue to improve and iterate on this.</p><h3>What I’m proud we accomplished</h3><p>Although there are many elements I’m proud we accomplished, here are some of the ones that were definitely highlights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0XygIGKMdCG8xV_q.jpg" /></figure><h4>A better balance of tech to non-tech</h4><p>When I first started, each C-level introduced new team members to the rest of the company. In the first few months, I was introducing one, maybe two, new people per month when the business team was introducing maybe 10–15. If, like me, you have worked in a place where you have more people with projects than capacity to work on them, you know what that would result in.</p><p>I worked closely with the people and especially recruiting team. We reworked everything from compensation and benefits, employer brand, recruitment processes and onboarding. Although we ultimately improved how we recruited and retained people in tech, I believe many improvements also benefited other departments as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ncgrvUXpad0dmgF0.jpeg" /></figure><h4>We’re not just diverse, but also more inclusive than before</h4><p>Like London, Berlin attracts all types of international people. In the last report I read, we had more than 60 nationalities in the tech department. I also wanted us to have diverse educational backgrounds and gender diversity, but I know focusing on diversity alone is not enough. We also needed to make sure we focused on inclusion.</p><p>Early on in my time, I sponsored the very first company wide International Women’s Day event. You can read more about it here. We set up a diversity channel on slack, added a bot that provided alternatives to gendered language like “guys”. ( <em>Sidenote: It’s amazing how many times we had to reinstall that bot!</em>) I believe these actions let more people bring their full selves to work and resulted in support for CSD, many other Employee Resource Groups to support better work-life balance.</p><h4>We avoided growing chaotically, instead doing so deliberately with a Target Operating Model</h4><p>As the tech team grew, I knew that we would need to change our organisational structure to maximise both autonomy and alignment. As the team grew, we restructured deliberately to address issues team members faced as bottlenecks moved to different parts of the organisation. We introduced new roles and capabilities to focus on issues, giving people new growth paths and new areas to work in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qcyd9FSjWpWcReCB.jpg" /></figure><h4>I was able to personally support many people in their own growth</h4><p>Growing companies offer people new opportunities for growth. However knowing that many roles like management or technical leadership are not a promotion but a role change, I’m happy to have supported many technical leaders in their own growth. I personally ran the Tech Lead Development Program approximately 5 times throughout my time. I mentored and coached people through many tough situations and I’m happy to have seen so many people grow and evolve. I even received some feedback that my support not only helped them professionally, but also in their personal life and relationships!</p><h3>What’s next?</h3><p>I very much appreciated my time shepherding the tech organisation, influencing the leadership team and direction of N26 and valued the experiences and tough situations I faced. I’m grateful for the experiences of working so closely with founders and other wonderful executive team members.</p><p>Many leaders ask themselves if they are having the best impact they can have. Are they able to bring their strengths to play in their role? I know where my strengths lie, and given my personal goals, it’s time for me to apply these strengths in a new context.</p><p>I will announce what exactly I’ll be working on in the new year, so watch out for a future post.</p><p><em>Originally published at </em><a href="https://www.thekua.com/atwork/2019/12/moving-on-from-n26/"><em>https://www.thekua.com</em></a><em> on December 27, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=675eff16c2b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting (More) Stuff Done Days at N26]]></title>
            <link>https://medium.com/insiden26/getting-more-stuff-done-days-at-n26-6886951da4f8?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/6886951da4f8</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[n26]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Fri, 04 Oct 2019 09:47:52 GMT</pubDate>
            <atom:updated>2021-06-22T09:58:48.684Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first joined N26, I wrote about how we have <a href="https://n26.com/en-eu/blog/getting-stuff-done-days-at-n26">Getting Stuff Done Days (GSDD)</a>, 2 days every 6 weeks where people in <strong>Product &amp; Tech</strong> down tools. During GSDD people choose where they spend their time versus working on a team priority. For a lot of people in tech, this often meant experimenting with libraries, tools or techniques, sharing lessons learned, teaching and sharing with each other. More importantly, GSDD are two days where people do not have any meetings, and they can focus on what they need to do to get stuff done.</p><p>Although this started in <strong>Product &amp; Tech</strong>, other teams have now adopted this practice, giving them strong focus time to get stuff done. This practice has been well adopted across <strong>Design</strong> teams, <strong>Marketing</strong> teams and <strong>People</strong> Team. In this article, I want to celebrate some of the examples of what people accomplished during their GSSD.</p><h3>DESIGN</h3><h3>Experimenting with Augmented Reality Cards</h3><p>Our design team constantly explores emerging technologies and how can they be amplified by design to bring customers experiences that not only delight but also prove useful. One of our design team members, Maja, used her GSDD to experiment with Augmented Reality (AR) and understand how its application might bring our card product closer to users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WSjpC7PgJUkiL8jhH91bOg.jpeg" /><figcaption>Experimenting with AR for new experiences</figcaption></figure><h3>PEOPLE</h3><h3>Bringing a greener focus to the office</h3><p>It’s easy in rapid growth to forget about topics that matter beyond the current company goals. A group from our people team looked at encouraging practices to create a more sustainable office, to propose more green initiatives and with the support from our Employee Group for Environmental practice, plan out what we could do for <a href="https://www.worldcleanupday.org/">World Cleanup Day</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bKSG1VHx3U7Dk_XybX1uhA.jpeg" /><figcaption>#worldcleanupday in Berlin 2019</figcaption></figure><h3>Accelerating Talent</h3><p>Our Global Future Talent Program Manager Jeff Lovejoy was tasked to tackle the war on tech talent. One idea he had was a N26 Talent Accelerator Program, with the tagline: “Building the best YOU”. The program focuses on developing internal talent and finding people passionate about technology who may not have the practical experience needed. The only way to deliver an award winning program would be to listen to our own people. Working closely with tech recruiter, Babet Van Oorschot, Jeff used his GSDD to pull people from different departments within the People Team to brainstorm what a program could look like. Using this as a kickstart to bring people together, Jeff then knew who and how to approach other people in the business to move this project forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qyEN7KjYBmqBvhbHflNIDw.png" /></figure><h3>MARKETING</h3><h3>Improving the SEO Health Score</h3><p>A Website Task Force (people from the Web, Product Comms, SEO &amp; Design teams) used a GSDD to find areas on the <a href="https://n26.com/">N26 domain</a> to improve the crawling efficiency of search engines. Team members had always wanted to improve this but never found the time. The members of the Task Force first identified different areas to tackle (e.g. incoming and outgoing links, images, HTML tags, localization issues, etc). They then prioritized these and assigned leaders to work on each area. After one intense day, the improvements significantly increased the Website Health Score. A bonus outcome was an agreed standard to ensure future success as the website continues to evolve.</p><h3>Amplifying good practices</h3><p>Great leaders amplify the effectiveness of others. This is why it’s been really great to see the adoption of our Getting Stuff Done Days (GSDD) spread beyond Product &amp; Tech. It’s clear that GSDD provides a good focus, a reminder to continually improve and to create space for everyone to take action to improve their own workspace.</p><h3>Want to take part in GSDD?</h3><p>If you’d like to join N26 and have the opportunity to Get Stuff Done as well as take part in our GSDD, take a look at our open <a href="https://n26.com/en/careers?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=getting-more-stuff-done">roles here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6886951da4f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/getting-more-stuff-done-days-at-n26-6886951da4f8">Getting (More) Stuff Done Days at N26</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A peek into Data Science at N26 with Gráinne McKnight]]></title>
            <link>https://medium.com/insiden26/a-peek-into-data-science-at-n26-with-gr%C3%A1inne-mcknight-6aea24d31d9a?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/6aea24d31d9a</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Mon, 02 Sep 2019 07:32:18 GMT</pubDate>
            <atom:updated>2019-09-02T07:32:18.432Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this interview, I sat down with Gráinne, a Data Scientist at N26, to explore a bit more about her field, and how the data team works. Data Science hasn’t played a strong part in my history in tech so was fascinated to hear some of results. Read on for more insights.</em></p><p><strong>Patrick:</strong> Hi Gráinne! Thanks for taking the time out of your day. Would you please introduce yourself?</p><p><strong>Gráinne:</strong> My name is Gráinne, and with my accent, you can probably tell that I’m Irish. I’ve always loved mathematics. I studied my Bachelor’s in Mathematics, and then specialised in statistics. I started working in more traditional, conservative banking as a credit risk modeller. I loved the job. I got to learn a lot about economics, topics we didn’t cover in school. I decided I wanted a change, and came to N26 where I’ve been here for more than a year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eUCTr_9rP1b6hwUx9UWA8Q.jpeg" /><figcaption>Gráinne (Data Scientist at N26)</figcaption></figure><p><strong>Patrick:</strong> How did you get into Data Science? At what point did you decide to move in this direction?</p><p><strong>Gráinne: </strong>For me, data science is statistics. But maybe with more of an emphasis on the infrastructure and tooling built around it. Before I focused on specifying models with other people building the infrastructure. Now I’m responsible more end-to-end. I was nervous before making the change. However I’ve always enjoyed programming and learning about today’s modern tooling.</p><p><strong>Patrick: </strong>What tools have you used?</p><p><strong>Gráinne: </strong>I previously worked with tools like R, or SAS. At N26, we use a lot of python in the data team. This was my first time using many of these tools, although I did practice a bit before I joined. I feel, like most things, once you’ve been exposed to the tooling, you know which questions to ask. Knowing the right questions means you can find answers online or ask the team.</p><p><strong>Patrick: </strong>You’re right. We are so lucky to live in a time of such open information. If you can’t find it, you can post something on Stackoverflow. Or you write an article, contributing back to that body of knowledge.</p><p><strong>Patrick: </strong>Why don’t you talk about a Data Science project that you’re excited about here are N26.</p><p><strong>Gráinne: </strong>I’m currently working on a few projects. One that I’m particularly excited about is modelling financial crime risk. My background in credit risk modelling has helped. I’ve learned a lot about how people attempt to defraud each other. It’s fascinating but also slightly depressing. We are lucky have so much freedom to innovate on how we detect financial crime. We have very modern tooling, enabling us to quickly build and iterate on our complex models. Topics like fraud are a constant ongoing <a href="https://en.wikipedia.org/wiki/Red_Queen_hypothesis">red-queen</a> game. Our tooling enables us to move quicker as the environment and behaviour changes.</p><blockquote>“We have very modern tooling, enabling us to quickly build and iterate on our complex models.”</blockquote><p><strong>Patrick:</strong> Great. What don’t you share a bit more insight into how the data department works? What roles do you have and what do they focus on?</p><p><strong>Gráinne:</strong> The data team is, unsurprisingly, focused on data. We have three broad groups — Data Engineering, Data Analytics and Data Scientists. I love how we work because we are all closely related and we work very collaboratively. This means we learn from each other and support each other. Data Analysts focus on learning and interpreting data for business projections. One example might be understanding future projections of growth. Data Scientists focus on building models to learn from the data, rather than analysing it. For example, we might develop a model that can learn how to recognise suspicious account behaviour. Data Engineers work at optimising our data pipeline. An example might be how data arrives, or how to feed data back into the system.</p><blockquote>“I love how we work because we are all closely related and we work very collaboratively.”</blockquote><p><strong>Patrick:</strong> That sounds very interesting. What’s an example of how you work together?</p><p><strong>Gráinne: </strong>As an example, when we start an initiative, we’d work very closely with Data Analysts to understand where the data is and what is relevant. I like to think of them as librarians of the data warehouse. We then iterate and test our models. As a model becomes closer to product ready, Data Engineers set up the right pipelines and then we integrate these models into the product.</p><p><strong>Patrick: </strong>It sounds like a very fluid collaboration style. I’ve seen companies where those groups don’t at all interact. In your team, it feels like you get the right people in different roles work together at different points very organically.</p><p><strong>Gráinne: </strong>Exactly.</p><p><strong>Patrick: </strong>What do you think is exciting about the field of Data Science today?</p><p><strong>Gráinne: </strong>I get really excited when I personally learn from Data or when Data shows an insight I never had before. One counter example might be our current chatbot. Our chatbot has been very successful at answering many queries. It can help people connect their questions to existing bodies of knowledge. However because English is very hard for a chatbot to truly understand. I can say, in a way, I am much smarter than the chatbot, though much slower at responding!</p><p><strong>Gráinne: </strong>An example might be when understanding credit or financial crime risk. Data Science teaches me more about what is risky behaviour and what is not. A good analogy is seeing stereograms. You can see patterns but it’s hard to understand what the meaning of those patterns are. Data Science teaches us to recognise those patterns. It also helps us understand if those patterns are positive or something to avoid. It’s like once you see it, you can’t unsee it (<em>laugh</em>). That’s what I find very exciting about Data Science. I’m also excited about the potential of Data Science at N26. We’ve only started to scratch the surface of what smart banking could be like. We have so many ideas of where it could go. We need more time and people to work on those ideas.</p><blockquote>“It’s like once you see it, you can’t unsee it”</blockquote><p><strong>Patrick:</strong> I agree. We have a good basis to build upon and we have many more experiments to try. What are three things you’ve learned since joining N26?</p><p><strong>Gráinne:</strong> The first and most difficult was learning how to make decisions. I would describe where I was previously working as very, “top down management”. In my previous employer, it felt like others made decisions for you, rather than by you. At N26 we have more end-to-end responsibility. We have more autonomy and decision making power. You might think for someone who builds decision models, this would be super easy but it’s not.</p><p><strong>Patrick: </strong>Shifting to leverage autonomy, is indeed, sometimes hard. What are two other things you’ve learned?</p><p><strong>Gráinne: </strong>My programming and infrastructure skills have improved a lot. I’ve learned a lot more about Data Engineering because I’ve most recently been working with a Data Engineer. This area blows my mind as there’s so much to learn!</p><p><strong>Patrick: </strong>Do you have a book you could recommend?</p><p><strong>Gráinne: </strong>There are so many books out there.</p><p><strong>Patrick: </strong>Do you have a favourite?</p><p><strong>Gráinne: </strong><a href="https://web.stanford.edu/~hastie/ElemStatLearn/">The Elements of Statistical Learning</a>, which is available as a pdf download from Stanford University’s website.</p><p><strong>Patrick: </strong>I’ll add it to my reading list as I haven’t read it. Finally, what would be a piece of advice you would offer to someone interested in Data Science?</p><p><strong>Gráinne: </strong>Maybe I’m biased because I come from a background of mathematics and statistics. It’s important people have a fundamental understanding of algorithms. Many people romanticise Data Science today. People often think all we do is draw on whiteboards, sketching algorithms. That’s only a small part of what we do. There is also data infrastructure, data pipeline construction, model performance monitoring and much more. I enjoy that, but you have to accept this will be a large part of your time as a Data Scientist.</p><p><strong>Patrick: </strong>That sounds like a lot of work. Even though compute, data and network is cheaper and faster today, I can see how patience is still very important. Thank you very much for your insights into Data Science, your team and how you work at N26.</p><p><strong>Gráinne: </strong>Thank you.</p><h3>Interested in joining <strong>Gráinne </strong>at the bank the world loves to use?</h3><p>Join us on the journey of building the mobile bank the world loves to use, and <a href="https://n26.com/en/careers?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=a-peek-into-data-science">take a look at our open roles here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aea24d31d9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/a-peek-into-data-science-at-n26-with-gr%C3%A1inne-mcknight-6aea24d31d9a">A peek into Data Science at N26 with Gráinne McKnight</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What does a Technical Program Manager do? With Meysam Sarabadani]]></title>
            <link>https://medium.com/insiden26/what-does-a-technical-program-manager-do-with-meysam-sarabadani-9f9e6005e9ed?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f9e6005e9ed</guid>
            <category><![CDATA[tpm]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[n26]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Mon, 26 Aug 2019 14:35:59 GMT</pubDate>
            <atom:updated>2019-08-31T08:25:56.836Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The Technical Program Manager (TPMs) is newer to our industry. You don’t read about it this in many agile teams yet many larger organisations have this role. In this interview, you’ll learn more about why the role exists, what some of the common focuses are and learn more about one of N26&#39;s Technical Program Managers.</em></p><p><strong>Patrick:</strong> Hi Meysam. Thanks for taking the time out of your busy day. Would you please tell us a bit about yourself?</p><p><strong>Meysam: </strong>Of course! I’m Meysam. I’ve been with N26 for almost a year now. My background is in software engineering and I moved into product and program management. Most recently in my career I’ve been working on mostly technical programs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLLSZUXK1lFQgHfWPXJ9Ig.jpeg" /><figcaption>Meysam (Technical Program Manager at N26)</figcaption></figure><p><strong>Patrick: </strong>You’re in this role, “Technical Program Manager”. How do you describe this role to other people?</p><p><strong>Meysam:</strong> This role manages multiple areas at the same time and mostly focused on technical projects. This means the person playing the role should have a technical background but also have great project management skills to manage programs of work. This is a very complex role requiring many interdisciplinary skills. This role coordinates projects across many teams who all have stakes in a technical project. This person requires a technical background because they need to understand and traverse technical dependencies, work very closely with deeply technical people and at the same time manage the roadmap and often non-technical stakeholders to ensure teams are on track.</p><p><strong>Patrick: </strong>Sounds hard! What is a concrete example of a technical topic that touches many teams?</p><p><strong>Meysam: </strong>I can think of many different examples. I can talk about some projects we’ve had in the past. One, which all European organisations have had is GDPR. There are strong technical elements to this, although I haven’t managed this topic. We also recently launched into the US and there are many technical infrastructure elements to something that cuts across all product teams. Another more recent example I’ve managed is migration from one environment to another. We’re constantly improving our standards and compliance. This means migrating many microservices from one environment to another. As an example, a recent project required touching 100+ microservices owned by 40–50 developers and tech leads across multiple teams. This makes it very complex.</p><p><strong>Patrick: </strong>If I understand it right, this is quite different from a typical product manager role because the nature of the initiative is often deeply technical. In the last example, migrating environments has business value but the topic is deeply technical, requiring a good understanding of infrastructure, configuration and technical dependencies. This is also classically different from a product manager who works with a single team because a change in environment touches almost all teams. Where a product manager may have zero external team dependencies or a few, these projects tend to touch many.</p><p><strong>Meysam:</strong> Yes that’s absolutely correct.</p><p><strong>Patrick: </strong>What do you think is required to be a good TPM?</p><p><strong>Meysam: </strong>I believe this is a relatively new role in the market. At least compared to both project and product management. Our industry seems to need this role because you need to have a very strong technical background to understand what you are managing. You need this deep understanding of technical topics, so you can dive into areas where there may be hidden assumptions or complexity to uncover. At the same time, you need someone who can also interpret or translate that complexity into an easy-to-understand format to help leaders and managers make better decisions.</p><p>It’s not enough to be a Product Manager or a Technical Product Manager because you need skills to manage multiple teams and stakeholders. At the same time, a Project Manager is not enough because you also need to have a deep understanding of the area you’re managing. I fell into this role because there are many companies with this need and they’re looking for people with this experience.</p><p><strong>Patrick: </strong>Let’s take a typical week. Who do you interact with and how do you interact with them?</p><p><strong>Meysam:</strong> It’s a very interesting role because on some weeks, I could be interacting with all parts of the company. That depends on the project and the current need. For the most part though, I’m working with technical people. This means mostly Tech Leads, Principal Engineers, Engineering Managers and Product Managers as well. I talk to engineers on a daily basis to understand what we are delivering, where the risks are and what is still outstanding. A TPM really needs to understand the detail. Of course, I also work with management such as the CTO to be able to outline the next steps or decisions that need to be made in a timely manner. I also work with a team of Technical Delivery Managers who help me with different projects and help me scale.</p><p><strong>Patrick:</strong> How would you describe the main value add for this role? Why can’t a team, or existing roles take care of this?</p><p><strong>Meysam:</strong> It’s a good question. I’m sure everyone can take care of some aspect. Let’s take a role of a Product Manager. That person is focused very much on a product area, or a piece of software they are delivering. They often don’t have time to manage technical integrations of that product. A TPM on the other hand doesn’t focus on a single area, but ensures a technical project moves forward. They use their technical background to ensure all dependencies and technical integrations move forward for the project, and not just a single product area. A TPM create a project roadmap based on this understanding and also communicates this to management to show milestones in a much easier to read way. A TPM is able to break down very complex technical projects, abstract technical complexity and can present this information to non-technical stakeholders who need to be informed and made aware of risks and trade-offs as a project progresses.</p><p><strong>Patrick:</strong> That can be really useful to drive decisions, keeping everyone, including non-technical stakeholders informed on topics that are very technical.</p><p><strong>Meysam:</strong> Exactly. This is very important for decision making. You have a lot of responsibility because management will use this data to make decisions. There are, of course, many other challenges on how to produce data that’s helpful to drive decisions.</p><p><strong>Patrick: </strong>I think it’s always useful to compare and contrast roles. How would you describe the difference between a TPM and maybe a Tech Lead and Engineering Manager?</p><p><strong>Meysam: </strong>Tech Leads are mostly focused on leading technical topics such as design and architectural decisions and enabling and aligning engineers within their team. Engineering Managers support the team, by creating the right environment for teams to deliver what they need and grow. A TPM does not focus on these two areas. Of course, a TPM can provide 1–1 feedback or give ideas on direction but that’s not their strong focus. Their role is really about connecting the dots. Particularly across teams where a technical initiative is not a team’s particular focus. A key responsibility of a TPM is to also drive the roadmap of that project, to see it delivered end-to-end.</p><p><strong>Patrick:</strong> Let me try to summarise my understanding from you described. A tech lead is driving the technical solution with the team for a particular product area. The engineering manager is working with that team to help grow people, ensure they have the right capacity for planning and to optimise the flow of development. You are working across product teams to coordinate dependencies, keep track of the critical path, to expose risk to the overall roadmap and to drive decisions around priorities that come in conflict with a cross-team wide versus a product team centric set of priorities.</p><p><strong>Meysam:</strong> That’s also how I would see it.</p><p><strong>Patrick: </strong>What do you enjoy most about the role?</p><p><strong>Meysam: </strong>It’s very challenging and I like challenges. Every day presents a new challenge. You’re challenged by management because they’re using the data you generate. They want confidence that the data is high quality to make better decisions. At the same time, you don’t have a team of people — they belong to product teams. So it’s a challenge to persuade teams to ensure their part of a project is prioritised. It’s a huge challenge to gain the support of all teams to ensure your needs are reflected in their plans. This can often be seen as quite disruptive.</p><p><strong>Patrick:</strong> It’s also a great way to develop and refine good influencing skills.</p><p><strong>Meysam:</strong> Absolutely. You need to practice influencing. However I really enjoy this challenge because it helps me grow while I see a project move forward.</p><p><strong>Patrick:</strong> What is one way that you’ve grown in since you’ve become a TPM?</p><p><strong>Meysam: </strong>One recent thing is helping me be more precise when I answer questions. It’s not enough to answer with a yes or no. You need back up answers with more information. When you’re talking with technical people details can potentially change a solution or spark an entirely different conversation. When an engineer asks questions, you also need to have the right answers. This has made me focus on how I answer differently, to be able to dive into the topic, drive good answers and it helps me be more precise.</p><p><strong>Patrick:</strong> I can imagine it’s also then adapting that mode of communication for a different audience such as talking to upper management, non technical stakeholders, down to an engineer. There’s a lot of different types of ways of communicating the same message.</p><p><strong>Meysam: </strong>Yes it’s really not that easy because you’re dealing with so many people with so many different backgrounds.</p><p><strong>Patrick: </strong>What do you think are the top three skills needed for the role?</p><p><strong>Meysam:</strong> The first one is having the expertise in the technical domain. If you don’t understand the complexities of this, you cannot drive conversations, or you will be blind to certain types of risks. It’s very helpful to have a solid background in engineering and perhaps even the domain in which you’re managing the technical project. The second skill is strong communication skills, as we’ve just talked upon. The last one is really strong leadership skills. Remember that you don’t often have a team — you need to rely on others. So you need to use leadership skills to lead a topic, generate buy in from others and to move the topic forward. You need to lead people to own their own topics because the success of your projects is dependent on how well they implement it.</p><p><strong>Patrick:</strong> What advice would you give to people considering the TPM role?</p><p><strong>Meysam: </strong>Apart from requiring the skills mentioned above, people should prepare themselves for this being a very high traffic role. This means having many conversations, often tough conversations with many people across an organisation. It depends on the complexity of the program, the size of the company and structure but the role itself requires a lot of adaptability. My advice for dealing with this is ensuring you have a good work-life balance for coping with this.</p><p><strong>Patrick: </strong>If someone is already in this role, what advice would you give them?</p><p><strong>Meysam:</strong> If you’re in this role, you’ll realise it requires a lot of context switching across people, teams and projects. You shouldn’t look at this role like you do as an engineer — with a binary perspective. It’s rare you have a day with a clear success or failure. You’re there to enable others to drive a topic forward on its milestones. Change your mindset from execution to enablement. Instead of doing, you will need to talk, communicate, lead and enable people from many different perspectives, teams and roles to lead a project to success.</p><p><strong>Patrick:</strong> Wow. It sounds very much like a strong leadership challenge and opportunity for people. Thank you so much for sharing your insights into this very interesting role.</p><h3>Interested in joining the bank the world loves to use?</h3><p>Join us on the journey of building the mobile bank the world loves to use, <a href="https://n26.com/en/careers/departments/13426?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=what-does-a-tpm-do">have a look at our open roles here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f9e6005e9ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/what-does-a-technical-program-manager-do-with-meysam-sarabadani-9f9e6005e9ed">What does a Technical Program Manager do? With Meysam Sarabadani</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing Distributed Development well in our Payments Group]]></title>
            <link>https://medium.com/insiden26/doing-distributed-development-well-in-our-payments-group-16cdd9957404?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/16cdd9957404</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[n26]]></category>
            <category><![CDATA[technology-news]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Mon, 22 Jul 2019 15:20:00 GMT</pubDate>
            <atom:updated>2019-08-19T09:18:10.288Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://alistair.cockburn.us/">Alistair Cockburn</a>, agile manifesto signatory and author of <a href="https://amzn.to/2GeQ9SY">Agile Software Development</a> (2002) wrote about the “bandwidth” of different communication styles. Distributed development forces modes where there is less “bandwidth” and is inevitable in today’s age of more connected and more distributed workplaces.</p><p>At N26, we’ve tried to avoid distributing work across multiple locations, preferring to have a topic owned by people in a single location. Although that’s the ideal, there are always exceptions. In today’s interview, I spoke with <strong>Sarah Abrantes</strong> (Engineering Manager) and <strong>Lukas Klinser</strong> (Product Manager) who work in our Payments Group where they experienced distributed development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtgrjIxQIq8Mj6YBDzeoJw.jpeg" /><figcaption><strong>Sarah Abrantes</strong> (Engineering Manager) and <strong>Lukas Klinser</strong> (Product Manager) in our Payments P&amp;T Group</figcaption></figure><p><strong>Pat: </strong>Some teams working in the Payments product area are quite different from others because they have a history of doing distributed development. Can you please share some examples of what that looks like?</p><p><strong>Lukas: </strong>N26 continues evolving as a global company. The Payments Group leads the way for N26, learning from pain points and creating blueprints to do distributed development well. I’ll give you two examples:</p><ol><li>We launched <a href="https://n26.com/en-eu/blog/the-beta-launch-of-n26-uk-begins">N26 last year in the UK.</a> Payment systems are different in the UK and we had a lot of existing work, so we worked with a team of external consultants in Barcelona to help us launch on time. With our engineering team in Berlin, we developed over two locations.</li><li>We have a feature enabling instant N26-to-N26 transfers called <a href="https://n26.com/en-gb/blog/say-hello-to-moneybeam-instant-payments">Moneybeam</a>. We wanted to start offering this across all of our markets (EU, UK and the <a href="https://n26.com/en-us/blog/n26-launch-in-the-us">recent launch in the US</a>). This meant moving from two to three locations (Barcelona, Berlin and NYC).</li></ol><p><strong>Pat: </strong>Distributed across two locations sounds hard enough. I can imagine three would be yet another challenge! What are some challenges the teams faced?</p><p><strong>Sarah:</strong> Onboarding is a constant challenge. Not only at the start of a project, but also throughout as we’ve continued to grow. Onboarding is much harder in a distributed environment. When you’re co-located, pair programming and asking ad hoc questions is easier. You feel connected all the time. When you’re remote, you need to find ways to constantly integrate everyone. You want to watch out for side conversations. For example, decisions might be made over a coffee break. Those not included will naturally feel excluded from the conversation. We set up practices to keep the conversation flowing as if we were in a single location.</p><p><strong>Pat: </strong>What are some of those practices?</p><p><strong>Sarah:</strong> We invested in as many face-to-face trips as possible. This was much easier between Berlin and Barcelona, than say, NYC. When people had face time, they built richer personal relationships. This improves empathy, understanding and communication. People understand each other&#39;s personalities better. When you read a message on slack after meeting someone, you can almost imagine it in their voice or tone. This reduces misunderstandings significantly. We also have all team ceremonies online with good video conferencing equipment. We make sure that no official team meetings happens without remote participants.</p><p><strong>Pat:</strong> Great! I can see how the face-to-face time makes a big difference. OK, so what does a typical day look like? How do people communicate and collaborate?</p><p><strong>Lukas: </strong>That’s a good question. It makes me think. We all start our day the same way. We arrive at the office and catch up on systems like email, slack or our electronic tracking systems, etc. We usually have stand-ups at around 11:00. When we had teams in Berlin and Barcelona, we’d ask for both sides to do their stand-up in a meeting room in both locations. We would then “walk the wall” during this meeting. We never tried a physical board and it worked well for us. As questions came up during the day, we introduced a practice of ad hoc meetings if messages over slack looked like they needed a longer discussion. We suggested some time slots. People voted with emojis and then people would jump on a video conference. These are our ways of establishing a remote-first team approach to discussions. We wanted to discourage simply turning around and chatting to whomever was closest, as this would exclude many people.</p><p><strong>Pat: </strong>Yes, I can see that. Let’s talk about tools. It’s a super common question I come across when talking about distributed development. What did you try? What didn’t stick? I already heard about Slack and your electronic tracking tool. What else helped?</p><p><strong>Sarah: </strong>When we were doing stands up in meeting rooms, we faced a problem many companies have… not enough meeting rooms. Our team evolved to be more efficient. People stay at their desks and everyone attends the meeting remotely. It makes the team space noisier but on the other hand, it means everyone is deep in the meeting. Everyone experiences the same environment and shares the same constraints. You avoid issues where one side feels less included because they struggle with video conferencing for the day. Our room constraint pushed us to try something new, and resulted in a very positive outcome.</p><p><strong>Pat:</strong> Now everyone is at their desk for remote meetings. Tell me about a person’s physical desk setup? What does that look like?</p><p><strong>Lukas:</strong> Everyone has a pair of good headphones. Most people seem to prefer over-ear headphones, which they also use for music to get into the “zone”. We encourage people to avoid furiously typing during meetings, and that everyone focuses on the call. We have a remote ally for a week who shares their screen to provide the shared view of our electronic tracking system.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_oVutF0rV0k%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_oVutF0rV0k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_oVutF0rV0k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/01edc50438fcf01b0c3403f2d632e0a0/href">https://medium.com/media/01edc50438fcf01b0c3403f2d632e0a0/href</a></iframe><p><strong>Lukas: </strong>When we worked more with meeting rooms, we tried a <a href="https://amzn.to/2XOgjGU">Meeting Owl</a> device. It solved the problem of many people hunching around a small camera or to get closer to the speaker. The Meeting Owl takes a 360 view of the room and always focuses in on who is talking without any additional software. That was very helpful.</p><p><strong>Sarah: </strong>We also experimented with some remote pairing tools but due to our risk analysis, we stopped using them. Security is our top concern, so we had to make a tough call and stop using such tools.</p><p><strong>Pat:</strong> Your teams developed distributed for some time. Are there practices that you tried, that stopped working? What did you try that didn’t stick.</p><p><strong>Sarah:</strong> We stopped remote pair programming because of the tool constraint. It was a showstopper. We moved to co-located pair programming and cross-office reviews.</p><p><strong>Lukas:</strong> I can’t think of any other things. We quickly found ways that worked. If we feel pain points, we try to solve them very quickly.</p><p><strong>Sarah:</strong> I think our focus on transparency and team culture helped here. In the past, we had speedback sessions so team members could swap feedback. It’s hard to detect when individuals have issues between them and our speedback sessions helped build this learning culture.</p><blockquote><strong>&gt;&gt; </strong><a href="http://joshuavial.com/speedbacking/">Speedback sessions</a> are very short feedback sessions involving all team members, in which they share a short feedback with a peer and move along to do the same in a different pair. Much like a speed dating.</blockquote><p><strong>Pat:</strong> Let’s talk about one of my favourite topics: Retrospectives. How did that work in your situation? What worked well for your team?</p><p><strong>Lukas:</strong> Software worked for us, essentially. Normally you would gather in a room, you’d have a facilitator and hand out post-its and pens. Then you would think about what works well, what didn’t go so well, discuss, etc. Since we didn’t have that we needed to find an equivalent. We found a tool that would allow us to mimic that same behaviour where you can have different columns and allowed people to anonymously add contributions.</p><p><strong>Pat:</strong> Who was facilitating and how did that work? How did you synchronise people in different locations?</p><p><strong>Lukas</strong>: We usually rotated facilitators between locations. Sometimes we had people outside of the team which worked very well. When we had more independent facilitators, team members could really focus on taking part in retrospectives.</p><p><strong>Pat:</strong> Imagine you’re sitting in front of another team, who’s about to go on their own distributed team adventure. What advice would you give them?</p><p><strong>Sarah:</strong> Remember that the main team workplace is no longer where you sit. The main team workplace is now the cloud environment. If you have two different teams, you want to focus on creating a shared third office, based in the cloud. Build a culture with no siloed conversations. Make sure you invest in face-to-face trips. Even though we’ve worked well remotely, in-person collaboration will always be more effective. It doesn’t need to be 100% but it’s important to have that personal connection between team members.</p><p><strong>Lukas:</strong> First, figure out your tooling quickly. If you don’t, you’ll end up in a rabbit hole of choice. Second, make your communication and decision making channels explicit. It’s much harder if people have different expectations. Finally, be really mindful of each other&#39;s time. When you’re co-located, you can tap people on the back, check to see when someone will return from a meeting. If you’re in a distributed setting and you have meetings, make sure people attend to respect other&#39;s time.</p><p><strong>Pat:</strong> You’ve shared some very useful insights into distributed development that I’m sure others will benefit from. Thank you very much.</p><h3>Interested in joining us in building the bank the world loves to use?</h3><p>If you’d like to join us on the journey of building the mobile bank the world loves to use, have a look at our open roles <a href="https://n26.com/en/careers/departments/13426?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=doing-distributed-development-well">we’re looking for here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16cdd9957404" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/doing-distributed-development-well-in-our-payments-group-16cdd9957404">Doing Distributed Development well in our Payments Group</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Teams to Groups to Segments — An evolution using the Target Operating Model]]></title>
            <link>https://medium.com/insiden26/from-teams-to-groups-to-segments-an-evolution-using-the-target-operating-model-36f26d6c7a98?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/36f26d6c7a98</guid>
            <category><![CDATA[n26]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Thu, 11 Jul 2019 09:07:15 GMT</pubDate>
            <atom:updated>2019-07-14T14:10:48.792Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Teams to Groups to Segments — An evolution using the Target Operating Model</h3><p>A few weeks ago, I published <a href="https://www.thekua.com/atwork/2019/06/introducing-the-target-operating-model/">an article</a> about how we grew Product &amp; Tech (P&amp;T) at N26 during <a href="https://medium.com/insiden26/what-hypergrowth-is-like-at-n26-bd3f3667cc46">hypergrowth</a>. I introduced the idea of a <a href="https://www.thekua.com/atwork/2019/06/introducing-the-target-operating-model/"><strong>Target Operating Model (TOM)</strong></a>. The first article focused on the why and what of this tool. In this article, I will share how we’ve evolved the core “building block” of P&amp;T at N26.</p><h3>From nominal teams to stable Product Teams</h3><p>When I first started at N26, we had a set of cross-functional teams. This meant that we had people from Product, Design and Tech all sitting together (yay!) We had some organisational smells we wanted to address.</p><p>A <a href="https://martinfowler.com/bliki/CodeSmell.html">code smell</a> is a potential indicator of a larger problem. A code smell does not always lead to a problem. Rather you have to investigate and decide for yourself. An organisational smell is similar but to do with the organisation itself.</p><p>One such smell was a person moving from one team to another on an almost weekly basis. It also felt like a team’s focus would change on an almost weekly basis. Teams were rarely stable. The result was a lot of activity, but not a lot of outcome.</p><p>Our first TOM formalised the expectations of a <strong>Product Team</strong>. Each <strong>Product Team</strong> had an ideal size (up to 8) and a product area to focus on. Each team then focused on the evolution and support of that product area. We mapped out the complexity of our product set, to our team size and realised that we had many gaps to fill</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*h8dPpnx-hzIujXLh.png" /></figure><p>A large goal of our first TOM was to bring sustainability to product development. We needed to move away from relying on a handful of individuals (common in a startup) to a more sustainable model. Comparing our rate of hiring to our current needs, and needs for the future showed a huge gap. We kicked off an initiative to improve our recruiting, onboarding and retention approaches.</p><p>Part of this model revisited responsibilities of the informal leadership of each team. Instead of having a Product Owner and Tech Lead, we added in an Engineering Manager at a <strong>Product Team</strong> level. We wanted Tech Leads to focus on managing and aligning technical complexity. We also wanted to provide people with the environment and people support. When a <strong>Product Team</strong> was small, this was manageable As a <strong>Product Team</strong> grew, Tech Leads could not focus on both areas well.</p><h3>From Product Teams to Product Groups</h3><p>As we filled empty roles in <strong>Product Teams</strong>, we addressed what we wanted to. Engineers felt less overwhelmed. People could take holidays without worrying about being a single point of failure. We had deeper conversations around architectural direction. We also started having conversations about individuals’ career growth. People had more consistent 1–1s and feedback.</p><p>As we grew and changed, we noticed some new trends and organisational smells. As an example, some <strong>Product Teams</strong> reached the boundary of a reasonable team size. We needed to start splitting teams to minimise communication overhead. Some <strong>Product Teams</strong> also demanded a stronger focus on skills. As an example, our Payment <strong>Product Team</strong> was more integration heavy. Our Onboarding <strong>Product Team</strong> needed more front-end skills. Each <strong>Product Team</strong> needed more flexibility in how they structured themselves. Sometimes a product area needed a short-lived task force. We wanted to push more self-organisation downwards.</p><p>As a result we introduced the idea of a <strong>Product Group</strong> in our second TOM. A <strong>Product Group</strong> has 30–40 people from a cross-functional mix of Product, Design and Tech. A <strong>Product Group</strong> still had ownership over a product area. A <strong>Product Group</strong> had more autonomy to shape their own team structures and ways of working. We also made sure <strong>Product Groups</strong> knew company or global standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*En1ySvE5ycv_cltR.png" /></figure><p>This meant that it was perfectly ok to have a <strong>Product Group</strong> with 5 teams. Or to have a <strong>Product Group</strong> with 3 teams and one small task force. Each <strong>Product Group</strong> had more flexibility to better fit their product area at the time. We expected <strong>Product Group</strong>s to be explicit about their choices and trade-offs. To aid this, the second iteration evolved the role of the Engineering Manager. Rather than being at a team level, the Engineering Manager moved to a <strong>Product Group</strong> level. This non-trivial decision deserves its own article, so I won’t discuss it further here.</p><h3>From Product Groups to Product Segments</h3><p>Our organisation continued to grow. An internal sample of different <strong>Product Groups</strong> showed more heterogeneity. <strong>Product Groups</strong> continued to ship product. <strong>Product Groups</strong> had more capacity to breath. <strong>Product Groups</strong> had more capacity to deal with more complex topics. <strong>Product Groups</strong> handled unplanned work better, minimising impact to other <strong>Product Groups</strong>. <strong>Product Groups</strong> had more people with relevant skills for their product areas.</p><p>The number of <strong>Product Group</strong>s continued to grow. We noticed that some <strong>Product Groups</strong> should co-ordinate more with some other <strong>Product Groups</strong>, but weren’t. As our business grows, domain complexity grows. We wanted to find a way to keep inherent domain complexity <a href="https://medium.com/clarityhub/low-coupling-high-cohesion-3610e35ac4a6">highly cohesive but low in coupling</a> . <strong>Product Groups</strong> alone were not solving this. We also knew that some areas needed further domain knowledge and specialisation. Hiring needs started to differ.</p><p>To address these issues we introduced the idea of a <strong>Product Segment </strong>in the latest version of the TOM. <strong>Product Groups</strong> working towards the same goal sit within the same <strong>Product Segment</strong>. <strong>Product Groups</strong> within the same <strong>Product Segment</strong> should better communicate and align their plans with each other as they should be more related to each other (highly cohesive). Hiring plans will now be made on a <strong>Product Segment</strong> basis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*mcl99-FewcEUnLM7.png" /></figure><h3>Reflecting on our journey evolving our TOM</h3><p>Our latest TOM is still recent, so it’s early days to see it’s impact. When designing software architecture, you consider explicit trade-offs as part of decisions. This is also true if you consider organisational and team structures. No organisation or team structure is perfect. You need to ask yourself, “What are you optimising for right now?” “How are you maximising autonomy and alignment?”</p><p>“What are you optimising for right now?”</p><p><a href="https://www.thekua.com/atwork/books/">Building Evolutionary Architectures</a> tells us to design software systems for constant change. Organisational systems are no different. A company rapidly growing needs to optimise for different issues at different scales. It won’t help you to copy our structures if you don’t share the same issues. Gather input and reflect deeply to consider what you need to optimise for. Evolve, document and communicate the <strong>TOM</strong> best suited for your situation.</p><p><em>Originally published at </em><a href="https://www.thekua.com/atwork/2019/07/from-teams-to-groups-to-segments-an-evolution-using-the-target-operating-model/"><em>https://www.thekua.com</em></a><em> on July 11, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36f26d6c7a98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/from-teams-to-groups-to-segments-an-evolution-using-the-target-operating-model-36f26d6c7a98">From Teams to Groups to Segments — An evolution using the Target Operating Model</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview with our Lead Android Engineer — Lucia Payo (Part 2) on her leadership journey]]></title>
            <link>https://medium.com/insiden26/interview-with-our-lead-android-engineer-lucia-payo-part-2-on-her-leadership-journey-9672b631e983?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/9672b631e983</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[n26-tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Thu, 11 Jul 2019 08:40:35 GMT</pubDate>
            <atom:updated>2019-07-11T08:40:35.769Z</atom:updated>
            <content:encoded><![CDATA[<h3>Interview with our Lead Android Engineer — Lucia Payo (Part 2) on her leadership journey</h3><p>In <a href="https://medium.com/insiden26/interview-with-our-lead-android-engineer-lucia-payo-part-1-1c130d80ba9e">Part 1</a> of this interview, we discovered Lucia Payo’s (LP) background, found out more about her personal journey at N26 and learned more about the Android team. In this part we’ll focus on uncovering her technical leadership journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jn7BgPqoPjopkisUzuVGVQ.jpeg" /><figcaption>Lucia Payo (Lead Android Engineer @ N26)</figcaption></figure><p><strong>PK: </strong>We’ve talked about the Android team. Let’s talk about your leadership journey. You’ve turned around a team. You’ve grown the team rapidly while providing a great environment for everyone to thrive. What have been your biggest lessons learned on your own leadership journey?</p><p><strong>LP:</strong> Good question. When we were starting to grow, none of us were super experienced. None of us were officially a leader, or had gone through this experience before. We wanted everyone to feel they could have an impact and influence; much like the way we felt when we joined. We left things very open. I learned how leadership during this time is particularly important. You don’t have to be a strong leader to set a line, but you need to know when to define a line, particularly as new people join. This reduces conflict by setting expectations early. I learned, as you onboard new people, it’s important they understand the technical vision and direction we have defined. It doesn’t mean they can’t change it or influence it. It sets the basic context.</p><p><strong>PK: </strong>If I understand it, then the first lesson is about articulating boundaries. Or about setting expectations on where people can have an impact in their roles.</p><p><strong>LP:</strong> Right.</p><p><strong>PK: </strong>What is another lesson you learned?</p><p><strong>LP: </strong>You have to learn how to say no. In the beginning I was trying to do too many things. It’s not always about saying, “No.” Rather, it’s more of a, “No, not me.” You have to learn what you can take on, or delegate, or being very straightforward with a no. This takes a lot of time and effort. I’ve learned to respect that process.</p><p>In the beginning I started very stressed out, as my internal expectations told me, “Just do it.” In my mental model, there was no time for processing this information. There was no time for coming up with a plan or figuring out what we want to do on a strategic level. I didn’t respect that this process takes time, creating more pressure for me. I discovered I needed time. Time to absorb new information or requests. Time to process information. Time to decide on the best way to handle the situation. Sometimes that means saying, “No”, or, “No, not now.”</p><p><strong>PK:</strong> This is, indeed, such an important part of leadership. Working out what you should be doing versus what others can help you with.</p><p><strong>PK:</strong> You said you wanted to grow when you joined N26. It sounds like you have grown a lot as an engineer and a lot in your own leadership journey. You’ve learned how to set boundaries and change the direction of a team. What has helped you personally on this leadership journey?</p><p><strong>LP:</strong> Having an environment that is very supportive. We don’t have an environment where people point fingers at each other. We are very collaborative. People help each other out, especially across roles, teams and departments. We are in an environment where you can make mistakes. Making mistakes is not bad. However it’s important to work in an organisation that supports you, as long as you do your best.</p><p>I’ve found it’s particularly important to also communicate what you’re trying to do and why. By involving other people, others can also give you input or feedback if they see you might be making a mistake.</p><p>I also had the support of specific people to talk through topics. I also had volunteers taking on more responsibility. As the team grew, we had more people stepping up. They benefit, because they can grow and it helps me scale myself. Additionally, you provided some great technical leadership training. What was most impactful was having an opportunity to put those skills into practice. It was important to get our hands dirty.</p><p><strong>PK:</strong> We’re running out of time, so my last question. What is one piece of advice you would give to aspiring technical leaders?</p><p><strong>LP: </strong>Be patient. With yourself. And with others. It takes time to adjust to a new role. It depends on your approach. I’m the sort of person who puts pressure on myself. If you’re that type of person, calm down. Be patient. Ensure you take a break. If you’re stressing out or panicking, you’re not going to be able to effectively help others out. You will also need to learn to repeat yourself (a lot!) People will keep coming back with the same question and you will need to repeat the answer. It’s just how it is!</p><p><strong>PK:</strong> Some really great insights into both the Android team and your own leadership journey. Thanks Lucia!</p><p><strong>LP:</strong> Thank you!</p><h3>Want to work with Lucia in Berlin, Barcelona, New York or Vienna?</h3><p>If you’d like to join us on the journey of building the mobile bank the world loves to use, have a look at the Android Engineer roles <a href="https://n26.com/en/careers/departments/13426?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=interview-with-our-lead-android-engineer-lucia-payo-part-2">we’re looking for here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9672b631e983" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/interview-with-our-lead-android-engineer-lucia-payo-part-2-on-her-leadership-journey-9672b631e983">Interview with our Lead Android Engineer — Lucia Payo (Part 2) on her leadership journey</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview with our Lead Android Engineer — Lucia Payo (Part 1)]]></title>
            <link>https://medium.com/insiden26/interview-with-our-lead-android-engineer-lucia-payo-part-1-1c130d80ba9e?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c130d80ba9e</guid>
            <category><![CDATA[n26-tech]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[n26]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Mon, 01 Jul 2019 07:59:12 GMT</pubDate>
            <atom:updated>2019-07-01T08:21:28.871Z</atom:updated>
            <content:encoded><![CDATA[<h3>Interview with our Lead Android Engineer — Lucia Payo (Part 1)</h3><p>A few weeks back, I spent time with <strong>Lucia Payo</strong> (LP), our <strong>Lead Android Engineer</strong>. We spoke on so many interesting topics that I’ll split this across two articles. In Part 1 (this article), we’ll learn more about Lucia’s background, her journey at N26 and the android team. In Part 2 (the next article), we’ll focus more on her tech leadership journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNSXFyO-16ws-YFcSZzTvQ.jpeg" /><figcaption>Lucia Payo (Lead Android Engineer @ N26)</figcaption></figure><p><strong>PK:</strong> Hi Lucia! Thanks for taking the time to chat to me. Why don’t you tell me about your background and what you’ve been up to since joining N26.</p><p><strong>LP:</strong> Before N26, I was an Android Engineer in a consultancy. Consulting gave me many insights in different companies. I learned different ways of working and different ways of approaching problems. Not only at a technical level. I worked with talented people, speeding up my technical and softer skills growth. I learned how to communicate well with clients on deadlines. Or how to arrive at a solution together. Consulting was a lot about adapting and learning. I had the chance to change projects once every eight months. At one point, I decided to commit to a product I believed in, and where there was room to have impact and influence. In 2016 I came across N26. It looked very good but was also very challenging.</p><p>Back then, the whole android team was leaving. When I joined, the new android team members had zero overlap with the old team. We inherited a codebase without any guidance. We joined an organisation that was moving very rapidly. It was like jumping into the deep end of a pool.</p><p><strong>PK: </strong>Tell us more about what happened when you joined.</p><p><strong>LP: </strong>When I joined, I wasn’t the Lead Android Engineer. I was a Senior Android Engineer. It was also very clear, to me, that the team needed leadership. We didn’t have strong Android leadership at the time. We had a Head of Mobile taking care of both platforms (iOS and Android) but he had a background in iOS. We sat down as a team and started with small baby steps, defining our team culture. We needed to agree on what culture we wanted and what practices we, as a team, wanted to use.</p><p><strong>PK: </strong>Can you give a concrete example?</p><p><strong>LP: </strong>One of the very first instances I remember was agreeing on a style guideline. One that we would all share and use in our IDEs. When I joined, we had just received our banking licence. We proved to customers and investors that this was going to last. At this point, we wanted practices that scaled. We wanted to work towards a codebase we knew would be around for many many years.</p><p><strong>PK:</strong> That’s a great act of leadership. Trying to shape and have an impact across the whole team.</p><p><strong>LP:</strong> I wasn’t the only person thinking this either. The whole team recognised the paradigm shift, moving into scale up mode. We needed to take over a foundation designed to find a market fit, but not designed to scale.</p><p><strong>PK: </strong>What was the biggest challenge?</p><p><strong>LP: </strong>Our biggest challenge is that we had to do a lot of these transformations without much context. We didn’t have the previous team around to guide us or to give insights into certain decisions. That was a huge challenge.</p><p>We started with some fundamentals. We established team rules or guidelines that everyone started following. We put together a shared architectural vision. We agreed on how we would approach unit testing as a team. The biggest technical challenge was not building something that scales. It is building something that scales without breaking what we already built.</p><p>It’s like changing the heart of a person while they’re running a marathon. It needs to keep pumping, or you know they won’t make it to the end line. At the same time, you know it needs an upgrade.</p><p><strong>PK: </strong>I love that analogy! So true about critical software. Fast forward to now. The Android Team is a very different team. You have more than 20 members across a few locations. You didn’t have much context, so what is one aspect about the team you’re proud of?</p><p><strong>LP: </strong>I think we grew a very good culture in the team. This has a lot of benefits. In the beginning, you can’t imagine the impact it has. It’s huge! With our technical achievements, I am proud that we are very consistent in how we write features. The first thing we did was defining our architecture.</p><p><strong>PK: </strong>This is the <a href="https://medium.com/insiden26/reactive-clean-architecture-with-android-architecture-components-685a6682e0ca">reactive clean architecture</a> you described in this talk right?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F16wPp91kyuE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D16wPp91kyuE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F16wPp91kyuE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e999f1661e92bc6d9f027996f577c174/href">https://medium.com/media/e999f1661e92bc6d9f027996f577c174/href</a></iframe><p><strong>LP: </strong>Yes. At the time, it was a bet. You know, the team didn’t know the project very well. Yet we felt it was the best approach we had. Team members started rolling this out in their features. There were bumps in the road. But we learn. We are now on version three of this architecture. We had to evolve it. It was a solid approach. It gave everyone a sense of how to write a feature. The architecture provided enough structure for developers to understand or evolve other features. Our architecture encourages good practices like modularisation and better testability. It’s been a couple of years since we introduced it. Now almost 70% of our features follow it, which has been a challenge since it’s a large codebase.</p><p><strong>PK:</strong> How did the team size affect help or hinder adopting this?</p><p><strong>LP:</strong> You might think that having a larger team slows us down. It’s been great to have a larger team because we’ve been able to move even faster towards our target architecture. When we started with four people, you can only do so much. It was frustrating because you knew what you wanted to do but there was so much code to transform. You could only change small pieces bit by bit. With a larger team, we’ve been able to move much faster as more of the codebase evolves.</p><p><strong>PK: </strong>Let’s talk more about your team. How would you describe your team?</p><p><strong>LP: </strong>The Android team is very collaborative, even though members work distributed in different product groups. We collaborate very heavily. Our slack channels are very active. We have a lot of events and we’re friends who often hang out after work! We have good vibes in the team. Everyone celebrates when something good happens. I’m super proud of this!</p><p><strong>PK:</strong> So you should be!</p><p><strong>LP: </strong>I am. I feel like this has been one of my greatest achievements. We hired over 18 people in a very rapid time. We have a great onboarding process that helps newcomers quickly come up to speed. I believe we are also one of the most stable teams in N26. It is a completely different picture from before, when all the Android team members left.</p><p><strong>PK:</strong> You should be proud of turning around the team culture. What are the three biggest challenges for the team in the next 12 months?</p><p><strong>LP:</strong> This coming year is key for the Android team. We have worked hard towards our technical vision. We’ve identified three more main challenges that will help us grow and scale. Our first challenge is finishing our modularisation work. The second challenge is the <a href="http://atomicdesign.bradfrost.com/chapter-2/">ADL (Atomic Design Language)</a>. We want to align everyone on how things look and define a common language to use across the organisation and across all features. The third challenge is moving towards our own <a href="https://samnewman.io/patterns/architectural/bff/">Backend For Front-End (BFF)</a>, which we believe will provide an even better user experience.</p><p>We believe that a user focus is very important. We want to provide value to the user quickly. We want to be able to customise what they see to provide a personal experience. To do this, we need to be flexible. Our three initiatives will help with this. These initiatives will have a big impact. It will have an impact not only in the Android team but in all the cross-functional product teams as well.</p><h3>Want to work with Lucia in Berlin, Barcelona, New York or Vienna?</h3><p>If you’d like to join us on the journey of building the mobile bank the world loves to use, have a look at the Android Engineer roles <a href="https://n26.com/en/careers/departments/13426?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=interview-with-our-lead-android-engineer-lucia-payo-part-1-1c130d80ba9e">we’re looking for here</a>.</p><p>This concludes Part 1 of this interview. Watch out for Part 2 where Lucia and I speak more about her technical leadership journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c130d80ba9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/interview-with-our-lead-android-engineer-lucia-payo-part-1-1c130d80ba9e">Interview with our Lead Android Engineer — Lucia Payo (Part 1)</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview with an Android Engineer — Mustafa Mutlu]]></title>
            <link>https://medium.com/insiden26/interview-with-an-android-engineer-mustafa-mutlu-f8c7c7b4f6ba?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8c7c7b4f6ba</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[n26]]></category>
            <category><![CDATA[n26-tech]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Fri, 24 May 2019 07:49:41 GMT</pubDate>
            <atom:updated>2019-05-24T07:49:41.612Z</atom:updated>
            <content:encoded><![CDATA[<h3>Interview with an Android Engineer — Mustafa Mutlu</h3><p>Our Android team is growing rapidly. As a company experiences hypergrowth, processes and structures break. I find it fascinating to see how teams learn and improve in this environment. In this interview, find out how our Android team grew and scaled. I sat down with <strong>Mustafa Mutlu</strong>, one of our Android Engineers, to get some relevant insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hEz8YQ_66vixzFRfpUBh5Q.jpeg" /></figure><p><strong>PK: Please tell me a little bit about your background.</strong></p><p>My name is Mustafa. I joined N26 about a year ago in April. Before that I was working in Istanbul, Turkey. I have three years of Android experience. I enjoy working at N26 and living in Berlin. I spent most of my time in the “Payment Schemers” team in the “Payments Group.” We’re focused on bringing more features to the UK and follow up after our launch last year. I’m also now working towards the US launch and excited about that as well.</p><p><strong>PK: You mentioned working as an Android Engineer in Istanbul. How would you describe the difference between how the team here works and how you’ve worked in the past?</strong></p><p>My previous employer in Istanbul was a lot smaller. We didn’t have several offices with lots of people working on the same application. N26 is a hypergrowth, scaleup company. We’ve grown rapidly and kept the same startup values. It’s not one of those huge companies where you don’t talk to people outside of your team. Everyone is very approachable. You can always approach anyone with your feedback or questions. It’s nice to have this openness and transparency.</p><p>In the Android team we are now about twenty people.</p><p><strong>PK: It’s massive!</strong></p><p>Yes. When I first joined, we were twelve people and it had doubled in size. We are growing exponentially, which is very exciting. At the same time, as we grow, we face new challenges on how we work as a team. We’ve had to evolve our processes.</p><p><strong>PK: What’s an example of a process you had to evolve?</strong></p><p>We run events called “Knowledge Sharing Events.” We have a weekly one-hour meeting focused on knowledge sharing. In the past, we met face-to-face in a room. We shared our screen, walked through code we recently wrote or discussed a problem we recently solved. I found it very helpful when I first started and still find it useful today. We also learn more about what everyone else works on. If you introduce a new component or a new way to solve a problem, this is the perfect place to share the knowledge.</p><p>After expanding the Android team to our Barcelona office, we had to evolve these “Knowledge Sharing Events.” In our current process, we create a new page on our wiki for each meeting. Every engineer who wants to share something prepares by writing topics and details to share in that page. In the meeting, we connect remotely, walk through the page and discuss.</p><p>It’s better because it’s based on documentation that you can later refer to. Information is not lost. If you don’t have time to attend the meeting, or if you’re on holidays, you can still catch up. We like to think it’s like an internal blog we use to share information with each other.</p><p><strong>PK: That’s a great scaling idea. You can also go back to something you discussed in the past.</strong></p><p>Yes! We also know finding information is important. We also keep the pages indexed so others can easily search and find relevant information. Our “Knowledge Sharing Events” used to be ad hoc face to face discussion. We’ve scaled up our practice to work remotely and more asynchronously. I think we tackled this challenge nicely. It works very well.</p><p><strong>PK: Much more scalable, too.</strong></p><p>Indeed! I expect we will continue to grow. Like when we have an Android Engineer in our New York office, we think this practice will scale well.</p><p><strong>PK: What have you learned so far since joining N26?</strong></p><p>Before I joined, I saw Lucia’s article on the <a href="https://medium.com/insiden26/reactive-clean-architecture-with-android-architecture-components-685a6682e0ca">Reactive Clean Architecture.</a> We use this here at N26. It excited me because I have never used a Reactive Architecture before. We use <a href="https://github.com/ReactiveX/RxJava">RxJava</a> intensively. I wanted to learn more about this and have learned a lot about how to use it since joining.</p><p>I have also learned how we evolve our architecture. During one of our team meetings, we shared what we thought the weakest aspects of our architecture was. We also brainstormed as a team on how to address them.</p><p><strong>PK: It sounds like a great technical retrospective, focused on the Android architecture.</strong></p><p>Right! We used post-its and everything like in a normal retrospective. It was great that all Android engineers contributed to this. We have already improved some of these areas, and have plans for others. Our architecture is battle-tested to support the features we need and the variety of devices we have to support.</p><p><strong>PK: What else have you learned?</strong></p><p>Our team works very closely with a team of Barcelona. This means working like a distributed team across two locations. Our daily standups and ceremonies are therefore held remotely. I’ve never had that experience before and it works very effectively.</p><p><strong>PK: Out of all the teams at N26 I know of, your team is probably pioneering these experiences and practices. More teams will need to learn from yours as our company continues to grow and becomes more distributed!</strong></p><p>Yes, I agree. I have learned so much. Now that we have New York and Barcelona, there are lots of lessons to share.</p><p><strong>PK: I’ve heard about the Android core team. Tell me more about it and how it works.</strong></p><p>Our Android team members normally work as part of cross-functional product teams. We also have a small, dedicated Android core team that does not contribute to product features. It’s a rotation-based team with a couple of permanent members. You join for a month, and then return to your cross-functional product team.</p><p>In the core team, we like to say, “You develop features for features.” You provide essential building blocks for other Android engineers. Those other Android engineers are more focused on product features.</p><p>As part of the core team, you also have more time to explore the latest Android technologies. You assess if they’re relevant for us. If it makes sense, you might even implement a technical spike to learn about them. Of course we then distribute those learnings as part of the “Knowledge Sharing Events.”</p><p>I learned a lot during my time as part of the core team. We had some cross-platform goals like improving modularisation, unifying our design approach, and expanding test and release automation. I improved modularisation by implementing a common navigation tool and method. I also added in more automation and instrumentation to our tests. These reduce our release cycle and better locate errors in our regression tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PZ2eUuecsQpvIZb-_q-Ohw.png" /><figcaption>Android Core Team Rotation</figcaption></figure><p><strong>PK: The rotating core team is a very nice model. You get to work on both a feature in particular domain and you get to work on some platform-like features. You get some variety this way.</strong></p><p>That’s right. We like to describe that we are members of two teams. I’m part of a cross-functional Product Team. At the same time, we like to think of ourselves as Android Ambassadors for that Product team. We are people who offer Android insights to help Product teams achieve their goals.</p><p>As an Android team, we also need to align so that the codebase is consistent. We aim to build a codebase that looks like a single person wrote it. We don’t want it to look like twenty different people wrote it, because we want to easily rotate to different parts. We continue to develop ways to distribute knowledge to ensure we are always up to date with others.</p><p>We work well as an Android team. I’m always aware of what other Android team members are working on. It doesn’t mean I know the detail. I do know who to approach on particular topics if I want to find out more. It’s very nice.</p><p><strong>PK: It sounds like you’ve learned a lot since being here. There’s also been a lot of change. What is one change you’re proud of working on?</strong></p><p>I was part of what we called, a “UK Taskforce.” Launching the UK required a lot of contributions from many teams in the company. My team was responsible for updating our application to offer UK customers the best experience. We had to touch a lot of different places in the application. I am one of the very few people who touched a lot of files at least once as a result.</p><p><strong>PK: I bet your Git username is all over the codebase (laughing)</strong></p><p>Yes (laughing). That’s probably right. Launching in the UK was our first experience launching a non-Euro currency in the app. There are also subtle localisation differences we had to support.</p><p>I’m proud that we accomplished this so rapidly. We’re also taking some lessons learned and applying them as we work towards the US launch. This is even more exciting.</p><p>To summarise though, I’m proud we made the UK launch and enabled new customers to enjoy the N26 experience in another country.</p><p><strong>PK: It’s not easy launching a bank into a new regional area. Particularly when it’s completely different currency. Is there anything else you’d like to share as we come to a close?</strong></p><p>Yes. I have three things to share.</p><p>First, I have a suggestion to Android Engineers to always write good quality tests. At N26 we expect engineers to write unit tests. If you open a Pull Request without unit tests, reviewers will definitely comment on that. We also introduced writing UI tests a few months back. We’re starting to see the benefits of these UI tests to ensure our features are always working. Always write good unit and UI tests. Make sure that your code is working as expected. You should always test things.</p><p><strong>PK: That’s definitely a hard bit about software. Not breaking things when you make a change. What’s the second point?</strong></p><p>Secondly, it’s very important to be as transparent as possible. It’s especially important if you’re working in a collaborative environment. Working in a team requires transparency and trust. Always be transparent. Give and receive feedback with your teammates. N26 is good with this.</p><p>We often have Q&amp;A with co-founders in the company. With C-level people. I like these sessions as you get to ask questions from people you don’t often to talk to. You get to learn more. You get to see things from their eyes. It’s very helpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u98hjntCwXv_sw9N" /><figcaption>Have fun! Photo by <a href="https://unsplash.com/@pineapple?utm_source=medium&amp;utm_medium=referral">Pineapple Supply Co.</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>PK: And your final point?</strong></p><p>Last but not least. Have fun! Having fun is one of the most underrated things. I also think it’s one of the most important ingredients. Work shouldn’t be tedious or boring. It should be fun.</p><p><strong>PK: Great advice and a great perspective in life as well! Thank you very much for sharing more about the Android team and your own experiences.</strong></p><h3>Want to work with Mustafa in Berlin, Barcelona, New York or Vienna?</h3><p>If you’d like to join us on the journey of building the mobile bank the world loves to use, have a look at the Android Engineer roles <a href="https://n26.com/en/careers/departments/13426?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=interview-with-an-android-engineer-%E2%80%94-mustafa-mutlu">we’re looking for here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8c7c7b4f6ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/interview-with-an-android-engineer-mustafa-mutlu-f8c7c7b4f6ba">Interview with an Android Engineer — Mustafa Mutlu</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview with an iOS Engineer — Meet Daniel Peter]]></title>
            <link>https://medium.com/insiden26/interview-with-an-ios-engineer-meet-daniel-peter-55031b81e031?source=rss-4ef627af4a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/55031b81e031</guid>
            <category><![CDATA[berlin]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[n26-tech]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Pat Kua]]></dc:creator>
            <pubDate>Mon, 13 May 2019 10:22:05 GMT</pubDate>
            <atom:updated>2019-05-13T14:24:35.018Z</atom:updated>
            <content:encoded><![CDATA[<h3>Interview with an iOS Engineer — Meet Daniel Peter</h3><p>N26 is the mobile bank the world loves to use. Late last year, we launched one of our most successful products, Spaces. This product really demonstrates how we apply our company value of Simplicity to helping people interact with their finances in a much simpler way. I spent some time behind the scenes with one of our iOS Engineer who was working on the Spaces product, Daniel Peter.</p><p><strong>PK: Hi Daniel. Thanks for making time to chat. Please introduce yourself.</strong></p><p>My name is Daniel Peter and I work as an iOS Engineer at N26. I have been in the company for more than a year now. I joined after finishing my Masters in Computer Science at the Technical University of Munich. I worked as a Software Engineer part time during my studies. This means I had some experience with iOS and writing Swift. I have been writing Swift since it was in Beta.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OqlCjiGwq7LXPcN6qnjr2A.jpeg" /><figcaption>Daniel Peter with his very popular dog, Benno!</figcaption></figure><p><strong>PK: An earlier adopter!</strong></p><p>Indeed! I was lucky. During my studies, my school offered a practical course, developing in iOS, which I took. At the time, Swift was super new. In the field of education, you can use new technologies without worrying about breaking production code. They taught Swift instead of teaching students and older, and more likely to be deprecated, programming language. We built a full game after just a week, called TinyWizard and you can still download it on the AppStore.</p><p><strong>PK: How did you come across N26 and the role?</strong></p><p>After finishing my masters’ thesis, I looked for a position in Berlin as an iOS Engineer. I felt more comfortable applying for an iOS job than I was applying for a TypeScript or JavaScript job.</p><p>It was a coincidence that I saw the job opportunity at N26. I have a friend who also works for N26 as a Backend Engineer. We were just sitting in a bar talking about new technology and trends. My friend referred me to the company. I completed the interview process and ended up with a job offer.</p><p>When I joined the company, I joined a team of 5 people. The team built a well modularised, but large application because it does so many different things.</p><blockquote>“Modularisation makes it really easy to test”</blockquote><p><strong>PK: Tell us more about how the iOS is modularised and how that makes your life as a developer easier.</strong></p><p>Every feature becomes a module. Modularisation makes it really easy to test. It scales really well. In your daily time, your build times are reduced by a massive factor. Rather than building the entire codebase, you rebuild the one feature and modules it needs. It also makes discovering code really easy because modules are named after features. You can jump straight to the module based on the feature that you’re working on.</p><p>Feedback is really quick.</p><p><strong>PK: What team are you working in and what does your day look like?</strong></p><p>I’m part of the Home Group, working on a new feature for <a href="https://n26.com/en-de/spaces">Spaces</a>. Spaces is a feature that allows you to manage money in a nice and simple way. In the end, they are similar to sub-accounts. You use drag and drop to move money around. I love it because it’s such a simple user experience.</p><p>In the Home Group, I work as a part of a cross-functional team that consists of backend engineers, an android engineer, and me, as the iOS engineer. We have a designer jumping in when necessary and a Product Owner (PO).</p><p><strong>PK: Tell us about how you ended up working on Spaces.</strong></p><p>When I joined I was part of a different Product Group, working on financial products like <a href="https://n26.com/en-de/credit">Credit</a> and <a href="https://n26.com/en-de/overdraft">Overdraft</a>. I still had some learning to do so I worked closely with the iOS Tech Lead, who showed me how we build the application. After some time, we said it would make sense to switch groups. Another developer, who was working on Spaces, went away for a conference and vacation. I took over for him and was working with the codebase for the next three weeks.</p><p>The codebase was really clean, well structured and well architected. This made it really easy for me to jump in. I fixed a minor bug on the very first day I joined the Spaces team!</p><p>It shows the speed of how quickly we can onboard people onto new features because they are so self contained and small.</p><blockquote>“Our user research challenges the assumptions and ideas you have about what “simple” means.”</blockquote><p><strong>PK: What was challenging about working on the Spaces product and why?</strong></p><p>The challenging part of building Spaces was nailing the user experience. To do that, we run a lot of user research with designers and user researchers. What’s interesting is how we end up with the product we built.</p><p>We all had ideas about how a flow should work. We all had opinions about how interactions should work. Through user research and testing, we discovered users expected something completely different. It was really interesting!</p><p>Our user research challenges the assumptions and ideas you have about what “simple” means. The testing really helps you understand how people want to use a feature in a certain way and why, that you can’t predict. It leads to a much simpler product.</p><blockquote>“It’s very different from bands who carry money around in a little box!”</blockquote><p><strong>PK: What’s your favourite part of Spaces?</strong></p><p>For me, it’s the ease of use. When you see Spaces, it’s instantly clear what it does. It’s super easy to set up a sub account when you compare it to other banks. It’s super easy to use and to set money aside.</p><p>For example, I also happen to play in a band. We sell merchandise like t-shirts and vinyl records. I’m responsible for managing finances for the band. I opened a Space and whenever we sell something, I just move money into a Space I created and it’s safe. If I compare this to how other bands manage their funds, it’s so easy and convenient. It’s very different from bands who carry money around in a little box!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J26BTrmYtCGKFkIu" /><figcaption>Photo by <a href="https://unsplash.com/@f7photo?utm_source=medium&amp;utm_medium=referral">Michael Longmire</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>PK: You were talking before about the modularisation such as how easy it was to find and make changes. What other aspects do you enjoy working with the iOS team or architecture?</strong></p><p>Coming from a technology perspective, it’s really exciting to work on application that is so big and used by so many people. In my previous jobs, I worked mostly on prototypes. Most of the time, they remained prototypes too. I published an internal application with some real users, but it was only for thirty end users.</p><p>The scale of the application is really exciting. You publish to the App Store. The next day, more than a million people update their app and use it. That’s really exciting!</p><p>The way we build the app reflects this scale too. The architecture is really important for us. We have a guideline on how to build features. As a team, we rely on architectural decisions. Whenever we want to introduce anything new, we come together as a team for a full day which we call an iOS Day. We sit in a room to discuss and then we make decisions as a team. It’s great that we can discuss approaches and agree as a team. In the end it makes our life a lot easier because we are aligned on how to design a feature and review code.</p><blockquote>“The Handbook provides a lot of context for new joiners.”</blockquote><p><strong>PK: You said that the team was 5 people when you first started. What is the size now and how did you onboard so many people?</strong></p><p>We grew to 14 people at this point (<em>PK: as of April 2019</em>). Onboarding is straightforward when you join. All the features are self-contained in their modules. When you work on a feature, you can easily find the code for the feature. We have an agreed foundation which we share through our Handbook. Our Handbook is the documentation about how we work and build features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t5AJRhX5m-zjKHBz" /><figcaption>Photo by <a href="https://unsplash.com/@craftedbygc?utm_source=medium&amp;utm_medium=referral">Green Chameleon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For example, we describe how we handle networking in our application, how we handle flows, and how we handle push notifications. All of these approaches are written down and kept up to date in this Handbook. The Handbook provides a lot of context for new joiners.</p><p>I also found that the iOS team is really supportive. I feel you can post any question to slack like, “I’m encountering this issue. Has anyone faced this before?” and you’ll end up with several responses. Everyone is super supportive.</p><p>Being supportive, having great documentation and building a team that cares about people who have just joined is the secret to onboarding a lot of people.</p><blockquote>“Don’t be afraid to ask questions.”</blockquote><p><strong>PK: If you were to give advice to a starting iOS Engineer, what would you say to help them be more effective?</strong></p><p>I would say, “Don’t be afraid.” Don’t be afraid to ask questions. Don’t be afraid to do something wrong. In the end, it will lead to a situation where you will learn something.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ElcOQwmTbst0cVOh" /><figcaption>Photo by <a href="https://unsplash.com/@helloquence?utm_source=medium&amp;utm_medium=referral">Helloquence</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I would also add, “Trust in your teammates.” We all have domain knowledge, which you build after a certain time. No one expects you can learn everything in a day, or know the whole domain in a day. I don’t think anyone knows the complete N26 domain at all times as the app is changing so fast.</p><p><strong>PK: Fantastic advice. I think this is true, not only for new starters in the iOS team but also for all engineers in all environments. Thanks for sharing your time and giving us some great insights into how the team works.</strong></p><h3>Want to work with Daniel in Berlin, Barcelona, New York or Vienna?</h3><p>If you’d like to join us on the journey of building the mobile bank the world loves to use, have a look at the iOS Engineer roles <a href="https://n26.com/en/careers/departments/13426?gh_src=3824fb5e1&amp;utm_source=magazine&amp;utm_medium=article&amp;utm_content=interview-with-an-ios-engineer-%E2%80%94-meet-daniel-peter">we’re looking for here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55031b81e031" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiden26/interview-with-an-ios-engineer-meet-daniel-peter-55031b81e031">Interview with an iOS Engineer — Meet Daniel Peter</a> was originally published in <a href="https://medium.com/insiden26">InsideN26</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>