Senior Solutions Architect resume example

• As workstream lead, ran technical discovery for a partner integration, mapping API permissions, event ownership, and customer requirements into an architecture decision record with explicit unsupported cases.
• With responsibility for the review standard, validated the integration architecture with retry, rate-limit, and permission-revocation tests; showed partners the technical recovery path instead of relying on a successful happy-path API call.
• Translated a customer workload into a reference architecture with identity, network and recovery boundaries; tested the highest-risk integration in a proof of concept before the design review.
• Owned an AWS integration assessment using networking and identity diagrams, resolved an unsupported routing assumption before the customer approved the architecture.
• Released technical documentation with tested security boundaries and recovery steps, enabling a customer team to reproduce the cloud proof of concept from a clean account.

• Ran architecture office hours for 34 partner engineers; aligned review standards and decision owners across the participating teams. Working with partner teams, gave support and product owners a clearer follow-up path.
• Updated a troubleshooting article after reproducing a reported failure, separated user actions from administrator-only steps, and checked the procedure with a colleague using a clean setup.
• Reproduced a customer issue on a clean configuration, compared the working and failing settings, and tested the proposed correction without administrator privileges. Published a troubleshooting sequence that preserved the customer’s original configuration.

• Created a production-readiness review covering 28 security and reliability controls; aligned review standards and decision owners across the participating teams
• Configured a separate test environment with a documented network diagram, account permissions and failure scenarios; captured the logs needed to distinguish connectivity, authentication and application faults.
• Tested the recovery guide from a fresh account, checked required permissions at each step, and added rollback instructions where a configuration change could disrupt the working baseline.
• Owned the recovery rehearsal using an isolated test account, resolved a missing permission prerequisite and completed the restore without changing the working baseline.

Relevant coursework: Algorithms, operating systems, databases, computer networks

• Published an independent troubleshooting guide using annotated logs, separating connectivity, authentication and application failures and documenting the rollback decision at each step.