We're looking for a Data Engineer to build out a series of resilient and flexible data pipelines, feeding mountains of information into systems to inform, evaluate, and execute on key product strategies. You’ll help tens of millions of people connect to each other and themselves – through astrology – in real, meaningful ways.

What you'll do

• Design, build and launch efficient and reliable data pipelines to move data between our internal systems, AWS, and GCP
• Collaborate closely with DevOps to schematize your work into Terraform templates
• Partner closely with data scientists, engineers, product and cross-functional coworkers to identify new data sources and transforms to elevate our products
• Build monitoring and observability systems to keep your pipes running effectively while absorbing faults 
• Work to model, investigate, and push greater efficiency in both the cost and speed of our products

What you'll bring

• 5+ years experience in building data management/processing systems in production (ETL)
• CLI-level experience with either AWS or GCP data processing tools
• Demonstrable experience using a scripting language like Python or Bash to stitch products and APIs together
• Clear communication and the ability to collaborate with cross-functional coworkers across product, data science, and engineering
• Creativity and an appreciation for our intentionally-not-like-other-apps aesthetic  

Our technical interview process

Our interview process is divided into four phases — an initial interview with a recruiter, a secondary interview with a manager, 3–4 virtual onsite interviews (1 hour each, 2 of which are technical screens) with peers and cross-functional coworkers, and lastly, a meeting with our founder.

We realize technical interviews can feel challenging to prepare for, so here’s what we’re interested in seeing from you: 

• Clean, easily-testable code that’s compiled frequently  
• Clear communication around your decision-making process 
• Creative and thoughtful problem-solving 
• Self-reflection around past projects and the ability to articulate what worked and what didn’t   
• Ability to partner with cross-functional coworkers outside of engineering 

We’re not interviewing for: 

• Pure coding skills (we’re a cross-functional company and the ability to collaborate across disciplines is equally as important as coding ability)   
• Memorization of complex algorithms or trivia (we all have access to some form of search engine and use it when we forget) 
• Your ability to know everything (we may ask you a question you don’t know the answer to and that’s ok) 
• “Cracking the Code” / LeetCode-type knowledge