Skip to main content

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months.

I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there.

My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains. We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks. 

And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes. 

At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on Git and continuous integration, and coaching them on mediation, trustteam worklistening and more.

This kept me busy for the last two years. My team grew from a team of 8 into a business unit with over 40 people. Teams have grown and split and grown and split again. I've facilitated and led more retrospectives, virtual team days and workshops than I can count, some on-site in Cologne and during one team-week in Prague, but mostly distributed from as far west as California, across Europe and as far east as Vietnam.

Through this time, a feeling grew that I was approaching a crossroads for my own career.  

The natural path was for me to continue developing as a coach to higher levels. I thought this was what I wanted for a long time, but the further I went down this path, the less time I had for software engineering and I missed it more and more. 

At the same time, I felt my impact and contribution as a coach was falling below my personal potential. I realized I wanted be a software developer again, with coaching as a my secondary proficiency rather than the other way around.

One option would've been to find a more technical role within eyeo, but I wasn't able to find one matching the kind of backend/server-side development work I'm experienced with and interested in.

So I began to search outside of eyeo. I activated my network and ramped up a speedy but structured process of applying to a set of companies in parallel. Long story short, I'm going back to software development, and I will again be working out of an office in Bonn, as soon as the conditions allow for it at least. More about that in a future post.

It's definitely been a wild ride at eyeo, and I'm grateful to all the people I worked with there and learned so much from. I hope they succeed on their mission for a safer and saner Internet, as that will benefit us all.

Comments

  1. A nice read! Wish you all the best and good luck! We should hook up and discuss experiences soon! :)

    ReplyDelete
  2. It was a great time. thank you for inviting me to be part of it. all the best for your next challenges!

    ReplyDelete
    Replies
    1. Thank you, Olaf! I'm sure our paths will cross again :)

      Delete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp

Joining eyeo: A Year in Review

It's been well over a year since I  joined eyeo . And 'tis the season for yearly reviews, so... It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling. Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes: How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies wit