> Markdown version of [/jobs/ext/4693957-senior-software-engineer](https://www.wearedevelopers.com/jobs/ext/4693957-senior-software-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 Engineer

- **Company:** Compsych Management Corporation
- **Location:** United States
- **Experience:** Expert
- **Salary:** $150,000 - $200,000
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Automation of Tests, Microsoft Azure, C Sharp (Programming Language), Computer Programming, Python (Programming Language), OAuth, OpenID, Open Web Application Security, Software Engineering, SQL Databases, Management of Software Versions, Agentic-AI, Kotlin, Event Driven Architecture, Kubernetes, Apache Kafka, Serverless Computing
- **Published:** November 12, 2026
- **Apply:** https://www.careerbuilder.com/job-details/senior-software-engineer--7e15caef-79a8-4bca-94b9-a20c73986905

## About the Role

Software Engineering, Psychiatry and Mental Health, Fortune 500 Customers, Artificial Intelligence (AI), Customer Relations, Product Design, Software Engineering, Computer Programming, Test Automation, Testing, * Deep server-side experience in a modern language such as Java, Python, C#, Kotlin, or Go. You've owned services end to end, not just features inside someone else's, and can pick up ours quickly.

 * Must have 5+ years of full stack development experience.
 * APIs and data models other people depend on: REST contracts, versioning, OAuth2/OIDC, schema design, and SQL that holds up under real load.
 * Async and event-driven systems in production - Kafka or comparable, idempotency, and a clear view of what at-least-once costs you downstream.
 * You've built and operated production systems at real scale on AWS or Azure - containers, Kubernetes or serverless, IaC, and CI/CD pipelines you've built, operated, or materially improved. You've carried the on-call load for them, so you know what "good" looks like independent of who or what wrote the code.

## Description

* A testing strategy you can defend - what belongs at unit, integration, and contract level, and how you know a release is verifiable before it ships.
 * Reliability and security you've been accountable for: SLOs you've been paged against, incidents you led, OWASP and threat modeling applied - and PHI/HIPAA or comparable regulated-data experience.
 * Agentic AI is your primary development surface, and you catch what it gets subtly wrong. Not occasional autocomplete, not a hunch - you've shipped and operated real production systems working this way, and can point to what you caught before it shipped.