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.
Using ChatGPT As A Composer
I’ve experimented with AI quite a bit over the last year. I’ve used it to try to train a model to adopt my specific document review approaches. I’ve used it to build a portal on the fly to manage document uploads. I’ve used it when allowed during coding interviews. I even used it to a degree when building the scaffolding I used for those coding interviews, including a basic code, API, and test project.
Where I was most resistant to using it, though, was in my composing. I want what I produce to reflect me, not a machine. That said, I’ve found a specific and effective use for ChatGPT, in spite of all the ads telling me to stop using it “like Google”, because that’s exactly what I do with it.
When composing, I used ChatGPT to unblock by having it hopefully coalesce Google searches I would have executed myself and had to sift through to arrive at an answer.
I am currently writing a symphony. My first question to ChatGPT was to outline a typical approach to a Baroque style symphony and how I should think about structure. That’s pretty basic.
But recently I was writing the second piece in the orchestral suite. It requires the second part of the piece to transition from D major to A major, and then close in D major at the end. I was really struggling based on my melodies and progressions to get from D to A without it feeling like it was absolutely dying to resolve back to the D major chord.
So I sent over a prompt:
Sadly my A section ends naturally on an A for a measure to an A7 for an extra measure before returning to D major. At the end of my second A section, how do I now get to A? I feel like just staying there won’t work. Can I shift to F# minor instead? Or is there a turnaround since this is supposed to transition keys to the major 5?
ChatGPT suggested two responses, which I tried.
Option A – Classic ii–V–I into A
Near the end of the section, let D go, and instead:Treat B minor as ii of A
E7 as V of A
Then A as I (new key)
Example last 3 chords of the section:B minor → E7 → A
Coming out of D‑world you can arrive on Bm very naturally (vi in D, ii in A),
Then Bm–E7–A is a textbook ii–V–I in A major.
You can still touch D before that (so it feels like you’re still in D), but your final phrase should clearly choose Bm–E7–A instead of A7–D.Option B – Use F♯ minor as a pivot (your idea)
Yes, you can go via F♯ minor: it’s vi in A and iii in D, so it’s a legit pivot.Something like:
… D → F♯m → Bm → E7 → A
In D: F♯m = iii, Bm = vi. Still sounds like D.
In A: F♯m = vi, Bm = ii, then E7 = V, A = I.
Both sounded pretty harsh, so I let ChatGPT know I wasn’t fond of either choice after giving each a listen. After doing the usual “Oh You Are Right” false praise that AIs love to do, ChatGPT offered a few suggestions, and in going through them I figured out why they weren’t working: the D natural in the suggested E7 chord was still pulling back to D major. Once I came up with my conclusion I let ChatGPT know.
Ok so this is what ended up working. The original turnaround at the end was 1 bar D, 1/2 bar Bm, 1/2 bar C#dim, leading into an F# minor, which is how this progression starts. I replaced that with 1 bar Bm, then 2 bars E without the 7; the D in the E7 was wreaking havoc with my ear.
And ChatGPT gave me positive feedback on why it worked.
That’s a very sensible fix, and it explains why your ear finally relaxed.
What you had before:
Old turnaround:
D (1 bar) → Bm (½) → C♯dim (½) → F♯m …
That strongly re‑stated D as “home” right before moving on, so anything after felt like it still wanted to resolve back there.What you changed to:
New turnaround:
Bm (1 bar) → E (2 bars, no 7) → F♯m …
Why this works:No strong D at the end
By removing that full bar of D, you stop telling the listener “we’re safely back at tonic.”
Bm → E already steers the harmony toward A/F♯‑world instead of D‑world.
Plain E instead of E7E7 (E–G♯–B–D) introduces a dominant‑of‑A feeling plus that D natural, which:
still evokes the original tonic D major in the background,
and makes the ear half‑expect A (and then D after that).
Using E major (E–G♯–B) without the D:
keeps the pull toward F♯m/A,
but doesn’t slam a dominant function in the listener’s face.
The result is more ambiguous / modal and less “I must cadence.”
Bm → E → F♯m is a smooth directional lineIn D terms: Bm feels like vi, E like a chromatic “brightening” step, and F♯m like iii/vi.
In A terms: Bm is ii, E is V, F♯m is vi; that’s all compatible with A/F♯ as a new region.
But because you don’t resolve E7 to A, the progression flows forward rather than closing.
So the new version:Stops reaffirming D right at the end,
Points gently into the new harmonic area via Bm → E → F♯m,
Avoids the D that made everything sound like “prep for a cadence.”
This is exactly the kind of local surgery you want in a modulation: same broad shape, but you trim out the one chord tone (D in E7, and the big D bar) that kept yanking your ear backward.
This is actually the critical bit that’s super helpful. While I don’t always adopt the suggestions, I have a concrete list of reasons why something worked or maybe didn’t, and a concrete list of options when I’m stuck that would have taken a while to pull together from searches if I couldn’t dig myself out on my own.
So, in this case, ChatGPT has become what AIs should be. A useful tool. But definitely not a replacement for the creative magic.
What I Would Look For In A Cover Letter
Recently I wrote about how my approach to cover letters changed during my recent job search. As part of that, I was asked what I would look for in a cover letter.
What I Look For
You’ve put the effort into writing a cover letter. Let’s make sure it delivers on that effort.
- Why You Want The Position
Clearly, everyone seeking a position would like a job for some reason. In this troubled job market, people need to be less selective. That’s understandable. But if you can come up with a compelling narrative for why you are interested, that’s a plus. I have a deep background in business marketplace search engines. If I am applying for a position oriented on search, I open with that relevant experience and my interest in those types of systems.
- Why You Will Succeed In The Position
These first three points are all similar, but have different framing. Take this opportunity to articulate why you will be successful if we hire you. It could be your experience, it could be your excitement about what the position will work on, it could be your drive and ability to learn, but make a case that you are going to succeed.
- What Are Your Relevant Strengths
You have strengths. You have experience. Not all of it will be addressable in depth on your resume. Take this opportunity to include a sentence or two for strengths that are directly relevant and will be helped by expansion. This is not for checklist items such as how much experience you have. For example, when positions mention strong communication or strength in mentorship, I use this opportunity to surface my bar raising roles at Amazon for both document writing as well as engineering manager onboarding.
- How Do You Communicate
Most resumes don’t have the space or the context to provide a chance to showcase communication skills. A cover letter provides a chance for you to show how you communicate, to surface your personality. I would not exclusively use AI for this reason; a seasoned communicator will know when you use it and will know it’s not representative of you.
- You Know Who We Are And What We Do
Hopefully you are interested enough to know who we are and what we do. Take this opportunity to tell the hiring manager what about the company resonates with you, and show that you are willing to take some initiative as you target your job search.
- A High Level Sense Of Who You Are
Inject some of yourself into your cover letter, so that the hiring manager can get a read on who you are. Hopefully my cover letter reads the way I want to come across in interviews, as a calm, confident, competent candidate.
What I Don’t Look For
There are things that I will not look for, or hold against a candidate. I don’t believe in mythical checklists or hidden gates that candidates need to be aware of. I’m a big fan of transparency, and won’t reject a candidate just because they aren’t aware of my preferences, especially if those preferences aren’t publicized.
- Personalization
I have seen suggestions that candidates should deeply research the personnel responsible for the position, including the recruiter and hiring manager. I have seen suggestions that cover letters that aren’t addressed to a specific person should be rejected.
Many positions don’t have this information, and even if they did, that has no bearing on whether or not the candidate is qualified for the position and falls into the category of hidden checklist. I address my cover letter as “Dear Hiring Manager”, and that’s acceptable in my view.
- Deep Research
It’s great if you understand what the position requires, have a general awareness of what the company does, and a general awareness of what the company values are should the company articulate them publicly. I don’t expect more than that.
- Appropriate AI Usage
AIs are writing cover letters a lot nowadays, along with other artifacts involved in the hiring process. I can generally glean whether or not writing was done with AI. If I feel like the entire thing is AI generated, that might give me pause; but I encourage candidates to use AI to clean up their writing and narratives.
- Perfect Writing Mechanics
I’ve been a Doc Bar Raiser for Amazon. I know how to evaluate writing mechanics. I can spot typos and other grammatical errors. I’ve also been in meetings where wonderful ideas or highly deserving promotion documents were picked apart due to writing quality. If a document is poorly written, that can be a red flag. But small typos and grammar errors, I’m inclined to ignore.
- Complete Qualification Match
Much like a screening interview, a cover letter is an introduction. The resume is the appropriate place to evaluate qualification matches; a cover letter should summarize why the candidate feels a resume review or a screening interview is in the best interest of both parties.
