Engineering Manager

Job highlights

• Requirements. What were looking for . Must have
• Experience taking over a team mid-transition
• Youll need one some days,and itll help on the good ones too.
• Prior exposure to release orchestration. Java development experience

Job Summary

This is the role today. If you do it well, theres room to take on more.

Youd inherit a team spread across three continents and about ten time zones, and likely pick up one or two additional small teams alongside it. The team includes engineers who do not need you to tell them how to write code. What they need is someone who clears the path between them and shipping and treats "I dont know, let me find out" as a perfectly good answer in a 1:1.

Responsibilities

• Own delivery and team health for Feature Management
• Steer decisions with questions, then let your engineers own the architecture. If youre the one drawing the boxes, somethings gone wrong
• Give feedback in the moment, not in a surprise essay once a year
• Hire, grow, and have the hard conversations when someone isnt where they need to be
• Cut process that exists because someone was once scared
• Use AI agents to run your own job faster: pull together whos on PTO next week, the lead time of your teams PRs, what ticket needs attention, what shipped and what it broke, instead of digging through five tools by hand

Not write code. Not approve every PR. Not sit in on every incident call because you dont trust the on-call rotation.

Requirements

What were looking for

Must have

• A track record of improving automation and developer tooling, not just using whats handed to you
• At least 5 years as a software developer before moving into management, so the technical instincts below are earned, not borrowed (ideally, you have developed in Go)
• 5+ years as an actual engineering manager, with 5 or more direct reports at once. Not a tech lead with 3 reports and half a week of coding
• Genuinely technical: enough hands-on background in CI/CD, feature flagging, or platform engineering to ask a sharp question in a design review, plus real experience managing engineers who are better coders than you, and youre comfortable with that
• A track record of running distributed, multi-timezone teams: clear owners, clear deadlines, decisions that dont wait on a meeting that nine time zones wont allow
• You take the heat for your team and hand them the credit
• The instinct to measure what shipped and what it did for customers, not green dots in Slack. You know deployment frequency, lead time, change failure rate, and time to restore, and you use them to start conversations, not to rank people
• A real appetite for AI: recent, hands-on use of at least one coding agent (Claude Code, Gemini, Cursor, Kiro, or similar) to run your own work, not necessarily to ship product code. You push your team to try these tools too, and have opinions about where they help and where they dont, not secondhand takes from a keynote you watched once
• Experience taking over a team mid-transition

Nice to have

• A sense of humor. Youll need one some days, and itll help on the good ones too
• Prior exposure to release orchestration
• Java development experience

Who this is for

Youd rather ask what's actually blocking someone than "why isnt this done yet." And when the unpopular call is needed, you make it, even when the timing is inconvenient.

Youre fine with ambiguity that has a shape, not ambiguity thats just chaos with a Jira board. Sharp and a little irreverent beats technically flawless but rigid, as long as you still ship.

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.