# Team Lead Published articles for Team Lead. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Grow Past Senior Engineer DevFeed: [How to Grow Past Senior Engineer]() Original publisher: [Read original article]() Author: Gregor Ojstersek Published: 2026-09-08T15:30:36Z Content type: opinion Language: en Sources: [Engineering Leadership]() Topics: [coding](), [meetings](), [implementation]() Tags: [career](), [productivity](), [software-engineer](), [team-lead]() ### AI overview An experienced software engineer shares four practical ways to move beyond the senior engineer level: discuss career goals with a manager, track accomplishments, become a go-to person in a project, technology, or domain, and propose and own an impactful codebase improvement. ### Source excerpt My 4 recommended starting moves that'll help you gain trust and credibility to grow to the next step! ## Why Engineering Player-Coach Roles Are Becoming More Demanding DevFeed: [Why Engineering Player-Coach Roles Are Becoming More Demanding]() Original publisher: [Read original article]() Author: Gregor Ojstersek Published: 2026-08-31T13:41:33Z Content type: opinion Language: en Sources: [Engineering Leadership]() Topics: [Tech Lead](), [Artificial Intelligence]() Tags: [engineering-manager](), [team-lead](), [tech-lead]() ### AI overview An opinion article argues that engineering leaders are increasingly expected to combine leadership responsibilities with hands-on technical work. It defines player-coaches as people who set direction, support teams, and also perform senior-engineering work such as coding, specification work, incident resolution, and prototyping. ### Source excerpt Engineering Manager, Team Lead, Tech Lead, and Architect roles are becoming harder than ever, but the problematic part is that many people don't understand that and don't give the deserved credit. ## EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech DevFeed: [EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-05-13T14:53:24Z Content type: opinion Language: en Sources: [Anna J McDougall]() Topics: [Code quality]() Tags: [code-quality](), [compliance](), [engineering-management](), [engineering-manager](), [engineering-mangement](), [identifier](), [improvements](), [iso](), [management](), [product-engineering](), [product-management](), [quality](), [relationships](), [team-lead](), [teams](), [tech-leadership]() ### AI overview An opinion article presents practices for building effective engineering manager and product manager relationships. It emphasizes shared ownership across business, team, and product goals, with quality improvements--including compliance work--as part of an engineering manager's contribution. ### Source excerpt EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech TeamsHeader image: purple background with the text "EM/PM Relationships Aren't About Luck. 5 Tips for Product/Tech Teams :)" and a photo of Anna and Tanja together.Introduction As my probation period at HelloBetter was coming to an end, my team's Senior Product Manager Tanja Lembcke remarked, "It's great working with an EM who cares so much about product." I could easily have said the same back to her, because it's just as valuable working with a PM who cares deeply about technology, something at which she truly excels. Together, we've become a strong team. Much of that relationship has developed naturally, but I've also noticed a few intentional practices that have helped us along the way. I want to share them here for all the product managers, engineering managers, and whoever else happens to like reading my sporadic blog posts. In the end, Tanja and I didn't just "luck out" working together. There are some tried-and-true strategies we both employ to make the most out of our work and get the results we need. If you prefer LinkedIn, you can view the short-form version of this post as a summary and carousel here. Tip 1: Purposefully be the intersection of business, team, and product As a Team Lead or Engineering Manager, it's important to operate at the intersection of business goals, the engineering team, and product. This means not only using the product but also critiquing it, asking thoughtful questions, and continually returning to the core "Why." It is all too easy to sit back and just wait for features to drop in your lap, estimate them, deliver them, and then dust off your hands with a "job well done" attitude that allows you to add a nice dot-point to your CV about value creation. What is much harder, is to actually focus on quality: that hard-to-measure, hard-to-prove value that is constantly competing with your time. For EMs, we tend to see the word "quality" and jump to the concept of code qu ## 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. ## 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. ## Lessons learned being a lead developer DevFeed: [Lessons learned being a lead developer]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2019-08-06T00:00:00Z Content type: article Language: en Sources: [Jeroen Mols]() Topics: [Development](), [LineageOS](), [App](), [Refactoring](), [Tech Debt](), [Kotlin](), [RxJava]() Tags: [android](), [app](), [architecture](), [blogs](), [developer](), [development](), [kotlin](), [lessonslearned](), [pull-requests](), [refactoring](), [rxjava](), [software-engineering](), [team-lead](), [tech-debt]() ### AI overview A lead Android developer at Philips Hue reflects on leading a component team while remaining a hands-on developer. The article discusses team responsibilities, a poorly structured and highly coupled codebase, Android technology changes, slow and unstable builds, and difficulties integrating large pull requests. ### Source excerpt Three years ago, we decided ramp up internal app development at Philips Hue. After interviewing candidates (78!) for six months, I became the lead Android developer of the freshly hired Android team.