Tech Job #2

Today marks the end of my third week at my new job (Technical Program Manager – Mobile) @ Pinterest.  It coincides with May Day and a Twitter stream today about #talkpay which was triggered by an article by Lauren Voswinkel over on Model View Culture.  The hashtag comprises of people “outing” their salaries over the years, location, levels of training, job titles, and a variety of other factors.

My participation was as follows:

For people who have also class-jumped or who understand what it’s like to live on social assistance or other low income realities, you will know from the above that it was not easy to leave my first ever well-paying, benefit-having, valued-for-your-knowledge, professional job.  But I did.  I took a leap of faith (and a strong referral) and turned it into my second ever well-paying, benefit-having, valued-for-your-knowledge, professional job.  ALMOST a pattern here…if I could only put aside impostor syndrome for a second and believe that I have transferrable skills and marketable ones to boot.

Anyway, the point of this blog post is to document for myself the differences now that I am in a new job and have gotten a bit of distance from the old one.  It’s important, also, to note that I am now able to reflect on my past 6 years as being a job.

Key areas I want to cover at this stage of being only 3 weeks in are recruiting, onboarding,  and culture. Here we go!

Recruiting

Mozilla got me through an internship and I left said internship with a job offer for when I completed my final year so I never did the all-day panel of interviews or any sort of salary negotiations.  I took what I was offered (because it was AMAZING) and I was quite happy about it.   Being ‘recruited’ by Pinterest was a wonderful experience.  I got to come in for the day and interview with 6 different people from various areas I was going to work with (iOS/Android engineers, product managers, and then a ‘culture fit’ interviewer that was just about the happiest person I’ve ever met).   In retrospect I worried they were easy on me because I was a referred candidate.  At some point I should ask them if that’s the case.  On my end I felt like it was all too easy.  I had some conversations, I asked some questions, I learned a ton about what they were doing and how different teams within the org operated, and then I went home with a nice notebook.  It didn’t feel stressful and shouldn’t interviewing for a job be stressful?  I suspect my experience was more laid back because I was coming from a place of already being employed and so I didn’t really need the job but I was curious about it and was being diligent about ensuring it would be a good fit for what I wanted to try next.  It was. I’ve read a few things about salary negotiations now and so for this job switch I tried out the advice. I’m quite pleased that it worked and felt good to do if only to test out the advice I’ve been giving others over the years but have never gotten to try.  The rest of the process was smooth and everyone had excellent communications – just the right amount of checking in and communicating status.  I appreciated that my Permanent Resident status coming in a week late, pushing out my start date, didn’t cause any problems.

Onboarding

Apples to apples – Pinterest is winning big time here.  At Mozilla new hires are introduced at an all-company meeting and then they are off with their team learning the ropes for their jobs.  We had an onboarding portal (I checked it out last year when my team had a new hire) and it contained some videos and wiki pages, a bit of direction for weekly tasks to accomplish.  While I know that it took a lot of work by some amazing people just to get that much set up, Pinterest is really firing on all cylinders when it comes to integrating people into the company.  They do a 3 week process where in the first week  you and your cohort spend 2 full days together being addressed by various company areas of importance to the larger goals and mission – it’s just the right mix of immersion and indoctrination – meanwhile you’re becoming familiar with, in my case, 17 people who will always be familiar faces to you going forward regardless of the diversity of work areas you’ll be in later on.  They also have 101/bootcamp classes over the next week or two to get folks on the engineering side learning all the tools, data, systems that are currently in place so that you’re not so green when you move into the next stage:  fixing some bugs.  Mozilla should really consider doing this sort of bootcamp, get new engineers to fix bugs from various parts of the code base as a way to learn how the whole picture works before going deep in their assigned areas.  Finally, at the end of your first week you are introduced to the whole company as a cohort and you must speak in front of everyone at the Q&A that happens on Friday afternoons.  At that point you and your cohort have bonded and you design and lead the theme for that week’s happy hour – all these little things give you tangible experiences to reminisce about as you go forward and that means a lot when trying to integrate into a 500+ person org.

Culture

Oh this is the big one, isn’t it?  This is the all-important catch-phrase of the knowledge worker class.  What is the culture? Are you a good culture fit? Here’s the thing:  when I first joined Mozilla the “culture” wasn’t a thing that was being discussed and analyzed yet.  I was excited to be part of a movement, a community, an ethos, and a politic of open-ness/transparency and general things do-goodish on the Web.  Culture as it is currently examined came later than my start date.  It came in the form of starting Homozilla, a mailing list for queer employees and their allies because I was starting to feel isolated not knowing if there were many other people at Mozilla who were also queer.  I was happy when I kicked that initiative off and there were all sorts of people that I never would have pegged as being LGTBQ.  It also came up when a handful of paid and unpaid contributors started highlighting awareness of diversity and inclusive behaviour in Mozilla communities.  I did a lot of work on that issue and put a lot of my ‘extra’ time into trying to drive materials and discussions around how Mozilla could be a strong player in encouraging, retaining, and promoting a welcoming culture.  I also put a lot of time and energy into building out opportunities for Mozilla to be a leader in educating and onboarding new contributors in more varied spaces – LGBTQ youth, lower income, PoC, any community that wanted to learn more about how to develop or integrate tech into their activism and community-building initiatives. Sadly, I don’t know how successful I was because without me driving them, those partnerships are not carrying on.

I’ve only been at Pinterest for 3 weeks but in that time I’ve learned that there is already a queer employees group (yay, I don’t have to create it!), there are already people working on diversity and inclusion at a level that surpasses our fledgling efforts at Mozilla (they have executive-level support and are building out programs and recruiting efforts in measurable ways), and there have been several instances where I’ve been pleasantly surprised at the positivity and open-ness to change/build/grow whatever is needed to support employees.  Example:  I emailed the workplace team about our new building’s plans to have non-gendered washrooms on one of the 3 floors – I asked if that would be possible to have on all floors – and the response was quick, warm, and welcoming of the feedback as well as being clear that having non-gendered washrooms was as much a priority (as build-out would permit) as having mother’s rooms and quiet rooms.  Both of those two things being already in existence in the current space because of there being employee need for them.  The takeaway for me?  I can ask for what I need and be heard and supported in (eventually) getting them.  That’s some great culture, in my opinion.  I wasn’t made to feel weird or out of order for asking for something that is probably always going to be an edge case in the workplace and I really appreciated that.

Wrapping Up

It’s been a whirlwind the last three weeks.  I’ve been getting up to speed with what I’ll be doing and I’ve got 30, 60, and 90 day roadmaps.  I’ve had a great time learning about things I’ve never done before – like iOS releases.  People have been super happy to hand off work to me, and I feel like I’m managing the work I’m taking on as well as having lots of energy for what’s to come – when I’ll have the basics down and can work on creating more ways to add value to a lean, fast-moving company doing very interesting things.  So all this to say that I’m grateful for all the years and roles at Mozilla, the people I’ve learned from, the experiences I’ve had and at the same time I have a ton to look forward to in this new space.

Contribution opportunity: Early Feedback Community Release Manager

Did you make a New Year’s resolution to build out your software development skillset with a focused contribution to an open source project? Do you want to work with a small team where you can have a big impact?

We’re once again looking for someone committed to learning the deepest, darkest secrets of release management when shipping a big, open source software project to half a billion users. Our small team of 3 employees already has one contributor who has been a consistent volunteer for Release Management since 2013 and has worked his way from these tasks to taking on coordination and growth strategy for the Extended Support releases. Our commitment to contributors is that we will do our best to keep you engaged and learning, this is not grunt work, it’s deep participation that matters to the organization and to the products we ship.

You’ll need to consistently commit a 1-3 hours a week to helping analyze our Nightly channel (aka mozilla-central or ‘trunk’) and raise issues that need prompt attention. The very fabulous volunteer who takes on this task will get mentoring on tools, process, and build up awareness around risks in shipping software, starting at the earliest stage in development. On our Nightly/trunk channel there can be over 3000 changes in a 6 week development cycle and you’d be the primary person calling out potentially critical issues so they are less likely to cause pain to the user-facing release channels with larger audiences.

A long time back, in a post about developing community IT positions, mrz recalled a post where I stated that to have successful integration of community volunteers with paid staff in an organization there has to be time dedicated to working with that community member that is included in an employees hours so that the experience can be positive for both parties. It can’t just be “off the side of the desk” for the employee because that creates the risk of burnout which can lead to communication irregularities with the volunteer and make them feel unappreciated. For this community release manager position I will dedicate 1-3 hours each week to actively on-board and guide this community Release Manager contributor in order to ensure they get the skills needed while we get the quality improvements in our product.

Here is the “official” call for help, come get in on the excitement with us!

You

  • Are familiar and interested in distributed development tools (version control, bug tracker) typically used in an open source project of size (remember when I said half a billion users? Ya, it’s not a small code base)
  • Want to learn (or already know) how to identify critical issues in a pool of bugs filed against a code base that branches every 6 weeks
  • Have worked in open source, or are extremely enthusiastic about learning how to do things in the open with a very diverse, global community of passionate contributors
  • Can demonstrate facility with public communications (do you blog, tweet, have a presence online with an audience?)
  • Will be part of the team that drives what goes in to final Firefox releases
  • Learn to coordinate across functional teams (security, support, engineering, quality assurance, marketing, localization)
  • Have an opportunity to develop tools & work with us to improve existing release processes and build your portfolio/resume
  • Can commit to at least 6 months (longer is even better) of regular participation – this will benefit you by giving you time to really get hands-on experience and understanding of release cycles

We

  • Mentor and guide your learning in how to ship a massive, open source software project under a brand that’s comparable to major for-profit technology companies (read: we’re competitive but we’re doing it for a mission-driven org)
  • Teach you how to triage bugs and work with engineers to uncover issues and develop your intuition and decision making skills when weighing security/stability concerns with what’s best for our users
  • On-site time with Mozillians: select attendance at team & company work weeks – access to engineers, project managers, and other functional teams – get real world experience in how to work cross-functionally
  • Provide work references about how awesome you are, various swag, and sometimes cupcakes 🙂

I’ll be posting this around and looking to chat with people either in person (if you’re in the Bay Area) or over video chat. The best part is you can be anywhere in the world – we can figure out how to work a schedule that ensures you get the guidance and mentoring you’re looking for.  Reach out to me in IRC (lsblakk), on Twitter (@lsblakk) or email (lsblakk at mozilla.com).

Look forward to hearing from you! Let’s roll up our sleeves and make Firefox even better for our users!

Ascend New Orleans: We need a space!

I’m trying to bring the second pilot of the Ascend Project http://ascendproject.org to New Orleans in February and am looking for a space to hold the program. We have a small budget to rent space but would prefer to find a partnership and/or sponsor if possible to help keep costs low.

The program takes 20 adults who are typically marginalized in technology/open source and offers them a 6 week accelerated learning environment where they build technical skills by contributing to open source – specifically, Mozilla. Ascend provides the laptops, breakfast, lunch, transit & childcare reimbursement, and a daily stipend in order to lift many of the barriers to participation.

Our first pilot completed 6 weeks ago in Portland, OR and it was a great success with 18 participants completing the 6 week course and fixing many bugs in a wide range of Mozilla projects. They have now continued on to internships both inside and outside of Mozilla as well as seeking job opportunities in the tech industry.

To do this again, in New Orleans, Ascend needs a space to hold the classes!

Space requirements are simple:

* Room for 25 people to comfortably work on laptops
* Strong & reliable internet connectivity
* Ability to bring in our own food & beverages

Bonus if the space helps network participants with other tech workers, has projector/whiteboards (though we can bring our own in), or video capability.

Please let me know if you have a connection who can help with getting a space booked for this project and if you have any other leads I can look into, I’d love to hear about them.