Senior Software Engineer, Virality and Activation

Your Impact

• Own features end-to-end: from technical design through launch to metric readout, operating with a high degree of autonomy
• Design and build scalable backend systems that power growth loops — sharing flows, invite mechanics, notification pipelines, and onboarding infrastructure
• Lead the instrumentation strategy for new features, ensuring the team has the data it needs to measure impact and iterate with confidence
• Drive A/B experiments: define hypotheses, instrument correctly, analyze results, and translate findings into concrete product decisions
• Raise the team's technical bar through rigorous code reviews, design feedback, and proactive documentation
• Partner with product and data to define what success looks like before building starts — and hold the team accountable to it after launch
• Identify systemic gaps and advocate for improvements that increase the team's velocity and reliability over time

We're looking for someone who

• Holds a Bachelor's degree in Computer Science or a related field, or has equivalent practical experience
• Has 5+ years of backend software engineering experience, with a strong track record of shipping impactful, user-facing features at scale
• Has deep proficiency in Python, and has used them to build and maintain production systems at scale; experience with Go or another high-performance compiled language is a plus
• Has strong command of relational databases (MySQL or similar) and has designed schemas and query patterns for high-traffic production workloads
• Has production experience with NoSQL and high-performance data stores — such as DynamoDB, Cassandra, Redis, or Elasticsearch — and can reason clearly about consistency, latency, and scalability trade-offs across storage systems
• Has production experience with Kafka or similar distributed messaging systems, and understands their operational trade-offs
• Is experienced with AWS infrastructure (EC2, S3, DynamoDB, or similar) and comfortable reasoning about reliability and cost in a cloud environment
• Has hands-on experience with A/B experimentation — not just running tests, but designing them rigorously and drawing well-grounded conclusions from results
• Defines success in terms of user outcomes and business metrics, not task completion
• Operates effectively in ambiguous environments: can scope a loosely defined problem, build alignment around a solution, and drive it to closure
• Communicates technical decisions clearly to both engineering peers and non-technical stakeholders