Java Software Engineer

IMMEDIATE INTERVIEW = Full Stack Software Engineer with AI IN Austin TX / Warren MI – ONSITE(NEED LOCAL CANDIDATE)Full Stack Software Engineer with AI Austin TX / Warren MI – need local from 1 location – onsite 5X Video Interview 12 Months Required Skills & QualificationsBackend Expertise: Strong professional experience in Java ecosystem architecture and microservices development.Frontend Expertise: Proven track record of owning frontend architecture and delivering complex UIs in React.AI/ML Frameworks: Hands-on experience with the modern AI stack, including LangChain, LlamaIndex, Hugging Face, and Vector Databases.System Design: Exceptional ability to conceptualize new services from the ground up, making sound architectural choices across the entire stack.Problem Solving: Demonstrated ability to navigate the unique technical challenges of AI implementation, including prompt engineering, context window limits, and output validation. Application QuestionnaireTo help us better understand your background and approach to engineering, please provide brief, specific answers (a few sentences each) to the following questions along with your application:AI-assisted development tools: Which AI-assisted development tools have you used (e.g., Cursor, GitHub Copilot, Claude Code, ChatGPT)? Describe a specific task where one of these tools meaningfully changed how you worked—what you asked it to do, how you validated its output, and where you found it fell short.Building AI-powered applications: Have you built any applications that use AI or LLMs (e.g., a chatbot, RAG system, summarizer, agent, recommendation feature)? Pick one project and walk us through what it did, your role, the architecture, and the hardest technical problem you had to solve.Models, APIs, and frameworks: Which AI models and platforms have you worked with (e.g., OpenAI GPT, Anthropic Claude, Llama, Gemini, or open-source models), and which frameworks or tools (e.g., LangChain, LlamaIndex, vector databases, Hugging Face)? How did you decide which model or approach was right for a given problem, and how did you handle cost, latency, or accuracy trade-offs?Java / Backend Experience: What kinds of backend systems have you built with Java (e.g., APIs, microservices, batch jobs), and what were your primary responsibilities on those projects?React / Frontend Experience: What types of React applications have you worked on (dashboards, internal tools, public sites), and which parts of the UI or front-end architecture did you own?System Design / Thinking: When you start a new feature or service, how do you typically approach deciding the overall design (APIs, data model, front-end flow) at a high level?