We are growing quickly and looking for software engineers on all our teams across product and infrastructure. Most of our software engineers would describe themselves as a T-shaped engineer with one skill they are expert it (e.g. frontend, backend or devops), and multiple skills they are familiar with. Please apply and we will make sure to match you with an opening that fits your background and interest. You can expect to get your hands dirty with:
- Building, testing and shipping features like chat, staffing, project management, design collaboration, integrations, workflow editor and more;
- Be part of important product discussions, and discuss with product managers, ux designers and other engineers;
- Creating and contributing to technical specs and testing/rollout plans;
- Mentoring and supporting team mates to help them grow;
- Be part of important technical difficult discussions.
The tech platform we are building
Superside is right now in a unique position to expand on existing deep customer relationships and we are gradually introducing a customizable creative operations system – specifically built for the large-scale enterprise use case. First iterations of many of these elements are already in place.
This "Creative OS" is structured around 4 distinct functional areas:
Drag&Drop Brief Editor: The customer can configure their own creative briefs per product and define rules for who should be allowed to submit projects.
Assignment, Planning & Project Management: The customer can create automatic assignment rules for incoming projects (e.g. all critical deadline projects should go to Superside) or decide on a per project basis inside the Superside PM tool who should do what. The customer can also plan campaigns, chat internally on an "Epic" level and manage their own non-Superside projects.
Project Execution, Design Commenting & Collaboration: The most important part of the Superside app is the actual project execution, where Superside should impose an opinionated process for how creative projects should be executed in various stages. Commenting by multiple team members should be made easy and centered around the creative use case.
Output, File Management & Result Measurement: Finally, all creative projects need to go where customers can see them, and Superside should make it easy to output projects to Digital Assets Managers, Marketing Clouds, Ad Servers or FB/Google ad managers. The dream is for Superside to eventually "close the loop" and link the actual project result performance back to the creative that has worked on the file.
Along every step of the 4-step framework the customer will also be given the opportunity to create workflows and automations. Inside the Superside's workflow editor, the customer can break down complex projects into milestones, decision points and automated integrations (e.g. «add final file to DAM», «create Facebook ad-group using final output» or «push final file to email marketing software»). When the customer creates a new project, they select the right workflow template to get started. By automating the process, the customer is free from having to update old process documents and to know what to do when and. Work items are sent to the participants notifying them of what they have new to do, and integrations are executed automatically.
Superside will continue to sell large-scale annual contracts of $100K-$1M+, and not move into "SaaS-land" of "charging $9 per seat". Superside will not sell stand-alone tech, but offer a combined bundle with Services+Technology. The return on the Superside Creative OS will primarily be through increased retention – a 3 percentage point increase in monthly retention is sufficient to double revenue over 2 years (1.03^24=2.03). Think about that for a second. Superside is targeting $50M in ARR in 12 months from now and if Tech can deliver "just" 3 percentage points retention that is then worth $50M in additional revenue. It's insanely hard to build a SaaS business with $50M in ARR. In addition the Creative OS will make it easier to close deals, and by restricting certain features to more premium plans only will make it easier to drive upgrades.
Our tech stack
Superside's backend is fully written in Kotlin and Spring, and our frontend is Typescript, React. We use Terraform to manage our infrastructures and deploy Docker containers to ECS, use Datadog and TrackJS for monitoring and are u
sing Gitlab as our Devops/CICD platform.
Superside's core principles
Be kind and trusting. We treat everyone with warmth and respect. We are open and transparent. We always start from positive intent and keep it there until that trust is violated.
Seek the truth and be ego-free. Never blindly say "yes, that sounds like a good idea". We believe disagreement is necessary to achieve progress, as long as our intention is constructive, and not selfish.
Insist on clear, simple solutions. Complex structures are hard to implement, costly to maintain, scale poorly, and difficult to improve. There is no shortage of good ideas to work on.
Know what NOT to do. Conclude, move on, say no. Ineffectiveness comes from endless search for the perfect solution, constant alignment meetings, slow decision-making and doing too many things at once.
Decide and take responsibility locally. Whoever is closest to the problem should own up to it and form a forceful opinion of what is the right decision. Management should view its role as enabling others to take the right decision.
Understand good design experience. We are in the business of delivering great design. Therefore, we must appreciate and understand beauty and function – both on and off the job.
Learn, create and have fun. Let's not forget that some of the greatest inventions in the world were the result of play.