Mid-Level Engineer. AGC and AZcare.

At Hive I had been a feature engineer. At AGC I was given services. Not tickets within a service, services. Authentication, billing, an integration layer, a recurring engine. A service is the responsibility for a system over time. You own the spec, the data model, the API contract, the test coverage, the deployment, the on-call rotation when something goes wrong. You own how it will look when the company looks at it in three years. You own the documentation that will outlive your tenure.

This is the chapter where I learned that documentation is not overhead. It is the artifact that makes ownership possible. If I owned a service, I had to write down what the service did, why it did it that way, how it could be extended, what its dependencies were, what would break it. Then I had to keep that document in sync as the service evolved. I produced documents the same week I produced the code. By the end of two years I could be handed a tangled legacy service from another team and produce a clear spec, a working refactor, and a deployment plan inside a week. Reliability had become my currency.

AZcare followed shortly after as a contributor role on a healthcare-related platform. Different domain, same operating habits. Healthcare is a domain where mistakes have consequences. The documentation discipline I had built at AGC translated directly. Schema versioning, audit logs, validation at the API boundary, integration tests that exercised the actual data flow. Production never failed because of code I wrote. That is the bar healthcare quietly enforces.