Jina AI is a Neural Search Company.
In general, we’d like you to:
- Be passionate about open source, AI and search;
- Work with craftsmanship and ownership;
- Be efficient and responsible on problem solving;
- Play along with the open source community;
- Speak and write good English.
If we don’t like something, we change it and make it better.
- We do not waste time on things we do not believe.
- We don’t lock up our value and innovation in "the way people have always done it." We are receptive to change.
- We don’t compromise our standard.
We are fully committed to open-source. That means you can view all our code, commits, issues, PRs publicly. Hence, when we conduct the interview, we do expect you to have a certain understanding about our products, tech stack and vision.
ℹ️ A Pull Request is required for Engineering role applicants
Every tech interview involves some kind of code screening. We do it differently at Jina. Since we are completely open-source, it is a good way to evaluate your engineering skills based on your first Pull Request to Jina.
If you apply for one of our engineering roles, you can pick one project (Jina, Dashboard, Examples) and work on one bug or new feature. Submit your work via pull request and pass the CICD. Then we will review it.
Note that not only the code, but also the coding style, documentations, commit style, affect our evaluation.
So what should you start to work on? Here are some good examples:
- Add an example built on Jina to our tutorial section;
- Solve a bug/feature request listed in the issues;
- Improve the documentations.
You are of couse not limited to this, choose your unique perspective and surprise us!
If you choose a very challenging task as the first pull request, it may take you too long and too much energy to finish. However, if you choose a very easy one, e.g. fixing a plural typo, then we can not fully evaluate your engineering skills.
It is your decision and wisdom to find a task at the proper size: proper enough to show your ability without overdoing it. Locking down the problem, estimating the difficulty and getting it done. This is the skillset we expect you to have.
We would like to hear from you about the feedback when using our products. Like really using it, not just looking at our screenshot or documentations. Following the PyPI install instruction or using Docker, either way you need to run the system by yourself. This is the basic requirement for our product related roles.
After playing with our products. We'd like to hear your feedback. What’s your view? What are the good and bad features? How can things be improved? What minimum resources (time & HR) do you need to get this done?
The more you can tell us, the more understanding we have about your skill set.