Teamcenter UI/UX Developer (Active Workspace)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real content. The posting includes: Job Description (maybe About the role), Must Have Technical/Functional Skills (Skills), Roles & Responsibilities (Responsibilities), Generic Managerial Skills (maybe Skills or Requirements), Key Words to search in Resume (maybe Skills), Pre-Screening Questionnaire (maybe Requirements? but it's questionnaire, not needed? It's content but maybe we can treat as Requirements? It's questions for candidate; we could put under Requirements or Qualifications. But we should not invent sections; we can include a section "Requirements" if there is content. The posting includes "Must Have Technical/Functional Skills" which is skills. Also "Generic Managerial Skills" could be skills. Also "Key Words to search in Resume" is also skills. Could combine into Skills section. Responsibilities: "Roles & Responsibilities" content. Pay: Salary Range given. Schedule: not mentioned. Benefits: not mentioned. Qualifications: maybe not explicit; but we could treat "Must Have Technical/Functional Skills" as Qualifications? But better to follow headings: Skills, Responsibilities, Pay. Possibly also "About the role" could be the initial Job Description paragraph? The posting starts with "Job Description Must Have Technical/Functional Skills ..." Not exactly a description. There's no separate "About the role". Could skip. We must not repeat job title. No metadata like Job ID. We must preserve all substantive information. So we need to include all bullet points etc. The posting does not have explicit bullet lists; it's paragraphs with commas. We need to convert to

• for any list of duties/requirements/benefits. We need to identify lists. The text includes many items separated by commas or semicolons. We could treat each distinct item as a list entry. For example under Skills: "Strong Teamcenter Active Workspace framework experience, including AWC build and deployment using SWF, Node.js, and Gulp." That's a sentence; we could break into list items: "Strong Teamcenter Active Workspace framework experience", "AWC build and deployment using SWF, Node.js, and Gulp", etc. But we must preserve all info; we can keep as prose

  if not a list. The instruction: "Use

  • for any list of duties/requirements/benefits, and

    for prose." So we need to decide what constitutes a list. The posting includes sections like "Must Have Technical/Functional Skills" followed by a long sentence with many skills separated by commas. Could be considered a list. Safer to treat as

    • each skill item. But we need to not lose nuance. Let's parse the content: Job Description (maybe intro): "Must Have Technical/Functional Skills Strong Teamcenter Active Workspace framework experience, including AWC build and deployment using SWF, Node.js, and Gulp. Good understanding of AWC module structure, staging layout, repository layout, and deployment packaging. Hands-on Declarative UI development using View/ViewModel JSON, actions, data providers, conditions, commands, and i18n bundles. XRT stylesheet customization for Summary, Create, and Table renderings, including objectSets, tableProperty, subrendering, and visibleWhen. ColumnConfig and table configuration, including UI behavior driven through *_DefaultChildProperties and XRT preference mappings. Proficiency in JavaScript/TypeScript, HTML, CSS, and Angular/AMX concepts. Experience invoking REST and Teamcenter SOA client services from Active Workspace ViewModels. Experience developing custom commands, command handlers, and command placements. Client-side performance tuning and browser-based debugging of Active Workspace applications. UX design practices covering personas, task analysis, accessibility, usability, and responsive layouts. Rich Client (RAC) Eclipse RCP customization for legacy screens is an added advantage." That's a block of skills. Then "Roles & Responsibilities Design, develop, test, and deploy Teamcenter Active Workspace user-interface customizations. Build Declarative UI components using View/ViewModel JSON, actions, data providers, conditions, commands, and localization bundles. Create and maintain XRT stylesheets, object sets, table renderings, subrenderings, and visibility rules. Configure columns, tables, and Teamcenter preferences that control UI behavior and displayed properties. Integrate Active Workspace ViewModels with REST and Teamcenter SOA services. Apply persona-based design, task analysis, accessibility, and responsive-layout principles to improve user experience. Troubleshoot browser issues, tune client-side performance, and support AWC build and deployment activities. Collaborate with architects, functional teams, UX stakeholders, and other vendors in an onsite-offshore delivery model." Then "Generic Managerial Skills, If any Communication, articulation, organization, coordination, independent delivery, and multi-vendor collaboration." Then "Key Words to search in Resume Teamcenter, Active Workspace, AWC, Declarative UI, ViewModel JSON, XRT, ColumnConfig, JavaScript, TypeScript, Node.js, Gulp, SOA, REST, RAC" Then "Pre-Screening Questionnaire Explain your hands-on Active Workspace customization experience and the AWC versions used. Describe an AWC Declarative UI solution built with View/ViewModel JSON, actions, data providers, and conditions. How have you customized XRT stylesheets, objectSets, tableProperty, subrendering, or visibleWhen? Explain your experience with ColumnConfig and UI preferences such as *_DefaultChildProperties and XRT mappings. Describe a REST or Teamcenter SOA client call implemented from an Active Workspace ViewModel. How have you developed custom commands and command placements, and tuned or debugged client-side performance? What UX practices have you applied for accessibility, personas, task analysis, and responsive layouts? Describe any RAC Eclipse RCP customization experience for legac y Teamcenter screens." Then "Salary Range: $90,000-$130,000 a year" We need to output HTML fragment with sections: maybe

      Skills

      with
      list of skill items.

      Responsibilities

      with
      .

      Managerial Skills

      maybe under Skills or separate? Could be

      Managerial Skills

      but we could combine into Skills. However the instruction: Prefer a few substantive sections over many thin ones. So we could have Skills (including technical and managerial), Responsibilities, Pay. Also maybe "Keywords" could be part of Skills. The Pre-Screening Questionnaire is not a section heading we have; we could treat as Requirements? But we have no heading for questionnaire; we could put under Requirements as list of questions? But the instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The questionnaire is specific content; we could make a section "Pre‑Screening Questionnaire" but that's not one of the allowed headings list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The allowed headings are those; we should not create other headings. So we need to map questionnaire to either Requirements or Qualifications. Probably Requirements. So we can put the questionnaire items under

      Requirements

      as a list. Similarly, "Key Words to search in Resume" could be part of Skills or Requirements; but we already have Skills. Thus sections: Skills, Responsibilities, Requirements, Pay. We must not include Benefits or Schedule. Now we need to convert each block into
      • items. Let's extract skill items from the Must Have Technical/Functional Skills paragraph. We can split by sentences (period). Each sentence could be a list item. Sentences: 1. Strong Teamcenter Active Workspace framework experience, including AWC build and deployment using SWF, Node.js, and Gulp. 2. Good understanding of AWC module structure, staging layout, repository layout, and deployment packaging. 3. Hands-on Declarative UI development using View/ViewModel JSON, actions, data providers, conditions, commands, and i18n bundles. 4. XRT stylesheet customization for Summary, Create, and Table renderings, including objectSets, tableProperty, subrendering, and visibleWhen. 5. ColumnConfig and table configuration, including UI behavior driven through *_DefaultChildProperties and XRT preference mappings. 6. Proficiency in JavaScript/TypeScript, HTML, CSS, and Angular/AMX concepts. 7. Experience invoking REST and Teamcenter SOA client services from Active Workspace ViewModels. 8. Experience developing custom commands, command handlers, and command placements. 9. Client-side performance tuning and browser-based debugging of Active Workspace applications. 10. UX design practices covering personas, task analysis, accessibility, usability, and responsive layouts. 11. Rich Client (RAC) Eclipse RCP customization for legacy screens is an added advantage. We'll keep each as
      • . Now Responsibilities paragraph sentences: 1. Design, develop, test, and deploy Teamcenter Active Workspace user-interface customizations. 2. Build Declarative UI components using View/ViewModel JSON, actions, data providers, conditions, commands, and localization bundles. 3. Create and maintain XRT stylesheets, object sets, table renderings, subrenderings, and visibility rules. 4. Configure columns, tables, and Teamcenter preferences that control UI behavior and displayed properties. 5. Integrate Active Workspace ViewModels with REST and Teamcenter SOA services. 6. Apply persona-based design, task analysis, accessibility, and responsive-layout principles to improve user experience. 7. Troubleshoot browser issues, tune client-side performance, and support AWC build and deployment activities. 8. Collaborate with architects, functional teams, UX stakeholders, and other vendors in an onsite-offshore delivery model. Now Generic Managerial Skills: "Communication, articulation, organization, coordination, independent delivery, and multi-vendor collaboration." This is a list separated by commas. Could be a single sentence; we could make each item a list item. Managerial skills items: - Communication - articulation - organization - coordination - independent delivery - multi-vendor collaboration We could add these to Skills section as well, but maybe better to include under Skills as part of managerial skills. But we already have Skills section; we could add a sublist? Simpler: add them to Skills as additional items. Now Key Words to search in Resume: list of keywords: Teamcenter, Active Workspace, AWC, Declarative UI, ViewModel JSON, XRT, ColumnConfig, JavaScript, TypeScript, Node.js, Gulp, SOA, REST, RAC. Could be added to Skills as well, but they are just keywords; we could incorporate them but might be redundant. Since we already have many skill items covering these, we could skip to avoid duplication. But we must preserve ALL substantive information; not summarizing away detail. If we skip keywords, we lose that info. However the keywords are essentially same as skills; but we could still include them as a list under Skills (maybe as "Key words for resume: ..."). Better to include them as a list under Skills as well. Now Pre-Screening Questionnaire: list of questions. We'll put under Requirements. Questions: 1. Explain your hands-on Active Workspace customization experience and the AWC versions used. 2. Describe an AWC Declarative UI solution built with View/ViewModel JSON, actions, data providers, and conditions. 3. How have you customized XRT stylesheets, objectSets, tableProperty, subrendering, or visibleWhen? 4. Explain your experience with ColumnConfig and UI preferences such as *_DefaultChildProperties and XRT mappings. 5. Describe a REST or Teamcenter SOA client call implemented from an Active Workspace ViewModel. 6. How have you developed custom commands and command placements, and tuned or debugged client-side performance? 7. What UX practices have you applied for accessibility, personas, task analysis, and responsive layouts? 8. Describe