Career trade-off case study / Case 02
You’re accountable for delivery. You don’t get the final say on everything.
Supporting someone can change what a team is able to deliver. Before accepting shared responsibility, ask whether the plan changes too.
- “Shared accountability”
We reviewed the complete current Australian engineering manager listing, its inline role description and the employer’s written explanation of its values. The redacted written ad appears below. The employer is anonymised; the listing describes an offer, not actual working practices.
- Role
- Engineering manager
- Industry
- Software
- Employment
- Full-time, Australia
- Pay information
- Range includes superannuation
Read the whole offer
What changes when the commitment can no longer be met?
An engineering manager is expected to deliver work on time, develop the people doing it and keep contributing code. Another manager controls the product scope, while a technical lead controls architectural direction. The two managers share responsibility for delivery and are expected to resolve problems together.
That is a fair request if they can agree on a workable commitment. It becomes a much harder deal if raising a limit changes nothing about the deadline. Before accepting shared responsibility, I would want to hear about a disagreement that actually changed what the team was expected to deliver.
This is a detailed advertisement. It names the reporting line, separates responsibilities and provides an escalation route. Those details matter: the question is how shared decisions work when priorities conflict, not whether the manager has any authority at all.
Read it for yourself
See the job ad we analysed
The full written listing is reproduced below from the 19 September 2026 check. Brackets mark identifying names, exact office details and the embedded-video link removed for this anonymised case. The linked video is not transcribed here.
Source materialRead the complete redacted advertisement
Posting details
- Role: Engineering Manager - Hybrid
- Location: Melbourne Office; Sydney Office
- Employment type: Full time
- Location type: Hybrid
- Department: Engineering, Product and Design
- Compensation: A$140,000–A$170,000; offers equity. The body specifies that its remuneration range includes superannuation.
Opening and role overview
[Embedded role walkthrough omitted from this written transcription]
Link to process walkthrough: [identifying video URL omitted]
👋 Thanks for stopping by and learning more about this role at [the employer]! ✨🏗️
We'd love to hear from you 😊 👩💻👩🏽💻🧑🏿💻👨🏻💻
📝 Overview
Build What Matters
The Engineering Manager leads the engineering side of a product team, reporting to and supporting their Product General Manager (PGM). They are responsible for the engineers in their team, including their performance, growth, and day-to-day execution, and for making sure work moves from "ready to build" through to "shipped and stable" with high quality and a predictable cadence, including delivering code themselves.
Delivery is shared with the Product Design Manager (PDM). The PDM owns the what: product scope, design, acceptance criteria, and production monitoring. The Manager owns the how: engineering capacity, sprint planning, unblocking engineers, and the quality of the engineering process. Both are jointly accountable for timelines and outcomes. When something slips or ships with issues, neither role can point at the other.
The Manager also works closely with the Tech Lead, who owns technical quality and architectural direction. The Manager focuses on execution and people. The Tech Lead focuses on technical standards and code quality. In practice these overlap and require close collaboration.
Employment and company background
Employment:
Full-time
Based: Sydney, Australia or Melbourne, Australia
Remuneration (Including Super): AUD $140,000 - $170,000 pending your experience
About [the employer]
[the employer] is the front line AI company for the built world. We build software and AI agents for construction, engineering, manufacturing, and energy companies, helping field teams capture work as it happens and the business turn that activity into structured, auditable records. The [the employer] platforms include [product name], [product name], the [product name], and [product name], and [the employer]’s AI agent is called [AI agent name].
[AI agent name] is our AI agent layer, working underneath [product name], [product name], the [product name], and [product name] to turn what happens on-site into structured, auditable records.
We’ve achieved strong product-market fit - generating thousands of new monthly leads through word-of-mouth and organic marketing alone.
Backed by [investor name], Australia and New Zealand’s #1 venture capital firm, and a graduate of the [accelerator name] Accelerator, [the employer] has grown from 5 people in 2018 to over 150 across 18+ countries. Our team blends deep industry experience with cutting-edge product design to build tools that modernise one of the world’s largest and most essential industries.
Why join and stated values
Why Join [the employer]
At [the employer], you’ll join a global team that values transparency, high velocity, hustle, diversity, and innovation.
We’re open about our metrics, honest about challenges, and obsessed with improving how the world’s most important industries operate. Our environment is flexible, fast-moving, and outcome-driven - designed to help you do the best work of your career.
You’ll be surrounded by people who take pride in their work, care deeply about results, and believe that great culture is built on trust, respect, and continuous learning.
Our Core Values
Our core values dictate “how we work”. We believe that basic human values such as honesty, trust and integrity are required to simply ‘get in the door’. Our values are designed to help us determine if an already great person, will be a great fit at [the employer].
Handle with Care: Handle with thought and care, decisions are considered and consciously delivered
Everything Engineered: Everything engineered, intentional, planned and systematic
Quality Certified: Do it well, with attention to detail and accuracy, or don’t do it at all
Fast Tracked: Fast, incremental, and constant delivery of change
High Vis: A high visibility, transparent and
open environment
Rain, Hail or Shine: Show up for your team, your customers and yourself
Learn more about our values:
Read:
On [the employer]'s Values, Culture and DNA
Listen:
[branded podcast title removed]
On scaling [the employer], diversity, and culture
Benefits and further reading
What We Offer
Competitive, performance-based remuneration
Equity options - own a piece of what you’re helping to build
20 days of paid annual leave, plus sick, carer’s, and compassionate leave
Paid parental leave - 16 weeks for primary carers, 6 weeks for secondary carers (including adoption and stillbirth support)
Professional growth budget and a transparent career development framework
Laptop and home-office setup budget
Flexible work - remote or hybrid, plus the ability to work from anywhere for a few weeks each year
Community & connection - weekly team lunches, global offsites, and our signature “[named session removed]” sessions
Sydney HQ perks - rooftop garden, wellness centre, showers, and cycle storage in [exact office area removed]
Melbourne office perks - micro-roasted coffee bar, on-site parking & bike storage, wellness & mothers rooms, opposite [nearby station removed]
Diversity & Inclusion
We’re proud to be an equal opportunity employer. [the employer] welcomes people of all genders, ethnicities, ages, sexualities, and abilities.
55% of our team identify as coming from underrepresented ethnic backgrounds, 43% identify as female, and our team spans ages 22–51. We believe our diversity makes us stronger - and we’re committed to creating an environment where everyone can do their best work.
Learn More About [the employer]
🎧 Podcasts:
2024: CEO [personal name removed] on scaling [the employer], diversity, and culture
2023: CMO [personal name removed] on accelerating your career
2022: CTO [personal name removed] on building quality features that solve real customer problems
💬 Want to know what it’s like to work at [the employer]? Hear it straight from the team: People of [the employer]
⭐ Read what our customers say: [review sites removed]
🎥 Team Offsites: 2022, 2023, 2024, 2025
How the role is described
🔧 What this role looks like at [the employer]
You'll have direct reports. You'll run 1:1s, progress [the employer] Development Plans and competency matrix levels, set goals, give feedback, and handle performance issues directly. You'll also plan sprint capacity, make sure work is broken into milestones with estimates, track progress, and surface risk before it becomes a problem.
Whilst you won’t be leading a feature or on critical path tickets, our engineering managers still actively contributing code and shipping improvements to our customers - this is not a hands off role. You should be able to follow a design discussion, sense when an estimate is off, and know when "it's nearly done" isn't. You are not expected to own technical architecture, but you are expected to know when to pull the Tech Lead in.
Two shifts are defining what engineering management looks like here:
Forward Deployed Engineering. Teams work closer to customers and ship in tighter loops. Your job is to make sure engineers have real customer signal in front of them, and that the process supports fast iteration rather than adding ceremony to it.
Agentic Engineering. AI is changing what a team of a given size can deliver, which changes how you plan, estimate, and sequence work. You'll need to hold the process standards that keep quality high as throughput goes up, in partnership with the Tech Lead who sets the technical bar.
Day-to-day duties
🔧 Day-to-Day
Plan and manage sprint or cycle capacity, making sure engineers have clear, well-sequenced work broken into milestones with estimates.
Track delivery progress and surface risk or slippage early, rather than waiting for things to go wrong.
Act as the primary escalation path when engineers are stuck, and remove blockers before they stall delivery.
Run regular 1:1s, progress [development plans] and competency matrix levels, set goals, and give consistent feedback.
Manage performance issues directly and constructively.
Deliver code yourself. Not as the bulk of your week, but consistently enough to stay sharp and to keep credibility with your team.
Hold the line on engineering process standards such as test coverage, PR quality, and deployment practices, in partnership with the Tech Lead.
Communicate delivery status to stakeholders proactively, and act as the focal point for communication into the engineering team.
Stay aligned with the PDM on priorities, sequencing, and any scope or delivery trade-offs.
Escalate to the PGM when decisions or resources sit beyond the team's control.
Advertised challenges
⚡ Challenges
Shared accountability. Delivery is shared with the PDM and technical direction sits with the Tech Lead. You'll get results through influence and close collaboration far more than through direct control.
People and delivery pull in opposite directions. Some weeks the sprint wins, some weeks the person does. Judging which is a large part of the job.
Pace. Fast-Tracked is a real operating value, so you'll need to balance speed with quality and sustainable delivery for your team.
Distributed teams across Australia, UK, Southeast Asia, Brazil, Canada. Time zones and async communication are part of the role, not an edge case.
Organisational maturity. Engineering leadership, frameworks, and career ladders are still being established, so you'll be building the plane while flying it.
Who the role is and is not for
✅ Who This Role is For
You've managed engineers before, or you've been a Tech Lead or Senior engineer already doing the job unofficially and want to make it official.
You get more satisfaction from a team shipping well than from being the one who shipped it.
You have difficult conversations early rather than letting things drift.
You still write code and want to keep doing it alongside leading a team
You're comfortable owning an outcome jointly with someone else and not needing the final say on everything.
You're drawn to real-world impact. Our users build wind farms, highways, and mines in 100+ countries.
You want to shape how an engineering org works through our next phase of growth, not inherit someone else's playbook.
🚫 Who This Role is Not For
You want to own architecture and technical direction. That sits with the Tech Lead here. If that's what you're after, the Engineering Tech Lead role is the better fit.
You want coding to remain the majority of your job. You'll still ship code here, but it isn't the bulk of the role.
You've moved fully out of engineering. Coding is a reduced part of this job, not an absent one.
You want full Engineering Manager scope with unilateral control over people, process, delivery, and technology. Ours is deliberately narrower.
You manage from a dashboard. This role needs someone in the detail with their team.
You avoid performance conversations or route them straight to HR.
You want a mature engineering org with a VP of Engineering, established ladders, and defined management frameworks already in place. We're building that, which is the opportunity if you want to shape it and a mismatch if you need it to already exist.
Skills, tools and hiring note
🎯 Skills & Tools
Must Have:
Experience managing or leading a team of engineers, with direct reports or clear equivalent responsibility
Strong delivery management across capacity planning, work breakdown, estimation, tracking, and early risk escalation
Current, hands-on coding ability. You'll still be delivering code, and understand best practices
Hands-on background in Javascript / TypeScript, Node.js, Angular or React, MongoDB
Track record of growing engineers through feedback, goal setting, and career development
Willingness to handle underperformance directly and constructively
Comfort operating in shared accountability with product counterparts
Nice to Have:
Experience in a scale-up or high-growth product environment
Experience managing distributed or multi-timezone teams
Experience improving engineering process such as sprint cadence, release process, or on-call
Practical experience with AI-assisted development workflows
Essential Tools:
Jira or an equivalent planning and tracking tool
Confluence or equivalent documentation practice
AI coding tools (Claude Code, Cursor, or similar)
Bonus Tools:
AWS
Observability tooling (Clickstack, Datadog, Bugsnag, Sentry)
PLEASE Note:
We hire directly and don’t work with agencies
Anonymisation note: This is the complete written vacancy description and listing details, with visible bracketed substitutions for the employer, products, investor, accelerator, internal programme acronym, review-site names, exact office areas, promotional titles and video URL. The embedded walkthrough itself is not transcribed. Wording, stated employment terms and duties otherwise follow the captured listing; spacing and section grouping are reformatted for the web. The saved original and replacement record remain private.
Four places to look closer
Four trade-offs inside this role
The ad states the responsibilities unusually clearly. Each statement still asks a candidate to weigh something they may gain against something they may give up. The questions below test how those choices work when priorities collide.
The engineering manager and product counterpart share delivery responsibility. Product scope and technical direction sit with other roles, while decisions or resources beyond the team’s control go to a general manager.
Sharing the result means agreeing on what can change
There is a sensible reason to split this work. Product decisions, technical decisions and people management require different kinds of attention. An engineering manager could value having capable colleagues responsible for those other parts, particularly if it leaves more time to help the team do good work.
Suppose a proposed feature needs more time than the engineers have available, and reducing it would remove something the product manager considers necessary. That is an illustrative situation, not something we know happened at this employer. It shows why a clear list of responsibilities still needs a way to settle a disagreement.
The ad names a general manager for escalation, so the manager is not left without a route to a decision. The trade is concrete: product and technical expertise are shared, while the engineering manager gives up the final say over scope and architecture but remains responsible for delivery. If Autonomy matters strongly to you, ask how much freedom remains to revise an unworkable plan. If you value Collaboration & relationships, shared decisions may be worth that loss of control, provided they produce one realistic commitment. The written ad cannot tell us how promptly this happens.
The managers agree a deliverable plan and get a timely decision when they cannot resolve a conflict themselves.
Scope, timing and resources remain fixed after a capacity objection, leaving the manager responsible for a commitment they could not make alone.
Can you walk me through the most recent disagreement between product and engineering about what could be delivered, including who decided and what changed in the commitment?
Then listen for
Listen for an actual change to scope, timing, staffing or another priority, or a concrete explanation of how the original commitment became achievable. An answer that ends with everyone working harder leaves the original capacity question open.
What the ad cannot tell you: How well the escalation route works in practice, or whether managers are held to commitments they could not reasonably meet.
The advertisement explicitly acknowledges competing people and delivery needs. It expects the manager to judge which takes priority while developing staff and managing performance alongside delivery.
When the person takes priority, does the plan change too?
A sprint is a short period of planned development work. The wording acknowledges that supporting someone and keeping delivery moving can compete for the manager’s time. A manager might postpone a routine development discussion during a release, then make time for it afterwards. They might also reduce the work planned for the week when someone needs more support.
Imagine that a team member needs substantial coaching during a week with a fixed delivery commitment. Spending time helping them changes the capacity available for other work. Unless the plan changes or someone provides extra help, the same amount of unfinished work remains. That is a possibility to investigate, not a conclusion about this team.
Supporting a person takes time from planned delivery. A manager who values people leadership may welcome that responsibility, but needs to know whether their own manager will change the plan and judge the decision fairly. That is where Kanso’s Leadership & management quality factor becomes relevant. Work-life boundaries matters only if unchanged work is pushed into personal time. The ad does not say that happens, so ask for a recent example instead of assuming it.
A decision to support someone is recognised in the work plan and in the judgement of the manager’s performance.
Supporting the person is accepted in principle, but the output commitment and appraisal expectations remain unchanged.
Tell me about the last time a team member needed support that affected planned delivery. What work moved, who agreed to it, and how was the manager’s performance assessed afterwards?
Then listen for
Listen for whether the support was recognised in the plan and in the judgement of the manager’s work. A sympathetic conversation matters, but it does not by itself explain what happened to the unfinished work.
What the ad cannot tell you: How often these demands conflict, whether coaching is protected, or whether unresolved work extends into personal time.
The role connects AI-assisted engineering with higher output while requiring the manager to maintain engineering-process quality with the technical lead. The linked values explanation advocates small, high-quality increments.
Faster work still needs an agreed quality threshold
Changing how work is done could be a useful opportunity. The ad does not establish that any particular productivity increase has been achieved, or that the team is expected to release unsafe or unreliable software.
The employer’s linked values explanation offers a substantive answer to part of this tension: keep each increment of work small enough to deliver quickly and well. The remaining question is what happens when even the smaller piece cannot meet the required standard in time.
Someone still has to decide whether to reduce the work again, move the date or supply help. The engineering manager’s responsibility for the process and the technical lead’s responsibility for standards need to produce one workable decision. The role offers faster delivery while asking the manager to protect quality. Speed and quality are not standalone Kanso factors. Autonomy matters if the manager can change sequencing or cut scope when standards take more time; Leadership & management quality matters if the product general manager backs that call. The written values explanation offers small increments as one way to reduce the conflict, but the ad cannot show how often that works.
Useful tools and smaller increments improve delivery, with standards kept clear and plans revised when necessary.
Output expectations increase while quality and the date stay fixed, without an agreed way to resolve the conflict.
What happened on the most recent delivery where the team could not meet the required quality standard within the planned time, and who authorised the change?
Then listen for
Listen for what the team changed and who backed it. Faster output alone does not answer whether the team had a workable way to resolve the conflict.
What the ad cannot tell you: Actual productivity gains, the quality of released software or how the team resolves a conflict between standards and timing.
Engineering leadership structures and career ladders are still developing. The advertisement also offers a growth budget and career framework, and welcomes people already doing management work informally.
Building the management system is part of the offer
The unfinished structures and advertised development provision may describe different stages or parts of the organisation. They are a reason to clarify what is available now, not to assume that one statement cancels the other.
A manager could welcome the chance to shape those practices. Building them could offer real Growth, especially to someone who wants a hand in how the team works. The possible cost is less established Learning & support while handling difficult performance conversations. Both factors can matter to the same person: a budget and the chance to shape a framework do not tell you who will help with the first hard decision. The ad is candid about unfinished structures, so ask what support exists now rather than treating the two statements as proof of a broken promise.
Some foundations exist, with experienced support and time to improve the practices the team needs.
The manager must build those practices while already handling delivery and difficult people issues, with less guidance than expected.
Which management practices and coaching support would I inherit on day one, and which would I be expected to build during my first three months?
Then listen for
Listen for existing documents, a person with time allocated to help, and a realistic first set of priorities. A development budget is useful; it does not tell you who will help with a difficult conversation next Tuesday.
What the ad cannot tell you: The amount or quality of support available now, or whether the advertised framework and unfinished structures refer to the same thing.
What you know so far
Which parts would you protect, and which would you trade?
- The role deliberately shares decisions and delivery responsibility.
- A general manager is named for escalation beyond the team’s control.
- Coding is required, but should not occupy most of the week or sit on a feature’s critical path.
- The employer acknowledges competing people and delivery needs and unfinished management structures.
- What changes when the managers disagree about achievable delivery.
- How supporting a person affects the plan and the manager’s appraisal.
- Who backs a change when quality standards take more time.
- What management support exists on day one.
None of these clauses establishes a dysfunctional team. Shared decisions can improve the work, direct involvement can make a manager more useful, and unfinished practices can offer room to contribute. The limit on coding is material: the manager is not meant to carry the work that a feature depends on.
The larger tension is how shared decisions, delivery pressure and responsibility for people work together when the plan stops being achievable. A candidate needs evidence that the people sharing the outcome can also agree to change the commitment. Hearing how that happened recently is more useful than another assurance that everyone takes ownership.
Your career values help determine which of these exchanges deserves the closest attention. You might welcome shared control but want strong management backing when delivery needs to change. You might value the chance to build new practices while also wanting experienced support for difficult people work. Kanso makes those priorities explicit; the advertisement and a few recent examples help you test what the role would ask in return.
Know which questions matter to you
Clarify what you value before you weigh the offer
Kanso’s free assessment asks you to rate workplace conditions independently. Your Trade-off Profile shows which career values you would protect and where you might compromise. Use it to decide whether shared control, people leadership, faster delivery or building new practices deserves your hardest question. It does not choose the job for you.