Hello Everyone,
Please share suitable profiles.
Don’t call me, Once I review the profile will give you a call.
|
If you are sharing any profile, please mention: Location – Work Authorization – "Before submitting any candidates please share the visa back and front copy must and LinkedIn id " |
Role: Java Developer
Location: Austin, TX (Hybrid) – Need local or Nearby
NO H1B, CPT, OPT
Job Description:
Must Have Skills
· Backend Java & Programming Skills, Experience with Gen skills such as prompt engineering, working with LLM models
· Java programming
· Gen AI experience.
The Sr. Software Engineer will be part of the LEP Intelligent Alert Triaging initiative, supporting the expansion of alert management and prioritization capabilities across the LEP organization. The role focuses primarily on designing, building, and onboarding integrations for observability and alerting platforms such as Datadog, Splunk, Kibana, Sentry, and SOR (BigQuery) (approximately 70–80% of capacity), while also supporting alert validation, tuning, and rollout activities in collaboration with partner teams (approximately 20–30% of capacity). The engineer will operate in an Agile environment, contributing to sprint planning, daily stand-ups, and backlog-driven delivery. Close collaboration with globally distributed engineering and operations teams is required to ensure high-quality alert coverage, improved operational efficiency, and system reliability. This is a time-bound, project-specific role focused on accelerating delivery during the scale-out of the Intelligent Alert Triaging service across LEP.
Daily Responsibilities
Majority of the worker’s time will be focused on engineering and implementation activities, including onboarding alert integrations, enhancing triaging logic, and performing testing and validation (approximately 70–80%). The remaining time will be spent on documentation, rollout support, and coordination with partner teams (approximately 20–30%). Work will be tracked and prioritized through a managed backlog to ensure predictable delivery.
The worker will have a high level of interaction with the IAH engineering team daily and will collaborate regularly with LEP engineering, SRE, and operations stakeholders. The role requires close coordination for design, integration, and rollout activities, while allowing independent execution of assigned tasks and deliverables.
Handles models and collaborates with teammates across domain, about 70% coding for SOPs and 30% for model support while following Agile practices and policies
What makes this role interesting & Unique selling points
This is a time-bound, project-specific role focused on accelerating delivery during the scale-out of the Intelligent Alert Triaging service across LEP. The contingent workers will follow standard business hours aligned with the LEP Intelligent Alert Handling (IAH) team, with flexibility to collaborate across global time zones as required. The role includes participation in Agile ceremonies such as daily stand-ups, sprint planning, and reviews, while executing assigned work within defined sprint timelines
Top Skills
· Backend Java & Python Programming Skills, Experience with Gen skills such as prompt engineering, working with LLM models
· Java & Python programming
· Gen AI experience
Team & Project Context
Team: Application Engineering Support
Nature of work:
o 60% development
o 40% support
o Support is real-time but within normal business hours (not on-call)
Key initiative: Intelligent Alert Handler
o Centralized alert triaging system
o Consolidates alerts across:
Datadog, Sentry, CAL, internal tools
Databases: Oracle, Postgres, MySQL
o Uses LLMs (ChatGPT 4.x) to auto-triage alerts based on SOPs
o Goal: reduce manual intervention and improve operational efficiency
Generative AI (Mandatory)
Candidates must have hands-on experience, not theoretical:
• RAG implementations
• Vector databases (basic configuration & usage)
• Model parameter tuning
• Prompt engineering:
o Expected proficiency: 7/10 or higher
• Familiarity with LLMs (ChatGPT-level models)
Java + GenAI = ideal
________________________________________
Nice-to-Have / Value Add
• Cloud exposure (AWS / Azure)
• Experience working across multiple systems / platforms
• Comfort collaborating with multiple engineering teams
________________________________________
Role Expectations (Very Important for Candidate Alignment)
• 60/40 split must be clearly communicated upfront
o Development + production support
• Candidates should:
o Be comfortable talking to engineering teams
o Understand alerting systems and dependencies
o Onboard new use cases independently
• Manager explicitly flagged past issues where candidates were surprised by support model — avoid this
________________________________________
Experience & Seniority
• Target: 6+ years experience
• Looking for:
o Self-starters
o Engineers who can take ownership after initial guidance
o Ability to lead implementation independently
GenAI Experience Expectations
Looking for hands-on GenAI experience, not just theoretical exposure
Candidate should be comfortable with:
RAG implementations
Vector database configuration
Model engineering (fine-tuning parameters, understanding trade-offs)
Prompt engineering (must be practical and production-oriented, not basic)
AI is core to the role, not a side skill
Current System & Scope of Work
Intelligent Alert Handler system already exists
Integrates with tools like Datadog or similar alerting systems
Automatically performs alert triage
The engineer will:
Work on an expansion project
Extend an existing design to support additional projects
Focus on scaling and broader adoption of the tool.
Tech Stack
Implemented using Java, LLMs, Claude, and ChatGPT-4.5
Experience in Java is acceptable, but Java experience is critical to add real value.
Problem Space
Alert triaging is complex across Client, Braintree, and Hyperwallet
This system was built to reduce operational load and improve response accuracy
Strong exposure to support models and production systems is important
Team & Role Context
Part of the Application Engineer team under Braintree
Team split:
60% building new applications
40% supporting engineering teams
Role requires balancing new development with support responsibilities