Backend Engineering Lead

All together 2024.jpg

Hi 👋

We are Bïrch. Our product is a mighty toolbox for all the things creative and growth marketing teams do — content creation, collaboration, and ad campaigns, all in one place. We’ve been in the game for over 8 years, trusted by 600+ companies and more than 5,500 marketers. With billions in ad spend running through our platform, we’re not just keeping up, we’re one of Meta’s fastest-growing partners and officially backed by both Meta and Google. Recently, we rebranded from Revealbot to Bïrch, and we wrote about this transformation journey here.

We’re hiring a Backend Lead to take over part of the engineering team so our CTO can focus on more strategic work like long-term architecture and product direction. In the first few months, this person will be deeply involved in day-to-day coding, while gradually taking on more leadership responsibilities**.** The role includes running 1:1s, supporting growth, catching quality issues earlier in the process, and contributing to architectural decisions. We’re looking for someone who can guide engineers, give clear and honest feedback, and help the team run effectively without depending on the CTO to step in.

🌍 Who are we?

We’re a remote-first team of 35 friends spread around the world with an HQ in Barcelona. We’ve built one successful product and now transitioning to a broader vision. We hire globally and love meeting offline: last two years we were in Barcelona, the year before in Istanbul. Here’s our team’s Instagram that can show you more of who we are. We are a spicy mix of different cultures and backgrounds.

Feel our vibe better from this video from our annual Onsite in Barcelona:

https://www.youtube.com/watch?v=ipn1JGdcFcA

✍🏼 What will you do?

You’ll report directly to the CTO and manage three talented backend engineers — Kamila, Marat, and Dmitriy. Some of your work areas:

[ ] You’ll start with a 70/30 split between hands-on coding and leadership, gradually moving toward a 50/50 balance. By leadership, we mean making technical decisions, shaping high-level prototypes, and overseeing implementation across the team.
[ ] You’ll work closely with the team to support their growth: running regular 1:1s, giving feedback, and helping team identify their strengths, areas to improve, and next steps in their development. You’ll also lead performance reviews aka feedback cycles.
[ ] Around 30% of your time will be spent on code reviews, with a focus on logic, readability, and overall quality.
[ ] You’ll take the lead on architectural design — thinking through and writing the foundational structures that other developers can use to build features, services, or entire parts of the product.
[ ] You’ll participate in planning sessions, helping to estimate, prioritize, and guide backend work in a way that aligns with product and technical goals.
[ ] Take part in hiring for the backend team as we grow — shaping the process, writing job descriptions, screening candidates, and interviewing potential new teammates. </aside>

How do you know you are succeeding at Birch:

In your first months, you’ll shadow the CTO to understand the product, the team, and how we work — preparing to step into a key leadership role.
Within 3 months, you’ll get up to speed on our industry (ads, Meta ecosystem), take over team communication, lead all 1:1s, and begin doing regular code reviews.
By month 6, you’ll be running deep, context-aware reviews that go beyond surface-level issues.
By month 12, you’ll be leading the architecture for mid-size projects and serving as the go-to technical lead for the backend team.

🧑‍🎤 Who are you?

You’ve led a small engineering team (around 5–6 people), ideally in a startup. You’ve helped people grow, improved how the team works, and introduced lightweight processes that keep things moving without slowing the team down.
You’re confident in Go, with solid PostgreSQL experience. Go is especially important right now, as it’s where we need the most support. Ruby is also active in our stack.
You challenge ideas constructively and aren’t afraid to say, “I think we should do it differently.” You back it up with reasoning, helping the team adjust without creating blockers or friction.
You’re good at quick prototyping — building simple MVPs that show value fast. You don’t overengineer, but you know when to keep the bar high and when to let things be simple.
Experience with Python is a plus, especially since we’re building AI tool and services that rely on it. It’s not required, but helpful. </aside>