In his essay “You weren’t meant to have a boss”, Paul Graham argues that humans evolved for hunter-gatherer sized groups—eight being the ideal number. This implies that startups are the ideal place for programmers—the structure of large companies just prevents you from getting much done. Graham’s essay is joined by many authors critiquing the scale of modernity. James C. Scott’s "Seeing Like a State" notes how 1800s bureaucrats attempted to impose process on the land, planting the single fastest growing tree species in a grid—and were met with rampant forest fire and disease. These authors make an excellent point. You can get a lot done as an eight-person team (Mercury launched with a team of nine), and imposing too much structure can be fatal. At the same time, the tension these authors ride up against is that scale has clearly won out: Graham’s Y Combinator now employs over 80 people, and the best permaculturist can’t compete with modern tree farms. Your job as an engineering manager at Mercury is to carefully balance this tension. In this role, you will: <ul> <li style="font-weight:400;">Ensure a team of ~6-8 engineers executes at a high level of technical excellence and stability.</li> <li style="font-weight:400;">Create a fulfilling environment for engineers.</li> <li style="font-weight:400;">Have the confidence and competence to give feedback to engineers of all skill levels.</li> <li style="font-weight:400;">Continue to hone your own engineering craft, by spending a portion of your time coding.</li> <li style="font-weight:400;">Align engineering work with Mercury values.</li> <li style="font-weight:400;">Onboard new engineering hires.</li> <li style="font-weight:400;">Work alongside other product experts to pick the highest impact projects.</li> <li style="font-weight:400;">Collaborate with other teams when work overlaps, ideally to achieve a more cohesive product and simpler, more maintainable underlying technical implementation.</li> <li style="font-weight:400;">Balance building new things with maintaining existing systems.</li> <li style="font-weight:400;">Provide technical mentorship such as PR reviews, pair programming, and virtual whiteboarding.</li> <li style="font-weight:400;">Empower your team to thrive and contribute to making Mercury’s product reliable, beautiful, and useful.</li> </ul> You should: <ul> <li style="font-weight:400;">Have demonstrated the ability to lead a technical team.</li> <li style="font-weight:400;">Have a strong individual engineering skill set. You will go through roughly the same interview process as our individual contributors, with additional interviews for manager skills.</li> <li style="font-weight:400;">Be familiar with our tech stack (specifically, Haskell and TypeScript), or have an interest in learning it.</li> </ul> We encourage you to try our <a href="https://demo.mercury.com/">demo site</a> if you’re interested in applying for the role. Our salary ranges are based on paying competitively for our size and industry, and all employees receive salary + equity + benefits. Individual pay decisions are based on a number of factors, including qualifications for the role, experience level, skillset, and balancing internal equity relative to peers at the company. The ranges shared are for the expectations as laid out in the job description, however we are often open to a wide variety of profiles, and recognize that the person we hire may be less experienced or more senior than this job description as posted. If that ends up being the case, the updated salary range will be communicated with you as a candidate. Salary range for candidates in the US is: $210,000-$248,500. Salary range for candidates in Canada is: CAD 200,000-236,500. #LI-CP1

Mercury is an equal opportunity employer.

See more open positions at Mercury

Privacy policy Cookie policy

Getro.org is a community-driven initiative to ease the impact of COVID-19 by connecting tech professionals and hiring companies. It's free for job seekers and companies, and curated by a growing list of referral partners.