Frontier Engineering Docs

Questions

4 min read

✎ Edit this page

❓ Questions

Each question has a block ID (^q-###) so other notes can link straight to it: [[Questions#^q-017|^q-017]]. When answered: add it to Decision Log and move it to Answered (keep the block ID). Priority: 🔴 blocks curriculum/commercial work · 🟡 needed before the trial · 🟢 can wait Status: 🔄 in discussion with Microsoft · ⏳ leaning, not final

Open

Outcomes

Credential

  • 🔴 Q-017 — Firm-wide use of the certificate. Individuals earn it (assumed). What may a firm claim, and when? E.g. “PwC is Frontier Certified” once it has N certified people? Can firms use the mark in proposals or on their website? Is there a firm-level listing or tier? Who polices misuse?
  • 🟡 Q-022 — Credential naming. Is “Frontier Certified” Microsoft’s chosen name, tied to its “Frontier Firm” messaging? Are there badge levels (workshop vs. post-deployment)?
  • 🟡 Q-023 — Renewal. Does the certificate expire? How do people renew as the products change?

Program structure

  • ⏳ 🔴 Q-018 — Deployment phase / ongoing monitoring. Leaning yes; structure still in discussion. How long is it? Real client work or internal projects? If teams work on internal projects, what data-privacy limits apply? Is it self-reported feedback rather than direct observation? How is it reviewed? See Deployment-phase review load.
  • 🔴 Q-004 — What level are we teaching to? Cohorts mix roles (engineering, project management, etc.) and seniority. Do we need content for different technical levels, and maybe a few tiers? See Learner Personas.
  • 🔴 Q-005 — Workshop length. Balance cost and attention span against proficiency: 3 days? Also cohort size, locations and cities. This drives Scale and Capacity Model.
  • 🔴 Q-010 — Sample project. One consistent example for every cohort, a few business-line examples, or a unique project per trainee org? Working idea: a fictional insurer (Capstone scenario).
  • 🔴 Q-024 — Scaling delivery to 10,000. Do Frontier engineers deliver every cohort, or do we move to licensed trainers after the trial?
  • 🟡 Q-019 — Eligibility. Nomination by firm? Prerequisites per role path?

Constraints

  • 🟡 Q-026 — Restrictions on engineers/PMs. What data-privacy, model-usage, tooling and network limits will learners face? They may be cohort-, firm-, client- or project-specific. These shape Environment and the sample project.

Microsoft relationship — 🔄 in flux

  • 🔄 Q-016 — Approval process. Content review scope, turnaround, Microsoft owner(s).
  • 🔄 Q-020 — Funding. Microsoft-funded, firm-paid, or a mix.
  • 🔄 Q-021 — Marketing terms & Frontier’s visibility. Is Frontier Engineering named (“delivered by”) or invisible?
  • 🔄 Q-014 — Timeline. A trial program is expected soon. Need: date, size, which firm.
  • 🟢 Q-013 — Microsoft partner programs. Does the certificate connect to Solutions Partner designations or specializations?

Content & labs

  • 🟡 Q-007 — Content sourcing & IP. Do we author everything or adapt Microsoft material (incl. HVE Core attribution)? Who owns the IP?
  • 🟡 Q-009 — Lab tenancy & cost. Microsoft-provided tenants/credits, or someone else’s? Critical at 10k scale.

Operations

  • 🟡 Q-008 — Course platform readiness. The platform is custom-built (Frontier Engineering Digital Learning). What must be added for branding, cohorts, submissions and the certificate handoff?
  • 🟡 Q-011 — Instructor requirements. Will Microsoft require MCT or specific certs for Frontier instructors?
  • 🟢 Q-012 — Pricing. Depends on Q-020.

Answered

  • Q-015 — Credential issuer. Microsoft issues the certificate. Microsoft is filing an internal staffing issue to enable the project.
  • Q-001 — Buyer vs. learner. Microsoft is the brand owner; consulting firms (e.g. PwC) are the learner organizations.
  • Q-002 — Meaning of “certification.” Earned through an in-person workshop, not an exam. Benchmark: Claude Frontier Academy.
  • Q-003 — White-label partner. Microsoft. Frontier engineers deliver Microsoft-branded workshops.
  • Q-006 — HVE scope. Microsoft’s open-source HVE Core, as published.

Graph View

Backlinks