jaime

README.md



Who Am I?
I'm a software engineer transitioning into my first Engineering Manager role, and I'm excited about this new chapter! I started my career in 2011 after graduating with a Bachelor's in Electronics and Computing Engineering from Guadalajara, Mexico, where I was born and raised.
My journey began at Intel as a software engineer, working on low-level projects like testing firmware for SSDs with Python, Graphics Card simulator development with C++, and various microcontroller projects. In 2014, I moved to Australia to pursue my Master's in IT at the University of Melbourne, which opened the door to web development. I discovered JavaScript and Node.js during an internship in 2015, then landed my first web development role at a health devices startup where I owned the entire backend implementation, deployments, testing, and infrastructure. This is where I fell in love with Go (even when Stack Overflow had no answers!).
Throughout my career across various startups, I've consistently been drawn to the management side of things. What motivates me every day is helping others, unblocking them, and helping people leverage their strengths to advance their careers. I'm driven by an empathetic approach to connecting with people - I like to listen, understand, and then help. Simply put, I want to help people and be useful in that way!
A bit about me personally:


🎵 I play basic piano (mostly classical pieces) and sing in a community choir called "Beyond the Bathroom"

🏐 I play volleyball weekly with Melbourne Spikers (local LGBT club)

🚴 I cycle when weather permits and love long walks in the city or along the beach

🎮 Gaming enthusiast with roots in 90s consoles (NES, SNES, N64) - currently playing on PS5 and Nintendo Switch (just finished Elden Ring Shadow of the Erdtree!)

🍦 My favorite ice cream flavor is plain vanilla (keeping it simple!)


Work Style
I like to plan things ahead but I've learned that too much rigid structure can be draining when things don't go as expected. My approach is to have a clear northstar while staying adaptable on how we get there.
Problem-solving approach: I'm naturally intuitive - I love puzzles in videogames and apply similar pattern recognition to work challenges. I enjoy collaborating with others and sometimes seek validation (something I'm actively working on to be more assertive and trust the process).
Daily rhythm: I'm a morning person who wakes up before 7am for gym sessions. I typically start my workday between 8:30-10am, depending on meetings and responsibilities. My most focused work happens in the morning when AMER is going offline and EMEA hasn't come online yet - that sweet spot of uninterrupted time.
Energy patterns: I don't work very well after sunset, but I'm flexible with my time. I prefer to consolidate most meetings into 2 days (ideally Mondays and Wednesdays) but can rearrange as needed.

Communication Style
Preferred channels: I strongly prefer written communication and work primarily through GitLab TODOs. I only skim email notifications, so if something needs my attention, please tag me directly.
Async-first approach: Being in APAC, I rely heavily on asynchronous communication. Please bear with me as I work through my to-dos - if you need something requiring immediate attention, reach out on Slack directly or in a channel.
Meeting philosophy: I try to keep my calendar up to date and I'm always happy to chat. Don't hesitate to put something on my calendar or message me on Slack - I'll get back to you ASAP! If you can't find a reasonable time for both of us, let me know and I can shuffle things around.
Scheduling requests: I'm flexible with my time, though I do have some commitments outside of work. For rescheduling meetings, I'd appreciate at least 24 hours notice when possible (emergencies are obviously different!).

Help Me Help You
I once read in the Software Engineering Guidebook: "Your manager is your best resource, and you should use them." Here's how to make the most of our working relationship:
Come prepared: Please bring items to 1-1 agendas so I can prepare efficiently for our meetings.
Be direct: I'm an open book - ask me about anything personally or professionally and I'll do my best to answer. Please be clear and direct when talking to me; I will always assume positive intent.
Feedback preferences: If you like receiving feedback, please tell me your preferences - how often, direct or more compassionate approach. If I miss something, please ask!
Status updates: I prefer async updates. Please leave an update when significant events happen. If nothing has changed, I'll assume the latest status remains the same.
When you're blocked: Please tell me:

What is your task?
How are you blocked?
What do you need?
How can I help?

Giving me feedback: If you have constructive feedback for me, please share it in a 1-1 meeting or through Slack privately so I can reflect and work on it.

Coffee Chats Welcome!
I like keeping in touch with people I've worked with, so you'll often find me in coffee chats. These are always flexible, so if you need to schedule time with me, please do and I'll figure something out. I always enjoy a chat, so don't be afraid to reach out!

This README is a living document as I grow into my Engineering Manager role. Please feel free to suggest updates or ask questions about anything here!