Retail Me Not – 2015

Got this email from a recruiter:

We’re growing our Engineering team and I thought you’d be a great person to speak with. Would you be interested in hearing about new opportunities?
Let me know if that’s of interest to you or brings to mind anyone who might be good for me to speak with, I’d be glad to sync up on the phone and discuss further at your convenience. I’ve also included our link so you can check out the company. Thanks!

That’s funny. The guy that fired me from Lombardi was VP of Engineering at Retail Me Not.
I emailed back:

Your VP of Engineering fired me from Lombardi. I don’t think I would be good fit. You are welcome to submit my resume, but I doubt he would bite.

I got this response:

I spoke with him and he agreed that he didn’t think it would be a good match. He had positive things to say about you but didn’t see a fit between your experience and what we’re ideally looking for.

Let’s definitely stay in touch. I’d love to reconnect when we have something come up that is a better match.

He had positive things to say about me? That’s actually nice. I was happy with that.

As for staying in touch, I am still (kinda) waiting…

Oh, and that VP was let go after a couple of more years. I don’t wish him ill, but I am sure he landed on his feet anyway.


Apple – 2015

apple maps
This image is from later than 2015, but you get the idea.

I randomly got a message one day on LinkedIn:

Want to re-join Apple 🙂 ?

We have some awesome challenges ahead in Apple Maps and I’m looking for key talent to join my organization – when I went through my connections on LinkedIn I found your profile – and you look like a potentially great fit.

Maps is a big data problem that is dynamically changing underneath a service and client architecture delivered across multiple platforms. Its a fantastic challenge. My team is looking for great engineering leaders who are interested in building intelligent automated systems to help streamline the content delivery process.

The organization is growing rapidly so there is a lot of opportunity for growth and a chance to play with all sorts of interesting technology with the smartest people on the planet.

If you are interested please shoot me an email and we can set some time up to talk and I will rope in my recruiting team.


Apple Maps had had a very rough introduction. Somebody who I worked with on the Mac OS X Program Team had been promoted to VP of Software, and he was let go after Maps had so many problems. That was 2-3 years earlier, but I had heard through the podcasts I listened to about the industry that Apple was doing a lot of hiring in this area.

So when, this Apple manager reached out to me, I listened. I still missed Apple. I did not miss California, but this opportunity sounded fantastic.

It just so happened that I was going to be a work trip to CA the next week anyway. After some back and forth, we setup a time to talk.

And I had a blast talking to him. We talked about front-end challenges (app vs. browser; ios vs. android), and we talked about the large amount of backend hardware necessary. We talked about getting map data from a vendor vs. collecting it organically. We both left the meeting amped up, and I was looking forward to hearing from him.

And the day after, I did:

Thanks a lot for your time and your insights – very appreciated. I was excited, but unfortunately we have decided to go a different direction with this position.

Initially, I thought that perhaps he had talked to somebody on campus about me and heard something he did not like, but that’s my own paranoia and imposter syndrome showing.

“We have decided to go a different direction” is code for “we were going to hire a manager from outside, but my bosses decided to re-org the department instead”. It looks like they decided to buy some tech to cover the gaps soon after I talked to this guy. So I was right; they no longer needed another manager because they bought a company.



Kansas City Royals – 2014

Your 2014 American League Champions!


I have talked about my interest in working in baseball throughout this blog (like Project Scoresheet – 1989). There is a website called TeamWork Online that is a place where the vast majority of teams in baseball post all of their jobs. I have an alert for jobs I might be interested in.

The Royals had just been to their first World Series in 19 years, and right after that, I got notified that they had a job opening called “Systems Architect/Deverloper, Baseball Analytics – Kansas City Royals (Kansas City, MO)“. The job listing talked about maintaining internal websites, working on databases, capturing statistics real time, etc. Right up my alley!

I was fairly happy at Mozilla, but, really, baseball!

This time, I got a response:

Thank you for completing the teamwork application. Just to give you a little background, the position we are looking to fill in the past was in charge of everything from managing our data imports to developing web/mobile applications for wider us through the organization. Our existing architecture mostly uses MySQL and Ruby on Rails, and we are looking for the new hire to take over a great deal of code a varying stages of completion along with moving forward into new areas. As this position will for the short term at least be our only dedicated developer they will work with autonomy in this area in terms of how they choose to execute projects. Based on your resume it looks like you are proficient in those technologies and many more, does our specific opportunity or are you more comfortable starting from scratch and/or working with a team of developers?

Our goal is to fill the position ASAP to get ready for next season but we will continue our search as long as necessary to find the right candidate. Because the baseball season is long and the commitment by employees significant the personality fit is as important as the skill-set in our search. As for next steps in our interview process we would like to see an example of work product if possible. A web app you have developed that is accessible publically would be great (or access to relevant code on GitHub). If not we can send along a self-contained project to accomplish the same. Thanks very much for your time and interest.

I could hardly believe it when I read this. I was doing a little happy dance inside. This sounded great!

I replied:

Thanks for getting back to me so promptly.

I am comfortable however things need to proceed. My vision is working alone on the code while developing a long-term strategy for where the system needs to be. Once the strategy is articulated, I can then build a team to build the new or overhauled system.

As for an example of my coding, you are going to have to send me a self-contained project. The only part of this entire stack that I really have little experience on is building the actual web apps. My development experience is with client-side or standalone app development. The rest of my experience is with the rest of project development – building of systems, deployment of web apps, testing, managing the product cycle, building teams, etc.. I hope this is not a hurdle, but I hope I can prove my ability to learn quickly by completing your self-contained project.

Let me know; I am looking forward to us talking more. Thanks!

We then talked on the phone for a while. He told me he was going to send me a task to do, a programming test. I told him the truth; we were travelling for the Thanksgiving holiday. And then, I had to go to Portland for Mozilla’s All Hands Meeting for another week, so it was going to be a while before I could tackle the problem.

And then I came back from Portland with the Mozflu, and I was laid out for several more days.

I finally got started on the project. It had sample anonymized data from PitchFX, a system which tracks every pitch. I was told I needed to present this data in an interesting way using Ruby-on-Rails, which I did not know at all.

I bought an online course and spent a few hours reading and playing with sample code, and the I wrote something which presented a histogram of average velocities of a given pitcher for the first 10 pitches, the next 10, etc.

I was quick and dirty and it was ugly, but I had something to turn in.

A couple of days later, the manager called me. He told me that they had narrowed it down to two. They liked my general experience a lot, but that the other candidate had more direct experience with Ruby-on-Rails, so they were going to go with him.

Still, I almost got a job in baseball!

It was hard to be disappointed.