layout: markdown_page

title: "Brie Carranza's README"

๐Ÿฆ„ Brie Carranza's README

Brie Carranza, Staff Support Engineer (AMER) This page is intended to help others understand what it might be like to work with me, especially people who havenโ€™t worked with me before.

Itโ€™s also a well-intentioned effort at building some trust by being intentionally vulnerable, and to share my ideas of a good working relationship to reduce the anxiety of people who might be on my team. Please feel free to contribute to this page by opening a merge request. :rainbow:

About me

๐Ÿ‘‹ Hello, world! My name is Brie Carranza. I am a Staff Support Engineer at GitLab. I joined GitLab in May 2020, just after GitLab 13.0 was released. ๐ŸฆŠ ๐Ÿ’œ I've been a member of the GitLab Support team during all my years at GitLab. Every year, I reflect a bit:

I spend my time working to understand the cause(s) of unexpected behavior and helping folks make the best use of GitLab. I fell in love with GitLab as a product before joining the team so it's super fun and exciting to get to help others experience how cool and fun it can be! I enjoy learning, thinking, writing and discussing general purpose troubleshooting principles.

Prior to joining GitLab, I worked in the School of Computer Science at Carnegie Mellon University for many years.

๐ŸŽฅ Videos

๐Ÿ”— Related pages

๐Ÿ›Ÿ How you can help me (help you)

๐Ÿ’ผ My working style

โœจ How I work and think

I am a 'perpetual learner'. I tend to value "academic" tools and find ways to incorporate these ways of thinking into daily work.

Eisenhower Matrix

I often find the Eisenhower Matrix useful.

What I assume about others

What I want to earn

[Consider 3-5 bullets on your goals for earning things like trust and respect, or a broader understanding of new topics. This enables others to understand what motivates you.]

Communicating with me

[Consider 5-10 bullets on your communication preferences. This includes traditional styles such as verbal, textual, and visual, but you are encouraged to be precise. You can mention things like routine, availability, your travel habits, etc. This helps others understand why you communicate in the manner than you do, and it enables them to tailor their communication in a way that resonates most with you.]

My preference for communication is via GitLab TODOs, Slack or email, in that order. I am very easy-going so feel free to disturb that order at your leisure.

๐ŸŽ—๏ธ I am to be responsive. Don't hesitate to ping me or DM me if you need something more quickly. Feel free to follow up.

When discussing technical components, I will almost always say yes to hearing more detail about what you are explaining to me. I always have more curiosity than I have time. I'll let you know if a conversation is too far in the weeds to be an effective use of time.


Words that are frequently used to describe me/my work:



Iteration is hard. I am newish to GitLab and am learning to iterate and assemble smaller scopes for work.

Eight months in: iteration ~~is hard~~ requires intention.

Two years in: iteration can be done. It requires intention. It's not easy. It sometimes feels like backward progress. It is worthwhile.

Almost four years in: iteration is really powerful. I'm getting better at it but I'll always back working on it.



Clifton StrengthsFinder

I completed the CliftonStrengths assessment in late 2023. I lead with Strategic Thinking. My top 5๏ธโƒฃ five strengths are Restorative, Learner, Intellection, Individualization and Harmony.

๐Ÿงญ Principles