Write code that makes a difference

Who You Are

You are regularly the most productive person on your team, but perhaps more importantly, the one everyone goes to for advice on their engineering dilemmas. You are a compelling communicator and excellent listener. And you’ve worked with many different software platforms, across the full stack, everything from making the first commit, designing a new DSL, deploying to production, and epically breaking the build.

Your Skills

  • You are an experienced engineer: you’ve built things that really work from the ground up, tools and applications that other people use
  • You write quick, concise clean code that is as much of a pleasure to read as it is to run
  • You are comfortable working across the whole technology stack, front to back and everything in between
  • You know when to write tests and when to write experiments and are regularly the most productive member of your team
  • You know that deleting code can be just as powerful as creating it
  • User focused, you expect to iterate on the product in response to what works and what doesn’t. Maybe the best user interface is text messages instead of mobile web. Maybe we need to build a kiosk
  • You are comfortable across a range of platforms and languages, but are an expert in a few. You like to learn new languages in your free time, and have built a project in a new language just to explore
  • Preferred Languages/Frameworks: Linux/Opensource, Ruby, Python, Javascript, Rails, Sinatra, Django, Flask, Node, Express, Angular, Ember
  • Preferred Experience: Mobile web a plus, web applications, third party APIs, particularly social and telephony (Twilio etc)

The Task

You’ll participate in our empathy and immersion program, meeting and spending time with folks from our Design Insight Group. Using the insights from this research, you’ll join our cohort of fellows to quickly brainstorm, prototype, and evaluate ideas. Integral to the whole process is product validation – quickly and creatively collecting data and teasing out insights.

At the end of the Research Phase, you’ll team up with a few colleagues and settle on an idea. Over the next 80 days, you’ll rapidly develop a prototype to test with potential users, iterating against user feedback. As the engineer on your team, you’ll pick the platform, develop an architecture and make decisions about how best to implement your team’s product.

How To Apply?

Applications have been closed for the 2017 fellowship.

Signup for our mailing list to be notified of future programs.


Applications have been closed for the 2017 fellowship.

2017 Key Dates

  • Applications open: 1/27/17 at 9:00am EST
  • Open House: 2/16/16 at 6pm EST.
  • Weekly Info Sessions:Every Thursday in February at 1pm EST
  • Applications close: 3/6/17 at 11:59pm EST
  • Finalist workshops: 4/1/17 or 4/9/17
  • Fellows Accepted: 4/15/17
  • Fellowship Start: Early June
  • Research Phase Ends: End of July
  • Build Sprint Ends: Mid October

Support includes:

  • Co-working space in downtown Brooklyn
  • Access to a pool of 200+ community members who can shed light on problem areas and provide feedback and validation
  • Connections to front-line organizations
  • Access to a strong network of talented mentors, social innovation funders, and our alumni
  • Free and discounted access to a number of services and products to help you get things done
  • An honorarium to pay your rent and bills
  • The opportunity to work on important issues with some of the best in the business

More Questions

For more information on the Fellowship or the application process, please see our FAQ or attend one of our weekly webinars.

You can also watch a recorded webinar.

Additionally, we'll be hosting an Open House on February 16th.

Alumni Profile

Dylan Butman, 2015 Engineering Fellow


  • One of the greatest parts of working with the Labs was the depth and breadth of experience that every person brought. No one was superfluous and no one was domineering. The results can come from a room where everyone knows what they're doing were refreshing to say the least.
    Chris Guess
  • I came away from the Labs fellowship with the experience of building an entire product from ideation to a stage where investors were eager to fund it. My team of 3 pivoted more than once, but we were able to do so because of the supportive structure of the program that encouraged creativity and allowed flexibility.
    Alex Berke
  • If you're looking to work with people who care and build products that matter for a grossly under served market then you should consider the Labs fellowship. If not, there's always 'Yo'.
    Paul Barnes-Hoggett
  • One of the reasons I left the corporate world last year was because I wanted to provide real value to products and people that I was building those products for. The Labs fellowship allowed me to do just that and really allowed me to see my impact first hand.
    Kevin Miller