1

Augmented Reality Developer Intern Jobs in Maryland

Showing results 21-25

Augmented Reality Developer Intern information

What types of projects and technologies can I expect to work with as an augmented reality developer intern?

As an Augmented Reality Developer Intern, you'll typically work on projects involving mobile AR applications, interactive prototypes, and possibly headset-based experiences using platforms like ARKit, ARCore, or Unity. You'll collaborate closely with designers and senior developers to turn creative concepts into functional AR experiences, often participating in brainstorming sessions and code reviews. This role gives you hands-on experience with 3D modeling, real-time rendering, and user interaction design, providing a solid foundation for a future career in immersive technology.

What is the difference between Augmented Reality Developer Intern vs AR Software Engineer Intern?

AspectAugmented Reality Developer InternAR Software Engineer Intern
Required CredentialsEnrolled in Computer Science, Software Engineering, or related fields; some familiarity with AR toolsSimilar educational background; more advanced programming skills expected
Work EnvironmentInternship in tech companies, startups, or AR-focused teams; collaborative and project-basedSimilar environments; focus on developing AR applications and software solutions
Employer & Industry UsageUsed by companies developing AR apps, games, or AR integrations in various sectorsCommonly employed in AR development teams within tech firms and startups

Both roles involve working with AR technologies, but AR Software Engineer Interns typically require more advanced programming skills and focus on building and optimizing AR software, while Augmented Reality Developer Interns often focus on assisting in the development and design of AR applications. The roles overlap in educational background and work environment, but differ in technical depth and responsibilities.

What does an augmented reality developer intern do?

An Augmented Reality (AR) Developer Intern assists in designing, developing, and testing AR applications and features. They typically work with tools like Unity or Unreal Engine and use programming languages such as C# or JavaScript to create interactive experiences that blend digital content with the real world. Interns often support senior developers, contribute to user interface design, and help troubleshoot technical challenges. Their work may also involve researching new AR technologies and prototyping innovative solutions.

What are the key skills and qualifications needed to thrive as an augmented reality developer intern?

To excel as an Augmented Reality Developer Intern, a strong background in computer science fundamentals, programming (especially in C#, C++, or JavaScript), and familiarity with AR frameworks is essential. Experience with AR development tools such as Unity, Unreal Engine, and platforms like ARKit or ARCore is highly valuable, and coursework or certifications in AR/VR technologies can be advantageous. Creativity, problem-solving abilities, and effective teamwork are standout soft skills in this role. These qualifications and qualities enable interns to create innovative AR experiences and efficiently collaborate in fast-paced development environments.
What are the most commonly searched types of Augmented Reality Developer jobs in Maryland? The most popular types of Augmented Reality Developer jobs in Maryland are:
What are popular job titles related to Augmented Reality Developer Intern jobs in Maryland? For Augmented Reality Developer Intern jobs in Maryland, the most frequently searched job titles are:
What cities in Maryland are hiring for Augmented Reality Developer Intern jobs? Cities in Maryland with the most Augmented Reality Developer Intern job openings:
Infographic showing various Augmented Reality Developer Intern job openings in Maryland as of July 2026, with employment types broken down into 87% Full Time, 9% Part Time, and 4% Contract. Highlights an 80% Physical, 3% Hybrid, and 17% Remote job distribution.

Principal Knowledge & Data Architect

Howard Hughes Medical Institute

Chevy Chase, MD • On-site

Other

Posted 27 days ago


Job description

The EverydayAI Accelerator exists to turn generative AI into daily reality across HHMI’s administrative and operational functions. This role owns HHMI’s knowledge management layer for AI: the discipline of turning institutional information (documents, records, policies, scientific content, operational data) into structured, retrievable, trustworthy knowledge that AI systems can actually use.

The work is technical and grounded. You will design and operate the retrieval-augmented generation pipelines that every Accelerator project depends on: the chunking, embedding, indexing, and retrieval patterns that turn HHMI’s content into something AI can find and reason over. For use cases where a graph representation is the right tool (complex entity relationships, lineage, multi-hop reasoning), the knowledge graph gets built and operated alongside it. This work happens in partnership with the Principal AI Architect, who owns the AI platform and engineering foundation, and the Technology and Systems Management (TSM) Data Integrations team, who owns the data pipelines from source systems. Whoever holds this role designs the knowledge architecture and is accountable for operating it.

Why this role matters

HHMI’s scientific, financial, and operational knowledge lives scattered across documents, databases, and systems never built to talk to AI. Without someone accountable for turning that information into something structured and trustworthy, every AI initiative at HHMI either repeats the same expensive groundwork or surfaces answers no one can stand behind. This role solves that problem once so that every Accelerator project and future AI effort can build on a governed, reliable knowledge foundation instead of reinventing it. 

What you will actually do 

  • Own HHMI’s knowledge management architecture. Design how institutional content is captured, structured, classified, retrieved, and maintained over time. Make the calls on representation (chunked text, embeddings, structured records, knowledge graphs, or hybrid) for each kind of content and each kind of use case, and own the consequences. 

  • Build and operate the RAG pipelines. Design and run the retrieval-augmented generation systems that every AI product at HHMI consumes, including document processing, chunking, embedding, indexing, hybrid retrieval, re-ranking, query rewriting. New projects inherit proven patterns; they do not roll their own. 

  • Build knowledge graphs where the use case requires it. For problems where graph representation is the right tool (complex entity resolution, multi-hop reasoning, lineage and provenance, relationship-heavy queries), design the data model, stand up the graph store, and operate it.  

  • Extract structure from unstructured content. Build the pipelines that turn HHMI’s documents (policies, applications, financial records, scientific content) into something AI can consume. Use the right mix of LLM-based extraction, classical NLP, and rule-based methods for each source, and be able to explain why. 

  • Solve entity resolution. The same person, fund, application, or concept appears across many systems with many representations. Build the deduplication, linking, and canonicalization that lets the institution rely on a single, defensible truth. 

  • Govern knowledge classification and lineage. Sit in the AI governance group as the technical voice on knowledge sensitivity, provenance, and retention. 

  • Partner with Data Integrations and the AI platform team. TSM Data Integrations owns the plumbing across HHMI’s source systems, and you define what AI needs from it while co-building the contracts that connect the two layers. The Principal AI Architect owns the AI platform; the knowledge layer it reasons over comes from this seat. 

  • Communicate across the altitude range. Translate knowledge-architecture trade-offs for engineering teams, then turn around and explain the same decisions to a business leader or executive in terms that actually land. Expect to do both regularly. 

What we are looking for 

  • Real production RAG experience. Proven experience shipping retrieval-augmented systems and running in production, with failures debugged back through the pipeline and the broken step rebuilt. Hybrid retrieval, chunking strategy, query understanding, and re-ranking used as working tools, not just concepts. This is the core of the role. 

  • Knowledge management and data modeling. A librarian’s instinct for content (what’s authoritative, what’s stale, who can see it), plus the ability to look at an unfamiliar domain and identify the right entities, relationships, and representation, defending why an attribute is a node, an edge, or not modeled at all. 

  • Knowledge graph and entity resolution experience. At least one knowledge graph designed, built, and operated in production, with a clear sense of when a graph beats a vector store or document chunk. Deduplication and linking problems solved where the same thing has seven names across four systems and none of them are wrong. 

  • Information extraction and production rigor. Extraction pipelines built to turn unstructured text into structured knowledge using a mix of LLMs, classical NLP, and rule-based methods, treating embedding versioning, retrieval evaluation, corpus drift, and re-indexing as first-class engineering concerns. “The model gave the wrong answer” is a debuggable system, not a shrug. 

  • Data engineering, security, and range. Fluency in a data integration team’s tools (SQL, Databricks, dbt, ETL patterns) pairs with designing around data classification, access controls, and PII handling from the first conversation rather than as a final review. Ability to lead engineers technically without a reporting line, and to explain the same decision to a non-technical stakeholder in terms that help them choose. 

  • Technical range to operate at this level. Strong proficiency in Python and SQL. Production experience with vector databases (Postgres pgvector, Pinecone, Weaviate, Qdrant, or comparable) and embedding pipelines. Production experience with at least one graph database (Neo4j, AWS Neptune, JanusGraph, TigerGraph, Stardog, or comparable) and graph query languages (Cypher, SPARQL, or Gremlin). Working knowledge of modern NLP and information extraction. Fluency in the modern data stack (Databricks, dbt, or comparable). 

  • Education and experience. Bachelor’s degree or equivalent, plus at least eight years of hands-on experience across data engineering, information retrieval, and applied machine learning, with at least three years focused on production knowledge management for AI systems (retrieval-augmented generation, knowledge graphs, or both). 

Nice to have 

  • Background in library or information science, formal ontology, or semantic web technologies (RDFS, OWL, SKOS).