Java Developer (Copilot / GenAI–Enabled Engineering)

Job Description: Java Developer (Copilot / GenAI–Enabled Engineering) Company Overview: NextAmp LLC is a digital modernization services company focused on transforming the insurance industry. We help insurance organizations redesign workflows and build AI-powered, automated systems that improve efficiency, accuracy, and scalability. Our solutions streamline core operational areas including claims processing, underwriting, billing, and back-office operations. Position: Java Developer – Copilot / GenAI–Enabled Location: Onsite/Hybrid (Webster, MA) Job Type: Contract / Contract to Hire Job Overview: We are looking for a hands-on Java Developer who knows how to use GitHub Copilot and GenAI tools to accelerate development without compromising code quality, security, or maintainability. This role is not about passive AI usage. You will work on real production code, using Copilot as a productivity multiplier—speeding implementation, refactoring, and testing through well-structured prompts, verification habits, and strong engineering fundamentals. Roles & Responsibilities: 1) Java Development with Copilot in the Loop Design, develop, and deliver Java-based solutions using Spring Boot or similar frameworks. Use GitHub Copilot for faster coding, refactoring, and debugging—while retaining full ownership of correctness and quality. Apply a structured Copilot workflow: clarify intent → provide context → generate → refine → validate with tests → deliver. Contribute clean, readable, and maintainable code with smaller PRs and clear intent. 2) Smart & Responsible Use of GenAI Use Copilot for: IDE completions and inline suggestions Planning and implementing features Safe refactoring of legacy code Debugging and code explanations Apply judgment on what Copilot output can be trusted, refined, or rewritten. Follow secure coding practices and data-safety expectations when using GenAI tools. 3) API & Backend Development Build and maintain RESTful APIs and backend services. Implement validation, error handling, logging, and configuration best practices. Work with authentication, authorization, roles, and permissions where applicable. Follow clean layering, DTO mapping, and transformation patterns. 4) Testing & Verification (Accelerated with Copilot) Use Copilot to accelerate test creation, not replace engineering judgment. Write: Unit tests with meaningful assertions and edge-case coverage Integration tests with deterministic setup and teardown API tests validating contracts, auth behavior, and negative paths Ensure Copilot-generated tests prove behavior—not just coverage. 5) Code Quality & Collaboration Participate in code reviews with a focus on clarity, correctness, and maintainability. Reduce rework and review cycles through better upfront implementation. Collaborate closely with other engineers and stakeholders in an agile environment. Qualifications 5+ years of professional Java development experience Strong hands-on experience with Spring Boot or similar frameworks Practical, real-world experience using GitHub Copilot / GenAI tools in a production codebase Strong fundamentals in: Object-oriented design Refactoring and debugging Test design and verification API and backend engineering Experience working in environments with enterprise security and governance expectations Ability to balance speed and quality while using AI-assisted development tools. What Success Looks Like Faster feature delivery without increased defects Cleaner PRs with fewer review cycles Better test coverage depth and fewer regressions Copilot used as a productivity accelerator—not a crutch Job Type: Contract Pay: $70.00 - $110.00 per hour Expected hours: 20 per week Application Question(s): Mixed-change discipline Yes/No: “Would you merge a PR that combines a refactor and a behavior change in the same diff?” Approve-with-guardrails Yes/No: “Would you approve shipping a change with a known gap if it’s behind a feature flag and has monitoring + a rollback plan?” Copilot in danger zones Yes/No: “Would you allow Copilot to generate authorization/permissions logic for production code?” Tests as proof vs checkbox Yes/No: “Would you accept Copilot-generated tests if they raise coverage but mostly assert ‘not null / no exception’?” Tools vs human judgment Yes/No: “If scanners and CI are green but your manual read raises an auth/PII concern, would you block the merge anyway?” In your day-to-day Java work, where does Copilot create the most durable leverage for you—meaning it makes you faster without increasing defects—and what is your repeatable workflow for turning its suggestions into code you’d stake your name on? Ability to Commute: Webster, MA 01570 (Required) Work Location: Hybrid remote in Webster, MA 01570