Impact is Queen. Be Measurably Better.

Two of our core values focus on outcomes, not activities. We use data to ensure we’re always confident in our decision making. Few features make it out to users without first running in an experiment. We have a simple but effective experiment framework. Periscope provides a way to share these metrics with both technical and non-technical team members. Engineers who build features consider how the data is collected, how it is surfaced, and work with the other stakeholders to determine how to measure the success of it. Beyond quantitative data, our design and customer success teams have feedback loops for collecting qualitative responses to new features to surface product challenges.

To say we’re data-driven is really an understatement. We’re data obsessed.

Enigma’s purpose is to move the world forward by engineering deeper understanding through data, so data is at the core of everything we do.

Having a passion for solving complex problems with data is an absolute must, regardless of whether you’re working directly on a data infrastructure squad, partnering with a data-scientist on a product squad, or building the frontend that powers a best-in-class user experience.

At the core of our offering is a promise to focus on the data and provide transparency into our data-science so customers can focus on getting the intelligence they need in order to make better decisions. Whether we’re working with a large financial institution to help them verify small businesses for loans or screen customers and transactions for sanctioned entities, we’re creating a simple, seamless way for our users to access actionable intelligence from hundreds of authoritative data sources.

We believe that data and metrics are the foundation of building trust and making impactful decisions.

We strive for integrity and accuracy to ensure that quality data is delivered to the market. We are metrics-driven in our decision-making both internally and externally. We want to make sure the decisions we make - we make with data and metrics backing it. We have Amplitude, Google Analytics, and Custom Grafana dashboards set up so that we can constantly monitor the effects of the changes that we make. We spent countless hours making sure we can trust the internal metrics, and that people have the metrics in place as their north star as they go about their day-to-day.

What is the overall company revenue? A lot of companies actually can’t answer this question. Arriving at a number that can be trusted can be very difficult because of different currencies, custom deal structures, and various payment methods. We constantly monitor and validate our north star metrics (Daily Active Users, Revenue, Press mentions) and discuss our progress during our bi-weekly All Hands meeting.

Data is at the heart of decision making in Digit.

We use Chartio and Redshift extensively to analyze and test all aspects of our product. Our product is designed to be passive in that customers can sign up for Digit and then go on about their lives. Digit will then work in the background to ensure they are financially healthy. Given this passive nature, we rely on data (both qualitative and quantitative) to guide product roadmaps and growth experiments. We currently have 35 features and experiments which are being tested in production right now.

As an engineer at Digit, you’ll be responsible for working with our data analysts and user researchers to define what metrics you care about and which you are trying to improve.

Decisions are never made without supporting data.

We are instrumenting all of our company’s processes. In operations, we collect data on customer activity, LTV, threats, and engagement. For engineering, we capture data about performance, failure rates, response times/latency, build times, service throughput, and developer efficiency/happiness/engagement. These are just the tip of the iceberg of what types of data we will collect.

Data informs every decision we make about our product, too. At a very high level, we collect data about the threats our customers see. This data dictates which threat behaviors we model (for machine learning) first. We target the threats that are seen most often by the largest number of customers. In addition to frequency, we track severity of each threat and then model the most severe threats to our customers. Engineers at ActZero always stay close to the data as our team is structured so that engineers and data scientists work in partnership.

Every engineer works with at least one analyst.

We love experimentation and letting the data tell us what our members like best. This allows us to quickly ideate, brainstorm hypotheses, and see how our members (end-users) respond. We use Mixpanel and Optimizely to do continuous A/B testing and every decision we make is based on data derived from controlled experiments.

As a result, we work very closely with the Analytics Department. While each team is responsible for deriving analytics and making decisions based on their data, it’s our policy that everyone has access to all analytics at Credit Sesame.

We look at data like click-through rates, how many members are completing a particular funnel, and see what resonates with our members. Before we start any experiment, we have strict guidelines around defining success criteria.

Even internally within our department, we use other data-driven metrics to make decisions. While the product team focuses on the business value, the engineering department considers metrics like tickets resolved, tickets completed in our sprint backlog, and other productivity metrics. This helps us improve our turnaround time for tickets and tells us how many tickets we can take on over the course of a week. Everything gets evaluated during sprint retrospectives.

Note: This is not a stock photo – it’s just us doing our thing :)

We track everything and make decisions based on numbers, not opinions.

We are an extremely data-driven organization. Our analytics team supports dashboard creation as well as ongoing and ad-hoc analyses. As an organization, we track and report against a plethora of metrics, some of which are related to user events, feature modifications, and revenue changes. The engineering team uses data for suppression, sunsetting, monitoring, and charts creation. Features are rigorously tested using both A/B and bandit algorithms. All teams use robust dashboards for weekly and quarterly strategic planning. Our analytics team uses platforms such as Chartio, Amplitude, and Redash.

Data improves the insurance experience for our brokers and clients.

By running a full-stack brokerage, we sit in a privileged position to analyze data. We collect structured information about risk from clients (e.g. property data, business metrics, etc.) and risk pricing data from insurance markets. This industry is particularly opaque and we have a rare opportunity to provide transparency and build the first ever multi-sided marketplace for risk.

There are lots of thorny technical problems to solve at Newfront, from workflow systems to data modeling to document generation. We always rely on the data we collect from brokers and clients to inform new projects and test initiatives before release.

Several engineers on our team have backgrounds in data analysis and mathematics, and we encourage the entire team to leverage their expertise when shipping products.

As an analytics platform, data drives everything we do!

Our core philosophy is to use data to help us learn where to evolve our product. We use Amplitude to instrument everything (>1 trillion data points per month) we do and all of our teams focus on understanding user behavior and using it to influence our roadmaps. In short, we use our own product in order to build a better product. We rely on Amplitude to research what we should be working on, identify which customers to reach out to, validate hypotheses, and determine leading and lagging indicators as we build new features. When we find shortcomings in our own system, we invest in building it. In fact, we never use other tools to do the job. When we needed a scalable data-ingestion platform, we built it in-house.

Sometimes, what we build for our internal use ends up getting rolled out. For example, Period-over-Period Analysis was a feature we built for ourselves to compare this week’s data to last week’s and give us a look at percentage change over time. We eventually rolled this out as a free feature for all of our customers to use and it continues to be one of the most popular.

We make decisions based on data.

Data informs everything we do at Stitch Fix, from which pants we should order to the images that should appear on the homepage. We believe we can use data to create a better experience for our customers. That's why we employ nearly as many data scientists as we do software engineers. Data informs so many of the decisions that we make here at Stitch Fix, that part of life here is working together with data scientists to craft experiments and solve problems.

One example of how we leverage data is in how our data scientists have improved our demand model. Our buying decisions are much more informed than they would be if they were based on traditional retail models, and give us a better grasp on things like, “How many customers do we think we’ll have?” and “How many customers will be wearing smalls vs. extra smalls?” Where traditional retailers rely on industry standard size breaks, we leverage data to make informed decisions when buying and are able to better utilize that inventory.