Whelp

Jun 1, 2026

Well, this is not the follow-up post I wanted to write.

At the end of January, I wrote that I was joining Webflow as a Senior IT Systems Engineer, Collaboration Technology. Unfortunately, I was part of the Webflow layoffs announced last week, so I am back on the job market.

Not ideal. Do not recommend.

Webflow announced the restructuring publicly in Linda Tong’s post about evolving Webflow for the agentic web. The short version is that the company is reorganizing around a more focused strategy for AI-driven marketing teams, and many Webflow employees were impacted. MSN also covered the layoffs, if you want the outside-news version.

I am not going to do the big public post-mortem thing. I was only there for a few months, and layoffs are complicated. I will just say this: the people I worked with were kind, sharp, and trying very hard to do good work in a very weird moment for the tech industry. I am grateful for the chance to work with them, even if it was much shorter than I expected.

So, What’s Next?

The short version: I am looking for my next role.

The slightly longer version: I am looking for work in the same general lane I have been writing about for the last year. Atlassian administration and engineering, collaboration tooling, internal systems, workflow design, ITSM, knowledge management, and the weird middle space between technical implementation and business process.

Basically: if your teams are drowning in Jira tickets, Confluence pages, approval flows, half-documented processes, and tooling decisions that seemed reasonable three years ago but now make everyone sigh loudly, that is my neighborhood.

I am especially interested in roles where I can do some combination of:

1. Design and improve Jira, Confluence, and Atlassian-based workflows.
2. Translate vague business needs into systems people can actually use.
3. Help internal teams scale without turning process into a punishment.
4. Own collaboration tooling, governance, documentation standards, and ITSM processes.
5. Work with engineering, product, IT, security, and business teams without needing every conversation translated through three layers of ticket comments.

Titles vary a lot, which is part of the problem. Solutions Engineer, Solutions Architect, Atlassian Engineer, Collaboration Systems Engineer, Business Systems Engineer, IT Systems Engineer, Application Engineer. I care less about the exact title than the actual work.

The Annoying Part

The annoying part is that I was excited about this job. I still think the role made sense for me, and I still think the direction I have been moving professionally makes sense. This does not really change that. It just means the timing got very stupid, very fast.

I am trying to take the useful lesson without pretending this is secretly great. Sometimes a layoff is not a beautiful pivot point or a hidden blessing or whatever LinkedIn phrase we are using this week. Sometimes it is just a layoff. You update the resume, send the messages, make the spreadsheet, and start having the same introductory conversation several dozen times.

Again: not ideal.

But I know what kind of work I am good at, and I know what kind of problems I want to solve. That part is at least clearer than it was the last time I started job hunting.

If You Know of Anything

If your team needs someone who can own Atlassian systems, untangle messy workflows, build sane internal processes, and explain technical tradeoffs to non-technical stakeholders without making everyone miserable, please reach out.

Until next time.