Full-stack Engineer resume example

• Built a React order workspace backed by a Java API and SQL transactions; tested duplicate submissions and permission changes so an interrupted request could not create a second order.
• Packaged the application in Docker and added CI/CD checks for schema compatibility and end-to-end checkout. Blocked promotion when an old client could no longer read the new response.
• Built a Python reconciliation job for the Java order API, comparing SQL order state with payment-provider events. Replayed delayed callbacks in staging and prevented fulfilled orders from being marked unpaid after a retry.
• Carried an account-setting change through the React form, API validation and database migration; exercised stale submissions and permission failures in end-to-end tests.
• Owned a React and Java account-settings flow using SQL migration tests, resolved stale form submissions and released an end-to-end regression suite.
• Built CI/CD checks using code-review findings and AWS preview environments, reduced repeated integration failures by 31% across six weekly releases.

• Instrumented 11 product journeys with trace and business events. Kept turnaround time within the agreed operating window.
• Reviewed a proposed change against the existing interface contract, reproduced a reviewer’s edge case, and added the missing test or example before merging the change.
• Investigated a failure reported by a downstream team using the exact version and input they supplied. Reduced it to a reproducible test, delivered the fix with compatibility notes, and confirmed the original case passed before closing the report.

• Introduced typed API contracts for 23 shared endpoints
• Built an isolated fixture with normal, malformed and interrupted inputs; recorded the expected response before running the implementation so failures were distinguishable from a changed assumption.
• Packaged the reproduction steps, configuration and regression tests with the project; checked the instructions from a clean environment and documented the unsupported cases instead of claiming production readiness.
• Owned the independent regression fixture using isolated inputs, resolved a failing edge case and released a reproducible test package with expected outputs.

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

React · API validation · Database migrations · End-to-end testing

• Published an independent technical note using the project’s before-and-after traces, explaining the failed assumption, regression coverage and cases the implementation does not support.