At lemlist, we focus on delivering value fast while maintaining simplicity in our architecture and development processes.
We use a monorepo and trunk-based development (monobranch with feature flags), allowing us to deploy code daily.
Our philosophy is to “ship value fast”—we prioritize delivering functional features quickly rather than getting lost in over-complicated architectures. For this reason, we opt for a simple monolithic architecture rather than microservices.
We already solved our main scaling / performances problems with MeteorJS or MongoDB. We make 32M$ / year and we have 40K users. We don’t need architects. We need to deliver features and value for our users.
We operate within two organizational frameworks:
- Vertical organization: CTO > VP of Engineering > tech leads > developers. This vertical structure is key for applying Lean principles and ensures continuous improvement through mentorship and training, not only for new hires but for the entire team.
- Horizontal organization: We use the ShapeUp methodology, which defines feature squads. Each squad consists of a developer, a PM, and a designer, where the developer is often the sole developer on the team.
➡️ This setup requires the developer to be:
- Fullstack: Capable of handling both frontend and backend tasks.
- Senior: The developer must represent the technical perspective within the product trio (PM, designer, and dev) and clearly communicate their thoughts, without shying away from discussions.
- Ownership and responsibility: Each developer is fully responsible for their features - from concept to production - and must care deeply about the quality of their code and customer feedback.
🧠 The mindset we seek in developers:
Given our fast-paced and lean-driven environment, we are looking for autonomous and experienced developers who thrive under responsibility.
You should:
- Be proactive in shipping features fast and comfortable with the idea of iterations (nothing has to be perfect on the first iteration)
- Be comfortable working in a fullstack role, confidently managing both backend and frontend tasks.