Core Skills: Java 8/11/17, Spring Boot, Spring MVC, Hibernate/JPA, Microservices, REST APIs, React, Angular, Oracle, MySQL, PostgreSQL, Kafka, Docker, Kubernetes, AWS, Git, Jenkins, Maven, JUnit.
Highlights:
Built and maintained enterprise Java microservices. Developed REST APIs and integrated backend services. Worked with React and Angular for full-stack development. Experience with Oracle databases, SQL optimization, Kafka, Docker, Kubernetes, and CI/CD pipelines. Strong background in Agile development, production support, and performance optimization.
I'm based in the Dallas–Fort Worth area and am open to remote, hybrid, or onsite Software Engineer, Java Backend Developer, or Full Stack Java Developer opportunities.
Email:kodalibhavana9@gmail.com Linkedin: https://www.linkedin.com/in/kodali-bhavana98/
AI engineer at U.S. Bank building production LLM systems: a RAG assistant over 500K+ documents for 200+ analysts, LLM eval harnesses (hallucination, PII, prompt-injection), and fine-tuned LLaMA/Mistral models. Outside work I built and published mendrift-mcp (PyPI, listed on the official MCP Registry) an autonomous MLOps incident-response agent with an HMAC-gated approval layer, evaluated on a 19-scenario trajectory harness. Looking for applied AI / ML engineer roles building agentic systems.
We're a Dental Support Organization running 65 practices across TX/OK/CO/MO/IA/NE/TN/AZ. The unsexy industry description hides what's actually an interesting technical role: a small dev team with real ownership, pushing hard on automation and AI to make dental operations actually work well.
Stack is primarily Rails 8 + React, Electron, C# .NET (OpenDental), and Go — all on AWS.
You'd be joining a tight team where developers own problems end-to-end: from understanding why a billing workflow breaks down, to designing the fix, to shipping it. The domain is surprisingly broad — patient communication, PMS integration, payroll, clinical workflows — and there's no shortage of genuinely novel problems once you learn the business.
Good fit if you like: stable company, small team, broad latitude, and work that visibly matters to the people using it. Not a fit if you need a large eng org — but there's plenty of greenfield work as we're still actively building new features, not just maintaining legacy code.
Drop me a line: dhanson [at] apexdp.com