I'm Joining Webflow

Jan 31, 2026

Oh hey, who was two thumbs and isn’t unemployed anymore? I’ve accepted an offer to join Webflow as a Senior IT Systems Engineer, Collaboration Technology. I start on 2/2.

That is a very corporate-sounding title, so the plain-English version is this: I am going to be working on the systems people use to collaborate and get work done, with a heavy focus on the Atlassian ecosystem. Jira, Confluence, workflows, integrations, governance, support, the usual beautiful mess. I’m also going to be involved in evaluating and onboarding new collaboration tools, helping scale IT processes, and moving more work from one-off support requests into repeatable, project-based systems: ITSM, documentation standards, change management, that sort of thing.

If you have read the last couple of career posts here, this is pretty much the shape of role I was hoping to find.

A few months ago I wrote about trying to figure out what to call the work I do. Solutions Engineer? Solutions Architect? Atlassian SME? Application Engineer? Annoying Jira wizard who asks too many questions? All technically possible.

Then I wrote about how I approach that work: start with the workflow, not the tool. Figure out what people are actually trying to accomplish, where the process breaks down, and how the system can make the good path easier without turning everyone’s day into an approval-chain scavenger hunt.

This role feels like a direct continuation of that thread.

Why This Fits

I have spent a lot of my career sitting in the weird middle space between technical systems and human process.

On one side, there is the actual platform work: Jira administration, Confluence structure, automation, permissions, integrations, data hygiene, migrations, and all the little edge cases that make enterprise collaboration tools either quietly useful or wildly irritating.

On the other side, there is the harder part: understanding how teams actually work. What do they need to track? Who needs to approve what? Which parts of the process are real risk controls, and which parts are just ceremony that nobody remembers creating?

That second part is the part I keep coming back to. The tool matters, obviously. You still need someone who knows how to build the thing correctly. But the difference between a good system and a bad one is usually not whether someone knows where the Jira workflow editor lives. It is whether they understand the actual work well enough to design something people will use without hating it.

That is what I am excited to do more of.

The Atlassian Thread Continues

I did not set out to become an Atlassian person. I sort of fell into Jira early in my career, got good at it, and then discovered that the interesting part was not memorizing every admin screen. The interesting part was using those tools to make messy work legible.

Over time, that turned into a pretty specific skillset: translating vague business needs into workable systems, keeping those systems from becoming unmaintainable, and helping teams find the right amount of process. Enough structure that things do not fall apart, not so much structure that the process becomes the job.

Webflow’s collaboration technology role lines up with that really well. It is still close to the tools I know best, but it also gives me room to work on the broader systems around them. That is exactly where I wanted to go next.

Gratitude and What’s Next

I am grateful for the people who helped me get here, especially the coworkers, managers, friends, and former teammates who talked through roles with me, gave feedback, referred me, or just let me think out loud while I tried to explain what kind of job I was looking for.

Job searching after almost a decade in one place was weird. Useful, but weird. It forced me to describe my work in a way that made sense outside of the specific context I had been living in for years. That exercise alone was probably good for me, even if I complained about it the entire time like a well-adjusted adult.

For now, the plan is pretty simple: start the new role, listen more than I talk, learn how Webflow works, and figure out where I can be useful.

I am excited. A little nervous, obviously. But mostly excited.

Until next time!