# Interviewing Published articles for Interviewing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Hot Chips 2026: Interviewing IBM's Christian Zoellin & Christian Jacobi DevFeed: [Hot Chips 2026: Interviewing IBM's Christian Zoellin & Christian Jacobi]() Original publisher: [Read original article]() Author: George Cozma Published: 2026-08-30T17:31:05Z Content type: article Language: en Sources: [Chips and Cheese]() Topics: [Arm](), [ibm](), [systems]() Tags: [2026](), [architecture](), [architectures](), [arm](), [core](), [decoding](), [ibm](), [interviewing](), [systems]() ### AI overview An interview with IBM engineers at Hot Chips 2026 discusses the company's next-generation z/Architecture processor, which supports both the z/Architecture and Arm instruction sets. The conversation covers its shared decode pipeline, separate instruction decoders, and handling of differing endianness in the load-store unit. ### Source excerpt Hello you fine Internet folks, ## I Failed to Implement the Diameter of a Binary Tree in a Coding Interview DevFeed: [I Failed to Implement the Diameter of a Binary Tree in a Coding Interview]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2025-06-21T01:00:00Z Content type: opinion Language: en Sources: [Daniel Doubrovkine]() Topics: [LeetCode](), [coding](), [Code]() Tags: [advice](), [ai](), [coding](), [interview](), [interviewing](), [junior](), [principal-engineer]() ### AI overview A Principal Engineer recounts freezing during a basic coding interview despite decades of programming experience. The article offers advice for recovering from interview failure, including maintaining perspective, practicing, and recognizing the role of luck in LeetCode-style interviews. ### Source excerpt Six months ago I failed a basic coding interview at a FAANG. Yes, I was a Principal Engineer, and yes, I was paid absurd amounts of money, yet I couldn't implement a diameter of a binary tree as a "warm up" exercise, 10 lines of code. The interviewer was very nice about it, and was equally surprised. You see, I've been coding for 35 years, and I am not "rusty" at it, which is a typical excuse for senior ICs bombing LeetCode interviews. At that time I was writing code every day. I simply froze, and couldn't do it. All I could think of was "why the hell am I here doing this to myself?". I couldn't turn my brain around, apologized, cut the interview short, and, while I did ace several coding interviews at other companies for IC roles, went back to management for which I am, obviously, more qualified. Did you just bomb a coding interview? Here's some practical advice of how to deal with it. First, keep your head high and do not let this negative experience get to you. It feels awful, but unless you are blogging about your failure to implement the diameter of a binary tree, nobody other than you and the interviewer will ever know. Most likely the interviewer was also a half asleep drone deep inside the borg, administering a coding puzzle every day to the next sucker, so they will forget about you the next day. I see a lot of junior Engineers affected by failing at these. If you are recently out of college, it's helpful to think of these interviews as a school test, such as an SAT. I never had to take SATs (my children did), but most European schools have oral exams where you get a ticket from a jar with the problem statement. I had slept through too many alarms to attend an 8 AM physics class around 1996 because of a grueling late night partying schedule, and only really knew maybe half the material. Luckily 2/3 questions in my ticket overlapped with those classes I did attend, and so I did well. If you don't like school and prefer video games, think of these interviews ## Rethinking Technical Interviews for Virtual Hiring and AI-Assisted Candidates DevFeed: [Rethinking Technical Interviews for Virtual Hiring and AI-Assisted Candidates]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-04-17T19:08:54Z Content type: opinion Language: en Sources: [Anna J McDougall]() Topics: [Tech Careers](), [Artificial Intelligence](), [LeetCode](), [Algorithms]() Tags: [ai](), [algorithms](), [artificial-intelligence](), [careers](), [chatgpt](), [engineering-management](), [interview](), [interviewing](), [software-development](), [technical-interview](), [technology]() ### AI overview This opinion article argues that virtual hiring and AI tools have exposed weaknesses in traditional technical interviews. It discusses limitations and equity concerns associated with algorithm assessments and take-home projects, and introduces the McDougall Method at HelloBetter as a proposed response. ### Source excerpt Building the McDougall Method at HelloBetter: A Fairer, More Modern Approach to Technical Interviews As someone obsessed with tech careers, business growth, and engineering management, I am constantly coming up against the boogey-man of technical interviews. In many ways, tech companies are stuck in the thinking of 20-30 years ago: white boards, algorithms, logic puzzles, and tasks that rotated around an in-person interview space. We're in a new era, where 99% of engineering interviews are done virtually and the candidate's workspace is uncontrollable by the interviewing team. We need to adapt to this, not by simply porting previous methods across to an online platform, but by fundamentally rethinking the skills we expect 21st century software engineers to have. Naturally, opinions about what is wrong with technical interviews are prevalent both from employers and (potential) employees. For example, leetcode-style assessments have long been derided as being a bad test of abilities. "Instead," opponents argue, "you should use take-home tests or projects that the candidate can explain back to you". Ah, but you see, not everyone can afford to let their evenings and weekends disappear into these take-home tests or side projects. Due to this inconveniently linear construct called "time", more experienced engineers start having or caring for families, adopting pets, or (lord forbid) doing sports and hobbies. It's also no big secret that the majority of housework and care duties still tend to be shouldered by women. To put your best foot forward as a candidate, you will create the best possible solution, no matter how many hiring managers tell you to "only spend 2-3 hours on a solution". Therefore, take-home or "own project" technical interviews tend to put older candidates and women candidates at a disadvantage. One other problem popping up nowadays is the prevalence of AI tools for engineers to pass technical interviews, ranging from manually entering prompts into ChatGP ## Learning Path: Ace Your Python Coding Interview DevFeed: [Learning Path: Ace Your Python Coding Interview]() Original publisher: [Read original article]() Author: Real Python Published: 2024-11-14T12:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [Python](), [coding](), [data-engineering](), [CSV](), [Databases](), [SQL]() Tags: [coding](), [data-engineering](), [databases](), [interviewing](), [learning](), [python](), [resources](), [sql](), [tutorial]() ### AI overview A learning path for Python coding interviews that combines interview preparation, coding challenges, CSV parsing practice, data engineering questions, and curated Python learning resources. It includes guidance on assessing skills, creating a study plan, practicing common problems, and using Python's built-in functions and modules effectively. ### Source excerpt Prepare for Python coding interviews with practice problems, tips for standing out, and resources from top PyCon talks and Python books. ## Finding a New Software Developer Job DevFeed: [Finding a New Software Developer Job]() Original publisher: [Read original article]() Author: Henrik Warne Published: 2024-02-11T16:57:27Z Content type: opinion Language: en Sources: [Henrik Warne]() Topics: [Job](), [Software]() Tags: [career](), [developer](), [interview](), [interviewing](), [job](), [job-hunt](), [job-search](), [jobs](), [linkedin](), [new-job](), [programming](), [software-developer](), [work]() ### AI overview A software developer describes finding a new job after being laid off, including the challenges of the search and the sources and preparation strategies he used. ### Source excerpt For the first time ever, I was laid off, and had to find a new software developer job. I managed to find a new one, but it took longer than I thought, and it was a lot of work. I ... Continue reading -> ## Shishir Mehrotra's 10 rules for leading great team meetings DevFeed: [Shishir Mehrotra's 10 rules for leading great team meetings]() Original publisher: [Read original article]() Author: Shishir Mehrotra Published: 2023-10-12T00:00:00Z Content type: opinion Language: en Sources: [Figma Blog]() Topics: [Development](), [hubspot]() Tags: [culture](), [development](), [interviewing](), [product-development](), [team-building](), [writing]() ### AI overview Coda co-founder and CEO Shishir Mehrotra shares principles for leading effective team meetings. Drawing on workplace rituals and interviews with more than 1,000 people, he argues that named, familiar, and templated rituals can improve company culture, collaboration, and hybrid-work meetings. ### Source excerpt Coda Co-founder and CEO Shishir Mehrotra explains why the best product teams often put as much care into how the work gets done as what product gets shipped. ## Preparing for Android Job Interviews: A Guide to the Typical Interview Process DevFeed: [Preparing for Android Job Interviews: A Guide to the Typical Interview Process]() Original publisher: [Read original article]() Author: blundell Published: 2023-05-16T21:19:15Z Content type: tutorial Language: en Sources: [Blundell]() Topics: [Android](), [App](), [Code]() Tags: [android](), [androiddev](), [blog](), [hiring](), [intermediate](), [interviewing](), [interviews](), [personal-experience](), [process](), [reference](), [reference-android-androiddev-interviewing-interviews]() ### AI overview This personal-experience guide describes common stages of an Android job interview, including an introductory conversation and take-home exercise. It offers preparation advice such as reviewing the job candidate's CV, researching the company, following the exercise rubric, and documenting code decisions. ### Source excerpt This post aims to demystify some of the steps in a typical Android interview process. We'll discuss steps, strategies, targets and solutions. Getting you better prepared to get your next Android role. This blog is from personal experience, caveat up front that your experience could be completely different, but I've been through A LOT of [...] The post Proven Prepping for Easy Android Interviews in 2023 first appeared on Blundell. ## Shopify's Technical Interview Process: What to Expect and How to Prepare DevFeed: [Shopify's Technical Interview Process: What to Expect and How to Prepare]() Original publisher: [Read original article]() Author: Ashley Sawatsky Published: 2022-07-07T14:00:00Z Content type: tutorial Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Google Calendar]() Tags: [communication](), [guide](), [how-to](), [interviewing](), [shopify](), [skills](), [support](), [technical]() ### AI overview A practical guide to Shopify's technical interview process, explaining what candidates can expect at each stage and offering preparation advice. It focuses on individual contributor roles and highlights the conversational Life Story interview, including the experiences and traits candidates may discuss. ### Source excerpt The interview process can be one of the most daunting aspects of finding a new gig--but it doesn't have to be. This guide pulls back the curtain on what to expect during the interview process for technical roles at Shopify and sets you up for success with tips for each stage. ## Working at Clever: a perspective from a former intern turned full time engineer DevFeed: [Working at Clever: a perspective from a former intern turned full time engineer]() Original publisher: [Read original article]() Author: Vijay Bharadwaj Published: 2022-04-25T17:37:36Z Content type: opinion Language: en Sources: [Clever]() Topics: [engineering-culture](), [Architecture & Design](), [Learning]() Tags: [company](), [covid](), [culture](), [engineering](), [intern](), [internship](), [interviewing](), [onboarding](), [remote]() ### AI overview A former Clever intern describes choosing the company for its culture and engineering practices, experiences during the internship and interview process, and the transition to a full-time engineering role. ### Source excerpt During my final search for an internship, I had an idea of where I wanted to work: a place with a friendly culture and strong engineering practices - something in between a startup and a big company. To my luck, I interned at Clever - an organization that surpassed those expectations in the span of [...] The post Working at Clever: a perspective from a former intern turned full time engineer appeared first on Clever Engineering Blog. ## How to Prepare for Data Structures and Algorithms Job Interviews DevFeed: [How to Prepare for Data Structures and Algorithms Job Interviews]() Original publisher: [Read original article]() Published: 2021-11-24T11:00:29Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Programming](), [Algorithms, Complexity](), [Data structures](), [Computer science](), [LeetCode](), [Mobile]() Tags: [advice](), [algorithms](), [android](), [blog](), [career](), [compose](), [data-structures](), [development](), [engineering](), [finance](), [functional](), [growth](), [interviewing](), [java](), [jetpack](), [jobs](), [kotlin](), [mobile](), [money](), [notes](), [opinions](), [remote](), [retention](), [shortage](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This article shares practical advice for preparing for software engineering interviews, especially Data Structures & Algorithms interviews. It recommends actively studying computer science fundamentals, algorithms, data structures and related strategies instead of solving random LeetCode questions without a structured study method. ### Source excerpt In case you weren't already aware, the market right now for software engineers is super hot - it's crazy out there. A combination of the entire world moving online, people burning out of their jobs and a chronic shortage of experienced software engineers means there's never been a better time to see what's on offer. If you want fully remote, better pay and a title change, there are many companies out there willing to give it to you. ## What is it like to interview with Apollo? (part 1 of 2) DevFeed: [What is it like to interview with Apollo? (part 1 of 2)]() Original publisher: [Read original article]() Author: Chris Shaw Published: 2021-08-13T14:19:33Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [consistency]() Tags: [alignment](), [fairness](), [hiring](), [interview](), [interviewing](), [interviews](), [job](), [life-at-apollo](), [onboarding](), [process](), [recruiting](), [skills]() ### AI overview Apollo's first article about its interview process explains how the company prepares interviewers and candidates, defines roles through missions, outcomes, and competencies, and designs interviews for consistency and fairness. ### Source excerpt We've all been there. You're interviewing for a company that has a job you're very interested in. But you have no idea what to expect in the interview process. You're wondering; what will this process actually be like? How much time will it take? Should I prepare? How much should I prepare? Will I get a chance to ask my questions so I can learn more about the company? ## Virtual Interview Reflection DevFeed: [Virtual Interview Reflection]() Original publisher: [Read original article]() Published: 2021-02-12T18:23:05Z Content type: opinion Language: en Sources: [Emily Kager]() Topics: [Job](), [HackerRank](), [coding]() Tags: [hiring](), [interviewing](), [virtual](), [writing]() ### AI overview A personal reflection on going through a real tech interview process for the first time, including imposter syndrome, remote interviewing, referrals, multiple offers, interview fatigue, and the value of personal support. ### Source excerpt I have a confession. ## From Nine Hundred to One: How We Hired Robin Malfait DevFeed: [From Nine Hundred to One: How We Hired Robin Malfait]() Original publisher: [Read original article]() Published: 2020-08-10T13:30:00Z Content type: article Language: en Sources: [Tailwind CSS Blog]() Topics: [Tailwind CSS](), [React](), [Vue.js](), [Open Source](), [Server]() Tags: [applications](), [community](), [components](), [customer](), [developer](), [discord](), [examples](), [interviewing](), [open-source](), [projects](), [react](), [support](), [tailwind](), [vue]() ### AI overview Tailwind Labs describes how it narrowed nearly 900 applications to hire Robin Malfait as a full-stack developer. The article explains the job-posting and selection approach, and notes Robin's React experience, community contributions, and work on open-source renderless UI libraries intended to support React and Vue in Tailwind UI. ### Source excerpt Back in May we published our first job posting for a full-stack developer to join our team. This is the story of how we worked through almost 900 applications, and eventually hired Robin Malfait, a talented developer from Belgium who is starting with us today. ## The Jane Street Interview Process -- 2020 Edition DevFeed: [The Jane Street Interview Process -- 2020 Edition]() Original publisher: [Read original article]() Author: Sam DeFabbia-Kane Published: 2020-07-24T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [Software Engineering](), [coding](), [Algorithms](), [Simulation]() Tags: [algorithms](), [coding](), [covid-19](), [interview](), [interviewing](), [technical-interview]() ### AI overview Jane Street describes its 2020 software engineering interview process for interns, new graduates, and experienced candidates. The process generally includes a technical phone interview and an onsite interview with two to four technical rounds, conducted by video conference during COVID-19. Technical interviews focus on coding and algorithms problems, communication, and collaborative problem-solving. ### Source excerpt We're busy preparing for our software engineering fall hiring season. Over the years we've done our best to make our interview process more transparent to candidates. While many candidates show up knowing something about what our interviews look like, much of the information floating around on the internet is outdated or wrong. These past few months have also changed a lot about the process as we've adapted to working from home and other effects of COVID-19. ## Changing the Interview Process during Remote Working DevFeed: [Changing the Interview Process during Remote Working]() Original publisher: [Read original article]() Published: 2020-06-30T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Back end](), [Slack](), [Availability]() Tags: [availability](), [backend](), [connectivity](), [covid](), [engineering](), [interviewing](), [remote](), [remote-work](), [slack]() ### AI overview SoundCloud describes how it adapted its backend engineering interview and recruiting process for fully remote work during COVID-19. Interviews were moved online and distributed across multiple days, with video calls, advance connectivity checks, and Slack coordination between interviewers and recruiters. ### Source excerpt Please also see Part 1: Rethinking the Backend Engineering Interview Take-Home Challenge and Part 2: The Recruiting Perspective and Results... ## Technical Interview Reform, Part 2: The Recruiting Perspective and Results DevFeed: [Technical Interview Reform, Part 2: The Recruiting Perspective and Results]() Original publisher: [Read original article]() Published: 2020-06-26T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Back end](), [Code Challenge](), [Code]() Tags: [backend](), [code-challenge](), [engineering](), [interviewing](), [recruiting](), [review](), [technical]() ### AI overview SoundCloud describes its backend engineering interview reform, focusing on a take-home code challenge that required substantial candidate and reviewer time. The article explains the recruitment bottleneck, high dropout rates, and process changes such as collaborative review squads and iterative improvements based on candidate feedback. ### Source excerpt Please also see Part 1: Rethinking the Backend Engineering Interview Take-Home Challenge Among the engineering groups at SoundCloud, backend... ## Technical Interview Reform, Part 1: Rethinking the Backend Engineering Interview Take-Home Challenge DevFeed: [Technical Interview Reform, Part 1: Rethinking the Backend Engineering Interview Take-Home Challenge]() Original publisher: [Read original article]() Published: 2020-06-25T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Back end](), [Code](), [coding]() Tags: [backend](), [code-challenge](), [engineering](), [hiring](), [interviewing](), [process](), [technical](), [technical-interview]() ### AI overview SoundCloud explains why it comprehensively rethought its backend engineering take-home challenge. The previous coding exercise often required many hours over several weeks, creating a burden for candidates and causing a significant dropoff in the hiring pipeline. The revised approach is framed as a code tryout intended to assess an essential engineering skill while reducing time costs and limiting bias through an anonymous audition. ### Source excerpt Most SoundCloud backend engineers have good feelings about the old backend engineering take-home challenge. It's commonly been characterized... ## Ask a Developer: Your Questions Answered DevFeed: [Ask a Developer: Your Questions Answered]() Original publisher: [Read original article]() Author: Ankia Wolf Published: 2020-03-20T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Programming](), [Job](), [Frameworks](), [Go Language](), [JavaScript](), [PHP](), [Angular](), [React](), [Python](), [Vue.js](), [R](), [Open Source]() Tags: [angular](), [backend](), [developer](), [engineering-culture](), [frameworks](), [full-stack](), [github](), [go](), [hackathons](), [interviewing](), [javascript](), [kotlin](), [open-source](), [php](), [python](), [q-a](), [react](), [requirements](), [tech](), [tech-stack](), [vue]() ### AI overview A trivago developer Q&A covers opportunities for React developers, interview expectations, ways for newcomers to contribute, full-stack requirements, and the company's technology stack. It identifies Kotlin, Go, and PHP for backend work; JavaScript for frontend; Python and R for data science; and Angular, React, Vue, and Melody as JavaScript frameworks. ### Source excerpt We recently hosted a Q&A on our trivago tech Twitter and Life at trivago Instagram page,... ## Six Tips for Interviewing Software Engineers When You Aren't Technical DevFeed: [Six Tips for Interviewing Software Engineers When You Aren't Technical]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-10T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Job](), [communications](), [Development](), [context](), [Code]() Tags: [communications](), [culture](), [development](), [hr](), [interview](), [interviewing](), [job](), [remote](), [startup](), [technical](), [tips]() ### AI overview An article offers six tips for nontechnical interviewers evaluating software engineers, covering relevant questions, communication, attitude, values alignment, work practices, and compensation or company details. It also briefly discusses the author's opposition to coding tests, especially for senior engineering roles. ### Source excerpt Interviewing engineers when you aren't one is a regular human resources task that tends to give non technical folk fits and for good reasons. 1. Focus on What You Can Interview them About To the non engineer, our job is all about coding but that's actually only a part of what an engineer does. Engineers exist in the same ecosystem as any employee and there are all kinds of questions about work practices that need to be asked. For example if remote work is a part of your work environment then dig down into how that person might function in a remote context. 2. Communications Ability Is Always Key Engineers do not work in a vacuum and the ability to communicate is a key ability that improves the quality of their work. Ask questions and see how the engineer communicates. 3. Look for Attitude A lot of engineers love to drown non technical people in what amounts to techno babel - it is a way for us (yes I am an engineer myself) to feel superior. Look for hints of that attitude during the interview and if you find it before they are an employee then you should expect it to be even worse once they are an employee. 4. Look for Values Alignment / Culture Fit When I'm an interviewer, I care most about whether or not the candidate can do the technical work because, honestly, I can work with anyone - in the end all I care about (mostly) is whether or not the code works. Now if you are non technical then you don't care about that but you likely care a lot about value alignment and culture fit so dig in there. 5. Look at Work Practices Even if you aren't technical, you likely have some idea around work practices in development from either past experience or media. It is ok to ask a general question like "I have a bug in what you are working on - how do you handle it?". And then what you are looking for is some kind of logical approach. Note: My first two answers on this one are: They either log the bug formally in the bug tracker / ticket system They try and reproduce it 6. Salar ## Antonio Leiva interviewed by Fernando Cejas - Celebrating 1k subs on YouTube \[Droidkast LIVE 6\] DevFeed: [Antonio Leiva interviewed by Fernando Cejas - Celebrating 1k subs on YouTube \[Droidkast LIVE 6\]]() Original publisher: [Read original article]() Published: 2019-06-04T00:00:00Z Content type: opinion Language: en Sources: [Antonio Leiva]() Topics: [Android](), [Kotlin](), [Programming]() Tags: [android](), [interviewing](), [kotlin](), [talk](), [youtube]() ### AI overview An episode of Droidkast LIVE features Fernando Cejas interviewing Antonio Leiva about his background, entry into the Android world, and personal experiences. The episode celebrates the channel reaching more than 1,000 YouTube friends. ### Source excerpt Everything Android, Kotlin and other random topics ## Shopify Interns Share Their Tips for Success DevFeed: [Shopify Interns Share Their Tips for Success]() Original publisher: [Read original article]() Author: Kristen Shi Published: 2018-05-03T15:40:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Pull Request](), [GitHub](), [Slack](), [monitor](), [Programming]() Tags: [careers](), [developer](), [github](), [internship-experience](), [interviewing](), [process](), [programming](), [review](), [shopify](), [slack]() ### AI overview Shopify interns describe their work, education, interview experiences, and advice for succeeding at the company. Their examples include using GitHub and Slack, responding to pull request feedback, collaborating with mentors, working on projects, and monitoring merged work in production. ### Source excerpt At Shopify, we pride ourselves on our people. Shopifolk come from all kinds of backgrounds and experiences -- our interns are no exception. So, we gathered some of our current and past interns to chat with them about their careers so far. They share insights about work, education, and tips for interviewing and succeeding at Shopify. ## What a Jane Street software engineering interview is like DevFeed: [What a Jane Street software engineering interview is like]() Original publisher: [Read original article]() Author: Sebastian Funk Published: 2017-02-28T00:00:00Z Content type: tutorial Language: en Sources: [Jane Street]() Topics: [Software Engineering](), [Code](), [Data structures](), [Jule]() Tags: [code](), [coding](), [data-structures](), [engineering](), [interview](), [interviewing](), [ocaml](), [software-engineering]() ### AI overview This article explains what candidates can expect from a Jane Street software engineering phone interview. It walks through a memoization coding problem, including discussion of programming languages, data structures, APIs, and a possible OCaml solution. ### Source excerpt Are you thinking about applying to Jane Street for a software engineering role? Or already have a phone interview scheduled but unsure what to expect? Read on as we walk through an example phone interview with you. ## Interviewing Igor Minar and Adam Bradley for AngularBeers DevFeed: [Interviewing Igor Minar and Adam Bradley for AngularBeers]() Original publisher: [Read original article]() Published: 2016-12-18T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Ionic](), [React](), [Angular CLI](), [NativeScript](), [React Native](), [bazel](), [Compiler]() Tags: [angular](), [bazel](), [cli](), [comparisons](), [compiler](), [interviewing](), [ionic](), [nativescript](), [react]() ### AI overview An AngularBeers AMA moderated by the author features Igor Minar and Adam Bradley discussing Angular versioning, Universal, mobile development, Angular Material, React comparisons, Bazel, Closure Compiler integration, and Ahead-of-Time compilation. ### Source excerpt Lorem ipsum dolor sit amet ## A Brief Guide to Square's Product Manager Intern Program DevFeed: [A Brief Guide to Square's Product Manager Intern Program]() Original publisher: [Read original article]() Author: Tyler Sanchez Published: 2016-09-14T20:20:25Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Product Management](), [Software Engineering]() Tags: [engineering](), [experience](), [internships](), [interviewing](), [product-management]() ### AI overview A former Square Product Manager intern shares a personal guide to the company's first Product Manager internship program, covering the application and interview process, culture fit, and how to choose and complete a substantial project. ### Source excerpt Two weeks ago was my last day as a Product Manager intern at Square. The summer went quickly and I wanted to share some thoughts in hopes... [Next page]()