Python Software Engineer
Walk to the top floor of our office in the center of Utrecht twice a week (or more), log in 💻 and be ready to take ownership of your work. You will sit next to like-minded tech-savvy Channapeople, who are as excited as you are to continue building Channable’s success as one of the best SaaS companies of 2022 🎉. We have a strong engineering culture that focuses on the correctness, maintainability, and reliability of our code. Are you ready to be part of our international team? 🌍
In this position, you will be part of our diverse product team, that works on our main web application. The Product team is mainly responsible for our Python3 backend, which powers our API and serves as the main entry point for our services. You will be working on our API integrations, ads services, our export channels, new user-facing features, and our background jobs through which we process billions of products per day. The Product team is working closely together with our Infrastructure and DevOps teams, which are developing many other services that power Channable under the hood, and all together we build our powerful tool!
- Contribute to our Python components and support new API’s
- Design, develop, and test new product features
- Collaborate with and review PRs of other team members
- Improve the reliability and robustness of our application
- Work on scalability and performance improvements
- Work together with the sales and support teams on requirements and issues
- Collaborate with the Integrations department about technical matters
We use the following technologies and tools:
- Languages: Python, SQL
- Libraries: Flask, SQLAlchemy, Click, requests, async, logging
- Tools: Postgres, Redis, GCS, Alembic, mypy, pip, Sentry, Icepeak
Want to read more about our development adventures? Then visit our inspiring tech blog: https://tech.channable.com/
And if this made you enthusiastic, you can also take a look at some of our open-source work at https://github.com/channable to get a feeling of how we work together and what our code looks like.
Something looks off?