Lab-Heavy Java EE Web Services + Java EE 6 Web Apps (Reusable Courseware Team)

Job Posting (Final): Lab-Heavy Java EE Web Services + Java EE 6 Web Apps (Reusable Courseware Team) Overview We’re hiring a courseware developer (or team) to create two example courses and then support additional similar courses in the future. The output must be highly reusable, consistent, and written for lab-ready delivery. Course #1 (40 hours total, 5 days): Programming Java SOAP and REST Web Services Course #2 (5 days): Web Application Programming with Java EE6 These two courses are examples only—we need a team that can build new courses using the same approach. --- Key Scheduling Requirements (Applies to BOTH Courses) Same lesson cadence as Course #1. You must design and deliver the course using 3 lessons per day or 4 lessons per day (you recommend which, but it must be consistent with Course #1’s format). Hands-on requirement (strict): At least 50% of total lesson time must be lab execution + verification, not reading. Lesson structure template (must be used for every lesson) Each lesson must include, in this exact order: Lesson title + estimated time Learning objectives (3–5 bullets) Key concepts (short sections; no long essays) Complete lab (required; step-by-step) Expected results (bullets) Quick check (3–5 questions) Common mistakes / troubleshooting (at least 2 items) --- Deliverables (Required for EACH course) For each course, you will produce the following: 1) Instructor PowerPoint (.pptx) 1 complete deck per course Must include: - course overview/agenda - all 10 lessons (or the equivalent lesson count based on your selected daily cadence, but the course must still cover the full objectives) - for every lesson: - concept slides (brief) - lab setup slide - “what students should see/verify” checkpoints - short speaker notes (focus on lab emphasis + likely issues) 2) Student PDF (1 combined PDF per course) 1 combined PDF per course (contains all lessons) Must include, for every lesson: - learning objectives - key concepts - complete lab instructions (numbered steps) - expected results - quick check (3–5 questions) - troubleshooting guidance 3) Lab code package(s) Must be included as part of the course package (zip folder with code + how to run) The code in labs must match: - student PDF instructions - instructor PPT verification checkpoints Code must use consistent: - indentation - naming conventions - package structure - code comments (simple, consistent) Tech Requirements Course #2: Java EE 6 Web Application (Tomcat-based) Labs must run on: Java 8 Eclipse Tomcat “Typical Java EE 6” topics/patterns No WebSphere requirement Course #1: SOAP + REST Course #1 must use: JAX-WS (SOAP) including WSDL/XSD understanding JAX-RS (REST) SOAP/REST client development + testing techniques Security concepts aligned to course objectives Online Store Scenario (Used in BOTH courses) Use a simple store theme. The scope must be limited to: Browse products (list) Create an order (simple “submit order” flow) REST APIs that expose product + order operations Do not expand into a full storefront (no complex checkout/cart flows). Hands-On Design Requirement (Strict) Labs must include: - prerequisites - how to build/deploy/run - exactly what to verify (“expected output” + where to look) - troubleshooting steps (what to check first) Across each day: - minimum 50% of the time budget should be lab execution + verification activities. Team/Workflow Requirements We want a repeatable workflow you can use for future course builds. In your proposal, describe: Who owns: - instructor PPT creation - student PDF writing - lab/code creation - final consistency + QA polish How you will ensure PPT verification checkpoints match PDF lab steps. How you keep templates consistent across lessons and courses. Milestones (Required) To prevent rework: Submit Lesson 1 for both courses first (student PDF pages + instructor PPT slides). We review and approve: - lesson structure matches the template - labs match the environment + online store scope - verification checkpoints align between PPT and PDF After approval, you complete remaining lessons. What You Must Provide in Your Proposal Cadence recommendation: Choose 3 lessons/day or 4 lessons/day for both courses, consistent with Course #1’s format. Include: - estimated duration per lesson - where the lab time fits to meet the 50% requirement Lab completeness approach: How you keep “complete lab” outcomes even with shorter lessons (if using 4/day). QA/consistency approach: A concrete method to keep PPT, PDF, and code aligned. Timeline estimate: - Lesson 1 first draft due date - remaining lessons delivery sequence Pricing model + revision policy: - per-course vs per-lesson vs weekly - number of revision rounds included - whether formatting/polish is included Qualifications (Must Have) Strong technical writing for developer audiences Experience creating: - instructor PPTX decks with lab verification slides/checkpoints - student PDFs with step-by-step labs, expected results, and troubleshooting Strong hands-on knowledge of: - JAX-WS (SOAP) + WSDL/XSD - JAX-RS (REST) - Java EE 6 web patterns + JPA - Java 8 + Eclipse + Tomcat Application / Portfolio Request Include: 1–2 samples of course materials (PPT and/or PDF) Examples of hands-on labs you’ve written (screenshots welcome) Typical turnaround time for a single lesson draft (including revisions)