Development Team Lead

Curio was built to be a different kind of agency, one that's high-performing but human. We do web design, development, and CRO for B2B SaaS companies, and we've built a small but mighty team that loves what they do.

At Curio, we're all about being resourceful, curious, and committed to getting things done. We work with people who are always learning and genuinely enjoy solving problems.

If you thrive in an environment where you have ownership, clarity, and support, while being trusted to just get on with your work, you're going to love it here.

About the role:

We're looking for a Development Team Lead to ensure Curio's development team operates at a consistently high standard - delivering builds that are on time, technically excellent, and scalable. The Development Team Lead sits at the intersection of people, process, and delivery, responsible for leading a team of developers, maintaining quality and velocity across all dev output, and building the systems and culture that allow the team to scale.

Most of that work happens in Webflow, and you need to be excellent there. Figma handoff to a clean build, CMS structures editors can actually use, interactions, custom code when you hit limitations.

We also build outside Webflow. Some projects call for a framework and a headless CMS instead, so you should be as comfortable in a repo as you are in the Designer: Git, pull requests, build pipelines, deploys, DNS, the whole path from local to live.

What you'll do:

Manage the Development team effectively

1. Ensure the team consistently delivers projects on time, within budget, and to Curio's quality standard, overseeing timelines and budgets across all active dev work to ensure deadlines are realistic and met.
2. Function as a developer on complex and high impact projects as needed, ensuring the team is trained to cover or maintain that work going forward.
3. Act as the first point of escalation for dev team issues before they reach senior leadership.
4. Oversee capacity planning, flag issues early, and coordinate resource allocation across internal developers and freelancers.
5. Set and uphold quality standards across all development & QA outputs, ensure processes are followed consistently by all team members, and review work where needed before it reaches the client or goes live.
6. Monitor performance, responsiveness, and cross-browser/device compatibility across builds.
7. Hold the team accountable to clean, scalable, and maintainable practices.
8. Foster a culture of ownership, curiosity, and continuous improvement within the team.

Own team development

1. Help the onboarding process for new developers joining the team.
2. Build and maintain a structured L&D program covering core skills, tools, and processes as the evolve.
3. Create and maintain internal documentation, tutorials, and reference materials.
4. Encourage knowledge sharing across the team through regular reviews, walkthroughs, or internal sessions.

Coordinate freelancers

1. Checking freelancer outputs against Curio's standards at all times.
2. Coordinate with freelancers on timelines, standards of practice, expectations, and deliverables.
3. Regularly review freelancer work and provide consistent feedback to Ops.

Maintain Development Team documentation & processes

1. Ensure all key workflows are documented, accessible, and up to date, including clear procedures for recurring workflows such as project kickoffs, QA, deployments, and handoffs.
2. Capture new processes systematically rather than allowing them to stay as tribal knowledge.
3. Continuously audit and improve existing processes to reduce friction and improve output quality, taking a careful and considered approach to implementing changes.
4. Work with leadership to align dev processes with broader company standards.

Ensure seamless cross-functional collaboration

1. Ensure handoffs between accounts, design, dev, and QA are smooth and clearly documented.
2. Work closely with design, accounts, and leadership to ensure dev is aligned with broader project goals.
3. Represent the dev team in internal planning conversations and provide realistic input on scope and timelines.
4. Communicate technical considerations clearly to non-technical stakeholders.
5. Collaborate with other team leads to continuously improve cross-functional workflows.