Application

Apply for this job using the link below that will direct you to Y Combinator Job Portal. We will do our best to contact you shortly.

Apply Now

Infrastructure Engineer

Location

Warsaw

Department

Technology

Annual Salary

$36k - $84k

Join our Technology team to build consumer products and business solutions on top of state of the art language models like OpenAI's GPT. From day one, you will take ownership and contribute to key parts of our technology.

We live and breathe Machine Learning. We love Python, Linux and Git. We tolerate JavaScript, CSS, even React Native at times.

What we look for:
  • 2+ years in Infrastructure or DevOps roles
  • Deep understanding of cloud infrastructure and server performance optimization
  • Interest in MLOps/DevOps
  • Technical fluency in English
  • Great communication skills
Bonus points for:
  • Experience managing high-volume applications using Nginx, Docker, Kubernetes
  • Advanced coding skills in Python
  • Experience scaling production systems
  • Strong knowledge of CI/CD best practices
  • Kaggle competitions (walk me through your solution!)
  • Interesting side projects (we will ask a lot of questions about them!)
  • Deeply technical interests other than software / Machine Learning
  • Currently live coding projects (we will want to have a look at them before your interview)
  • Teaching us something we didn't know before about our product or industry
  • Experience with web sockets, Django, single-page applications, API design
  • Deep understanding of and experience working with GPT-3 and other language models
  • Telling us about something that's wrong with our product along with a concrete and detailed plan on how you would try to improve it
  • Deep first-principles understanding of some computing process, e.g. what exactly happens when you type a URL and press enter, exactly how, for example, blockchain / a neural network / a chess-playing algorithm / Google's Ad bidding / Shazam's song search works (we will definitely want you to tell us all about it!)
  • A story about how you spent 3 days debugging something and finally found a solution
  • A story about how you had no idea how your users were using your product until you started measuring it
  • Expertise in middle-out compression