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.
Front-end Practices: web and iOS