Amazon Leadership Principles — Text Copy, July 2026
Verbatim text of Amazon’s sixteen Leadership Principles, archived from amazon.jobs in July 2026.
Recent content on Mark Loves Tech
Verbatim text of Amazon’s sixteen Leadership Principles, archived from amazon.jobs in July 2026.
An archived copy of the dbt Labs company values and leadership principles, preserved from getdbt.com before the company's closure.
An archived copy of Grab's company values — the 4Hs — preserved from grab.careers.
An archived copy of MongoDB's company values, preserved from mongodb.com.
Mark moderates a panel at RAISE Summit 2026 on why open source is the engine of AI innovation, with Ion Stoica, Thomas Wolf, Dillon Rolnick, Eiso Kant, and Robin Rombach.
In this talk, I focused on what works for teams and what doesn’t. How to know what a good team is, whether you’re on one, and if you’re not, whether you should try to be part of the solution - or exit the team gracefully.
A company succeeds or fails based on the speed and quality of the decisions it makes. Slides hide weaknesses in reasoning; documents expose them. My guidelines for writing good memos, the key questions for each meeting type, and how to run a meeting that ends in a decision instead of a follow-up. Licensed Apache 2.0.
A pro forma process for incubating new ideas alongside the regular flow of a product engineering org. Four phases — research, ideation, incubation, productization — with three decision gates between them. Drawn from variations I’ve used at NASA, Oracle, NewsCorp, Grab, MongoDB, and dbt Labs.
A working framework for thinking about every decision in five distinct phases. Originally a scratchpad I wrote as CTO at dbt Labs while thinking out loud about how to make and communicate decisions better — sharing here as a work in progress.
On Patrick Lencioni’s The Motive : rewards-based leadership vs. value/team-based leadership, and why senior leaders never change because they’re told to — only because they change what they value. Originally a note to my engineering managers.
A framework for understanding the fundamentally different jobs at each rung of the engineering leadership ladder — IC, Manager, Director, VP, C-Level, and CEO. Being promoted isn’t doing your current job better; it’s a new job with new skills, new mindsets, new success criteria, and new failure modes.
A single-dimensional performance rating loses a huge amount of information about most humans. Eight dimensions I factor in when looking at leaders — and why lack of self-awareness about where you stand on them trumps all of them, and is a criteria for exit at director-and-above levels.
Sometimes people need to change to adapt to the company, and we’re not sure of the journey or how to help them. Six levels from unaware-of-the-gap to changed-and-maintaining — and a warning about the 3-4-5-3-4-5 cycle that can fool you into thinking someone has actually changed.
Reorganizations are hardly ever viewed as positive by the troops. As a leader you’ve been sitting with the new structure for weeks; for everyone else, it lands as a surprise. The job isn’t moving boxes — it’s running the announcement like a well-orchestrated Broadway play, where the unpopular things are called out as the plot, not ignored.
Fleet uptime is a fine starting point, but it doesn’t represent the customer experience. The LIFE framework — Length, Impact, Frequency, Experience — is how I think about availability NFRs in a way that actually maps to what customers feel.
Cascading isn’t just forwarding emails. It’s the practice — and discipline — of synthesizing, filtering, editorializing, and sometimes deleting the information that comes at you as a leader, then deciding what your team needs to know and how they need to know it. Originally written as a leveling note for my direct reports.
In this talk, I work to empower people to manage their own careers and give pointers from my own limited experience on things that work and things that don’t. Everybody’s journey is different…hopefully mine and what I learned from it are useful to you.
Highlights from Mark’s March 2023 reading of Patrick Lencioni’s The Five Dysfunctions of a Team — absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results.
Eight cultural guidelines for product and engineering organizations, written during my 18 months as CTO at MongoDB. Topics: balancing non-functional requirements with features, treating tech debt as a choice, pride in your work, trust, Conway’s law, Dunbar’s number, experimentation, candor and context for accountability, and avoiding unnecessary approvals.
An argument against the false fairy-tale of cloud-agnostic abstractions. Why letting the workload dictate the cloud, taking advantage of best-in-class services where you can, and focusing teams on being great on every environment they deploy to beats commoditizing yourself across the lowest common denominator. From conversations with many CTOs during my time at MongoDB.
Three talks I gave at the MongoDB World 2022 Builder’s Fest in New York City — slide decks below.
Thirteen leadership principles from a leader I admire — included here in their original framing as a reference for the parent Leadership Principles page.
For my first-ever Techsylvania talk, I talked about the challenges in culture and operations that occur as companies grow. I compared the culture of 4 companies in the talk, as well as some of the ways that our human minds work that make getting along easier and harder.
Mark's thoughts on the AWS Service Outage of Dec 7, 2021 -- examining AWS's response during and after the outage, plus implications for affected customers.
MongoDB CTO Mark Porter contests AWS's characterization of DocumentDB as 'MongoDB compatible'
Highlights from No Rules Rules on Netflix’s culture of freedom and responsibility — talent density, candor, removing controls, and leading with context instead of process.
Highlights from Peter Drucker’s The Effective Executive — the five habits of effectiveness, managing time, focusing on contribution, building on strengths, and concentration.
About 70% Clay Christensen, 30% me. The case against balancing work and home as two separate budgets — and for integrating them into one prioritized list for your whole life. Licensed Apache 2.0 so others can adopt it.
Highlights from Chris Voss’s Never Split The Difference — mirroring, labeling, calibrated questions, and the illusion of control. Mark’s commentary in italics.
Highlights from Jocko Willink’s Extreme Ownership — on standards, Decentralized Command, Cover and Move, and the Dichotomy of Leadership.
People ask me this often enough that I decided to put it on my home page: Aren't you one of the SQL folks? Why would one of you join MongoDB?
Grant Sanderson’s seven-chapter visual walkthrough of neural networks, from the basics through transformers and how LLMs might store facts. The single best resource I’ve found for understanding what’s actually happening inside modern AI.
About Mark Porter
Personal and private software projects Mark is working on
Get in touch with Mark Porter
Cultural principles Mark has refined throughout his career
Articles and videos I find interesting
Books and resources that have shaped how I think about technology, leadership, and building products
How to work with Mark Porter — a guide to my API
Bios, headshots, and resources for press, conferences, and event organizers.
Tools and techniques Mark uses to stay productive
A first-person trip through every tech I touched — from a 4K TRS-80 to running databases at planetary scale.
ACM SIGMOD '94 paper on the Oracle Media Server platform for distributed multimedia access