Senior Full Stack/Web Developer and Digital Experience Engineer

Senior Full-Stack Web Developer / Digital Experience Engineer NextGen Cyber Pro LLC is seeking an experienced Senior Full-Stack Web Developer / Digital Experience Engineer to implement and expand our external digital platform. This is an implementation-focused engagement. Our enterprise architecture, governance model, business structure, digital strategy, branding direction, and implementation requirements have already been developed. The selected developer will be expected to work from our approved implementation guides and technical requirements rather than redesign the enterprise architecture from scratch. PROJECT OBJECTIVE Build and enhance a secure, scalable, responsive, professional external digital platform for the NextGen Cyber Pro ecosystem. The platform will support multiple enterprise capabilities, including: • NextGen Cyber Pro corporate website • NGCP Consulting • NGCP Institute • NGCP Government • NGCP Foundation • Careers & Staffing • Events & Community • Marketing and digital engagement • Lead generation • Contact and appointment scheduling • Future enterprise capabilities The architecture should provide a unified NextGen Cyber Pro experience while allowing individual business capabilities to maintain appropriate identities, content, workflows, and legal boundaries. IMPLEMENTATION-GUIDE REQUIREMENT The selected developer MUST be willing to work from our existing: • Enterprise implementation guides • Approved architecture • Information architecture • Security requirements • Branding standards • Domain/subdomain architecture • Integration requirements • Governance requirements • Data-flow requirements • Acceptance criteria This project is not an invitation to replace the existing architecture with the developer's preferred architecture. Recommendations are welcome, but material architectural changes must be documented, justified, and approved before implementation. ACCOUNT ACCESS & LEAST PRIVILEGE This is an important requirement. The developer will receive only the accounts, roles, permissions, environments, and credentials necessary to perform the approved job functions. We follow least-privilege and separation-of-duties principles. The developer should NOT expect: • Global Administrator access • unrestricted Microsoft 365 access • unrestricted Azure access • unrestricted production access • domain registrar ownership • unrestricted DNS administration • access to unrelated enterprise systems • access to financial systems • access to HR systems • access to sensitive governance repositories • access to systems unrelated to the assigned implementation Where privileged changes are required, NextGen Cyber Pro may perform the change internally or provide temporary, scoped access appropriate to the approved task. Access may be: • role-based • time-limited • environment-specific • task-specific • logged • monitored • reviewed • revoked upon completion The developer must be comfortable working within this model. TECHNICAL RESPONSIBILITIES The selected developer may be responsible for: • Full-stack web development • Responsive web design implementation • Front-end development • Back-end development where required • CMS implementation • Reusable component development • API integrations • Forms • Lead capture • CRM integrations • Appointment scheduling • Email workflow integrations • Contact forms • Analytics • SEO implementation • Accessibility • Performance optimization • Security hardening • Authentication integrations where required • Payment integrations where approved • Donation integrations for NGCP Foundation where approved • LMS/student-system integrations where approved • AI chatbot integration where approved • Deployment automation • Testing • Documentation ARCHITECTURAL PRINCIPLES The implementation must support: Security by Design Least Privilege Defense in Depth Separation of Concerns Defense Against Fragmentation Single Source of Truth Vendor Independence Deliberate Simplicity Controlled Growth Scalability Accessibility Performance Maintainability REUSABLE ARCHITECTURE We do not want multiple disconnected websites built independently. Where appropriate, the platform should use: • reusable components • common design system • shared branding foundations • standardized navigation patterns • common security controls • common analytics architecture • reusable integrations • standardized development practices Business divisions and affiliated organizations may have different content and experiences while remaining part of a coordinated digital ecosystem. DATA OWNERSHIP The website should not become an unnecessary competing system of record. Where authoritative enterprise systems already exist, information should flow to the appropriate system. Examples: Website Lead → Authoritative CRM Course Inquiry / Registration → Appropriate NGCP Institute system Appointment Request → Approved scheduling system Foundation Transaction → Approved Foundation-controlled process The developer should avoid creating unnecessary standalone databases or data stores where an approved enterprise system already owns the information. SOURCE CODE & INTELLECTUAL PROPERTY All project source code, configurations, documentation, infrastructure definitions, integration documentation, deployment artifacts, and other contracted deliverables must be delivered to and controlled by NextGen Cyber Pro LLC as required by the engagement agreement. Development should occur using company-approved repositories and environments. The project must not depend on a contractor's personal account for continued operation after the engagement ends. DOCUMENTATION REQUIREMENTS The selected developer must document: • architecture implemented • components • dependencies • APIs • integrations • environment configuration • deployment process • environment variables • secrets requirements • DNS requirements • external services • data flows • troubleshooting procedures • known limitations • maintenance requirements Another qualified developer should be able to assume responsibility for the platform using the documentation provided. SECURITY REQUIREMENTS Security is a core requirement, not a final-stage add-on. The developer should understand: • OWASP web application security principles • secure authentication • authorization • secrets management • secure API development • input validation • encryption • logging • dependency security • vulnerability remediation • secure deployment • privacy considerations • least privilege • secure third-party integrations Production credentials must not be stored in source code. REQUIRED SKILLS Strong experience with: • Full-stack web development • Modern JavaScript/TypeScript • Modern front-end frameworks • Responsive design • HTML5 • CSS • REST APIs • API integrations • Git / source control • CMS architecture • Cloud deployment • CI/CD • Web security • Performance optimization • Accessibility • SEO • Analytics Experience integrating platforms such as CRM, scheduling, email, marketing automation, payment, LMS, and AI services is highly desirable. MICROSOFT EXPERIENCE Experience integrating with the Microsoft ecosystem is strongly preferred, including familiarity with: • Microsoft Entra ID • Microsoft Graph • Microsoft 365 • Microsoft Teams • Microsoft Bookings • SharePoint • Power Automate • Azure This position does not require unrestricted administrative access to these systems. WORKING STYLE We are looking for someone who can: • follow established architecture • work from implementation specifications • ask questions when requirements are unclear • identify risks before implementation • recommend improvements without automatically replacing approved designs • document assumptions • document dependencies • work through controlled changes • test their work • provide implementation evidence • communicate clearly • leave behind maintainable code and documentation DELIVERABLE EXPECTATIONS Work will be delivered through controlled milestones. Potential phases include: Phase 1 — Platform Foundation Architecture implementation, design system, CMS, security baseline, deployment pipeline, analytics, SEO, accessibility and reusable components. Phase 2 — Core Digital Experiences Corporate site, NGCP Consulting and NGCP Institute. Phase 3 — Enterprise Expansion NGCP Foundation, Careers & Staffing, Events & Community and other approved capabilities. Phase 4 — Advanced Integrations CRM, automation, AI/chat, scheduling, portals, payments, learning integrations and other approved capabilities. Actual milestones will be finalized with the selected developer. SCREENING QUESTIONS Please answer the following when applying: 1. Describe a multi-site or multi-brand enterprise web platform you have built. 2. How would you build multiple business experiences while preventing them from becoming disconnected websites? 3. Are you comfortable implementing from an existing architecture and implementation guide rather than redesigning the solution from scratch? 4. Are you comfortable working with least-privilege access where you receive only the permissions necessary for your assigned tasks? 5. Describe your experience integrating websites with CRM, scheduling, email automation, payment, LMS or similar enterprise systems. 6. Describe your experience with Microsoft Entra ID, Microsoft Graph, Microsoft 365 or Azure integrations. 7. How do you manage secrets, API credentials and production access? 8. How do you document a platform so another developer can maintain it after your engagement ends? 9. Describe your approach to OWASP security, accessibility, performance and SEO. 10. If our implementation guide specifies an architecture you disagree with, how would you handle that situation? IMPORTANT APPLICATION INSTRUCTION Begin your proposal with the words: “IMPLEMENTATION GUIDE” Then briefly explain how you would approach implementing an existing enterprise architecture while preserving security, maintainability and scalability. Generic proposals that do not address the implementation-guide and least-privilege requirements may not be considered.