Imagine yourself developing a product that is loved by hundreds of digital marketing agencies around the world. You’re surrounded by teammates that care about getting remarkable work done and you get to develop yourself and your career. That’s what being an engineer at SEOmonitor is like.

There are currently 3 teams in our engineering department - which is not that large, by the way: there’s only 12 of us. We’ve done a quick brainstorming session, as we like to do from time to time, to identify some key traits in a top-notch colleague.

The results are in:

“A strong attention to detail and analysis capacity, keen on respecting deadlines”

“Strong sense of ownership on their work, from development to release”

“Proactivity and self-learning”

“Autonomy after the initial adjustment period”

“Good sense of humour”

“Clean (-ish, at least) code. (Only -ish, because it’s a skill that can be learned)”

“A higher interest in creating value than in merely solving the tasks at hand”

“Enjoys working with a smaller team”

“Takes pride in their work and its high quality”

• The Topics team solves problems like delivering a comprehensive resource for free keyword research, on over 100 million entities.
• The Platform team was the first group that was created. The platform is the core product that helps SEO agencies run complex forecasting scenarios, manage hundreds of campaigns and uncover insights, by gathering lots of data from Google Analytics, Ads, Search Console, Search Results, and plenty of other sources. And when we say a lot of data, we mean it: we currently have 30T worth of data stored in our databases.
• The Signals team makes sure our users never have to use Excel to build insightful reports, by automatically interpreting thousands of data points and presenting just the right ones.

From time to time, teams might also switch members, to keep things challenging - we like challenges a lot. You can learn about some problems we have overcome, in your first interview.

You’ve seen by now that we value quite a number of qualities on the more human side of things. But for an engineer, we would also look for some technical traits and experiences.

Technical requirements:

• Min. 3 years of practical experience in OOP programming
• Strong knowledge of PHP web frameworks (experience in at least one of the following: Laravel, Zend, Symfony)
• Good knowledge of JavaScript (previous experience with jQuery, Vue, React, etc.)
• Good understanding of HTML 5 and CSS 3
• Understanding of MVC design patterns and REST-ful API
• Solid background in building scalable distributed products and practical experience with caching