2

Evening Remote Java Developer Jobs in California

Fluent in java programming and be comfortable with stateful web applications Desired Experience * GitLab, Jenkins, IntelliJ. Bash, Groovy and ZSH scripting * Genesys Voice Platform (GVP) * Speech ...

Remote : OK Job Role: As a software developer, you'll be the brain behind crafting, developing ... Proficient in Java, C++, Ruby on Rails or other programming languages. * Hands-on with SQL or NoSQL ...

Remote Software Developer

San Francisco, CA · On-site +1

$200 - $300/hr

As a Software Engineering evaluator, you will create cutting-edge datasets for training ... Java, Rust, and Go; evaluating and refining AI-generated code for efficiency, scalability, and ...

With remote work and global talent pools, even entry-level roles receive hundreds of applications ... Java / Full Stack / DevOps Roles * Bachelor's or Master's in CS, CE, EE, IT, or IS * Java ...

Full Stack Developer

Ridgecrest, CA · Remote

$83K - $100K/yr

This is a remote position. Job Summary: This role supports enterprise modernization and software ... Experience developing backend services and APIs using technologies such as Python, Java, or Node.js.

next page

Showing results 1-20

Evening Remote Java Developer information

What is the difference between Evening Remote Java Developer vs Evening Remote Software Engineer?

AspectEvening Remote Java DeveloperEvening Remote Software Engineer
Required CredentialsBachelor's in CS or related, Java certifications often preferredBachelor's in CS or related, with Java or software development certifications
Work EnvironmentRemote, evening hours, focused on Java developmentRemote, evening hours, broader software development tasks
Industry UsageTech companies, financial services, startupsTech firms, consulting, enterprise software
Common Search IntentJobs focusing on Java programming in evening remote rolesRoles involving software engineering skills in evening remote settings

The main difference between an Evening Remote Java Developer and an Evening Remote Software Engineer lies in their focus. Java Developers specialize specifically in Java programming, while Software Engineers may work across multiple languages and systems. Both roles often require similar credentials and work in remote, evening environments, but Java Developers are more niche-specific, whereas Software Engineers have broader responsibilities.

What are the most commonly searched types of Remote Java Developer jobs in California? The most popular types of Remote Java Developer jobs in California are:
What are popular job titles related to Evening Remote Java Developer jobs in California? For Evening Remote Java Developer jobs in California, the most frequently searched job titles are:
What job categories do people searching Evening Remote Java Developer jobs in California look for? The top searched job categories for Evening Remote Java Developer jobs in California are:
What cities in California are hiring for Evening Remote Java Developer jobs? Cities in California with the most Evening Remote Java Developer job openings:
Infographic showing various Evening Remote Java Developer job openings in California as of June 2026, with employment types broken down into 50% Full Time, and 50% Contract. Highlights an 50% In-person, and 50% Remote job distribution.

WebMethods Integration Developer

MAVLRA CORPORATION

Sacramento, CA • On-site, Remote

Other

Posted 5 days ago


Job description

Job Title: WebMethods Integration Developer
Type: (Contract)
Engagement: Hybrid – First 3 days onsite (Sacramento, CA), remainder remote

SCOPE OF WORK:

The WebMethods Integration Developer will be responsible for developing web service APIs and other integrations to support the implementation of various capital projects across .

Key Responsibilities:

API Development

• Design and develop RESTful and/or SOAP web service APIs to connect enterprise systems (GIS, ERP, asset management, project controls, document management)

• Ensure APIs support data exchange using secure, standardized formats (JSON, XML)

• Implement authentication and authorization protocols including OAuth 2.0, JWT, SAML

• Provide comprehensive API documentation using OpenAPI Specification (Swagger)

• Ensure APIs are version-controlled with backward compatibility

Integrations & Interoperability

• Develop connectors or middleware for interoperability between legacy systems, cloud solutions, and third-party applications

• Design event-driven integrations supporting asynchronous updates and webhook capabilities

• Implement robust error handling, transactional integrity, logging, and proactive monitoring

Security

• Ensure compliance with  cybersecurity policies and NIST / CIS Controls

• Utilize data encryption in transit and at rest, secure API gateways, and conduct vulnerability assessments

• Provide audit trails and detailed transaction logging

Scalability & Performance

• Design for high availability, horizontal scalability, and resilience

• Define and implement performance benchmarks (TPS, latency thresholds)

Testing & Quality Assurance

• Develop and execute comprehensive test plans (unit, integration, system, UAT)

• Support automated regression testing

MANDATORY REQUIREMENTS:

• 5+ years of experience on the webMethods integration platform

• 2+ years with webMethods.IO (or webMethods Cloud Integration - IC) SaaS platform

• Proven SAP RFC (Remote Function Call) integration experience

• Demonstrated custom integration services development using Java

• Senior-level proficiency including:

  - Integration Server

  - Universal Messaging

  - API Gateway

  - wM Test Suite

  - EDI/TN (Trading Network)

  - Java Service Development

  - webMethods.IO

DESIRABLE QUALIFICATIONS:

• Proficiency with wM Test Suite, EDI/TN (Trading Networks)

• Certifications: Software AG Certified webMethods Developer, MuleSoft, AWS Certified Developer, Microsoft Azure Integration, PMP, or equivalent

• Prior experience in public sector, utilities, or energy industry

• Knowledge of secure software development, identity and access management, and cybersecurity best practices