Archive
The Next Adventure
Yesterday, January 26, 2026, was my last official day as an Amazonian. I was impacted by layoffs in October 2025 after nearly eight years of successful delivery. The moment is bittersweet, as I’ve spent much of my time over this three-month transition period buried in job searches while trying to enjoy the holiday season in spite of the uncertainty. I’ve learned a lot over the last eight years, both what to do and what not to do, and I’ve worked with so many incredible individuals.
Immediately after the layoff occurred, I began looking for next steps. One of the more enjoyable aspects of my Amazon career was being a Document Bar Raiser. Giving back and helping so many people improve their writing was an amazing experience. I prepared a professional service, Hopeful Writing, to engage those who want to be better writers and offer professional help. I’m not sure if I’ll continue it or not if I were to get traction, but I wanted to be prepared in case I was not able to find a new role. Now that I’ve found one, I doubt I will engage much with this, except with interns or students.
That said, I’ve accepted an offer as Senior Engineering Manager at Atlassian, starting in mid-February. I’m super excited to work for Atlassian, and to continue to improve experiences for customers, developers, product owners, document authors, and anyone else involved in building something amazing for their customers. I wanted to find something I could focus on for the next several years, and I’ve been impressed with Atlassian for a while now and can’t wait to get started.
I’ll be posting more about my job search experience and reflections on this period of my life in the coming weeks.
My Resume Approach
Once it was clear I needed to find a new role, I took a hard look at my resume, which needed a refresher after my lengthy tenure at Amazon. With the advent of ATS scanning, AI, and the competitive job market, it was unclear what the ultimate purpose of my resume was. Was it to get past the technology-driven screening? Was it to meet some arbitrary format requirement? Was it to just “get in the door” and get a conversation with a recruiter?
The answer to this might have been “yes to all three”, but that’s just not my style. If I’m going to produce a resume, I want it to present me in the best possible light, and be reflective of my values and the bar I hold. My resume should make it clear who I am and what I can accomplish first. At some point in the process, a hiring manager or a recruiter is going to read it, and when they do, I want them to have a clear perspective on my career and value.
With that, I decided to ignore a lot of the conventional wisdom I’d received in favor of creating a resume that felt right to me. The risk of misrepresenting myself in two pages felt greater than the risk of going over page length to get the information correct.
First, I decided to create a template with the full list of skills, experiences, and education, which I would then adjust or trim down as necessary depending on the position. My goal was to be able to create a solid resume in the 3 page length range in just a few minutes. I also created a “standard” version of this template I could use for virtually any position if I didn’t want to tailor it. This was useful for such things as LinkedIn’s Easy Apply, which I did use early on in my search.
I separated management and engineering experience, treating them as equal yet different, which in my opinion, they are. This allowed me to call out the depth of my experience in each, and to list different skills for each. I took the time and space to explain details that are important for each item in the skill list. “Written communication” is great, but “taught more than 2,500 Amazonians effective writing culture” is more impactful and more in line with my overall impact. Nuance can be lost in a list of skills; “technical management” means different things if I’m running a team of 5 versus three teams of 8 each, and I can do both if necessary.
I did my best to get skills down to the first page, but always valued clarity over page length, so if things were really relevant, they didn’t come off even if page length was over.
I then followed that with my list of experience by company and role. For each company, I’d list 3-4 relevant projects, along with the role I played, regardless of title, the project, several bullet points, and the result. Many projects I played more than just the management role. When I was at CoStar, technical managers were expected to code half the time; in many of the projects there I was also the most experienced engineer and did a lot of the design work. So one of those projects would read like this:
Project: Land & Farm Data Imports
Team: Marketplace Verticals
Role: Technical Manager, Principal Engineer, Full Stack Engineer
- Managed the release of a new data import system supporting third party data imports.
- Designed high throughput system maximizing tracking, batching, and parallel execution, including more than 10 million property images
- Participated in implementation of the feature including administrative pages and performance monitoring.
Result: System supported continual import management of more than 750,000 land listing from external data providers
After my experience, I listed my degree. As part of my degree plan, I was awarded 18 certifications between 2012 and 2014. Few are relevant today, but if they are for a particular position, I will include them as part of my education.
With a template listing all the things, I can then make targeted adjustments based on the position’s requirements, often comparing them side by side to my list of skills. In most cases, I can get this down to 3 pages, sometimes 4, within just a few minutes. It was more important to me to have a solid case for getting a phone call that wasn’t just driven by ATS, and to make sure that I did not remove key skills just to satisfy page length.
To be fair, I did incorporate a lot of specific technical feedback I received. My current resume has no dates on it, on the advice that my capabilities were more relevant than timing. In cases where a cover letter was not asked for, and I felt a cover letter would help, I would insert a cover letter as the first page of the resume.
One might suggest this doesn’t fulfill the AI screening requirements, but I think it does. First, if skills are in alignment based on my comparison, that’s a good sign we’ll match. But second, most AI tools I’ve worked with require prompts or narratives, and my resume is richly narrative. I have no data on this, but I assume that if there are no hard page length restrictions, my narratives enhance my ability to match an AI tool.
An online version of this format, without projects and including dates, is found here.
I noticed an almost immediate increase in contacts once I implemented this format and shied away from the shorter, less accurate resumes I originally sent. I’m pretty happy now with how it presents me and will continue to use this as my search continues.
If you are currently looking for a new role, I wish you good luck!
My Cover Letter Approach
As I’ve been involved in my search for a new role, I’ve taken several different approaches to cover letters. I’m going to outline what I am currently doing and my rationale for doing so.
One of the challenges of preparing resumes or cover letters has been the depth and breadth of my experience. I spent time as a long term engineer, as an engineering manager with a high percentage of hands on coding expected, and as an engineering manager not expected to code but to be firmly involved in technical processes and decision making. That can make things like “tailored” details on resumes difficult. I felt that it was difficult to adequately state what I perceive my value to be.
I wanted to arrive at a repeatable, scalable process that would take just a few minutes for each job posting. I wanted the documents I prepared to adequately represent my career and qualifications. I needed speed and ease as I, like many of my colleagues, cycled through hundreds of applications.
As of this writing, it’s up for debate if my approach will ultimately be successful. I do think it has managed to get the attention of quite a few companies that might not have otherwise noticed. Responses to those applications seem to be better. During several interview cycles my cover letter was referred to as a resource for the conversation.
There were several general sentiments I heard when this journey began. There was a predominant feeling that cover letters are never read. It was suggested that even though they weren’t read, they couldn’t necessarily hurt. They could be viewed as a tiebreaker should recruiters or hiring managers be choosing between strong candidates in this highly competitive market.
After a couple of weeks of choosing to ignore cover letters, since the prevailing wisdom is they were ignored, I actually decided to completely change direction. If cover letters are never read, except in rare instances, I could do what I want with them.
I chose to use my cover letter to surface all of the information I couldn’t fit on the resume I was including with my application.
I recognize this flies in the face of conventional wisdom, but, hey, if no one’s going to read it….
¯\_(ツ)_/¯
Thus, I went from no cover letter to a 9 pager that includes:
- Page One: A targeted cover letter, with mostly templated information, summarizing my career highlights and the value I bring. It contains a paragraph introducing me; a paragraph on my general philosophy; a paragraph on what I’ve done as a manager; and a paragraph on what I’ve accomplished as an engineer. Within two or three minutes, I can adjust content, add specific information, and optimize for the position I am interested in. A variation of that cover letter can be found here.
- Page Two: A portfolio of the websites, systems, and companies that I have had an impact on. Many times candidates are asked for this portfolio, and I automatically include it in my cover letter, just in case someone opens it and decides to scroll past the first page. That portfolio can be found here.
- Pages Three through Nine: A list of the critical projects I’ve delivered, and my role in delivering them, along with the results. I’ve missed a few here and there and update this list as I recall things. For example, in a recent interview I talked about a feature I built into one of my web portals that would include the entire logging history of the system into the web page, piggybacking and enhancing Microsoft .NET’s native tracing feature. I’m going to add that to the list soon.
Having the list ready to go gives me a couple of other efficiencies.
First, if a company doesn’t ask for a cover letter, and I really want to send one, I’ll simply include it as the first page of my resume by copying page one from here and adjusting it for those needs.
Second, I have my list of projects ready to go, already in consistent format with my resume. I then pick and choose the relevant projects from this list to include on the resume I will send based on the company’s requirements.
So, while I am tailoring my resume, I’m not rewriting narratives or reorganizing. I can be ready to apply to any position within 5-10 minutes with a consistent, complete narrative.
If you are also searching for a new role, I wish you good luck.
Be welcome and true.
Rob Hope 