# How do you make juniors accountable without pointing fingers? — retained record

> Retained reddit record from reddit:ExperiencedDevs.

Canonical: https://highsignal.app/data/records/9b98bdeb0d06c610

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ExperiencedDevs)  published 2026-09-05 16:43 ingested 2026-09-06 02:37

[original source ↗](https://www.reddit.com/r/ExperiencedDevs/comments/1w85of9/how_do_you_make_juniors_accountable_without/)

## retained text



```
I have a couple of juniors working on my team who would use AI to make changes without caring for actual system integrations because AI thought the implementation is ok vs requirements without correlating with the actual integrations contracts at all.

Maybe if they feel frisky they would go about trying to understand what actually needs to be done on a brownfield project but only upto a point that matches the acceptance criteria. Frustration like I thought this was going to be an easy fix is quiet common feedback when tried to make accountable. Well its not because you did not priortize understanding the fix over telling claude to build you a plan to get this over with.

Our team does a lot of middleware integrations so we constantly have to run transactions with systems that are not under our control, difficult to QA, subject to flakiness, rate limits while having strict contract integrations to prevent abuse because they are used by many other tenants which are not our team.

Most of the time this translates to the fact that QA tests are not enough to mark a bug or feature as complete. Often times, you need to test against the real live system integrations to make sure SLO, SLI, SLA, regressions are as expected, using automated checks as much as possible or in certain cases by hand because of the complex nature of the test.

Juniors just assume QA being green gets them off the hook and they can close their tasks as completed while the real closure comes from the fact that live systems do not get regressions or upset other live systems that we have stake at.

We (me and another senior engineer) often find out after live deployment that things are failing silently for weeks or loudly right after until the next on call because no one tried to be accountable to see their changes go through. At the end, it falls upon to either me or my colleague to fix the mess left behind by our juniors because we are the primary owner of our system SLA, SLI, SLO. We tried to coach them but it always comes down to how they feel about the topic vs their current shiny task that just keeps burning us out in response to fight fires.

How do I communicate the missing accountability with my manager without sounding condescending in favour of sanity and not burning out while not pointing fingers?
```



document fetched 2026-09-06 00:24 · canonical https://reddit.com/r/ExperiencedDevs/comments/1w85of9/how_do_you_make_juniors_accountable_without
