Stop applying to remote jobs that are already dead.
StillOpen is a remote job board that reads openings directly from each employer's own applicant tracking system (ATS), checks that each one is still listed, and closes it about 4 hours on average after the employer takes it down.

All listings

Christie via Workable

Engineering Manager

United States manager
still open verified 17h ago posted 1d ago seen 1h ago
Apply at apply.workable.com

This is the employer's own posting, not a copy on a job board.

What we know

Is it still open?

Confirmed still open

Last checked 17h ago — checked against the employer's own applicant tracking system, which is the company answering directly.

We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.

Check this listing's status as JSON

How old is it?

Posted 1d ago

The date the source published, not the day we noticed it (2026-11-20). Last seen at its source 1h ago.

Is it remote?

Marked remote on the employer's board

Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.

Who may apply?

United States

The description states no restriction of its own. This is the source's own tag.

Pay not stated

Similar roles pay $190.2k–245k/yr

Middle 50% of 226 listings that do state pay — Engineering · Manager · United States · USD/year. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.

Skills named in the ad

AI ToolsAzureCode ReviewDesign ReviewsDevOpsERPIncident ManagementReactWorkforce Planning

Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.

Carried by 1 source

The listing

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.
Apply at apply.workable.com