Java Sr. Lead Software Engineer - US Regulatory Reporting Technology

JPMorgan Chase JPMorgan Chase · Banking · Jersey City, NJ +1 · Corporate Sector

Senior Lead Software Engineer role focused on building and operating microservices and web applications for US Regulatory Reporting Technology at JPMorgan Chase. The role involves hands-on coding, design, testing, deployment, and operational ownership, with a significant portion dedicated to technical leadership, setting engineering standards, and mentoring. Key technologies include Java/Spring Boot, React, AWS, CI/CD, and observability tools. Experience with AI coding assistants is mentioned as a requirement for accelerating delivery.

What you'd actually do

  1. Lead by example: contribute production‑quality code daily, write tests, perform code reviews, and pair program.
  2. Design and deliver secure, high‑quality microservices and web applications with Java/Spring Boot and React; own deep debugging, root‑cause analysis, and performance tuning for high-availability services.
  3. Own end‑to‑end build‑and‑run: design, implement, test, deploy, and operate services (“you build it, you run it”).
  4. Provide technical leadership across teams; set engineering standards and coach on architecture, code quality, security, and operational excellence.
  5. Act as SME for microservices, CI/CD, observability, performance engineering, and data modeling.

Skills

Required

  • Java
  • Spring Boot
  • React
  • RESTful API design
  • AWS (EC2, ECS, S3, Lambda, RDS, IAM)
  • Microservices
  • CI/CD (Jenkins/GitHub Actions)
  • Automated testing (unit/integration/contract)
  • Relational databases
  • NoSQL databases
  • Monitoring and logging (DataDog, Dynatrace, Splunk)
  • Reliability engineering
  • Performance engineering
  • Kubernetes
  • AI coding assistants (e.g., GitHub Copilot)

Nice to have

  • Regulatory finance/external reporting
  • Cloud certifications
  • Cloud-native delivery on AWS
  • Large-scale distributed systems
  • Event-driven architectures
  • Messaging/streaming patterns
  • SRE
  • Telemetry pipelines
  • Alerting strategies
  • Incident response
  • Post-mortems

What the JD emphasized

  • production‑quality code
  • secure
  • high‑quality microservices
  • high-availability services
  • end‑to‑end build‑and‑run
  • technical leadership
  • engineering standards
  • architecture
  • code quality
  • security
  • operational excellence
  • test automation
  • CI/CD
  • security‑by‑default
  • quality gates
  • disciplined change management
  • reliability
  • scalability
  • cost efficiency
  • auditability
  • non‑functional requirements
  • security
  • scalability
  • reliability
  • observability
  • cost
  • logging
  • metrics
  • tracing
  • SLOs
  • error budgets
  • alerting
  • runbooks
  • inclusive team culture
  • continuous improvement
  • craftsmanship
  • Advanced proficiency in Java and Spring Boot
  • strong fundamentals
  • design patterns
  • secure coding
  • Full‑stack delivery
  • secure RESTful API design
  • Hands‑on AWS experience
  • containerized workloads
  • networking
  • secrets management
  • Microservices design
  • deployment
  • operations
  • CI/CD pipelines
  • automated testing
  • enforcing quality gates
  • Relational and NoSQL databases
  • schema design
  • performance tuning
  • secure data access
  • Monitoring and logging
  • Reliability and performance engineering
  • concurrency
  • thread management
  • caching
  • resiliency patterns
  • cost awareness
  • Proven track record shipping and operating production systems
  • troubleshooting in Kubernetes
  • CI/CD
  • cloud environments
  • Hands‑on use of AI coding assistants
  • accelerate delivery
  • prompt design
  • code/test generation
  • refactoring
  • documentation synthesis
  • validate outputs for correctness
  • security
  • performance
  • licensing compliance
  • company-approved tools and policies