Last active
December 21, 2015 05:39
-
-
Save arches/6258925 to your computer and use it in GitHub Desktop.
[DRAFT] Job posting for a mobile developer at Aisle50 in Chicago. We believe in diversity and are trying to construct a welcoming interview process for all. Please leave some feedback if you have any ideas how we can improve this posting! Is anything unclear? Unaddressed? Insensitive? Offputting? What else do you want to know about the company, …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I have found these resources particularly helpful in preparing this posting: | |
Hiring Engineers, a Process | |
http://hueniverse.com/2013/02/hiring-engineers-a-process/ | |
Join the Lift Team | |
http://blog.lift.do/post/24988178079/join-the-lift-team | |
How Etsy Increased Diversity in Its Engineering Department: An Interview with Marc Hedlund | |
https://www.youtube.com/watch?v=0D66GVc7ztA | |
via (@SuzAxtell)[twitter.com/suzaxtell] | |
New Study Exposes Gender Bias in Tech Job Listings | |
http://www.wired.com/wiredenterprise/2013/03/hiring-women/ | |
http://www.futurity.org/top-stories/wanted-gender-free-job-ads/ | |
via (@meaganewaller)[twitter.com/meaganewaller] and (@coryaw)[twitter.com/coryaw] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## What We're Doing | |
Aisle50 is all about huge savings on groceries. Our sales team sources deals directly from manufacturers, | |
and we pass those savings (typically 30-60% off) to the shopper through our website. We're able to | |
provide uniquely interesting opportunities for both manufacturers, shoppers, and grocery stores: | |
Shoppers love our us because our offers are easy to use and provide much bigger savings than typical | |
coupons. Our biggest single offer to date saved shoppers well over $10. | |
Manufacturers love us because our programs are cheap and easy to run - printing paper coupons is | |
expensive. We also reach the shopper before they're in the aisle looking at dozens of competitors' | |
products. Often 80-90% of shoppers who take advantage of an Aisle50 deal haven't bought the product in | |
the previous three months, so we're truly introducing the product to new people - the ultimate goal of | |
the manufacturer. | |
Grocery stores love us because we drive trips to the store. As with a paper coupon, the store receives | |
the full value for all the products regardless of what the shopper pays. We've even found that people with | |
Aisle50 deals buy more than they normally would - a bonus for the store. | |
## Why We're Hiring | |
Mobile is such an important part of grocery. Not everyone has a smartphone in the store, but NOBODY has | |
a desktop. The vast majority of our users' problems arise in the store itself, yet we feel mobile is the | |
weakest part of our current offerings. We have a mobile-optimized site and native apps that basically just | |
frame the mobile site. It's a pretty good stop-gap solution but we're leaving a lot on the table. We want | |
to provide an awesome customer experience in the store and we need native mobile apps to do it. | |
## What It's Like Here | |
Aisle50 currently has (fifteen employees)[http://aisle50.com/team]. The tech team reports to the | |
co-founders. | |
We believe in the paramount importance of the customer experience. We have a number of | |
constituencies, so walking the line between what's good for shoppers, manufacturers, and retailers is | |
a difficult but rewarding daily challenge. We're humble about our code because what's important is | |
finding the best way to do things. We're all very curious people and enjoy working together to explore | |
a problem space and find the best ideas. We try to mitigate risk by taking small steps and creating | |
safety nets (eg: test-drive development, continuous integration). | |
We don't use Agile or Kanban or Waterfall or really any project management methods at this point. We have | |
a weekly meeting (and a morning check-in when we remember) to make sure we aren't losing focus, but in | |
and out of those meetings we just talk with each other about what we're working on, what's important, and | |
how to solve problems. We're all responsible for actively improving the company and product and kind of | |
just leave it at that. Our ideas as developers are consistently included in our products. We occasionally | |
use Trello to track larger projects when we feel like it'll be useful. Maybe eventually we'll need | |
something more formally defined but so far we've been pragmatic about doing what works and not | |
over-engineering the process. | |
We tend to be in the office most of the time because that's how we feel we're most effective, and we | |
look forward to working with you in person. However we do understand and encourage work-life balance. | |
People routinely work from home or take off a little early or whatever they need to do. As a tech team | |
we have very few deadlines and are good about proactively managing them which has made it easy to be | |
flexible. | |
We have a community manager who handles most of the customer support, but we all pitch in at various | |
times. It's nice to be able to get some first-hand contact with our customers. We have a close working | |
relationship with the sales team. A big part of our tech focus is on building internal tools to make | |
their jobs faster and easier. | |
We eat lunch together every day. It's not required or anything, we just like each other :) | |
## Stack | |
Our current tools include: | |
* Rails 3.2 (migrating to 4.0 soon) | |
* Ruby 1.9.2 (migrating to 2.0.0 soon) | |
* heroku | |
* postgres | |
* mailgun | |
* S3 | |
* rackspace (we need a static IP for some of our retailer integrations) | |
* rspec | |
* json API | |
We develop on Macbook Pros and IKEA desks. We all use different editors. | |
## Who We're Hiring | |
Our current team has very little mobile experience, so we need someone who has a good handle on it. | |
You won't be entirely on your own - we'll be able to pick up the languages pretty fast. But with any | |
technology, the environment and tooling is often the biggest hurdle. We need someone who knows how to | |
set up a project from scratch, pull in the right libraries, and create a solid foundation that is going | |
to work for us long-term. Once we have a stable development environment it's going to be much easier | |
for the rest of us to help out. Years of experience is a very rough rubric, but we expect a successful | |
candidate will have 4-6 years of software experience with at least the last 1-2 being mobile. This | |
person needs to be familiar with software design principles, able to reason and communicate at an | |
architectural level. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Line 7 has an extra word :)
I think this posting is definitely welcoming! You address the company background and mission, a typical day/week, the part about everyone eating lunch together is nice too and definitely speaks to the atmosphere in the office.
I don't really see anything in this posting that makes me feel excluded, or makes me think this posting is only looking for a certain type of person.
If I was a mobile developer in Chicago this is the type of listing I would definitely respond to, I hope you find a great fit.