Jobs · Information Technology · Maryland

Amazon Connect Developer

Global CI (Global Commerce & Information, Inc.) · Windsor Mill, MD · 1 mo ago
On-siteInformation TechnologyContract
We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No metadata like Job ID. Remove boilerplate. Need to preserve all substantive info. Let's parse the posting. First paragraph: "Your Success is Our Success. Global CI is an award-winning 30-year IT Services company founded on the principles of providing high-quality, value-added technology consulting services. Our vision is to create a better future by improving the lives of the people we serve through emerging technologies. Join us and together we will advance the future of technology services. Global CI offers competitive compensation and non-salary benefits to all eligible employees." That's about the company, could be "About the role"? Actually "About the role" is typical heading for role description. But we have company description. Could put under "About the role" or maybe "About the company". Since only allowed headings list includes About the role. We'll use that for company overview and role intro. Next: "Key Required Skills The successful candidate will have fluency in AWS Connect design and development principles and work with stakeholders to develop enterprise business solutions that leverages industry processes and best practices." That's a skill requirement. Could go under Requirements or Skills. Then "Position Description Position Description: Design, develop and implement AWS Connect processes to include new or modifications to applications, forms, workflow, policies, actions, access control, interfaces, and any other configurations required to support client processesProvide recommendations for enhancing existing operations and provide recommendations for new updates or modificationsSupport and enhance existing processes based on new requirements or upgradesFacilitate requirements gathering, review and document requirementsDesign and develop solutions within the ServiceNow environmentAll other duties as assigned or directed" That's responsibilities. Then "Basic Qualifications Bachelor's Degree in Computer Science, Mathematics, Engineering, or a related field7 years of experience working with large enterprise framework7 years of hands-on experience working with AWS Cloud platform3 years of hands-on experience working with Amazon Connect3 years of experience using Node.js, Python or Java for development3 years of experience in designing call routing & messagingExcellent interpersonal and communication skills (Required Skills) **Selected candidate must be able to obtain and maintain a public trust clearance** **Selected candidate must be willing to work on-site in Woodlawn, MD 5 days a week** **Master's and 10+ years of experience, Bachelor's and 12+ years of experience or 18+ years in lieu of a degree**" That's qualifications/requirements. Then "These Skills Will Help You Succeed In This Position Solid AWS Cloud and AWS Connect Developer experienceExtensive experience and knowledge with IVR, Automatic Call Distribution (ACD), Skill-Based Routing, Live ChatExperience with process flow documentation creation.Experience with Lambda, Lex Conversational, Bots/NLP, Kinesis Streams, Glue, VPC, SMS (Simple Notification Service), AppSync, EventBridge, Kinesis Firehouse, DynamoDB Streams, Service Catalog, Kinesis Data AnalyticsStrong verbal and written communication skills. (Desired Skills) Showcase your knowledge of modern development through the following experience or skills:Adept at working independently, but also in a team environmentDemonstrated experience delivering technology solutions in a fast-paced, deadline driven enterprise environmentExcellent understanding of change management, testing requirements, techniques, and tools to ensure high availability of systemsPrior Federal government experienceSelf-starter, highly motivated individual who adapts to a dynamic work environmentStrong attention to detail with an ability to operate effectively across multiple priorities" That's desired skills. Then "Benefits Include Comprehensive medical, dental, vision, life, and short & long-term disability insurance + health savings accountMatching 401k retirement plan + IRA's and Roth IRA'sGenerous paid time off and paid holidaysEmployee recruitment/referral bonusPaid community service hoursTuition reimbursementEmployee discounts" That's benefits. No explicit Pay or Schedule info besides "must be willing to work on-site in Woodlawn, MD 5 days a week" which is schedule info (on-site 5 days a week). That could go under Schedule. Also maybe Pay not mentioned besides "competitive compensation". That's vague; we should not create Pay section unless actual numbers. "competitive compensation" is not specific; rule says do not create Pay section unless posting actually states them. It states "competitive compensation" but not numbers. Likely we should not create Pay section because it's not specific. However "competitive compensation" could be considered stating compensation but not specific. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits, so Benefits section is okay. It states schedule (on-site 5 days a week) so Schedule section is okay. Pay: only "competitive compensation" which is vague but still states compensation. Might be considered stating it, but rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation, albeit generic. I'd include Pay section with that statement? But they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive compensation" is somewhat vague but not exactly filler; it's a statement. I'd include Pay section with that sentence. Now we need to structure. We'll have sections: About the role (company overview + maybe role intro), Responsibilities, Requirements (or Qualifications), Skills (maybe split into Required and Desired?), Benefits, Pay, Schedule. We must not repeat job title. Use

for each heading. We need to use
  • for any list of duties/requirements/benefits. So for responsibilities list, we need to break into items. The responsibilities paragraph is a run-on sentence with multiple duties separated by line breaks? Actually it's a single paragraph with no punctuation besides maybe missing commas. We need to split into logical items. Let's parse: "Design, develop and implement AWS Connect processes to include new or modifications to applications, forms, workflow, policies, actions, access control, interfaces, and any other configurations required to support client processes" "Provide recommendations for enhancing existing operations and provide recommendations for new updates or modifications" "Support and enhance existing processes based on new requirements or upgrades" "Facilitate requirements gathering, review and document requirements" "Design and develop solutions within the ServiceNow environment" "All other duties as assigned or directed" We'll make each a
  • . Requirements: Basic qualifications list: Bachelor's Degree..., 7 years experience..., etc. Also clearance, on-site, alternative experience. We'll list each as
  • . Skills: Required skills: fluency in AWS Connect design and development principles, work with stakeholders... Also maybe "Excellent interpersonal and communication skills". Also "Solid AWS Cloud and AWS Connect Developer experience" etc? Actually those are under "These Skills Will Help You Succeed In This Position" which are desired skills. Also there is a list of desired skills after that. We need to decide sections: Could have "Required Skills" and "Desired Skills" but only allowed headings list includes Skills (generic). We could combine both under Skills with subheadings? Not allowed; only headings from list. Could we have two Skills sections? Probably not; better to have one Skills section that includes both required and desired, maybe separate
      for each? But we need to preserve all info. Could do:

      Skills

      Required skills:

      • ...

      Desired skills:

      • ...
      That's okay. Benefits: list items. Pay: include statement. Schedule: include statement about on-site 5 days a week. Now ensure we don't include boilerplate like EEO etc. Remove those paragraphs. Now produce HTML fragment. Let's craft. About the role: combine company intro and maybe role summary: "Your Success is Our Success. Global CI is an award-winning 30-year IT Services company founded on the principles of providing high-quality, value-added technology consulting services. Our vision is to create a better future by improving the lives of the people we serve through emerging technologies. Join us and together we will advance the future of technology services. Global CI offers competitive compensation and non-salary benefits to all eligible employees." That's fine. Now Responsibilities

      Responsibilities

        ... items. Requirements

        Requirements

          ... items. Skills

          Skills

          Required skills:

            ...

          Desired skills:

            ...
          Benefits

          Benefits

            ... items. Pay

            Pay

            Global CI offers competitive compensation and non-salary benefits to all eligible employees.

            (maybe just that sentence.) Schedule

            Schedule

            Selected candidate must be willing to work on-site in Woodlawn, MD 5 days a week.

            Check for duplication: The sentence about competitive compensation appears also in About the role; we might duplicate. But we need to preserve all substantive info; duplication okay? Might be redundant but we can keep in Pay section only and maybe remove from About the role to avoid duplication. However About the role already includes that sentence; we could keep it there and not repeat in Pay. But Pay section needs content; we could state "Compensation is competitive (see above)." But better to keep Pay section with the statement about competitive compensation, and maybe remove duplicate from About the role? The About the role currently includes that sentence; we could keep it there and not have Pay section? But we decided to include Pay. To avoid duplication, we could edit About the role to exclude that sentence, but we must preserve all substantive information; we can move it to Pay section and keep About the role without that sentence. Let's see About the role content without that sentence: "Your Success is Our Success. Global CI is an award-winning 30-year IT Services company founded on the principles of providing high-quality, value-added technology consulting services. Our vision is to create a better future by improving the lives of the people we serve through emerging technologies. Join us and together we will advance the future of technology services." That's still substantive. Thus Pay section will have the compensation sentence. Now Benefits: list items: Comprehensive medical, dental, vision, life, and short & long-term disability insurance + health savings account; Matching 401k retirement plan + IRA's and Roth IRA's; Generous paid time off and paid holidays; Employee recruitment/referral bonus; Paid community service hours; Tuition reimbursement; Employee discounts. Make each a
          • . Now Required skills: from "Key Required Skills The successful candidate will have fluency in AWS Connect design and development principles and work with stakeholders to develop enterprise business solutions that leverages industry processes and best practices." Also "Excellent interpersonal and communication skills (Required Skills)" appears in Basic Qualifications parentheses. Also maybe "Solid AWS Cloud and AWS Connect Developer experience" is under desired? Actually that line appears under "These Skills Will Help You Succeed In This Position" which is desired skills. So required skills list: fluency in AWS Connect design and development principles; work with stakeholders to develop enterprise business solutions that leverages industry processes and best practices; excellent interpersonal and communication skills. We'll list those. Desired skills: many items: Solid AWS Cloud and AWS Connect Developer experience; Extensive experience and knowledge with IVR, Automatic Call Distribution (ACD), Skill-Based Routing, Live Chat; Experience with process flow documentation creation.; Experience with Lambda, Lex Conversational, Bots/NLP, Kinesis Streams, Glue, VPC, SMS (Simple Notification Service), AppSync, EventBridge, Kinesis Firehouse, DynamoDB Streams, Service Catalog, Kinesis Data Analytics; Strong verbal and written communication skills.; Adept at working independently, but also in a team environment; Demonstrated experience delivering technology solutions in a fast-paced, deadline driven enterprise environment; Excellent understanding of change management, testing requirements, techniques, and tools to ensure high availability of systems; Prior

Similar jobs

Amazon Connect Developer

The Amatriot GroupWoodlawn, MD· 1 mo ago
Information Technology$130k–$180k/yrapply on amatriot.clearcompany.com