lvl100Sign in

Christie

Engineering Manager

  • United States · Remote
  • Full-time
  • Posted

Skills

  • C#
  • React
  • Logistics
  • Microsoft Azure
  • Scheduling

Job description

You run the team day to day and are accountable for its outcomes and its health. You are inside the team, not above it: one-on-ones, hiring, performance and merit reviews, capacity planning, the on-call rota and the team's record are yours. You answer for capacity when the product owners set quarterly priorities, and you say no out loud when the queue is longer than the team. The release calendar itself is run by the delivery lead; the technical standard is set by the Technical Lead. You make sure both have the people and the time to do it.

You will be one of the first two hires into a team that does not yet exist, so the first year is a build: you interview and onboard every seat after you, in waves, while the platform is transitioned from the current provider.

What you will do

•Hire the team with the VP and the Technical Lead: write the briefs, run the loops, write the decision with its evidence, and own the first 120 days of every joiner.
•Run one-on-ones and keep the record: performance, merit, growth, and the written decision when a hire is not right.
•Own capacity planning: what the team can commit to each quarter, what it declines, and how displacement is shown to the business before a re-plan.
•Keep the on-call rota fair: equal turns, published a quarter ahead, nobody two weeks running, nobody in their first month.
•Keep the approved tool list and the team's working policies, with the VP approving changes.
•Read design reviews and pull requests well enough to judge the quality of an engineer's review and coach on it. You are not expected to code.
•Watch the measures and act on them: delivery against promises, escaped defects, service levels, time off actually taken, review turnaround.
•Run the people side of the transition from the outsourced provider: who shadows what in production, in what order, and how knowledge is written down rather than carried in heads.

Requirements

•Has built or scaled a software team of ten or more engineers, ideally remote, for a North American company.
•Has run hiring loops, performance reviews and difficult conversations, and can show how decisions were made and written.
•Technical enough to follow a .NET and React codebase, an architecture discussion and a pull request, and to tell a good code review from a weak one.
•Has run or materially improved an on-call practice and can describe what made it fair.
•Understands AI-assisted development well enough to tell whether a team is using it well: what to look for in review quality, defect rates and the state of the repository guides.
•Clear written English; writes decisions, not slides.

Preferred Qualifications

•Experience taking a platform over from an outsourced provider or a previous team.
•Experience with multi-tenant SaaS or operational business software (ERP, logistics, rental, scheduling).
•Experience with Azure DevOps Boards and delivery metrics.

Browse all jobs by role, city or company