Find the weak points · 10 example briefs
A review that turns uncertainty into a plan.
I review an existing system against its actual requirements, map failure modes and trade-offs, then produce prioritized changes your team can act on.
- ↗Evidence-backed architecture findings
- ↗Prioritized risk and dependency maps
- ↗Migration steps and validation criteria
Ways I can apply this capability
10 concrete examples.
Example briefs showing the challenge, the approach I would take and the deliverable you can review. Related work is linked below.
01Example brief
Service boundary review
- The challenge
- Business changes cross too many services and teams.
- Review approach
- Trace a real workflow, map ownership and examine coupling at each boundary.
- What you get
- A boundary map with proposed changes and their trade-offs.
Discuss this challenge ↗02Example brief
Scalability review
- The challenge
- The team knows traffic is growing but cannot explain the first bottleneck.
- Review approach
- Inspect peak traffic, latency distributions, queues and database access patterns.
- What you get
- A capacity risk register and prioritized load-test plan.
Discuss this challenge ↗03Example brief
Database design review
- The challenge
- Queries slow down and data ownership is unclear.
- Review approach
- Review schema constraints, indexes, transaction boundaries and retention.
- What you get
- A query and schema action plan with migration safety checks.
Discuss this challenge ↗04Example brief
API contract review
- The challenge
- Consumers break whenever a service changes.
- Review approach
- Examine versioning, error models, compatibility and consumer expectations.
- What you get
- A contract report and a backward-compatibility checklist.
Discuss this challenge ↗05Example brief
Tenant isolation review
- The challenge
- Access checks do not clearly separate customer data.
- Review approach
- Trace tenant context through APIs, storage, caches and background jobs.
- What you get
- An isolation matrix and cross-tenant test cases.
Discuss this challenge ↗06Example brief
Resilience review
- The challenge
- Retries and timeouts amplify downstream incidents.
- Review approach
- Inspect retry budgets, circuit breakers, fallback behavior and recovery paths.
- What you get
- A failure-mode map with corrective changes and drills.
Discuss this challenge ↗07Example brief
Agentic system review
- The challenge
- Agent behavior is difficult to reproduce or approve.
- Review approach
- Review tool permissions, retrieval boundaries, evaluations and execution limits.
- What you get
- A control-gap report and an agent release checklist.
Discuss this challenge ↗08Example brief
Release architecture review
- The challenge
- Deployments are risky and rollback depends on a few people.
- Review approach
- Inspect artifact promotion, migrations, health gates and operational ownership.
- What you get
- A release-readiness report with a tested rollback plan.
Discuss this challenge ↗09Example brief
Observability review
- The challenge
- An incident cannot be traced from a customer symptom to a service.
- Review approach
- Follow correlation IDs, coverage, alert thresholds and runbook ownership.
- What you get
- An instrumentation map and a focused incident-response backlog.
Discuss this challenge ↗10Example brief
Cost and architecture review
- The challenge
- Infrastructure spend grows faster than useful workload.
- Review approach
- Inspect resource usage, data movement, storage lifecycle and environment sprawl.
- What you get
- A cost-to-workload assessment with measured optimization opportunities.
Discuss this challenge ↗Bring the hard part
Build it. Review it. Give it a better foundation.
Tell me what you are building, what is breaking and what needs to change. We can start with a focused diagnostic and a concrete next step.