Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
The Software Engineer's Guidebook

The Software Engineer's Guidebook

Navigating senior, tech lead, and staff engineer positions at tech companies and startups
Move from senior engineer to staff-level influence without losing sight of the code or the business.
by Gergely Orosz 2023 413 pages
4.08
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat your career as a project only you can own

Choose your direction. The author entered engineering assuming good work and hard work would naturally bring progress. After being passed over for a senior promotion and receiving little useful guidance, he learned that managers vary in their capacity to support careers. Engineers need to name their goals, seek feedback, and create opportunities to grow rather than wait for someone else to plan their path. That path need not be a straight climb: people move between individual contributor and management roles, change specialties, start companies, or take breaks.

Make support easier. A manager can advocate more effectively when they understand an engineer’s ambitions and can see the work behind them. Regular conversations, clear requests, and reliable follow-through help turn a manager into an ally, without making them solely responsible for career development.

Analysis

What's valuable here is the distinction between agency and control. Engineers can choose what to pursue, but cannot dictate promotion budgets, manager quality, or the distribution of high-impact assignments. Ownership is therefore not a promise that effort guarantees advancement. It is a method for making goals explicit, gathering evidence, and deciding when the surrounding system no longer fits. The advice also challenges a familiar professional myth: that independence means never asking for help. In practice, self-direction includes deliberately recruiting advice and sponsorship.

Choose a workplace for its tradeoffs, not its prestige

Compare the whole job. The same engineering title can bring compensation that differs by two to four times across companies. The book groups employers into three broad pay tiers, from local-market employers to companies competing regionally or internationally. Those differences come with tradeoffs: startups offer autonomy and variety but face funding risk, while many traditional employers offer more stability and predictable hours but fewer senior IC roles.

Look beyond the label. A profit center directly contributes to revenue; a cost center supports the business without directly earning it. This can affect visibility, promotions, and security, especially at senior levels. Still, categories are rough guides, not verdicts. A strong team at a traditional company may be a better fit than a struggling team at a famous technology firm. Individual priorities, including mission, colleagues, flexibility, and health, belong in the comparison.

Analysis

A useful extension is to treat a job choice as a portfolio of risks and rewards, not a ranking exercise. High compensation may reflect a demanding environment or liquid equity, while private-company stock can remain only a paper promise until an exit. Similarly, a cost-center label describes how leaders account for work, not whether that work matters socially or technically. The framework is strongest when used to ask better questions about a specific team. It becomes misleading if a company category is mistaken for a reliable prediction of daily life.

Ship consequential work, then make its impact easy to see

Prioritize outcomes. Completing many small tasks is not the same as moving an important project forward. The book urges engineers to identify their top priority, protect time for it, and explain the tradeoffs when new requests compete. A weekly work log records projects, reviews, planning, mentoring, and measurable results. It counters recency bias, which makes recent work easier to remember than achievements from earlier in the year.

Prepare before review season. Performance systems vary from informal manager judgments to formal processes involving peer input, self-reviews, and calibration. In the latter, a concise record helps a manager describe both what was delivered and how. The author estimates that roughly 20% receive above-average reviews, 60-70% average ones, and 10-15% below average. These reviews matter, but they are snapshots, not a full measure of a career.

Analysis

The distinction between doing valuable work and making it legible is central to organizational life. A work log is not merely self-promotion; it is an external memory aid for both employee and manager. Yet visibility can reward people who are comfortable narrating their contributions, while quiet support work remains easy to overlook. The remedy is not to turn every task into a performance, but to record outcomes consistently and include contributions that helped others. That produces a more complete account than either modest silence or inflated claims.

Write code for the next engineer, not just today's ticket

Build for maintenance. Software engineering extends beyond writing code: it includes testing, shipping, operating, and changing systems over time. Readable names, focused functions, consistent structure, and useful explanations make future changes safer. Testing adds another safeguard. In one team, a senior engineer opposed unit tests until a large refactor caused regressions that took two days to repair. Tests helped expose the mistakes and gave the team a safety net.

Treat debt as a tradeoff. Technical debt is the future cost created when a shortcut makes later work harder. It is not always a mistake: an early startup may rationally accept rough code to test whether customers want a product. The key is to understand the cost, avoid letting it accumulate unnoticed, and address it when the expected benefit justifies the effort.

Analysis

This is a long-horizon view of craft: code is communication with people who arrive after its original context has faded. Readability and tests reduce the interpretive burden on those future engineers, especially when systems change under pressure. The example also makes an important distinction between confidence and evidence. An experienced programmer may produce reliable code without unit tests in some settings, but that does not mean a team can safely refactor a complex system without a repeatable check. The right safeguards depend on the system’s risks and release practices.

At senior level, multiply output by unblocking others

Shift from solo delivery. Senior engineers still need technical depth, but their value increasingly comes from helping a team deliver. They notice when colleagues are stuck, pair to teach problem-solving rather than simply hand over an answer, and resolve dependencies across teams. They also communicate roadblocks early, with options such as reducing scope, accepting a temporary shortcut, or asking another team to help.

Think like a product partner. A product-minded engineer asks why a feature matters, learns how customers use it, and tests assumptions before calling work complete. At Uber, a mobile platform team addressed memory leaks by teaching teams to find and fix them, then measuring the aggregate effect through experiments. The approach turned a scattered technical concern into shared learning and a measurable product improvement.

Analysis

The shift is from personal throughput to team capacity. Pairing, clear communication, and product curiosity can prevent repeated delays instead of merely completing one more task. The memory-leak example is instructive because it combines technical work with education and measurement, rather than treating a platform team’s output as valuable by default. Still, helping can become invisible or consume all available time. Senior engineers need to make that work legible and protect enough focused time to deliver their own highest-impact contributions.

Lead projects by aligning decisions, scope, and stakeholders

Align before building. A project kickoff clarifies why the work matters, what success means, and who must contribute. An engineering kickoff then develops the technical approach. Written plans let people raise misunderstandings before they become expensive rework. Small milestones provide checkpoints, reveal estimation errors, and create chances to adjust.

Negotiate the real constraints. The book’s model of “software project physics” links project scope, time, and people: if one changes, at least one other must change too. Adding engineers may help when work can be divided and newcomers can onboard quickly, but it is not a reliable shortcut. Tech leads should surface risks early, communicate tradeoffs, and protect teams from unexplained priority changes. A good wrap-up records results, recognizes contributors, and captures lessons, even when a project misses its business goal.

Analysis

Project leadership is presented as coordination under uncertainty, not as a more senior person issuing instructions. The constraint model is useful because it makes hidden costs discussable: a deadline can be protected by shrinking scope, adding suitable capacity, or accepting more labor hours. Those options are not interchangeable, and overtime can reduce quality rather than increase output. The model also has limits. Some work changes the constraints themselves through automation or a new approach, so leaders should use it to expose assumptions, not to treat every plan as mechanically predictable.

Staff engineers should find valuable problems, not just solve assigned ones

Understand the business. Staff-plus engineers are expected to look beyond the task list and identify problems worth solving. That means learning how customers use a product, how the company earns or saves money, and how a team’s work connects to wider goals. They often partner with engineering and product managers to shape strategy and priorities, and may speak directly with business stakeholders or customers to get context.

Question the scoreboard. Teams use KPIs, or measurable performance indicators, and OKRs, a goal-setting system pairing a qualitative objective with measurable results. These can focus attention, but a metric can be improved without improving the product. The book describes teams that met a reliability target by changing how success was counted, not by changing the system. Staff engineers should test whether metrics reflect customer value and add countermeasures where needed.

Analysis

The move from solving problems to finding them is a meaningful change in engineering scope. It asks technical leaders to translate between customer experience, business priorities, and system design rather than assume that the loudest request is the best investment. Metrics help coordinate this work, but they remain proxies. A useful discipline is to ask what real-world change would make a number improve, and what separate measure would expose gaming or unintended harm. This keeps business awareness from becoming simple obedience to whichever target is easiest to report.

Treat reliability as a loop of detection, mitigation, and learning

Test at the right level. Unit tests check isolated components, integration tests check components working together, and end-to-end tests exercise a product as a user would. Each has different costs and failure modes, so the familiar testing pyramid or testing trophy is a guide, not a quota. In production, monitoring should include business signals, not only infrastructure measures. A service can appear technically healthy while a key customer action is failing.

Make failure recoverable. Canaries and staged rollouts expose changes to a small group before wider release. Alerts need to be actionable, and oncall engineers need runbooks for diagnosis and mitigation. After an incident, a blameless review should examine the conditions that allowed it and assign follow-up work. The purpose is not to excuse mistakes, but to make recurrence less likely.

Analysis

Reliability is not a property that testing can certify once and for all. It is a feedback system: checks catch some failures before release, production signals catch others, and incident reviews improve the next response. The emphasis on customer metrics prevents an overly narrow definition of health, while staged rollouts limit the cost of learning. There is a practical tension, however: more alerts and tests can create noise and delay. Good engineering chooses protections in proportion to the harm a failure could cause and keeps the safeguards useful.

Prototype uncertain designs, and keep expensive decisions reversible

Replace speculation with evidence. Before committing to a complex architecture, build a throwaway proof of concept when important unknowns can be tested in code. In one payments project involving about ten teams, months of documents failed to settle disagreements. A small cross-team group then built a basic prototype in two weeks, resolving many questions and clarifying how systems should connect. The prototype was discarded, but its learning shaped the real design.

Match effort to risk. A decision that is easy to undo, such as renaming an internal class, rarely deserves prolonged debate. A choice of public API, programming language, or data model can be costly to reverse and deserves more investigation. Good architecture stays simple, fits business plans, and limits how many teams or customers a future correction can affect.

Analysis

Prototyping is a way to make disagreement empirical. A working sketch gives teams something concrete to inspect, and exposes implementation friction that abstract diagrams can hide. The reversibility lens also helps allocate attention: debate should be concentrated on choices whose reversal would be expensive, not spread evenly across every decision. A prototype can still mislead if its success depends on shortcuts that production cannot support. Its assumptions and throwaway status therefore need to be explicit, with a deliberate transition from demonstration to maintainable implementation.

Keep learning across a long career, without living in permanent sprint mode

Stay curious on purpose. Strong engineers keep learning languages, tools, and unfamiliar parts of their systems. The most dependable teacher is often building something, debugging it, and explaining what was learned to others. Pairing, mentoring, reading code, and trying a new platform can all widen skill and perspective. When an engineer becomes an expert, teaching or choosing a new challenge can restart the learning curve.

Vary the pace. The book describes three work modes: stretching into unfamiliar, demanding work; executing at a sustainable level; and briefly coasting to recover or handle life outside work. Stretching can accelerate growth, but staying there too long risks exhaustion. Prolonged coasting can dull skills and weaken team trust. A decades-long career requires noticing which mode fits and changing course before strain becomes the only signal.

Analysis

The strongest account of lifelong learning is not relentless self-optimization. It combines curiosity with recovery and recognizes that expertise can become either a platform for teaching or a reason to seek new problems. Learning by doing is especially useful because it joins knowledge to judgment: a concept becomes more durable when it has survived debugging and real constraints. The caution is that career advice about constant growth can itself become pressure. Sustainable development depends on choosing learning that serves genuine interests and work needs, rather than chasing every new technology out of fear.

Analysis

The book’s organizing idea is a widening circle of responsibility. Early-career engineers learn to produce working code; senior engineers make that code maintainable and help teammates deliver; tech leads coordinate projects and protect focus; staff engineers connect technical choices to business needs and organizational health. The progression is less about abandoning coding than about increasing the distance between one’s actions and their effects. A reliable senior engineer improves a system. A staff engineer may improve the conditions under which several teams build systems. That arc also reveals a tension. Companies need visible impact to allocate promotions and resources, but the strongest contributions are not always easy to count. Platform reliability, mentoring, onboarding, documentation, and preventing a failure may have broad value while leaving weak evidence in conventional scorecards. The book’s advice to record work and quantify outcomes helps individuals navigate this problem, but it cannot eliminate the incentive to favor measurable wins over quiet maintenance. Leaders have a corresponding responsibility to recognize enabling work, not merely ask individuals to advertise it.

The most persuasive practical principle is contextual judgment. There is no universal best testing ratio, architecture pattern, release process, or career ladder. A startup seeking product-market fit, a bank protecting money flows, and a mature consumer platform face different costs of delay and failure. The book’s examples repeatedly ask engineers to identify those costs before importing a fashionable practice. This is a stronger standard than either rigid process or reflexive pragmatism: understand the risk, choose an appropriate safeguard, and learn from the result.

Ultimately, the guide treats engineering as technical work embedded in a human institution. Career growth depends on skill, opportunity, trust, communication, and timing. Systems quality depends on code, incentives, operational feedback, and collaboration. The practical reader should therefore track two things together: whether the software is improving, and whether the organization is becoming better at making that improvement repeatable.

Summary in 30 Seconds
Engineering impact grows from delivering code to enabling teams, coordinating projects, and finding high-value problems across an organization. Make work visible with a regular record of outcomes, and assess jobs by compensation, stability, autonomy, and team quality. Use readable code, tests, staged releases, and incident reviews to limit risk. Prototype uncertain designs before committing, and investigate decisions that are costly to reverse. Balance demanding growth with sustainable work and recovery.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.08 out of 5
Average of 500+ ratings from Goodreads and Amazon.

The Software Engineer's Guidebook receives mixed reviews, with praise for its comprehensive coverage of software engineering careers and practical advice for junior to mid-level engineers. Critics note its broad but shallow approach, repetition, and lack of novel insights for experienced professionals. Many find it well-structured and valuable for career guidance, particularly for those early in their careers. Some readers appreciate its coverage of both technical and soft skills, while others feel it lacks depth on specific topics. Overall, it's considered a useful resource for understanding the software engineering career path.

Your rating:
4.55
340 ratings
Want to read the full book?

Glossary

work log

Record of contributions

A regularly updated record of meaningful work, such as code shipped, reviews, planning, mentoring, and project outcomes. It helps an engineer remember contributions for feedback and performance reviews, gives a manager better context, and makes competing tasks easier to prioritize. The book also refers to a similar document as a brag document.

product-minded engineer

Engineer focused on product value

An engineer who takes an active interest in the product, its customers, and the business goals behind its features. Rather than only implementing a specification, this engineer asks why a feature is needed, explores alternatives, considers user behavior, and helps validate whether the shipped work solves the intended problem.

Definition of Done

Shared completion criteria

A team-agreed description of the minimum requirements for considering work complete. Depending on the project, it can include testing, documentation, accessibility, or rollout checks. Making the definition explicit reduces disagreement about quality and helps teammates hold one another to the same standard. It can change with the team and the project’s risks.

testing pyramid

Model for test mix

A mental model that recommends covering much of a system with fast, focused unit tests, using integration tests for interactions, and keeping slower, more brittle end-to-end tests comparatively limited. It is especially useful for some backend systems, but it is not a universal prescription. The suitable mix depends on the product, platform, and testing tools.

testing trophy

Integration-focused test model

A testing model that gives particular weight to integration tests, especially in frontend development, where important failures can occur between components. It emerged partly because modern tools make these tests easier to write and because isolated unit tests may miss interactions. Like the testing pyramid, it is a guide for reasoning, not a required test ratio.

software project physics

Scope, time, people tradeoff

The book’s model for the relationship among a project’s scope, timeline, and labor. If one changes, at least one other usually needs to change as well. Expanding scope may require more time or more labor; shortening a deadline may require reduced scope or additional effort. Onboarding and coordination costs can make added staff less helpful than expected.

Domain-driven design

Model software around business domains

An approach to software design that begins by understanding the business area the system serves. It builds shared vocabulary between engineers and domain experts, separates complex areas into bounded contexts, and models concepts such as entities and domain events. The goal is to make software reflect business rules more accurately and remain easier to understand and extend.

blast radius

Reach of a change’s impact

The number of systems, teams, or customers that a decision or change can affect. Retiring an internal feature used by one team has a small blast radius; breaking a public API used by many customers has a large one. Engineers can reduce the radius with staged changes, adapters, or migration paths.

error budget

Acceptable service degradation

A defined allowance for temporary service degradation that a business considers acceptable. Teams can use it alongside service reliability measurements to judge whether riskier deployments are reasonable. If the allowance is depleted, the team may pause risky releases and focus on restoring reliability. Its usefulness depends on meaningful service indicators and clear operational practices.

one-way door and two-way door decisions

Choices sorted by reversibility

A way to distinguish decisions that are easy to reverse from those whose reversal is costly. Internal naming changes are usually easy to undo, while choices such as a public API or core data model can create substantial migration work. The distinction helps teams decide when to move quickly and when to research or prototype first.

FAQ

What's The Software Engineer's Guidebook about?

  • Career Navigation Focus: The book provides insights into navigating software engineering roles, from entry-level to senior and staff positions, emphasizing understanding company cultures and expectations.
  • Practical Advice: It offers practical advice on performance reviews, promotions, and job switching, helping engineers take ownership of their careers.
  • Skill Development: Covers essential skills for software developers, including coding, collaboration, and project management, making it a comprehensive resource for professional growth.

Why should I read The Software Engineer's Guidebook?

  • Real-World Insights: Written by Gergely Orosz, the book provides real-world insights that can help you navigate your career effectively.
  • Structured Learning: Allows readers to focus on specific areas of interest, whether they are just starting out or looking to advance their careers.
  • Timeless Advice: Captures observations and advice designed to stand the test of time, making it valuable for both current and future software engineers.

What are the key takeaways of The Software Engineer's Guidebook?

  • Own Your Career: Emphasizes the importance of taking ownership of your career path, encouraging readers to actively seek growth opportunities.
  • Understand Company Types: Categorizes different types of tech companies and their cultures, helping engineers choose the right environment for their career goals.
  • Continuous Learning: Stresses the importance of lifelong learning and adapting to new technologies and methodologies in the fast-paced tech industry.

What are the best quotes from The Software Engineer's Guidebook and what do they mean?

  • "No one cares about your career as much as you do.": Highlights the necessity for individuals to manage their career paths proactively.
  • "The higher 'tier' a business is, the more tends to be expected of engineers.": Points out the varying expectations across different companies, especially between startups and Big Tech.
  • "Software development is a craft that takes years to master.": Emphasizes the long-term commitment required to become proficient in software engineering.

How does The Software Engineer's Guidebook define career paths for software engineers?

  • Single-Track vs. Dual-Track: Explains the difference between career paths that require a switch to management and those allowing growth as individual contributors.
  • Common Career Progressions: Outlines typical progressions, such as moving from software engineer to senior engineer, and then to staff or principal engineer.
  • Unique Paths: Discusses the variety of career paths, including specialization in technologies or transitioning into roles like product management.

What strategies does The Software Engineer's Guidebook suggest for getting things done?

  • Prioritize Effectively: Advises identifying the most important tasks and focusing on completing them first to build a reputation for reliability.
  • Unblock Yourself: Emphasizes recognizing when you are blocked and taking proactive steps to resolve issues.
  • Break Down Work: Encourages breaking down larger tasks into manageable pieces to maintain productivity.

How does The Software Engineer's Guidebook address performance reviews?

  • Preparation is Key: Stresses the importance of preparing for performance reviews by gathering context, setting goals, and keeping a record of achievements.
  • Understanding the Process: Explains different performance review systems and how to navigate them effectively.
  • Managing Expectations: Advises understanding your standing with managers and setting realistic expectations for outcomes.

What advice does The Software Engineer's Guidebook provide for promotions?

  • Know the Criteria: Emphasizes understanding the specific criteria for promotions within your organization.
  • Build Relationships: Highlights the need to cultivate relationships with managers and peers who can advocate for you.
  • Be Realistic: Advises focusing on continuous improvement, regardless of whether a promotion is achieved in a given cycle.

How can I effectively switch jobs according to The Software Engineer's Guidebook?

  • Explore Opportunities: Encourages actively exploring job opportunities, whether unhappy in the current role or curious about the market.
  • Assessing Offers: Advises considering compensation, career growth potential, company culture, and challenges when evaluating job offers.
  • Prepare for Interviews: Provides guidance on preparing for technical interviews, including understanding the process and practicing skills.

What role does continuous learning play in The Software Engineer's Guidebook?

  • Lifelong Learning Emphasis: Stresses that continuous learning is essential for career growth as technologies evolve rapidly.
  • Skill Development: Encourages mastering primary programming languages and exploring new technologies to stay relevant.
  • Mentorship and Collaboration: Highlights the importance of seeking mentorship and collaborating with peers to enhance learning.

What is stakeholder management in The Software Engineer's Guidebook?

  • Definition: Refers to identifying, engaging, and communicating with all parties interested in a project.
  • Importance: Helps prevent misunderstandings and ensures relevant feedback is considered for smoother project execution.
  • Methods: Suggests using meetings, asynchronous updates, and hybrid communication methods to keep stakeholders informed.

How does The Software Engineer's Guidebook define "team dynamics"?

  • Healthy Teams: Describes healthy teams as those with clear goals, good morale, and effective communication.
  • Unhealthy Teams: Contrasts with teams lacking clarity, experiencing poor execution, and struggling with communication.
  • Improvement Strategies: Provides strategies for improving team dynamics, such as facilitating open discussions and addressing conflicts constructively.

About the Author

Gergely Orosz is a prominent technology influencer and author of The Software Engineer's Guidebook. He writes The Pragmatic Engineer, the top technology newsletter on Substack. Orosz has extensive experience in the tech industry, having worked for major companies including Uber, Skype/Microsoft, and Skyscanner. His writing focuses on practical advice for software engineers, covering career development, technical skills, and industry insights. Orosz's work is known for its pragmatic approach and is particularly valued by those seeking guidance in navigating the software engineering career path. His background in big tech companies informs his perspective on the industry and career progression.

Download PDF

To save this The Software Engineer's Guidebook summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.39 MB     Pages: 22

Download EPUB

To read this The Software Engineer's Guidebook summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.37 MB     Pages: 26
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...