Experience: 2-4 Years
● A good idea of Engineering design principles, both at a high level and low level.
● Strong knowledge of data modelling and normalization.
● A strong idea of practical uses of data structures and algorithms. We don’t expect you to have strong theoretical knowledge, but enough to
understand what would make your system slower as it scales, and how could you avoid that in the first place.
● Awareness of the trade-offs and benefits of the programming mindset/paradigm you are accustomed to (and it’s alternatives you know less about but want to learn). For example, if you have chosen OOPS as your go-to methodology, you should be aware of where what makes for good object design, or why should the state be bundled with behaviour in the first place. Likewise, if you prefer functional programming, you should be able to justify why pure functions without state make sense to you.
● A strong idea of practical uses of data structures and algorithms. We don’t expect you to have strong theoretical knowledge, but enough to
understand what would make your system slower as it scales, and how could you avoid that in the first place.
● Hands-on experience with scripting languages in the back end (Python/Ruby/NodeJS, etc) and JS in the frontend. Our code is Python but we are exploring frameworks that make asynchronous easier to do, so Nodejs or Python 3 event loop knowledge is very helpful.
MongoDB/Cassandra, or other document databases, our current schema is in Postgres, but schemaless design will come into play soon.
● React, CSS and frontend design
● AWS or GCP
● Contribution to any open source library code is a huge plus.
● Being aware of good practices when collaborating in version control (Git, Mercurial).
● Some knowledge of DevOps. It would be awesome if you have been part of the deployment process and understand it in your projects!