Java Backend- EX-Amazon- W2

Job Title – Java Backend Developer - W2Job Type – Hybrid Job location – Minneapolis, Minnesota Duration- 8 Months This is W2 roleNeed EX- Amazon candidatesRelocation is fine USC, GC, GC-Ead, H4-ead, Opt-Ead, L2S can apply Job Description: The strongest candidate will likely demonstrate:Previous Amazon software development experience, ideally at an SDE II or comparable levelAt least three years of professional software development experienceStrong Java development skillsHands-on backend application and service developmentExperience designing systems using sound architecture and design principlesOwnership of projects across the full software development lifecycleA track record of releasing applications or products to actual end usersExperience modifying and improving an existing production codebaseAbility to create operational metrics and use them to evaluate system performanceStrong examples aligned with Insist on the Highest Standards and Deliver ResultsAbility to work effectively with internal technical and business teamsExperience mentoring junior software engineersExposure to AI-assisted or AI-related software developmentWhat the Engineer Will Be Expected to DoHet Sheth described the work as partnering with internal teams to develop new code, modify existing code, build metrics and backend services, and drive projects from end to end.1. Hands-On Software DevelopmentThe engineer must be able to:Write new production codeWork effectively within an existing codebaseEnhance or refactor existing functionalityTroubleshoot application-level issuesDeliver maintainable, production-ready softwareThis is not a role for someone who has moved completely away from coding. The resume should show recent, substantive software development responsibilities.2. Backend ServicesThe intake emphasizes Java and system design. Relevant backgrounds may include:Backend APIsMicroservicesDistributed servicesEvent-driven applicationsWorkflow or automation platformsHigh-volume data processingInternal enterprise applicationsSystems supporting operational decision-makingThe team builds automation tools used in warehouse operations to help associates understand how, where, and what work should be performed. The environment processes billions of events and involves technology that the manager described as difficult to find at other companies.3. Metrics and Operational VisibilityCandidates should have experience creating or integrating metrics into applications or backend services. Recruiters should listen for examples involving:Application health metricsService performance indicatorsOperational dashboardsLogging and monitoringAvailability or latency measurementsBusiness or workflow metricsUsing metrics to identify defects or improve a serviceThese examples should be connected to software the candidate personally helped build, rather than only to a separate monitoring or support role.4. End-to-End Project Ownership“Drive project from end to end” should be interpreted as evidence that the candidate can move work through multiple stages, such as:Understanding requirementsEvaluating technical optionsDesigning a solutionDeveloping the application or serviceTesting and reviewing the implementationDeploying or releasing the solutionMonitoring resultsAddressing defects or follow-up improvementsThe intake specifically identifies successful candidates as people who have developed applications and shipped products to end users.