Archive

Posts Tagged ‘resumes’

Tactical Reflections – Job Search 2025

February 12, 2026 Leave a comment

I wanted to summarize some tactical thoughts I had as I searched for a new role at the end of 2025 and beginning of 2026. I won’t name names or companies here, because the idea is not to shame any particular entity. That said, if people can learn from my experience, that would be a positive. I’ll address my emotional thoughts as well as the interview experiences themselves in other posts.

I should start by saying I’ve hired many engineers throughout much of my career. I’ve lost count, but it’s more than a hundred. I’ve also hired engineers at Amazon, and participated in over a hundred Amazonian interview loops, for my team and on behalf of other teams, at every level from junior developer and intern to senior engineer, product manager, technical project manager, and engineering manager.

Valuing the Candidate Experience

With the exception of a few companies, the candidate experience bar no longer exists. This shouldn’t come as a complete surprise to anyone, but having been on both sides, I found the experience to be mostly unpleasant. I expected it from the discussions on social media, so I made sure as much as possible to dismiss the lack of response as part of the process. Becoming discouraged would have not helped in any way.

As a result, I didn’t spend a lot of time reflecting on the experience if the company did not reach out to me. If they only sent a conciliatory email saying my resume had been reviewed and I was not chosen, I also did not reflect much on those events once I felt I got my resume formats under control.

Two things really caught my attention from a candidate experience standpoint.

When I was a hiring manager, when I found the right candidate, it was time to move and get that person in their seat. Notice I did not say the perfect candidate. The first right candidate. The number of reposted jobs in the market indicate that companies have become very risk averse, or have decided to look for the perfect candidate, and that’s translated into a lack of urgency that is honestly disturbing. As a hiring manager, I have a team that needs to get stuff done. I’ve seen companies waiting months for the perfect person rather than getting value out of an excellent person. In one case, I had passed all the interviews, and the company was still hesitating. I sent a polite email to my recruiting contact basically saying that I was ready to accept an offer, the role seemed like a good fit, interviews had passed, so if they were to extend the offer I’d accept. They sent me a note the next day removing me from consideration. Companies are letting perfection get in the way of progress, and the lack of urgency is showing. As a result, after the first three weeks I stopped applying to any positions I found that had been reposted.

I withdrew myself from candidacy several times during my search. In all cases but one, there was a clear misalignment in some capacity, and I felt I would not be good for the role. That’s expected and it’s necessary to have an objective viewpoint on your own appropriateness for a position.

However, one company’s screening call was so horrible that I withdrew on the spot. While I can’t guarantee it, it seems as though the person doing the call was a contractor. They were short-tempered, monotone, appeared to be reading from a script, and automatically shut down any question or nuance in any answer given. For example, when I was asked for a start date, and I reasonably mentioned that would be contingent on offer timeline, they interrupted me mid-sentence and again demanded a start date. Similarly when I was asked about compensation, my question about compensation components and equity structure was also immediately shut down. The interviewer closed the conversation by saying they’d pass my information on to the hiring manager. I went into their jobs portal and withdrew.

There Are Quality Recruiters and Companies Doing The Best They Can

With the exception of that one screener I mentioned, the recruiters I did speak to were excellent, and they represented their companies well. Several went above and beyond to ensure transparency of communication and alignment of expectations. One went so far as to call me to ensure that the holidays would not impact their ability to extend an offer if a hiring decision was made as the holiday period impacted people’s availability.

In one instance, a no hire decision was delivered via conference call, in person, promptly. While I was not selected, I was impressed with the company’s commitment to their candidates.

The other no hire decisions were delivered with less personal notes or tone, but I remind myself that there are now legal ramifications to how information is delivered. I was not ghosted after getting into hiring pipelines, but a couple of the no hire decisions were odd and abrupt, at a time I was expecting to discuss an offer. A few other companies might have ghosted me after final interviews, but I was diligent in following up and asking for next steps. The lack of feedback in these situations is frustrating to be sure, but having been a hiring manager I understand it.

The one use case where the lack of feedback has a direct impact is with companies that follow a model where you can only reapply to other positions after six months, or possibly even a year, has elapsed. In theory this allows the candidate time to address any perceived gaps. In cases where there were missing data points, or spots where a particular bar was not quite met, offering a chance to reapply after growth has occurred doesn’t really help if feedback is not provided, because gaps can’t be perceived with any accuracy. Many companies do this as part of their process.

Companies Don’t Know What They Want

I’ve been an engineering manager for more than 12 years. With that, I can generally get a sense of how teams are running based on the information I can ascertain during an interview. Two things stood out to me as I cycled through the process.

In some cases, companies don’t understand what a healthy engineering culture looks like. This surfaces in topics like their approach to operational excellence, their perspective on support or on-call rotations, and their approach to collaboration. In one instance, I went through seven interviews for a company. The recruiter, and an “advisor” that I had a chance to speak with, both stressed leading with empathy as a key component of their culture. It appeared that their interviewers did not share their sentiment, as none of them asked me to introduce myself, and one of them actively interrupted me almost at every step of every answer to keep the process moving.

Some companies that are growing fast and trying to scale either personnel-wise or technically don’t really know what they are looking for from a skills or experience perspective. This leads to some difficulties in things like a proper job description, or a proper evaluation of skills. One company advertised for an engineering manager but really wanted a senior engineer that could lead projects. Another was reimagining the engineering manager as more of a hyper-technical TPM or operations role. Others weren’t sure how stable the team size would or should be. When that’s combined with either leadership that doesn’t really understand how engineering works, or with an unhealthy culture, getting to a hire decision becomes very difficult.

In these cases, I tried to ask open ended questions when my time to ask was provided, but also looked closely at the questions I was being asked. I paid particular attention to the types of challenges the interviewer was referencing. In situations like this I seek to remove as much ambiguity as possible about the role and the environment, while still presenting myself in the best way possible.

Managing Applications, Resumes, And Cover Letters

I’ve previously posted about my adjustments to my resume and my change in cover letter approach. I won’t go over those again here, other than to reiterate that I eventually decided on formats and approaches that were right for me, along with my background and experience. I think one should be happy with how they represent themselves to prospective employers should a human actually read what one produces.

I used Teal’s free job tracker to manage my applications, and it worked mostly well. The one gap that I found, but did not explore too much, was I could not see a clean way to track applications through statuses, meaning I could not filter by applications that were once in Interviewing but were not any longer. Other than that, it was reasonable, and the integration between their browser extension and job application sites was mostly well done.

I put up the famed green #OpenToWork banner on LinkedIn almost immediately. I’m not sure it made any difference in the early stages, and there was debate about its effectiveness as well as possible negative outcomes by using it, such as companies not wishing to hire people who were unemployed, or giving up leverage during the offer stage. After some consideration, I took the banner down publicly, choosing to leave it up only for recruiters. I have no way of gauging its impact on my job search, but I felt vaguely better not having it on my profile.

LinkedIn’s notifications systems have degraded considerably. There are noticeable delays, sometimes hours, between when an action occurred and the notification arrived. I am repeatedly reminded to accept a connection request that I had accepted hours before. Even the job search alerts seem less relevant time wise. I’m going to assume it’s a scale thing given the traffic likely on LinkedIn at the moment.

Referrals Ultimately Made The Difference

My ultimate success story would not have happened without a timely and unexpected referral. I think they remain the best way to get in the door. That said, I do think my resume adjustments had an impact on response times, and were helpful in landing the other interviews I participated in.

Results

Overall, I applied to 241 positions over close to four months.

StatusTotalPercentage
No Response15062.2%
Rejected without Interview7631.5%
Withdrew during screening41.6%
Interviewed114.6%
Interview: Did not make final round52.4%
Interview: Made final round52.4%
Offer accepted10.4%

Categories: Career, LinkedIn, Work Tags: , , , ,

My Resume Approach

January 12, 2026 1 comment

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

January 8, 2026 2 comments

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.