# manager Published articles for manager. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Beyond the data: what a Business Analyst does at Nubank DevFeed: [Beyond the data: what a Business Analyst does at Nubank]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-15T12:14:41Z Content type: opinion Language: en Sources: [Nubank]() Topics: [Data analysis](), [decision-making](), [context](), [Tech Lead]() Tags: [adoption](), [business-analyst](), [data](), [data-analysis](), [data-analytics](), [data-science-machine-learning](), [decision-making](), [manager](), [tech-lead](), [user-experience]() ### AI overview A first-person account of the Business Analyst role at Nubank, describing how BAs connect data analysis, context, and experimentation to product and business decisions. The article emphasizes clarifying trade-offs, investigating metrics, and collaborating with product and technical roles. ### Source excerpt Understand how Business Analysts at Nubank use data, context, and experimentation to guide product decisions. The post Beyond the data: what a Business Analyst does at Nubank appeared first on Building Nubank. ## There's more to software development than coding DevFeed: [There's more to software development than coding]() Original publisher: [Read original article]() Author: Dan Lew Published: 2026-08-17T16:38:20Z Content type: opinion Language: en Sources: [Dan Lew Blog]() Topics: [Development](), [coding](), [Artificial Intelligence](), [AI Development](), [Software Engineering]() Tags: [ai](), [career](), [developer](), [developers](), [development](), [engineering](), [engineering-manager](), [like](), [manager](), [product](), [quality-assurance](), [software-development]() ### AI overview This opinion article argues that software development involves much more than writing code. It describes requirements refinement, design and logic review, communication, tradeoff discussions, architecture, project coordination, mentoring, and cross-functional work as important parts of the role. It concludes that these non-coding skills may remain valuable as AI improves at coding. ### Source excerpt Like many software developers, I've been considering the future of my profession in the face of AI. AI can write code. Our job is to write code. It seems natural that we'd be replaced by AI, no? But recently I've been considering the warning ## Why engineering managers lose hands-on coding time DevFeed: [Why engineering managers lose hands-on coding time]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-08-04T06:01:00Z Content type: article Language: en Sources: [Manager.dev]() Topics: [engineering-culture](), [Software Engineering](), [Development](), [AI-assisted coding]() Tags: [ai](), [coding-agents](), [engineering](), [engineering-manager](), [manager]() ### AI overview The article examines how engineering managers gradually lose hands-on coding time as meetings, coordination, and project responsibilities increase. It argues that this shift can become a habit and discusses the case for managers remaining connected to the codebase. ### Source excerpt Never prompted until today ## Engineering management is a career change, not a promotion DevFeed: [Engineering management is a career change, not a promotion]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-07-30T15:00:17Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [Tech Lead](), [systems](), [debug]() Tags: [career](), [coaching](), [debugging](), [engineering-management](), [management](), [manager](), [metric](), [outage](), [promotion](), [support]() ### AI overview An interview with Ryan Murphy examines engineering management as a career path, including promotion criteria, management training, feedback, stakeholder communication, and the shift from optimizing code to owning outcomes. ### Source excerpt Ryan Murphy on what actually gets engineers promoted, why delayed feedback is cruelty, and the manager who told him on day one that he was a resource ## How corporate politics actually work DevFeed: [How corporate politics actually work]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-05-07T15:03:00Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [Job](), [meetings]() Tags: [advice](), [corporate](), [engineering](), [hr](), [job](), [manager](), [manipulation](), [mentor](), [relationships](), [remote](), [work]() ### AI overview An interview with former Amazon Vice President Ethan Evans about corporate politics and career advancement. It examines why strong technical work alone may not determine promotions, how managers evaluate visibility and collaboration, the role of influence and relationships, early warning signs before performance-improvement plans, and mentoring in remote teams. ### Source excerpt With Ethan Evans, a former Amazon Vice President. ## Technical Skills Every Technical Program Manager Should Learn in 2026 DevFeed: [Technical Skills Every Technical Program Manager Should Learn in 2026]() Original publisher: [Read original article]() Author: Dean Hume Published: 2026-05-05T14:12:37Z Content type: tutorial Language: en Sources: [Dean Hume]() Topics: [Development](), [Architecture & Design](), [Cloud](), [CI/CD](), [Containers](), [systems](), [Testing](), [Serverless](), [dashboards](), [Artificial Intelligence]() Tags: [architecture](), [ci-cd](), [cloud](), [code](), [containers](), [dashboards](), [engineering](), [learn](), [manager](), [technical](), [technical-program-manager]() ### AI overview A practical guide to technical skills for Technical Program Managers in 2026. It covers understanding system architecture, APIs, queues, microservices, cloud concepts, development workflows, testing, logs, and dashboards so TPMs can plan and collaborate more effectively with engineering teams. ### Source excerpt The technical skills every TPM needs in 2026 from cloud basics to AI agents and governance. A practical guide to staying close to the tech. ## How to Improve Coding Interview Performance with Personal Stories and Targeted Technical Practice DevFeed: [How to Improve Coding Interview Performance with Personal Stories and Targeted Technical Practice]() Original publisher: [Read original article]() Author: Brian Jenney Published: 2026-03-24T15:05:22Z Content type: opinion Language: en Sources: [Brian Jenney]() Topics: [coding](), [Development](), [Code](), [JavaScript]() Tags: [approach](), [career](), [coding](), [interviews](), [javascript](), [manager](), [recursion](), [software-engineer]() ### AI overview The author describes struggling with coding interviews despite being able to do the underlying job. They recommend cataloging personal work stories for recurring behavioral questions and focusing practice on recurring technical gaps. ### Source excerpt Five years ago, during an interview for a senior dev role, I had a panic attack. ## Put scope on your resume DevFeed: [Put scope on your resume]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-03-04T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Job](), [Ansible Roles]() Tags: [employees](), [individual-contributor](), [manager](), [resume](), [scope]() ### AI overview An opinion article argues that resumes should emphasize the scope and impact of a person's work rather than relying on job titles. It recommends explaining responsibilities, stakeholders, results, progression, and measurable context such as company revenue or employee count. ### Source excerpt Your resume titles don't matter. Just tell me what did you do. ## The agentic future with Temporal: A fireside chat DevFeed: [The agentic future with Temporal: A fireside chat]() Original publisher: [Read original article]() Author: Jeroen Vollenbrock Published: 2025-09-22T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Artificial Intelligence](), [Testing](), [Software Engineering](), [reliability]() Tags: [agentic-ai](), [ai](), [cost](), [guardrails](), [how-to](), [manager](), [testing]() ### AI overview A fireside chat among Temporal, Essent, and Navara examines the practical challenges of building agentic AI systems. It discusses testing unpredictable outputs with evaluations and guardrails, deciding which tasks should use LLMs versus deterministic code, and limiting agent actions to improve control and reliability. ### Source excerpt Key takeaways on agentic AI: testing unpredictable systems, hybrid workflows with Temporal, context engineering, cost tradeoffs, and practical next steps. ## How Managers Can Develop Team Leadership Through Meeting Delegation DevFeed: [How Managers Can Develop Team Leadership Through Meeting Delegation]() Original publisher: [Read original article]() Author: Ryan Murphy Published: 2025-07-14T12:00:13Z Content type: opinion Language: en Sources: [The Software Engineering Times]() Topics: [meetings](), [decision-making](), [trust](), [real-time]() Tags: [coaching](), [decision-making](), [leadership](), [manager](), [meetings](), [real-time](), [retro](), [support](), [sync](), [trust]() ### AI overview This opinion article argues that managers should avoid leading every meeting and instead give team members opportunities to run standups, retrospectives, and stakeholder syncs. It recommends providing preparation support, staying available, and debriefing afterward to develop independent leaders and reduce managerial burnout. ### Source excerpt Let's just say it straight. If you're the one leading every single meeting, you're either inexperienced, insecure, or haven't been shown how to be a real manager yet. If that stings a little, that's okay. Maybe it should. There are a few exceptions. Sure, incidents. Maybe a gnarly stakeholder review or a performance conversation. But even in those high-stakes moments, there's usually room to coach. Let someone else run the show. As long as someone is clear on decision-making, you don't need to be the one running the room every time. That's not what good leadership looks like. Good leadership is about building people who can do the job without you. Why You Keep Grabbing the Mic Most managers hog the meetings for one of a few reasons: It's faster if I do it They're not ready yet What if they mess it up? I'll be blamed if it goes wrong I'm the one accountable If that sounds like you, you're not alone. I've heard them all before. I've said a few of them too, early in my career. But you need to realise what those excuses are actually saying to your team: You're not ready. I don't trust you. I don't care enough to help you grow. Not great. What It Looks Like to Coach Instead This isn't about disappearing. It's not about sitting out. It's not delegating and walking away. It's about showing up differently. Coaching in real time. Supporting from the side, not from the front. Let them lead the standup. Let them chair the retro. Let them run the stakeholder sync. Then debrief. What worked? What would you do differently next time? What was hard? That's coaching. That's how they get better. That's how you build a team that can do hard things without you steering every move. The Real Reason You're Still Leading Everything Sometimes, it's not about fear. It's about ego. If everything runs through you If you always need to be in the room If you secretly like being the person with the answers That's ego. It's not sustainable. It's not leadership. It's how you end up with a team that ## New Grad to Staff at Meta in 3 years DevFeed: [New Grad to Staff at Meta in 3 years]() Original publisher: [Read original article]() Author: Evan King Published: 2024-12-12T05:46:36Z Content type: opinion Language: en Sources: [Evan King]() Topics: [Development](), [Meta]() Tags: [career](), [dev](), [manager](), [meta]() ### AI overview Evan King reflects on progressing from junior engineer to Staff at Meta in three years. He attributes the unusually rapid progression to favorable circumstances, including organizational growth and managerial support, as well as principles such as working efficiently, operating beyond one's level, sharing ideas without needing certainty, focusing on problems rather than technologies, and building goodwill. ### Source excerpt By Evan King, co-founder of hellointerview.com Junior to Staff at Meta in 3 years. That sentence raises eyebrows. I've dodged telling this story for years. Maybe it's the ex-athlete in me cringing at self-promotion, or maybe I'm just uncomfortable with attention I'm not sure I deserve. But after countless requests to share it, I figured it's worth putting out there -- even if it makes me squirm. Let's start with the reality check: I hit the timing jackpot. Right org, explosive growth phase, and a manager who saw something in me before I saw it myself. If you're looking for a pure meritocratic story, this isn't it. Nobody lands promotions this fast without the stars aligning. Still, there were patterns and principles that emerged -- insights that might be useful to others on their own paths. Looking back, six key principles had the largest effect on my career. First principle: Speed is your multiplier. Everyone talks about thinking bigger or making an impact, but none of that matters if you can't nail your core work faster than others. When you can complete your normal workload with 70% of your time, that extra 30% becomes your secret weapon. That's where the real growth happens. The second principle relies on the first: Keep your head up and your aperture wide. Use that extra bandwidth to operate like someone a level above you. As a junior dev, I studied what my teammates were doing, connecting dots they might have missed. At senior, I expanded that lens to sister teams. By Staff, I was thinking across entire organizations. Here's the third thing, and it's a liberating truth: No one has all the answers. Not your boss, not the VPs, not even the CEO. This isn't meant to dismiss their expertise -- I've learned invaluable lessons from every leader I've worked with. But realizing this freed me to put my ideas out there without the paralyzing weight of needing to be right. The fourth principle grounds everything else: focus on problems, not technologies. You don't need to be ## Spin Verman - The Version Manager Plugin DevFeed: [Spin Verman - The Version Manager Plugin]() Original publisher: [Read original article]() Author: Andrew Steurer Published: 2024-10-01T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Command-line interface](), [version]() Tags: [cli](), [easily](), [manager](), [plugin](), [using](), [version]() ### AI overview A tutorial for using the Spin CLI Version Manager plugin to switch between Spin versions. ### Source excerpt Get started using the Spin CLI Version Manager plugin to easily switch between versions of Spin ## Engineers Should Take Responsibility for Bugs in AI-Generated Code DevFeed: [Engineers Should Take Responsibility for Bugs in AI-Generated Code]() Original publisher: [Read original article]() Published: 2024-09-24T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Artificial Intelligence](), [bug](), [Git](), [coding](), [trust]() Tags: [ai](), [autonomous](), [bug](), [code](), [coding](), [commit](), [git](), [junior](), [management](), [manager](), [solve](), [support](), [team](), [testing](), [trust](), [value]() ### AI overview This opinion article argues that engineers remain accountable for bugs in code generated with AI. It says attributing defects to AI reduces an engineer's perceived value, and that responsible use requires testing, judgment, and ownership. ### Source excerpt AI didn't write that bug. If you're name is on the commit in Git, you wrote the bug. ## Self-organizing companies don't need managers but coaches DevFeed: [Self-organizing companies don't need managers but coaches]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-01-20T05:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Self-organizing Team](), [Agile]() Tags: [agile](), [coaching](), [developer-experience-developer-productivity-engineering-leadership-high-purpose-environments-lea](), [manager](), [motivation](), [organizational-structure](), [organizations](), [self-organizing](), [teams]() ### AI overview The article argues that self-organizing companies need coaching roles beyond traditional management and classic agile coaching. It presents self-organization as a way to improve organizational adaptability and create more impact, enjoyment, and human connection at work. ### Source excerpt Self-organizing companies don't need managers but coaches If you are a manager or consider managing teams and organizations a significant part of your profession, the title will likely cause a feeling of rejection or a strong disagreement. I invite you to read on anyway. ## How LLMs Could Assist Managers With Everyday Problems DevFeed: [How LLMs Could Assist Managers With Everyday Problems]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2023-08-18T08:37:09Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Artificial Intelligence](), [Large Language Model](), [ChatGPT](), [Azure]() Tags: [ai](), [ai-assistant](), [chatgpt](), [llms](), [manager](), [privacy]() ### AI overview The article argues that LLMs can help managers handle simple, everyday problems by capturing intent, synthesizing relevant literature, and suggesting checklists or next steps. It says privacy, security, missing context, and the need for human judgment limit their use for diagnosis and strategic decisions. ### Source excerpt Much like AI came for artists first, it might affect the Manager role quicker than we think. ## Can AI Replace Engineering Managers? DevFeed: [Can AI Replace Engineering Managers?]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2023-04-28T07:05:06Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Artificial Intelligence](), [Software Engineering](), [Large Language Model](), [Language models]() Tags: [ai](), [automation](), [chatgpt](), [engineering-management](), [large-language-model](), [llms](), [manager](), [software](), [software-engineering]() ### AI overview This opinion article considers whether AI could replace engineering managers. It argues that AI systems can handle many tasks once reserved for humans by retrieving, combining, and summarizing information, while noting that AI can also produce credible-sounding errors. ### Source excerpt AI is changing software engineering. But can it replace a manager? ## Three Mindset Shifts in the Transition from Engineer to Engineering Manager DevFeed: [Three Mindset Shifts in the Transition from Engineer to Engineering Manager]() Original publisher: [Read original article]() Author: Tom Bartel Published: 2023-01-03T00:00:00Z Content type: opinion Language: en Sources: [Trivago]() Topics: [Job](), [meetings](), [Code]() Tags: [engineering-culture](), [engineering-management](), [engineering-manager](), [leadership](), [management](), [manager](), [meetings](), [productivity]() ### AI overview This article discusses the transition from engineering to engineering management, emphasizing that it is a different job rather than simply a promotion. It focuses on redefining productivity when managerial work brings more meetings, interruptions, and less hands-on coding. ### Source excerpt You have always been an engineer, solving problems and writing code. Now, there is an opportunity to become an engineering manager. You are interested.However, questions arise. ## Advice on Managing Imposter Syndrome and Choosing a Software Engineering Team DevFeed: [Advice on Managing Imposter Syndrome and Choosing a Software Engineering Team]() Original publisher: [Read original article]() Author: Rahul Pandey Published: 2022-10-07T15:05:55Z Content type: article Language: en Sources: [Alex Chiou]() Topics: [Software](), [coding]() Tags: [career](), [discussion](), [event](), [manager](), [remote-work](), [risk](), [slack](), [software-engineer](), [startups](), [team](), [video]() ### AI overview This newsletter covers group office hours for Taro Premium members, four ways to address imposter syndrome, and advice on choosing a company and team as a software engineer. It emphasizes priorities, team supportiveness, risk tolerance, and the differences between Big Tech and startups. ### Source excerpt Hey everyone 👋🏽 Today we'll cover: ## How Managerial Authority Can Undermine Developer Empowerment and Productivity DevFeed: [How Managerial Authority Can Undermine Developer Empowerment and Productivity]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2022-02-04T08:00:42Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Software](), [Job]() Tags: [article](), [developers](), [leadership](), [manager](), [managerial-roles](), [motivation](), [performance](), [power](), [problems](), [product](), [productivity](), [pull-request](), [team]() ### AI overview This opinion article argues that managers who rely too heavily on authority, including micromanaging approvals and imposing their own ideas, can disempower developers and reduce engagement, performance, and product delivery. It advocates servant leadership through clarity, enablement, and team empowerment. ### Source excerpt More power, more problems ## The Nuts and Bolts with Tom Drapeau DevFeed: [The Nuts and Bolts with Tom Drapeau]() Original publisher: [Read original article]() Author: Squarespace Engineering Published: 2021-10-15T16:08:12Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [engineering-culture](), [Job]() Tags: [culture](), [manager](), [q-a](), [team-lead](), [times]() ### AI overview A Q&A with Tom Drapeau about moving from engineering into management, choosing an Engineering Director role at Squarespace, and defining and building engineering culture. ### Source excerpt "The Nuts and Bolts" is a reoccurring Q&A with Squarespace engineers. Questions are compiled by their peers to guarantee we get right to the good stuff. ## Managers should take responsibility for compensation conversations and decisions DevFeed: [Managers should take responsibility for compensation conversations and decisions]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2021-09-21T18:44:35Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Job](), [Finance](), [trust]() Tags: [employees](), [employment](), [job](), [manager](), [money](), [trust]() ### AI overview This management commentary argues that managers should understand their reports' compensation, participate in setting pay policies, communicate employment and compensation decisions, handle salary discussions thoughtfully, and advocate for their teams rather than delegating these responsibilities entirely to HR and Finance. ### Source excerpt Everything you wanted to know about money but were afraid to ask ## Kotlin Multiplatform Mobile Standardizes Cox Automotive Mobile App Analytics - Touchlab DevFeed: [Kotlin Multiplatform Mobile Standardizes Cox Automotive Mobile App Analytics - Touchlab]() Original publisher: [Read original article]() Published: 2021-09-13T02:20:41Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Mobile](), [Kotlin](), [ci]() Tags: [analytics](), [ci](), [ci-cd](), [engineering](), [engineering-manager](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [manager](), [mobile](), [team-lead](), [touchlabshare]() ### AI overview A Touchlab discussion with Cox Automotive engineering leaders Robert Szabo and Turker Nessa Kucuk about using Kotlin Multiplatform Mobile to standardize analytics in the Provision mobile app, including their production experience and CI/CD priorities. ### Source excerpt We're joined by Robert Szabo and Turker Nessa Kucuk from Cox Automotive to discuss Kotlin Multiplatform Mobile for analytics. ## 7 ways to convince your engineering manager to pilot Kotlin Multiplatform - Justin Mancinelli DevFeed: [7 ways to convince your engineering manager to pilot Kotlin Multiplatform - Justin Mancinelli]() Original publisher: [Read original article]() Published: 2019-11-05T23:45:18Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [business logic](), [Mobile](), [Android](), [iOS]() Tags: [android](), [code-sharing](), [engineering-manager](), [how-to](), [ios](), [kmp](), [kotlin](), [kotlin-multiplatform](), [manager](), [multiplatform]() ### AI overview A tutorial offering seven talking points for developers who want to propose a Kotlin Multiplatform pilot to their engineering manager. It argues that shared business logic across iOS and Android can reduce duplicated work and that a pilot can be introduced incrementally. ### Source excerpt Engineers are excited about KMP but don't know how to sell a Kotlin Multiplatform pilot internally. Justin providies 7 tips to get the conversation started. ## How Product Managers and Engineering Managers Can Stay Aligned DevFeed: [How Product Managers and Engineering Managers Can Stay Aligned]() Original publisher: [Read original article]() Author: Map Published: 2019-06-30T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Product Management](), [meetings]() Tags: [engineering](), [engineering-manager](), [manager](), [philosophies](), [product-management]() ### AI overview The article argues that product managers and engineering managers should present a unified position to their teams. It recommends explicit communication, regular one-on-ones, advance review of team communications, and resolving disagreements privately rather than in team meetings. ### Source excerpt I've worked as a PM at a number of size companies for a few years now. At a startup and then as a part of a larger company once startups were acquired. I've been the first PM for a team as well as first for a company. I've written at times about product management, and today I'd like to drill into one aspect that doesn't seem to get talked about enough and that is the pairing of product manager and engineering manager. Mom vs. Dad As parents my partner and I have learned very quickly that we need to have a consistent voice and unified view of things. I care that our son watches less power rangers otherwise he's going to use his megazord powers on our TV and we'll be watching a lot more of nothing. My partner cares that when we're visiting family in the south they drink enough water so they don't get dehydrated. Meanwhile my kids are experts at leveraging us to get what they want. My daughter came to me last night asking if she could play on her iPad some. Not knowing if she had or if she'd already given an answer my safest question was have you asked your mom? In the absense of knowing my default isn't a yes or no, it's a "let me learn more." and then potentially discuss it. EM vs. PM As a PM I want us to build a rich and powerful product, but there is a strong balance to doing too little vs. too much. It isn't always a question of doing more, we need to make sure the product is well built. In order to do that we need to say no at times. Saying no, as well as yes, needs to come from a unified front, both engineering and product. If one side is agreeing without being aligned with the other half you're going to wind up with a confused and frustrated team. There are a number of ways engineering managers and product managers can stay aligned. The first starts with being explicit with each other, so if you're struggling with one side communicating things the other don't agree with... sit down and have a conversation about it. From an ongoing perspective you can get to a be [Next page]()