Careers in Technology
From the first year of code and the first job to seniority without management, engineering leadership, hiring and the mentoring of juniors in the age of AI, careers in technology as told through the free samples of the Leanpub books about them.
Created from the free samples of 9 Leanpub books and the descriptions and tables of contents of 21 more, with every source cited.
A career in technology is a working life spent building, testing, running or managing software and the systems around it, and the literature about it is largely advice from people a few years further on to those just behind. Its first lesson is that the work is not what the advertisement says. One career guide here remarks that to say software engineers write code is true in the way it is true that surgeons use scalpels: the actual work is making systems on which other people depend go on functioning, and the code is only how decisions about them become permanent.[1]
The books fall along the course of such a life: learning the trade and finding a first job, the daily job and its frustrations, the climb from junior to senior and to the senior grades that involve no management, the move into management for those who choose it, and the hiring and bringing-on of others. Most are written from one person's experience and say so. One finding recurs across them: advancement depends less on technical skill than newcomers expect. A principal engineer writes that seniority is not about delivering more and better but about helping others to deliver more and better.[2]
This article follows that course, from getting in through the job itself, growing in seniority, management and leadership, hiring and mentoring, and the other paths open to a technologist. Its sources are the free samples of the Leanpub books listed at the end, with the descriptions and tables of contents of those whose samples were not available or not read, and every claim that rests on a source is cited to it.
Where to start
The beginner, whether a student, a pupil of a coding school or self-taught, can start with Your First Year in Code (2022), much the most widely read book here, an edited collection that mixes instruction with career advice and encouragement.[10] Someone who wants a first paid job in web development has a manual built around projects, Zero To Code (2022),[11] and someone drawn to testing has Starting Your Software Testing Career (2024).[3]
The working engineer in the first ten years of a career is the reader of Software Engineer (2026),[1] and the one who wonders how to advance without giving up programming of The Seniority Trap (2023).[2] Testers who know their craft and are unsure where to go next have The Software Tester’s Journey (2024).[4]
Those taking on responsibility for others can read The Manager's Manual (2021), a short guide for new technical leaders by three who have been through it,[19] and Hiring Developers, a booklet for anyone who hires developers.[24] Managers and heads of engineering concerned with how juniors now learn should read Fix the Ladder (2026).[5]
History
Programming became a recognised occupation in the 1950s and 1960s and a mass one with the personal computer and the web. For most of that time the route in was a degree or an apprenticeship on the job, and the route up led into management. The 2010s added short intensive schools for career changers and, in larger companies, a second ladder on which engineers could rise to staff and principal grades without managing anyone. Remote work spread after 2020, and since 2023 tools that write code have unsettled the question of how beginners are to learn.
The books mark these stages. The Seniority Trap is an account of the second ladder from someone on it, a principal engineer without formal authority whose influence extends over a department.[2] LinkedIn for Mobile Developers (2018) belongs to the period when a profile on a professional network became the way to be found.[7] And Fix the Ladder describes the present difficulty, in which the slow years of friction by which juniors became seniors have nearly disappeared and, across the industry, the hiring of juniors has contracted.[5]
Getting in
Your First Year in Code sets out to start its readers a year or two ahead of where its contributors began, and spends most of its pages on what surrounds the code: how to learn, being stuck, self-doubt, recruiters and working in a team.[10] Zero To Code ties a review of the basic web technologies to the building of a set of projects to show employers, with a mock interview.[11]
Starting Your Software Testing Career reads job advertisements closely. It separates the skills employers ask for from those that prove useful in the work and observes that the two lists only partly overlap. Experience of one tool, it advises, can honestly be offered as a reason to expect competence with an equivalent one. Agile working means different things in different companies, so a candidate should be ready to say what it means to them. Many employers believe that testing means writing test cases in advance and running them, which is only one way to test. And the plainest skill is undervalued: a clear bug report that others can reproduce earns a new tester credibility, because the bugs raised are bugs the team can find and so are fixed. It recommends finding a mentor and closes with advice gathered from testers in many countries. The book adds a caution about the demand for test automation, which often comes from employers who could not say what good automation looks like, and it calls targets such as automating everything dangerous.[3]
Being found is its own subject. LinkedIn for Mobile Developers begins from how the network's search works: a search matches the text of profiles within three degrees of connection and orders them by relevance, and each result shows only a photograph, name, headline, place and current post, which is therefore what a recruiter sees first. The search will treat a plural as its singular but should not be relied on to be clever, the book warns, and paying subscribers are shown more prominently; small companies search as any member does, while large recruiting firms use an account of their own. It then builds a profile in stages, as software is released.[7] Resumes That Will Land You the Interview (2020) is a short guide to the written application for any field,[12] The Enterprise PM Interview Playbook (2025) prepares candidates for interviews for product management posts,[13] and What Every IT Business Analyst Should Know (2025) introduces one role, the business analyst, to those entering it.[14]
The job itself
Software Engineer opens by setting the posted description of a job, with its scalable services and collaboration, beside the job. The second is the making of decisions under uncertainty, many times a day, with incomplete information, in a codebase one did not design, on systems people are using while the work goes on. Every test not written and every default accepted is a decision, and production differs from a tutorial in that nothing can be deleted and begun again: the data has been there for years, the customers are using it now, and the repair that would take forty seconds must fit a limit measured in fractions of one. Even the adjectives of the advertisement need context, since a service built for a hundred requests a minute and one built for a million are both scalable if each suits its load. The book's account of autonomy is that it is one transaction with ownership, and it quotes with approval an advertisement that says as much, offering freedom to choose the right tool in return for responsibility for what is built. An engineer who wants freedom to choose tools and does not want to be woken when they fail has misunderstood the offer, and the gap between wanting the one and accepting the other is where, on its account, most early careers stall. Its later parts cover getting hired, communication, which it counts an engineering skill and not a soft one, the arc of a career and the ethics of the profession. The intended reader may be technically strong and professionally invisible, or promoted for good code and now expected to lead without having been told that this was coming; the book offers nothing, it says, to those who want the title without the craft, and the author says where stories have been disguised: its chapter on interviews is built on the written feedback given about one real candidate who failed, with the names removed.[1]
Quicksands of software development (2022) is a warning about everything that is not code. A new programmer, it says, is absorbed in languages, patterns and tools, the tools of the trade that earn pay and reputation, all of which concern the programmer alone; but the first job will probably be on a project that is not going smoothly, among other people, and every business is a business of people. With time the roles change as well, to leading teams, mentoring novices, hiring and dismissing, and talking to clients and executives, none of it technical. Problems arrive gradually, and teams grow so used to them that they look normal, a state the author compares to the frog in slowly heated water and notes is often signalled by the jokes people make about their project.[6] The good teammate makes the same point briefly, that awareness and everyday behaviour are the main lesson of a career in teams,[15] and Time Management for Software Developers (2025) is about protecting attention and planning the week.[16]
Growing in seniority
The Seniority Trap takes its title from a dilemma: to earn more and have wider effect, a developer seems obliged to give up hands-on work for meetings and spreadsheets. Seniority, the book holds, does not come from years spent in the same chair but from knowledge applied. The author reports escaping the dilemma, becoming a principal engineer with few meetings, and attributes the escape less to technical books than to books on psychology, management and careers. For years, the account runs, growing technical competence and help given to colleagues were followed by disappointing annual reviews, until the rules of the game were understood, after which two promotions came in three years. The advice that follows is ordered by the questions of a career: what kind of company to work for, and how to adapt to the hierarchies and odd culture of a large one, how to shed a junior's habits of mind, why one should look for work one can become passionate about and not for a passion, how to treat failure, and why few rewards are simply given. The author claims no special talent and no long hours, only steady reading, and warns that the advice comes from large corporations and fits other workplaces less well.[2]
The Software Tester’s Journey maps the choices open to an experienced tester along three paths, of people, technology and business, and covers promotion, managing one's manager and leaving testing altogether. Its sample chapter is on feedback, which it treats as a skill able to build or destroy working relationships; given well it is specific and usable, and it helps to make an environment in which failure is safe and experiments are therefore possible. The contents list the questions the earlier chapters take up, among them whether all tests should be automated, what automation costs in other work forgone, and whether testers are needed at all.[4] Staff-Level Testing Roles (2026) carries the idea of the staff-level engineer into testing and quality roles.[17] The Entrepreneurial Employee (2020) recommends treating employment as an entrepreneur would, widening one's attention from oneself to the team, the company and the market,[18] and Creating a career in enterprise-architecture (2022) does for the enterprise architect what these do for the engineer, describing a generalist's career that depends on conversations and allies; its sample advises a newcomer to an organisation to look first for the people already committed to neighbouring causes, since the personal networks on which the work depends take years to form.[8]
Management and leadership
The Manager's Manual covers what the manager's role involves, the passage from engineering into the management of people, the giving of feedback and the manager's relation to product development.[19] The Engineering Protocol Stack (2026) arranges the skills of an engineering leader in three layers named after the parts of a network, the self, the team and the wider organisation, and holds that a company hires engineers for their technical skills while it is mostly the other kind that decides how far they go.[20] Habits that Ruin your Technical Team (2018) names seven habits of technical leads that damage trust and motivation, among them withholding feedback and pressing constantly for speed.[21] The Agile CIO (2017) applies agile values to the work of the most senior IT executives,[22] and A Practical Introduction to Coaching (2019) teaches the coaching conversation to people who work in software.[23]
Hiring and mentoring
Hiring Developers follows the hiring process in order, from defining the post and the ideal candidate through the advertisement, the screening and technical interviews and the decision to the offer and the first weeks, and treats hiring as a kind of selling in which speed matters.[24]
Fix the Ladder is about what happens after hiring, and whether there will be any. Its author, reviewing a change submitted by an engineer who could not explain it, saw that tools which write code had let both of them skip a climb, and that only one of them had earlier been forced through the slow years that produce understanding. The book finds two problems where it first saw one. The ladder is broken, because the friction of dull tickets, bad merges and stinging reviews was doing more teaching than anyone credited, and because remote work has thinned the chance encounters on which apprenticeship ran: the junior who overhears a senior struggling with an error is now a tile on a screen, easy to forget, while the seniors who might teach are the busiest people in the company. The friction taught juniors to think, the author writes, and the proximity taught them that they belonged. And the door is closed, because companies reason that a senior with an AI agent can do a junior's work today. The two are one problem, it argues: to repair learning is useless if nobody hires juniors, and to hire them is reckless without a way of bringing them on. The author does not argue against the tools, having been, by the book's account, the child who wished for exactly such machines; the open question is what is done with the time they give. Its remedy is a mentoring course of six sessions in which engineers practise challenging the AI's output, and it admits that when the course was run the participants were not juniors but capable mid-level engineers, in whom the gap appeared all the same.[5] Building Dev Teams For Tomorrow (2025) proposes a different future, software teams of two people supported by agents.[25]
Other paths
Not every career stays in employment or in engineering. Leaving the Rat Race with Python (2021) treats freelance programming as a business with its own strategy for rates and clients,[26] and Red Yellow Green: What Color is Your Money? (2020) argues from its author's life as an executive for building income outside a salary, beginning with skills learned and a client taken on while still employed, on the reasoning that an employer's venture is a poorer bet than oneself.[9] I Am a Developer Advocate (2025) describes the work of representing a product to developers and developers to a company,[27] and Transitioning to Project Management (2024) treats a change of career as a project to be planned, with an inventory of skills, a plan, and advice for the first weeks in the new post.[28]
Two small books concern the gatherings at which careers are quietly made. Conferences for Introverts (2017) walks a reluctant attendee through preparing, meeting people, taking breaks and following up,[29] and 10 Days to Better Networking (2025) sets ten days of short exercises in building a professional network.[30]
Sources
Every source is a Leanpub book. The note after each says which part of it was read; where no sample was available, only the public description and table of contents were used.
- 1.Software Engineer, Joel Bryan Juliano: A Field Guide to the Profession Free sample: the preface and the opening of the first chapter, on the job description and the job. 2026. Free sample: PDF · EPUB
- 2.The Seniority Trap, Sandor Dargo: Become a senior engineer without losing your soul Free sample: the introduction. 2023. Free sample: PDF · EPUB
- 3.Starting Your Software Testing Career, Nicola Lindgren: A guide to finding your first role as a Software Tester, upskilling so you are relevant in the job market and succeeding as a Software Tester once you have landed a role. Free sample: part of the chapter on the skills employers ask for and those that prove useful. 2024. Free sample: PDF · EPUB
- 4.The Software Tester’s Journey, Nicola Lindgren, Vernon Richards: Exploring Career Opportunities and Adventures Free sample: the contents and the opening of the chapter on feedback. 2024. Free sample: PDF · EPUB
- 5.Fix the Ladder, Giordano Scalzo: Growing Junior Engineers in the Age of AI Free sample: the opening chapter, on the broken ladder and the closed door. 2026. Free sample: PDF · EPUB
- 6.Quicksands of software development, D. Petre Bogdan Free sample: part of the introduction. 2022. Free sample: PDF · EPUB
- 7.LinkedIn for Mobile Developers, Dan Zinngrabe Free sample: the opening section on how search works. 2018. Free sample: PDF · EPUB
- 8.Creating a career in enterprise-architecture, Tom Graves: Theory, roles and practice Free sample: a post on starting enterprise architecture in an organisation. 2022. Free sample: PDF · EPUB
- 9.Red Yellow Green: What Color is Your Money?, Noah Gift, Matt Harrison: The survival manual for gig workers and consultants Free sample: part of the introduction. 2020. Free sample: PDF · EPUB
- 10.Your First Year in Code, Isaac Lyman: A complete guide for new & aspiring developers No sample: from the description and table of contents. 2022.
- 11.Zero To Code, Kevin Moore: How To Launch Your Career As A Software Engineer No sample: from the description and table of contents. 2022.
- 12.Resumes That Will Land You the Interview, Trantor Liu: An Easy to Follow Guide From the description and table of contents. 2020. Free sample: PDF
- 13.The Enterprise PM Interview Playbook, Anusha Ravi: A simplified interview guide for Enterprise PM's No sample: from the description alone. 2025.
- 14.What Every IT Business Analyst Should Know, Riyaz Millwala From the description and table of contents. 2025. Free sample: PDF
- 15.
- 16.Time Management for Software Developers, Sandor Dargo: Your Playbook for Deep Work and Direction No sample: from the description and table of contents. 2025.
- 17.Staff-Level Testing Roles, Jesper Ottosen: [ A Path for High-Level Testing Contributors ] From the description and table of contents. 2026. Free sample: PDF
- 18.The Entrepreneurial Employee, Pim Elshoff No sample: from the description and table of contents, which marks one section as unwritten. 2020.
- 19.The Manager's Manual, Keyvan Akbary, Félix López, Alvaro Salazar: A practical guide for Engineering Management No sample: from the description and table of contents. 2021.
- 20.The Engineering Protocol Stack, Guillem Fernandez: A Layered Model for Engineering Leadership No sample: from the description and table of contents. 2026.
- 21.Habits that Ruin your Technical Team, Marcus Blankenship: Pitfalls and solutions for Technical Managers No sample: from the description and table of contents. 2018.
- 22.The Agile CIO, Todd A. Jacobs: Redefining IT Leadership in the Modern Enterprise, 2017 Edition From the description and table of contents. 2017. Free sample: PDF · EPUB
- 23.A Practical Introduction to Coaching, Heidi Helfand: For Software People No sample: from the description and table of contents. 2019.
- 24.Hiring Developers, Stephan Schmidt: Select the best developers No sample: from the description and table of contents.
- 25.Building Dev Teams For Tomorrow, Muthukumaran Navaneethakrishnan, Prabagar Ganapathy : Always Two. AI-Powered. Future-Ready. From the description and table of contents. 2025. Free sample: PDF · EPUB
- 26.Leaving the Rat Race with Python, Finxter, Lukas Rieger: An Insider's Guide to Freelance Developing From the description and table of contents. 2021. Free sample: PDF
- 27.I Am a Developer Advocate, Andrea Chiarelli: Personal notes on developer advocacy No sample: from the description and table of contents. 2025.
- 28.Transitioning to Project Management, Adam Russell: Unlocking Your Potential with Transferable Skills and Practical Strategies No sample: from the description and table of contents. 2024.
- 29.Conferences for Introverts, Alan Mendelevich: Stop looking at your shoes and thrive in the world optimized for the other half No sample: from the description and table of contents. 2017.
- 30.10 Days to Better Networking, Daniel Scheufler No sample: from the description and table of contents. 2025.
Further reading
Other books in the library on neighbouring ground, not cited above.
- Cloud Computing for Data Analysis, Noah Gift: The missing semester of Data Science Cloud computing for people doing data science and machine learning. 2021.
- The Agile Coaching DNA, Manoel Pimentel Concepts and techniques for agile coaches helping organisations to change. 2019.
- The Visual Coach Handbook, Zhi Lee: Inspiring visual approaches for getting people from A to B Hand-drawn templates for coaching conversations, meetings and workshops. 2026.
- CoachRetreat, YvesHanoulle, Oana Juncu, idetido, Ilan Kirschenbaum A handbook for organising a day of coaching practice in a fixed format. 2020.
- Create your own manifesto, YvesHanoulle, Nele Van Beveren A workshop in which a team writes its own manifesto of working values. 2024.
- Sticky Situations, Sarah K Peck: Word-For-Word Scripts You Can Use To Get Out Of Almost Any Situation Word-for-word scripts for awkward conversations; in progress. 2020.
- 100 Patterns For Success, Bill Keck About a hundred and ten short named patterns for programmers and founders. 2017.
- No One is Coming to Save You, Stuart Young, Dave Prior: The Power-Ups to Help Surf the Chaos Human skills for working life in uncertain times, the rise of AI included. 2025.
- Kill The Good Options, A. C. Weishaupt: To Make Space For The Great Ones On dropping good commitments to make room for better ones. 2026. Free sample: PDF
- What to Code, Finxter: The Indie Hacker's Guide to Finding Profitable Micro-SaaS Ideas in the Vibe Coding Era Choosing what to build when building software has become cheap. 2026. Free sample: PDF
- Stop Facilitating, Start Leading, Tristan Libersat: The Scrum Master's Path to Value Flow Management How the Scrum Master's role could change from running meetings to owning the flow of delivery. 2026. Free sample: PDF · EPUB
- The AI-Powered Freelancer, Alex R. Insight: Master the Essential AI Toolkit to Double Your Income and Reclaim Your Time. A short guide to generative AI tools for freelancers. 2026.
- AI Money Systems, Finxter: The Finxter Playbook for AI-Driven Wealth Eight ways for an individual to earn with AI, each set out as a repeatable system. 2026. Free sample: PDF
- 10 Days to Better Presentations, Daniel Scheufler Ten days of small exercises for giving better presentations. 2025.
- Yoga for Public Speaking, Margie Newman: An Embodied Approach to Mastering Your Onstage Presence Breathing, movement and mindfulness practices for steadier public speaking. 2022.