Hi B***e, I’m J***e, an HR Recruiter at StrategyBrain. I came across your profile and was really impressed by your work on active pedagogies and immersive learning,especially your experience with VR/AR, serious games and AI-driven approaches at U***e. We’re partnering with E***s on a Senior Instructional Designer , Immersive & AI-driven Learning role, and your background seems like a great fit. Would you be open to a brief conversation to explore this opportunity? Looking forward to hearing from you! Best regards, J***e

Hi B***e, Great to hear you’re interested! I’d be happy to set up a brief call to dive into the Senior Instructional Designer , Immersive & AI-driven Learning role at E***s,covering the core responsibilities (VR/AR, serious games, AI personalization), the team structure, and next steps. Would any of these slots work for you? • Wednesday, May 1 at 10:00 AM CET • Thursday, May 2 at 3:00 PM CET • Friday, May 3 at 9:00 AM CET If none fit, just let me know your availability and I’ll do my best to accommodate. Looking forward to speaking with you! Best, J***e

Hi B***e, Perfect,Thursday, May 2 at 3 PM CET is confirmed. Ahead of our chat, here are a few of the key challenges our Immersive & AI team is tackling at E***s: 1. Scaling truly immersive VR/AR and mixed-reality modules across diverse hardware and learner profiles. We want to maintain high fidelity and accessibility without ballooning development time. 2. Embedding AI-driven personalization into serious games to adapt learning paths in real time,balancing algorithmic recommendations with pedagogical goals. 3. Streamlining our end-to-end instructional design lifecycle (storyboarding in Articulate or Unity, prototyping in H5P, production oversight) so we can iterate faster and maintain rigorous quality standards. 4. Conducting UX research and rapid prototyping to ensure learner-centric experiences that also meet SMEs’ content requirements. 5. Mentoring junior designers and fostering a culture of active pedagogies and AI best practices across the team. Given your proven track record in VR/AR, active learning and AI workshops at U***e, we’d love to hear your thoughts on prioritization and execution. On our call, we’ll dive deeper into these points, the team structure, career growth opportunities and the resources you’ll have at your disposal. Let me know if there’s anything else you’d like to unpack in advance. Looking forward to speaking on Thursday! Best, J***e

Hi B***e, Thanks for taking the time to align those challenges with your background,I’m excited to hear your thoughts. If there’s any particular area you’d like more context on (for example our AI-driven branching logic in serious games, or device compatibility across headsets), just let me know and I can share additional details ahead of Thursday’s call. On the call we’ll also dive into our current VR compliance-training and AR sales-simulation pilots, review the team structure (five designers, three developers plus SMEs), and explore how you’d help shape our immersive-learning roadmap and mentor junior colleagues. Feel free to reach out with any follow-ups in the meantime. Looking forward to our conversation on Thursday! Best, J***e

Hi B***e, Great question,striking the right balance between speed and depth in UX is something we take seriously. Here’s how our team manages it: 1. Phased Prototyping • We start with low-fidelity prototypes (paper sketches, simple Unity scenes) to validate core interactions before investing in full assets. • Early feedback from a small group of target users flags show-stoppers quickly, so we only build what’s proven valuable. 2. Agile Sprints with Built-in UX Milestones • We operate in two-week iterations. Each sprint includes a dedicated UX research and testing checkpoint midway, plus a mini “pilot lab” session at the end. • This cadence keeps us on a fast timeline while preventing last-minute usability surprises. 3. Embedded UX Researcher • A UX specialist sits alongside our designers and developers throughout the build. They run quick guerrilla tests (10,15 minutes) and synthesize findings in real time. • Their insights feed directly into our backlog, ensuring each sprint addresses priority UX issues. 4. SME Collaboration & QA Gates • We align with subject-matter experts before and after user tests to ensure the narrative and learning objectives remain intact. • At the end of each sprint, both UX and learning-design leads sign off on a “go/no-go” for the next development phase. 5. Continuous Feedback Loop • As you observed in your U***e projects, rapid iteration thrives on tight feedback loops. We host weekly “show and tell” sessions with internal stakeholders and pilot users so there’s no disconnect between speed and quality. By structuring our process this way, we hit our deadlines without cutting corners on usability or pedagogical rigor. I’d be happy to walk you through a sample VR-pilot timeline and even share anonymized user-test reports on Thursday’s call,let me know if that would be helpful. Looking forward to diving deeper! Best, J***e

Hi B***e, Great point,deep experimentation and team well-being are just as important as rapid delivery. Here’s how we strike that balance at E***s: 1. Scheduled “Innovation Sprints” • Every fourth two-week cycle, we dedicate one sprint entirely to VR/AR R&D: prototyping wild ideas, testing new interactions and exploring cutting-edge hardware. • This gives designers and devs breathing room to iterate without sprint-end pressure. 2. Built-in Reflection Blocks • In our regular sprints, we carve out a half-day “reflection block” mid-sprint for design critiques, brown-bag learning sessions or solo playtests. • These slots let team members step back, recharge creatively and share fresh insights. 3. Well-Being Rituals • We maintain “focus days” (no meetings) twice a week so folks can dive deep or recharge without interruption. • Managers run weekly one-on-ones that include a well-being check-in and encourage setting healthy boundaries around workload. 4. Rapid Feedback with Low Stakes • Early prototypes go through quick guerrilla tests rather than full user-testing cycles. By keeping initial tests low-stakes, teams learn fast and avoid burnout. • We track team health metrics (sprint happiness scores, velocity vs. stress) and adjust scope or cycle length if we see signs of overload. 5. Culture of Psychological Safety • We encourage experimenting,even if an idea “fails,” it’s viewed as valuable learning. • Monthly “Demo & Debrief” gatherings let everyone share successes, lessons learned and highlight next-steps for deeper dives. I’d be happy to walk you through a sample calendar that we use for innovation sprints and reflection blocks on our call Thursday. Let me know if there’s anything else you’d like to unpack beforehand! Best, J***e