Hi! I’m Ryan, the Head of Marketing at Modash.
I’m looking for a software engineer to join our marketing team. Here's a little background, examples of the things that you might work on, and things you probably want to know.
Having an engineer in the marketing team has been part of our secret sauce for the past 2-3 years. The role isn’t new, but our current engineer (Silver Taza) is moving onto new pastures soon. We're looking for someone to fill his (rather large) shoes.
90% of your time will be spent in the Discoverability team, working with Usman.
For context, our marketing team is split into three (Brand, Product Marketing, Discoverability).
“Discoverability” includes all the initiatives that help Modash get found when people search for stuff. Mostly SEO & LLM visibility.
Here are three examples of what we have built via engineering for SEO purposes.
These are subfolders in our website that contain thousands of templated pages, using our own data. The main two are:
These are exactly as they sound: free tools for specific, small use cases. Examples:
The idea behind all of them is to rank for specific search queries, solve the user's immediate need (like finding the engagement rate of an Instagram account), then show the user that more data is available if they sign up.
Most of our landing pages and blog content is automatically translated using a system built with Crowdin. This means that every single thing that we publish in English gets amplified (+10-50% more traffic typically).
For example, this English article has alternative language versions like these that capture additional search traffic:
Outside of those projects, the remaining 10% of your time will be spent as needed in other areas of marketing. This lets us move fast without depending on other teams or taking engineering resources away from Product. Here are two random (non-discoverability) examples.
The stack is Vite + Vue, deployed to S3 via AWS.
From Silver’s perspective, these are some of the technical challenges that you’ll need to solve:
1. Build and deployment speed at scale. Some projects generate over 10,000 statically built pages. A naive full rebuild could take 40+ hours. The role requires designing smart incremental build and deployment strategies that keep pages up to date without unacceptable build times.
2. Infrastructure breadth. There are already ~15+ different tools/projects to understand and maintain, each with its own nuances. You’ll need to be familiar with all of them in order to be fast in making updates & fixes.
3. Memory constraints. Everything needs to be built in a way that doesn't exceed memory limits during build or runtime. This requires thoughtful architecture decisions.
Requirements
Benefits

Velera

Twilio

Guidehouse

Neato®

Segment

Modash

Modash

Modash