# Mapbox

## Company blurb

Mapbox is a mapping platform for developers. Our building blocks make it easy to integrate location into any mobile or online application. We want to change the way people move around cities and understand our planet.
From finding a coffee spot on Foursquare, to pinning a vacation spot on Pinterest, to geo-tagging notes in Evernote – we do the geo stuff so developers can focus on building their app. Mapbox is the foundation for other platforms, letting enterprises analyze their data, drone companies publish flyovers, real estate sites visualize properties, satellite companies process cloud-free imagery, and insurance companies track assets.

Mapbox is an open source company. We build our product with open source parts, work in the open, and release as much code as possible – [it's the right thing for people, technology, and business.](https://www.mapbox.com/about/open/)

## Company size

350+
Mapbox has closed a series C and is growing rapidly.

## Remote status

The team are partly remote - [about a dozen of us are remote in the U.S. and Canada, Europe, and South America](https://opensource.com/life/14/7/interview-justin-miller-mapbox)

## Region

Remote locations include U.S., Canada, Europe, and South America.

## Company technologies

Mapbox GL JS for web, iOS, Android, React Native, Unity, Qt.

### Software

Our focus for releasing software as open source is on reusable, general-purpose parts. In many cases, this means modules, rather than applications. We distribute these modules for other developers to use on websites like [npm](https://www.npmjs.com/) and [PyPI](https://pypi.python.org/pypi). For instance, [rasterio](https://github.com/mapbox/rasterio) is a core part of our image processing pipeline that we make available for any Python programmer to use.

A minority of our software is closed-source:

* Software that connects server processes and is heavily dependent on our configuration. This is a prevalent category but tends to be very small, in terms of code.
* Software that packages up business workflows. Software highly specific to Mapbox’s product, tied into our design, and core to our competitive advantage is often kept closed. These projects are usually applications and servers composed of parts that we release as open source so that others can build from the same foundations.


### Standards

Standards make modern software possible by connecting modular parts into systems. Open formats are the groundwork of open data. Mapbox is built on open standards: we adopt existing specs like GeoJSON and author new standards for new purposes, like [MBTiles](https://github.com/mapbox/mbtiles-spec) and [GL Style Spec](https://github.com/mapbox/mapbox-gl-style-spec). We release them under [permissive licenses](http://creativecommons.org/licenses/by/3.0/us/) that enable everyone to freely implement them in products and software, and to improve upon them.

### Design

Design components that are **reusable, general purpose, and not explicitly tied to the Mapbox brand**, like [Maki](https://www.mapbox.com/maki/), make sense as open source. We also release templates that show how to use our tools, like those in [Guides](https://www.mapbox.com/guides/).

Most of our artwork is copyrighted and not placed under any open license. It’s tied to the Mapbox identity: reusing the Mapbox.com website style isn’t a use-case we want to support. The uniqueness and specificity of our style is important to how customers identify “oh, this is Mapbox”.

### Data

The vast majority of Mapbox’s data is in the open. Large sources include [OpenStreetMap](http://www.openstreetmap.org/), [USGS](http://www.usgs.gov/), [Landsat](http://landsat.usgs.gov/), [Natural Earth](http://www.naturalearthdata.com/), and [OpenAddresses](http://openaddresses.io/). We contribute to these sources, participate in their communities, and invest in tools that help improve them.

We also work extensively with proprietary sets of data that we buy: we legally can’t open these. Nor do we release heavily processed data. Processing data and delivering the final products has obvious and real costs: server infrastructure and bandwidth, as well as labor. Our ability to distill meaning out of raw material is a core part of our product.

## Office locations

We are located in DC, SF, Ayacucho, Bangalore and Berlin.

## How to apply

Check the [job listings](https://www.mapbox.com/jobs/).
Read this [blog post](https://blog.mapbox.com/how-we-hire-at-mapbox-cd946418299f) for info on how Mapbox hires.