Full-Stack Reliability Audit & Testing
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted12 hours ago
I need an experienced, senior-level full-stack engineer to put my entire application—everything a user touches through to the deepest backend service—under a microscope. Right now we are dealing with two painful issues: crashes or failed requests that surface unpredictably, and occasional data loss or incomplete actions that leave users confused and support overwhelmed.
Your assignment is to uncover the weak points, then translate those findings into a concrete safety net of tests and monitoring. I am less interested in a lengthy post-mortem and more interested in future-proofing: where should automated tests be introduced, which runtime metrics truly matter, and what logging or tracing will give us the earliest possible warning when something is about to break?
Deliverables I expect:
• A clear test strategy mapped to the critical user journeys, complete with sample test cases or frameworks you recommend using.
• A monitoring and alerting blueprint that specifies tools, metrics, thresholds, and dashboards so the team can act before users notice problems.
• A short hand-off session (video or written) walking through how to integrate both into our CI/CD pipeline.
You’ll have access to the full codebase (frontend, APIs, database migrations, and infrastructure as code) and a staging environment that mirrors production. Familiarity with tools like Jest, Cypress, Postman, k6, New Relic, Datadog, Grafana, or similar will help you move quickly, but I’m open to your preferred stack if it achieves the same guardrails.
If you thrive on tracing elusive bugs, designing resilient test suites, and setting up pragmatic observability that keeps engineers and users happy, I’d love to work with you.
Your assignment is to uncover the weak points, then translate those findings into a concrete safety net of tests and monitoring. I am less interested in a lengthy post-mortem and more interested in future-proofing: where should automated tests be introduced, which runtime metrics truly matter, and what logging or tracing will give us the earliest possible warning when something is about to break?
Deliverables I expect:
• A clear test strategy mapped to the critical user journeys, complete with sample test cases or frameworks you recommend using.
• A monitoring and alerting blueprint that specifies tools, metrics, thresholds, and dashboards so the team can act before users notice problems.
• A short hand-off session (video or written) walking through how to integrate both into our CI/CD pipeline.
You’ll have access to the full codebase (frontend, APIs, database migrations, and infrastructure as code) and a staging environment that mirrors production. Familiarity with tools like Jest, Cypress, Postman, k6, New Relic, Datadog, Grafana, or similar will help you move quickly, but I’m open to your preferred stack if it achieves the same guardrails.
If you thrive on tracing elusive bugs, designing resilient test suites, and setting up pragmatic observability that keeps engineers and users happy, I’d love to work with you.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.