> Markdown version of [/jobs/ext/4582507-senior-software-test-engineer](https://www.wearedevelopers.com/jobs/ext/4582507-senior-software-test-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Test Engineer - **Company:** Curative Inc. - **Location:** Austin, TX, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Testing (Software), Artificial Intelligence, Software Quality, Cursor, Software Debugging, Programming Tools, Python (Programming Language), Network Planning and Design, Software Engineering, TypeScript, Large Language Models, Claude Code, Juniper, Agentic-AI, LangSmith, Evaluation of Large Language Models - **Published:** November 5, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-software-test-engineer-austin-tx--dcabc6f8-1f4e-4d42-bc1a-d5eba6155a62 ## About the Role Software Testing, Software Engineering, Co-Payments, Health Insurance, Network Design, Artificial Intelligence (AI), Funding, Juniper Networks M-Series, Healthcare, Team Player, Foundational skills * 5+ years in software quality, testing, or engineering with real range. You've written automation and done serious exploratory testing, moving between them as the problem demands. * Real fluency with LLM evaluation. Golden datasets, LLM-as-judge, programmatic graders, regression suites for prompts and agent loops. You can point to evals that caught real problems. * Hands-on experience with AI agents and the ways they fail: silent drift, tool misuse, compounding errors. * A tester's instincts. You find the bug nobody else does, and you have the track record to prove it. * Debugging depth. Logs, traces, queries, production forensics. You find the bug and can fix it yourself in Python or TypeScript. * Fluency with business stakeholders. You can run a session with a non-technical operations lead, extract what they actually need, and leave them feeling heard. * Comfort with ambiguity and speed. You've been effective without mature processes. You don't need a ticket or sprint boundary to start. * Pragmatic quality judgment. You can say "this risk is acceptable, ship it"as often as "this one isn't" * Sharp written communication. Your findings change what people do. ## Description * Claude Code, Cursor, or equivalent is already your primary development tool. * You use AI to accelerate the quality work itself (eval cases, graders, triage) and know where AI judgment ends and yours begins. * You review every AI-generated diff. You do not merge on vibes. Strongly preferred * Stood up eval or observability infrastructure from zero, and it stuck. * LLM observability tooling: LangSmith, Braintrust, Arize, or homegrown. * Defined what an agent may do unsupervised and built the guardrails. * Worn a product hat: requirements, behavior, de facto PM for a surface. * Built deep domain expertise from scratch in a complex operational business. Why this role Most testing roles keep you at arm's length from the business and the product. This one doesn't. Every engineer here owns what they ship. You give the whole team the tools, testing, and domain insight to move fast and get it right. Eval infrastructure, hands-on testing, real relationships with the business, and sometimes the product call itself: if you want that range with real production stakes and no bureaucracy in the way, this is that role.