What are the responsibilities and job description for the Lead Backend Engineer (Agentic AI) position at Lorven Technologies?
Role: Lead Backend Engineer (Agentic AI)
Location: Hartford, CT
Duration: Contract
Job Description:
About the Role:
We're looking for engineers who can design and build production systems that combine strong software
fundamentals with hands-on exposure to modern AI/ML tooling - specifically agentic AI workflows and
Model Context Protocol (MCP) servers. You don't need to come from a pure AI/ML background; what matters is strong core engineering skills, sound architectural judgment, and the ability to pick up (or already know) how to integrate AI agents into real systems. This is a single posting covering both Senior and Lead
levels - candidates with 7-10 years of experience are encouraged to apply.
Must-Have Skills
Design & Architecture Thinking Required:
Lead Should Have:
Location: Hartford, CT
Duration: Contract
Job Description:
About the Role:
We're looking for engineers who can design and build production systems that combine strong software
fundamentals with hands-on exposure to modern AI/ML tooling - specifically agentic AI workflows and
Model Context Protocol (MCP) servers. You don't need to come from a pure AI/ML background; what matters is strong core engineering skills, sound architectural judgment, and the ability to pick up (or already know) how to integrate AI agents into real systems. This is a single posting covering both Senior and Lead
levels - candidates with 7-10 years of experience are encouraged to apply.
Must-Have Skills
- Python - strong, production-grade proficiency (primary language)
- Databases - solid relational/SQL fundamentals; schema design, query optimization, data modeling
- Cloud platform - strong hands-on experience with at least one of: Google Cloud Platform (GCP)
- (preferred), or AWS (acceptable alternative)
- 6 years of professional software engineering experience
Design & Architecture Thinking Required:
- Strong grounding in modular design - clear separation of concerns, well-bounded components/services, low coupling / high cohesion
- Ability to design systems that scale horizontally - statelessness where it matters, partitioning/sharding
- strategy, load distribution, avoiding single points of contention
- Working fluency in core design patterns and principles (e.g., SOLID, domain-driven boundaries,
- event-driven/async patterns, idempotency, caching strategies, API versioning) and knowing when to
- apply vs. avoid them
- Comfortable reasoning about tradeoffs: consistency vs. availability, latency vs. throughput, build vs. buy,
- synchronous vs. async workflows
- For Lead specifically: expected to drive these principles - set direction in design reviews, push back on
- designs that won't scale, and mentor others toward this way of thinking rather than just applying it
Lead Should Have:
- Owns technical direction for a workstream or service area
- Drives modular, horizontally-scalable design decisions across the team - not just follows them
- Leads design reviews, sets technical standards, mentors other engineers on architectural thinking
- Drives adoption of agentic AI / MCP patterns across the team Partners with product/architecture stakeholders on tradeoffs
- What We're Really Screening For
- Strong in Python SQL/databases as a baseline
- Solid architectural instincts - modular, scalable design, not just "make it work" Proven in one major cloud (GCP strongly preferred, AWS acceptable) Comfortable or curious about Java (bonus, not blocker)
- Solid API/WebSocket integration practices - reliability, security, and observability by default Open to learning / already exposed to agentic AI MCP server patterns
- Ideally has touched healthcare/health-tech systems before, but this is a plus, not a gate