Like many professionals, I was actively seeking my next big opportunity as a Technical Writer. During a routine LinkedIn job search, I stumbled upon a golden find: the Senior Technical Writer role at GitLab. As a technical writing enthusiast (and a coffee lover), this role felt like the perfect match. Collaborating with engineers? Check. Working with a docs-as-code approach? Double check. Becoming part of a large open-source project? I was all in! Sign me up!

The job description for the Senior Technical Writer role at GitLab reflects their values of transparency and collaboration. I was particularly impressed by their emphasis on the docs-as-code approach, working closely with engineers, and the focus on continuous improvement. The mention of the GitLab Handbook stood out—GitLab’s open, well-structured documentation practices and commitment to fostering a transparent and inclusive work culture truly set them apart. It’s clear that GitLab gives technical writers the credit they deserve and values their contributions to the company’s success.

While exploring their Handbook for Technical Writing, I was amazed at the level of transparency. GitLab shares its roadmap, detailing all epics and issues, whether open or closed. The Documentation Style Guide, Public Training, and clear breakdown of responsibilities showed how organized and open the company is about its processes. This level of transparency truly reflects GitLab’s values.

Despite the alignment with my passions, I was informed on December 19th 2024  that I wasn’t selected this time. Cue the heartbreak music! Jokes aside, while the rejection stung momentarily, it also sparked a period of reflection and learning.

Why GitLab Got Me Excited

GitLab isn’t just any tech company. They’re at the forefront, leading with their AI-powered DevSecOps platform. Over 100,000 organizations trust GitLab—a testament to their innovative and forward-thinking approach. They don’t just solve problems; they anticipate future needs. Imagine combining creativity, collaboration, and cutting-edge tech, and you have GitLab’s secret sauce.

Here’s why the role stood out for me:

• Docs-as-Code Philosophy:
  Managing documentation as code? I’ve been there; I love that. GitLab’s docs-as-code approach resonated with me because it emphasizes creating documentation in tandem with the development process, keeping it agile and efficient.
• Collaboration Across Teams:
  Working with engineers to refine docs processes? Yes, please! The close collaboration GitLab encourages between technical writers and engineers is exactly the kind of environment I thrive in.
• Commitment to Iteration:
  GitLab’s commitment to continuously improving documentation aligns perfectly with my values. Crafting clear, user-friendly content isn’t just work for me—it’s a mission.
• Respect for Technical Writers:
  GitLab’s handbook clearly defines the role of technical writers, showing how integral we are to product development. This clarity and acknowledgment of the profession is inspiring. It’s something other companies should take note of and give technical writers the credit they deserve for their essential contributions.

Lessons Learned from the Process

While I didn’t secure the role, I gained valuable insights:

• Gratitude for the Experience:
  Just applying to a company like GitLab, with its global impact and transparent values, felt like a win.
• Opportunities for Growth:
  I’m not sure what went wrong this time, but I’m committed to figuring it out. I’ll dive deeper into open-source contributions and level up my skills.Hey, GitLab, if you’re reading this, feel free to tell me how to improve!
• Resilience is Key:
  Every “no” is just another step closer to a “yes.” It makes the journey more interesting, doesn’t it?

What’s Next?

This experience has sparked some big plans:

• Enhancing My Skills:
  Taking my expertise in Git, CI/CD, and user-focused writing to the next level.
• Contributing to Open-Source Projects:
  Time to roll up my sleeves and give back to the community while learning from the best.
• Keeping the Momentum Going:
  Rejections won’t stop me. I’ll continue chasing opportunities that align with my passion.

A Note of Thanks

Thank you, GitLab, for the opportunity and for setting the bar high. Your transparency, collaboration, and inclusivity are values every company should aspire to.

While this chapter didn’t have the ending I hoped for, it’s far from the end of the story. I’m excited to keep following GitLab’s journey and staying connected through social media platforms.

Final Thoughts

To anyone out there eyeing their dream job: go for it. The experience is worth it, whether you land the role or not. As for me, I’ll keep building, learning, and growing.

To GitLab, thank you for raising the bar. I look forward to learning and evolving, and perhaps our paths will cross again—this time with a positive outcome.

Here’s to perseverance, growth, and staying curious!