# Learning & Growth Published articles for Learning & Growth. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kogan.com's Engineering Culture Emphasizes Ownership, Collaboration, and Continuous Delivery DevFeed: [Kogan.com's Engineering Culture Emphasizes Ownership, Collaboration, and Continuous Delivery]() Original publisher: [Read original article]() Author: Kogan Dev Blog Published: 2026-02-22T03:33:30Z Content type: article Language: en Sources: [Kogan.com]() Topics: [engineering-culture](), [Development](), [Testing](), [CI/CD](), [Deployment](), [observability]() Tags: [ci-cd](), [code](), [culture](), [deployment](), [development](), [engineering](), [engineering-culture](), [learning-growth](), [observability](), [testing]() ### AI overview This article describes Kogan.com's engineering culture, emphasizing ownership, pragmatic decision-making, collaboration across teams, and continuous improvement. It also outlines a delivery process involving clear requirements, incremental work, peer review, automated testing, CI checks, CI/CD deployment, and production monitoring. ### Source excerpt At Kogan.com, engineering is about building software that is useful and seeing them used at scale. We work in a fast moving e-commerce environment, so the problems are real and often complex. Performance, reliability, scale, legacy constraints, new features, tight feedback loops. We ship frequently, deploy daily, and continuously improve what is already live. You can see the impact of your work quickly, and so can our customers. Yes, there are hackathons, plenty of snacks, meetup pizzas and team events. But what defines the culture is ownership. Engineers are trusted to make decisions, go deep into systems, challenge assumptions, and drive outcomes. That might mean building a new platform, untangling and modernising legacy code, improving observability, or removing bottlenecks that affect millions of users. Teams are pragmatic and hands on. We care about clean code and good architecture, but we also care about delivering value. There is a strong bias toward action and continuous improvement over perfection. Collaboration is key. Engineers work closely with product, design, data, and commercial teams. Context is shared openly, trade offs are discussed honestly, and ideas are judged on merit. To bring our culture to life, we spoke to three of our engineers about the engineering culture here: Shams SaatichoHow do ideas go from concept to production here? Ideas come from stakeholders, marketing, product, UX or engineering. The first step is clarity. What problem are we solving? What measurable outcomes define success? What constraints or trade offs exist? Engineers and stakeholders align on requirements and break larger initiatives into small, testable increments with clear acceptance criteria. Once scoped, work is prioritised in the backlog. During development, changes go through peer review, automated testing and CI checks, plus user acceptance testing where needed. Deployment happens through CI/CD. Shipping is not the finish line. We monitor production metrics and be ## Four Years Strong: Celebrating Our Koganniversaries DevFeed: [Four Years Strong: Celebrating Our Koganniversaries]() Original publisher: [Read original article]() Author: Kogan Dev Blog Published: 2025-10-07T03:28:12Z Content type: opinion Language: en Sources: [Kogan.com]() Topics: [engineering-culture](), [Software Engineering](), [Tech Lead](), [Development]() Tags: [culture](), [leadership](), [learning-growth](), [software-engineer](), [software-engineering](), [team](), [tech-lead]() ### AI overview Kogan.com highlights three team members reaching four-year milestones and discusses their career growth, engineering experiences, leadership development, and reasons for staying with the company. The article also describes Sam O'Halloran's work improving product-variant handling across pipelines, batch jobs, OpenSearch, and the UI. ### Source excerpt In a talent landscape full of competitive opportunities, where change and turnover are part of the norm, Kogan.com stands out as a place where people choose to stay, grow, and advance their careers. Many of our team members have long tenures, with some contributing as long as 12 or 15 years, reflecting the strong culture and opportunities here. This month, we celebrated three team members reaching their four-year milestone. To mark the occasion, we spoke with them about what has made their journey so rewarding, what has kept them at Kogan.com, and what continues to inspire and excite them as part of our team. Adam Slomoi Adam is currently the Tech Lead of a squad. He joined Kogan as a Software Engineer and quickly progressed to Senior Software Engineer, and most recently to Tech Lead. In this role, he continues to sharpen his technical skills while growing his passion for people leadership. How has your role or perspective on engineering evolved over the last four years?I've been fortunate to work across different areas of the business and on various components of our system during my time at Kogan. One theme that has remained consistent throughout, and that I've gained a greater appreciation for, is the focus on business outcomes. How did you feel stepping into your first leadership role, and what did you learn from the experience? I felt well prepared before officially taking on a leadership role. We have a very collaborative team, and there have been many opportunities along the way to have a say and help set the direction for the team. Sam O'Halloran Sam started at Kogan in his first formal software engineering role straight out of university. He has honed his technical skills, contributed significantly to his team, and grown in both technical depth and breadth, applying best practices efficiently. Which project are you most proud of, and what made it exciting or unique? I'm most proud of the work on product variants. It wasn't one big launch, just lots of small ## Kogan.com Engineering Growth Paths: From Pricing Manager to Data Engineer DevFeed: [Kogan.com Engineering Growth Paths: From Pricing Manager to Data Engineer]() Original publisher: [Read original article]() Author: Kogan Dev Blog Published: 2024-07-01T01:36:02Z Content type: article Language: en Sources: [Kogan.com]() Topics: [data-engineering](), [Software Engineering](), [data](), [Python]() Tags: [career](), [data](), [data-engineering](), [engineering](), [growth](), [infrastructure](), [learning-growth](), [processes](), [python](), [tools]() ### AI overview Kogan.com describes its engineering growth paths through the internal mobility story of Reuben Orange, who moved from a 10-year career in Purchasing and a pricing manager role into data engineering. The article highlights mentorship, learning, and the use of data querying, Python, infrastructure, tools, and processes in his new work. ### Source excerpt Committed to learning and continuous improvement, Kogan.com's Engineering team develops its engineering talent through giving and taking responsibility, co-creation, mentorship, and internal mobility opportunities to grow and advance their careers. There are opportunities for Engineers at Kogan.com regardless of background. Some engineers at Kogan.com are Individual Contributors, Tech Leads or People Managers - and engineering growth paths and aspirations are supported throughout their journey. Featured here is Reuben Orange, our latest addition to the team who joined us through Kogan.com's internal mobility program. After a highly successful 10-year journey in the Purchasing team, we were excited to support Reuben's career aspirations and his passion in all things data and software engineering. With an Educational background in Mathematics and extensive experience across various roles within Purchasing, Reuben brings a unique skill set to his new role. Collaborating closely with our Data Engineering and Business Intelligence squad,Reueben plays a crucial role in developing, managing, and optimizing infrastructure, tools, and processes important for meeting Kogan.com's analytics and data requirements. Reuben's wealth of domain experience, coupled with his genuine passion for data and meticulous attention to detail, positions him as an outstanding Data Engineer member to the team. Tell us Reuben.... What initially sparked your interest in transitioning your previous role as pricing manager to data engineering? The pricing manager role was created to develop a "pricing strategy", I called it "making sure we don't end up on an episode of Hoarders". We needed to bring Kogan's inventory level down from our very high post COVID levels, to a more reasonable position, while salvaging as much value as possible. Together, the whole team did that very successfully, and we now get much more value from a dollar invested into inventory than we did before. The role involved a lot of