DRAFT I'm applying for a position with Mozilla, part 3

For background on this, see Part 1 and Part 2. 


DRAFT


And here's the final page of notes. This has been a pretty refreshing experience, actually. Now I just have to tweak my CV/résumé. (Yes, there are two accents. Attention to detail: check.) 

My current résumé is largely focused on project management, so I don't think I'll have to make many changes.

Format

I like how plain looking my résumé is, but I sometimes wonder about how I could improve its appearance. More white space? Will consider. 


Header/contact info


Remember to switch email to reidcomms. 

Just in case: brentonwalters (at) gmail (dot) com

Highlights of qualifications
A bit too generic. Specify:

• What kind of project management?
• What scale? 
• 
  

Experience

I operate somewhere between being a contractor and a consultant. I am in the process of incorporating, but haven't had to yet. 

I am also in the process of developing a website for my work, but it's about halfway done right now. I am therefore limited to a résumé, which I worry doesn't quite convey appropriately my experience over the past several years.

I should also have an accurate LinkedIn profile, but as yet have not seen any utility there. 

Do I include a link to my bog-standard placeholder WordPress site? (In the end, I did.) 

I would normally pare down my various experiences. I usually delete the Logistics Coordinator one - after all, it was working in a produce warehouse. But it was a warehouse that moved millions of dollars of produce that I ran, managing staff and coordinating the work between the warehouse, sales and transportation departments. 

Education

I went to the Social Change Institute. It's a bit of a cross between a conference and training. With a bunch of networking. Meh, I don't know. Feels significant right now. 

(This is a bit of a workaround vanity line...) I removed my "Best Undergraduate Essay in Political Science" award. Felt a too high school. For anyone wondering, it was a piece on Aristotelian ethics and foreign aid. 

I'm applying for a position with Mozilla, part 2

Below are my notes for the actual application for the project management position with the Mozilla Foundation. See Part 1 for background. 

Part 2

The Mozilla world feels very similar to the political world:

• Working with disparate groups
• Tight deadlines
• Focus on financial sustainability
• Idealism supported by strong pragmatism
• An absolute need to get shit done

Campaigns are projects or with a different name, and managing them requires the exact same skills, experience and mindset.

I love political campaigns, a lot. But it feels good to be looking outside of politics into an area that will be both comfortable and challenging.

My process

I'm taking a fairly simple approach to this:

1. Learn about organization
2. Learn about the position
3. Figure out how my experience and skills will fit
4. Strengthen areas of weakness and highlight areas of strength
5. Write, re-write, edit, re-edit and proof the application
6. Hit Submit/Send - there is always some uncertainty 

Learn about the organization

There are some aspects of the organization that I feel I should be more familiar with, as prompted by the position description and a friend who is familiar with the org:

• #lovetheweb
• digital literacy
• work open
• Bugzilla
• Webmaker
• Open Badges
• Monday meetings (these are available online, to the public)

I'm fairly familiar with the open web movement, and have a general understanding about the advocacy work that Mozilla does. I have done more reading, and (warning: shameless plug ahead) made my first donation to keep the web open. And I feel confident in my understanding of (though not my level of comfort with) the work open concept.

 But I started poking around a bit more, and before too long had filed a few bugs on Bugzilla (see here, here and here). They are just grammar issues from the main and Bugzilla sites, but the job description says "Be at peace with Bugzilla", so I tested it out. (And one of the bugs was a grammar mistake in the org brand guide - kind of important.)

Aside: I'd like to file a bug on the process itself, but perhaps I'll save that for later.
Aside to that aside: Does "Be at peace" imply get to know or does it imply learn to appreciate it despite its faults? How many bugs have been filed about Bugzilla itself? No matter, the original aside stands.

It's an amazing system for trouble-shooting. I can only imagine how difficult it is to manage across a massive volunteer-driven organization, especially when it comes to coding.

I also looked into Webmaker and Open Badges, both of which are very interesting programs/ideas aimed at improving digital literacy, with some focus on how kids interact with and on the web. With a 2-year-old daughter, this is a particularly important issue for me. I dread the time Sylvie first uses the internet, with all the shit that is out there and the stories about cyber-bullying, etc. 

Monday meetings - This is partly important for understanding the work open concept, but also for getting a sense of what the org is like. There is maybe no better indicator of how an organization functions than sitting through a general meeting.

The above three projects are indicative, it seems, of the work that the organization is doing. 

So, some of the organizational research is done. (If I had a wiki, I would make a table and insert check marks beside the above bullets.)


Learn about the position/Figure out how I fit

Beyond the position description, I asked a few friends that have some familiarity with the org, and they had some pretty valuable insight. I'll get to that below - for now, the description and how I could fit in it.

Position responsibilities

The first eleven responsibilities are project management-focused: Work with disparate groups, manage tight deadlines, ensure everyone knows what everyone else is doing, develop tracking mechanisms, etc. As I read them I felt entirely comfortable. The scale of the projects may be bigger than much of what I've done, but it's all scalable. This is what I've done for the past five years, this is what I love doing, and where I've had my biggest successes.

The last two are something different - basically, advance the aims of Mozilla through various outreach efforts (blogging, speaking, community-building). With different goals in mind, this is what I do in the political world. I would definitely need to become more comfortable with the specific subjects, but that's both manageable and something I should do anyway.

I feel quite confident that I will do well in this position. That has given me some confidence as work through this process. 

Qualifications

Right off the bat, I liked this section. "You're passionate and engaged about project management. You consider it your profession."

I've been trying to figure out how to fit in to the work that some organizations do, because I consider myself a generalist in that I am not a comms or fundraising or outreach specialist. I can do all those things, but what I love is organizing all those things. Plus events. Plus HR. Plus etc, etc. Only recently have I embraced that aspect of what I do in name - in practice I've been doing it for years. 

I may be on the low end of their years of experience. 

"Direct experience with large-scale communications and marketing campaigns." - I feel a bit vulnerable here. I have comms and marketing experience, but that "large-scale" might mean a lot. 

Next there are some general project management stuff that I love to see: extremely organized, able to communicate everything well, consensus-driven, capable of herding cats, etc. Solid. Wheelhouse.

Grants and funding cycles - yep. 

Spreadsheets, etc - be still my beating heart. Seriously. (I once wrote "I love to excel, and I love Excel." in a cover letter.) 

Bugzilla - dealt with in part 1. 

Gantt charts - I had to look this one up. I definitely won't be able to rant for hours about why they're evil, but yowzah, they sound evil. Claustrophobic. There is nothing nimble about a Gantt chart. 

"You are comfortable working with diverse colleagues who are capable of brilliance and chaos, often in the same moment" - Welcome to politics. Throw in some awkwardness, some conflict, and some bad coffee and you've got every campaign office ever.

- 30 -

Okay, that feels really good. 

In Part 3 I look at how I will change my résumé and word the application form. 

I'm applying for a position with Mozilla, part 1

TL;DR

What follow are three posts outlining my thoughts on my application for a project management position with Mozilla. 

Part 1: background
Part 2: application process 
Part 3: résumé and application form

I used a work open approach, and found it refreshing.

The position responsibilities and qualifications are great. I have rarely felt as good about applying for a position.

The organization sounds like it needs someone who can pull together various teams, get everyone working together, and work towards organizational sustainability. This is what I do, and what I love doing. 

Part 1

I'm working on an application for a project management position with the Mozilla Foundation. 

Having gone over the position description, I am confident this will go well. Every point of responsibility or qualification felt great. 

Part of the Mozilla ethos is "work open", an approach to work that values participation, agility and speed, and transparency. Everything is public, available for all your co-workers (and any interested public) to browse through. Maybe not everything. A lot. Open source, but on an organizational scale.

Here, read this piece that summarizes why the Mozilla Foundation uses this approach.

With that in mind, and with some excitement but some trepidation, I thought that I would use this space to document my application process. My notes, thoughts, and the finished product. Probably.

Upsides

• Focuses my thoughts on what is and isn't important.
• Good practice for what would be a necessary embrace of the work open concept. 
• Hopefully it stands out from the other applications, something that is explicitly encouraged on the application form.
• Beyond the gimmickry, there is value in demonstrating a thought process rather than merely handing in a finished product. 

Downsides

• It's a bit gimmicky. EDIT: It's outright gimmicky. 
• Someone else applying for the same position could use this to put themselves in a better position. (Okay, pretty unlikely)
• It's taking quite a bit of time to plan this and carry it out - I may have to apply with this unfinished.
• I may not like the work open process. 

Personal trepidation

I'm not very tech-savvy - for evidence of that, look no further than this poor little website that I've been using for many years. Or to my use of "tech-savvy". If I knew how to whip up a wiki page for this, I would. And I get the sense that every other employee at Mozilla could do that on their coffee break.

Mozilla is an organization of software developers. There is a vocabulary (or likely a set of vocabularies) in the organization that is foreign to me. And I struggle at times with more than the nomenclature.

Is there the potential in an interview (assuming I get that far) to be confused by some Mozilla or web terminology? Yes.

I am likely overstating this issue - I'm sure there are plenty of people at Mozilla that aren't radical hackers. Or tubular hackers. *Yah, Barney, bitchin'... 

Anyway, it all feels a bit like uncharted territory for me, which is still intimidating. If anyone has any ideas for how to work through this, please let me know.

Independent of this application I have been working on my own digital literacy, learning about how to work in WordPress, how to host a website, etc. So, there's that...


Working open in the political world

I wanted to write a bit more about the concept of working open, an idea that both fascinates and unnerves me. I work in a world that values proprietary knowledge. The better you can leverage that knowledge, the better you will fare, be it in fundraising, voter contact, or media relations. Lists are difficult to build and maintain, and are closely guarded secrets. 

I'm amazed that the Mozilla 2013 year-end fundraising plan is available online for anyone to read. It's not exactly rocket science, but it's also more than I've seen from any other organization. And Andrea Wood, the lead online fundraiser, plans to make available info about their email fundraising program.

A fascinating approach, and an admirable ethos. I really hope it works for Mozilla. 

So that's the background for this. Part 1, I guess. In part 2 I explore the actual application. 

Why Steven Beitashour is a great signing

Steven Beitashour made all of $49,612.50 last season playing for San Jose. He is set to make a sight more than that in 2014 playing for the Whitecaps ("upwards of $200k", says MLS writer Ben Jata), and deservedly so.

Some people are questioning that amount, and in a salary cap league, all salaries should be judged on their value (though not necessarily on their replacement cost - the contract/trading system in MLS renders that difficult at best). So let's take a look at what the value of a good right back is in MLS. Or rather, in the Western Conference, because it's easier, quicker, and within my realm of knowledge.

Team	Player	Games	Minutes	G	A	Salary
CR	Marvell Wynne	28	2315	0	2	285,000.00
LA	Sean Franklin	33	2736	1	4	248,333.33
VW	YP Lee	32	2747	0	6	231,100.00
PT	Jack Jewsbury	26	2240	0	1	194,750.00
RSL	Tony Beltran	25	2230	0	1	166,800.00
FCD	Zach Loyd	25	2132	0	0	136,997.50
CHV	Mario de Luna	30	2637	1	0	120,000.00
SS	DeAndre Yedlin	31	2710	1	2	53,500.00
SJ	Beitashour	27	2426	1	3	49,612.50

-->
Notes:

1. Salary is the guaranteed salary as published by the MLS Players Union. 
2. I apologize for relying on goals and assists, but it's the most accessible data.
3. Kellyn Acosta took over for Zach Loyd in Dallas, but Loyd had twice the starts on the season.

So a fairly wide range of salaries for starting right backs, but in general those are likely a higher wages than many people would guess at. Basic conclusion seems to be that a good starting right back in this league is going to cost you $150-250k, and the player acquisition mechanisms and restrictions mean you'll likely have to overpay (one way or another) to get one in the first place.

What jumps out at me when looking at that list is that the quality of fullbacks in this league is not that high. Is Beitashour one of the best right backs in MLS? Well, yes, but that's mostly because there isn't a ton of quality in the league. He's certainly very good at this level.

Beltran is the best of the group, and deserves a higher salary. Both Beltran and Beitashour are solid, very good players, nothing too spectacular, but smart, organized, athletic, etc. Franklin is a little flashier at times, but I rarely notice him when I watch LA - I wondered at his salary when I first noticed it last season, and LA was probably smart to let him go. Yedlin shows promise, and in a couple years I think he'll be the best right back in the league. Expect him to get a significant raise soon.

Lee was a joy to watch in 2012, but his drop-off in 2013 was significant. Jewsbury is not a natural right back, but is smart and effective, and knows his limitations. De Luna, we barely knew ye... Wynne has has phenomenal recovery speed, but $285k for a fullback with questionable ball skills is a really poor use of cap space. Kellyn Acosta will be one to watch in Dallas - he's just 18, and I think won the starting job from Loyd on merit.

Clearly Beitashour was being criminally underpaid. What's interesting is that apparently San Jose tried to renegotiate his salary up but he wouldn't. And now he's getting a huge pay raise. The Whitecaps will pay somewhere in that $150-200k range, and all of a sudden a ridiculous off-season doesn't look so bad.

UPDATE: If you haven't yet, go read Ben Massey's comprehensive look at Beitashour's career so far:

http://www.maple-leaf-forever.com/2014/01/29/those-steven-beitashour-statistics-in-full/

Whitecaps roster - 2014 salary cap edition

Name	Salary counts	2013 cap hit	2014 cap hit
Signed
Sam Adekugbe	no	51,500.00	51,500.00
Bryce Alderson	no	80,000.00	80,000.00
Caleb Clarke	no	46,500.00	46,500.00
Russell Teibert	no	65,600.00	65,600.00
Omar Salgado	no	136,868.67	136,868.67
Kekuta Manneh	no	84,500.00	84,500.00
Jay DeMerit	yes	375,000.00	325,000.00
Jordan Harvey	yes	112,500.00	112,500.00
Eric Hurtado	yes	81,500.00	81,500.00
Gershon Koffie	yes	176,000.00	176,000.00
Matt Watson	yes	79,251.98	79,251.98
Aminu Abdallah	yes	46,500.00	46,500.00
Johnny Leveron	yes	71,187.50	71,187.50
Darren Mattocks	yes	212,000.00	212,000.00
Carlyle Mitchell	yes	46,500.00	60,000.00
Andy O'Brien	yes	230,012.04	230,012.04
David Ousted	yes	166,156.25	200,000.00
Kenny Miller	yes	387,000.00	195,000.00
Nigel Reo-Coker	yes	237,362.50	387,000.00
		Total	2,175,951.52
Unsigned
Creative mid	yes		387,000.00
Starting RB	yes		150,000.00
Back-up RB	yes		60,000.00
Back-up GK	yes		70,000.00
Mehdi Ballouchy	yes	152,006.00	80,000.00
Andre Lewis	yes		80,000.00
Mamadou Diouf	yes		80,000.00
		Total	907,000.00
		Grand total	3,082,951.52
Christian Dean	no		100,000.00
Marco Carducci	no		35,000.00
Ben Fisk	no		60,000.00
Marco Bustos	no		46,500.00
Kianz Froese	no		46,500.00
Jackson Farmer	no		70,000.00

Here are my estimates for the Whitecaps' salary cap situation, as it stands on January 20. For updates, check out new posts on Two Fat Bastards.

1. The MLS salary cap for 2014 will be somewhere close to $3.097 million. 
2. If I haven't heard or thought differently, I have carried 2013 salaries over to 2014. There are some exceptions. I am considering building in a 2-5% raise for everyone. 
3. The table wouldn't fit further squad info that would explain why players are or aren't on the cap - suffice it to say that I think I'm pretty solid there. GA, homegrown, salary amounts, etc. 
4. I've guessed at DeMerit's salary based on a few things - it's much higher than other estimates I've seen ($200k, etc). I'd be willing to wager that he hasn't taken much of a pay cut.
5. Kenny Miller's amount is for a half-season as a DP. That could change quickly - so much depends on whether he'll be heading back to Scotland/Europe in the summer transfer window.
6. I've generously given our unsigned midfield playmaker a DP salary. Here's hoping we find someone whose skills demand it.
7. The amounts for the unsigned players are obviously estimates, but I've looked at a lot of salaries in the league for most positions, and I think I'm pretty solid there. We could pay more for a starting right back. If we pay more for a back-up keeper we're foolish.
8. The Homegrown Generation Adidas situation is not clear at all right now. We have no idea if Teibert remains a homegrown, if players ever transition to normal from homegrown, and so far it's unclear how much salary teams are allowed to allocate to Homegrown GA players above the league minimum before it counts against the cap. Yay MLS. 
9. I expect we'll see some signed players leave before the March 1 roster deadline - if I was a betting man, I would guess Abdallah won't be here, maybe Hurtado, maybe one CB.