> Markdown version of [/jobs/ext/4713661-software-engineer-backend](https://www.wearedevelopers.com/jobs/ext/4713661-software-engineer-backend). 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). --- # Software Engineer - Backend - **Company:** Pro Integrate - **Location:** New York, NY, United States (Remote available) - **Salary:** $104,000 - $208,000 - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Artificial Intelligence, Bug Tracking Systems, Software Bug Management, C++ (Programming Language), Data Structures, Software Debugging, Python (Programming Language), Machine Learning, Performance Tuning, Software Engineering, TypeScript, Reinforcement Learning, Rust (Programming Language), Scripting, Backend, Code Restructuring, Golang - **Published:** November 14, 2026 - **Apply:** https://www.careerbuilder.com/job-details/software-engineer-backend-new-york-ny--20aa53ce-8717-4b24-89d1-d002ffbadfba ## About the Role Software Engineering, Reinforcement Learning, Software Engineering, Refactoring, Testing, Performance Tuning/Optimization, Bug Tracking/Defect Management, Artificial Intelligence (AI), Engineering, Python Programming/Scripting Language, 1. Significant hands-on expertise in at least one of: Python3, Java, Rust, Go, C++, or TypeScript. 2. Deep understanding of algorithms, data structures, and software engineering principles. 3. Proven ability to debug complex systems, resolve bugs, and deliver effective optimizations. 4. Experience with large codebase refactoring and legacy system modernization. 5. Track record of delivering high-impact features from conception through delivery. 6. Strong documentation and communication skills to articulate technical concepts clearly. 7. Interest in AI and its technical challenges - previous AI experience not required. ## Description 1. Create realistic, challenging coding tasks for frontier AI models, drawn from repositories you know well. 2. Design problems that require real engineering skill - subtle bugs, non-trivial features, meaningful performance work - not lookup or boilerplate. 3. Build a reproducible environment for each task. 4. Write deterministic verifiers that accept correct solutions across different valid implementations, while rejecting incorrect, incomplete, or hard-coded approaches. 5. Provide a reference solution showing how the task can be solved. 6. Flag tasks that turn out to be ambiguous or unverifiable rather than submitting them.