Skip to content
👋 - The documentation for being an Artsy Engineer
Branch: master
Clone or download
dleve123 Merge pull request #179 from sweir27/on-call-slo
RFC: Clarify when we promise to be on-call
Latest commit 0dcf4d0 Apr 16, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Adds CI Sep 10, 2018
.github/ISSUE_TEMPLATE Update Mar 19, 2019
careers Update links to https 🔒 Dec 2, 2018
conference-notes Cleanup commit. Nov 30, 2018
culture Replace artsy/meta with artsy/README Apr 5, 2019
onboarding Move README suggestions to documentation playbook Jan 3, 2019
playbooks Merge pull request #179 from sweir27/on-call-slo Apr 15, 2019
practices Some spring cleaning in the repo Feb 7, 2019
resources Some spring cleaning in the repo Feb 7, 2019
scripts Updates the metadata generated Sep 11, 2018
.gitignore Initial merge of potential, meta, guides and mobile in README Aug 19, 2018 Update links to https 🔒 Dec 2, 2018
spellcheck.json Initial merge of potential, meta, guides and mobile in README Aug 19, 2018
tsconfig.json More tweaks and adds #readme to all of the TOC links Aug 22, 2018

Artsy Engineering CircleCI

Welcome to Artsy! If you're a new team member, we're excited to have you! Here are your onboarding docs.

This repo is a work in progress. In fact, your first pull request could be to fix or add to this doc. Reach out to your mentor or anyone else on the engineering team with questions, or try the #dev Slack channel 🔒.

Whether you're seasoned or fresh out of school, take a moment to read Your First 60 Days at an Engineering Job.

We split this repo out into different sections, each one has a summary of what's inside to make it easy to browse.

Careers at Artsy How do we grow people
Conference Notes Artsy Engineers' notes from attending conferences.
Engineering Culture What makes Artsy Engineering tick?
Events at Artsy Documentation on regularly occurring events and meetings.
Onboarding Notes for New Engineers Your first steps to being productive
Playbooks Tips, procedures, and best practices
Engineering Practices How do we handle cross-functional concerns.
Engineering Recommendations Collections of further reading.

Artsy Engineering Operations

Product & Engineering Teams

Artsy product engineering is organized in product teams. Each team has a purpose, eg. "Help galleries get the most out of Artsy and run their business better", and Key Performance Indicators, or KPIs, eg. "The number of artworks uploaded by partners." Each team has members with different responsibilities, including a Project Manager, a Designer, a Technical Lead and Engineers, depending on size. Sometimes the same person wears multiple hats.

You can see this organization in the Product section of Notion 🔑.

Engineers typically work on a product team and may also belong to an Engineering Practice.


If you are on call or asked to fix an immediate issue, check out our doc on how support works and reference our support wiki 🔒 for up-to-date playbooks on how to solve issues.

Creative Commons License

You can’t perform that action at this time.