Welcome to Artsy! If you're a new team member, we're excited to have you! Here's 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.
| Section | |
|---|---|
| Best Practices | What are our agreed upon best practices? |
| Engineering Culture | What makes Artsy Engineering tick? |
| Events at Artsy | Documentation on regularly occurring events and meetings. |
| Playbooks | How we get stuff done. |
| Engineering Practices | How do we handle cross-functional concerns. |
| Engineering Recommendations | Collections of further reading. |
| Onboarding | Your first steps to being productive. |
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, an Engineering 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 belong to an Engineering Practice.
-
Platform Practice
- Team lead: Joey joey.aghion.com
- Slack: #platform-humans
- Platform Practice Overview
-
Front-end Practice
- Team lead: Orta orta.io
- Slack: #front-end, #front-end-ios
- Front-end Practice Overview
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.
