Jobs · Information Technology · Mississippi

Software Developer

XDIN · Byhalia, MS · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections only if real content. The posting includes description paragraph, then "Software Developer Responsibilities" list, then "Software Developer Requirements" list. Also mentions "XDIN Offers Competitive wages, BOE.Major health, dental insurance benefits and vision savings plan. 401k, and basic life.Supplemental benefits such as short-term disability, accident, cancer and life insurance.Paid company holidays and earned time off." That's benefits info. Also maybe pay? It says "Competitive wages" but not specific numbers. According to rules, we should include Pay/Schedule/Benefits sections only if posting actually states them. It states "Competitive wages" but not specific numbers; is that considered real content? It says "Competitive wages" is a statement about pay. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive wages" is a statement, not placeholder. So we could include a Pay section with that sentence. However they also say "Prefer a few substantive sections over many thin ones." Might combine Benefits and Pay? But we have separate headings: Benefits, Pay, Schedule. We have benefits details. Pay: "Competitive wages". Schedule: none mentioned. So we should not create Schedule section. Benefits: we have list of benefits. Could format as
  • . Pay: maybe just a

    with "Competitive wages." Since it's not a list, we can use

    . Also description paragraph at start: we can put as

    . No heading for description? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
    • for any list of duties/requirements/benefits, and

      for prose. Do NOT repeat the job title as a heading. So we need headings for sections we include: maybe "About the role" for the initial description? Could also use "Responsibilities" and "Requirements". Benefits and Pay. Should we include "About the role"? The description includes company overview and mission. That could be considered "About the role". It's substantive. So we can have

      About the role

      then

      ...

      . Then

      Responsibilities

      then
        list items. Then

        Requirements

        then
          . Then

          Benefits

          then
            list items. Then

            Pay

            then

            Competitive wages.

            . Ensure we don't include empty sections. No Schedule. Now extract responsibilities list from text: "Software Developer Responsibilities Modifying software to fix errors, adapt it to new hardware, improve its performance, or upgrade interfaces.Directing system testing and validation procedures.Directing software programming and documentation development.Consulting with departments or customers on project status and proposals.Working with customers or departments on technical issues including software system design and maintenance.Analyzing information to recommend and plan the installation of new systems or modifications of an existing system.Consulting with engineering staff to evaluate software-hardware interfaces and develop specifications and performance requirements.Designing and developing software systems using scientific analysis and mathematical models to predict and measure outcomes and design consequences.Preparing reports on programming project specifications, activities, or status.Conferring with project managers to obtain information on limitations or capabilities.Create Databases with photo capabilities.Create packaging instructions data base, to display the way the parts should be pack.Create a quality report, can be update by the auditors and saves the information into a database." We need to split into list items. Each sentence separated by periods. We'll create
          • for each. Responsibilities items: - Modifying software to fix errors, adapt it to new hardware, improve its performance, or upgrade interfaces. - Directing system testing and validation procedures. - Directing software programming and documentation development. - Consulting with departments or customers on project status and proposals. - Working with customers or departments on technical issues including software system design and maintenance. - Analyzing information to recommend and plan the installation of new systems or modifications of an existing system. - Consulting with engineering staff to evaluate software-hardware interfaces and develop specifications and performance requirements. - Designing and developing software systems using scientific analysis and mathematical models to predict and measure outcomes and design consequences. - Preparing reports on programming project specifications, activities, or status. - Conferring with project managers to obtain information on limitations or capabilities. - Create Databases with photo capabilities. - Create packaging instructions data base, to display the way the parts should be pack. - Create a quality report, can be update by the auditors and saves the information into a database. Now Requirements list: "Software Developer Requirements Bachelor's degree in computer science or related degree.3+ Years development ExperienceGood understanding of Front End Development and also Back End.Experience in C#, .Net, or JavaKnowledge of the software development life-cycle.The desire to work in fast-paced environment.Ability to develop unit testing of code components or complete applications.Creativity is always a plus.Must be a full-stack developer and understand concepts of software engineering.Experience working on a variety of software development projects.Deep programming language knowledge." We need to split sentences. Some missing spaces after periods. We'll parse: - Bachelor's degree in computer science or related degree. - 3+ Years development Experience - Good understanding of Front End Development and also Back End. - Experience in C#, .Net, or Java - Knowledge of the software development life-cycle. - The desire to work in fast-paced environment. - Ability to develop unit testing of code components or complete applications. - Creativity is always a plus. - Must be a full-stack developer and understand concepts of software engineering. - Experience working on a variety of software development projects. - Deep programming language knowledge. Now Benefits list: from "XDIN Offers Competitive wages, BOE.Major health, dental insurance benefits and vision savings plan. 401k, and basic life.Supplemental benefits such as short-term disability, accident, cancer and life insurance.Paid company holidays and earned time off." We need to extract benefits items. The text is messy. Let's parse: "Competitive wages, BOE.Major health, dental insurance benefits and vision savings plan. 401k, and basic life.Supplemental benefits such as short-term disability, accident, cancer and life insurance.Paid company holidays and earned time off." We can treat each benefit as separate item: - Competitive wages - BOE (maybe "BOE."? Not sure what BOE stands for; but it's part of text. We'll keep as "BOE." maybe it's a typo. We'll keep as "BOE." - Major health, dental insurance benefits and vision savings plan - 401k - basic life - Supplemental benefits such as short-term disability, accident, cancer and life insurance - Paid company holidays - earned time off But we should avoid splitting incorrectly. Perhaps better to list as: - Competitive wages - BOE (maybe "BOE.") but we can keep as "BOE." - Major health, dental insurance benefits and vision savings plan - 401k - Basic life - Supplemental benefits such as short-term disability, accident, cancer and life insurance - Paid company holidays - Earned time off We'll output as
            • items. Pay section: we already have Competitive wages mentioned; but we also have it in benefits. To avoid duplication, maybe we should not duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we list Competitive wages in benefits, we still need to convey that info. Could keep it only in benefits and not have separate Pay section. But the rule says we can create Pay section only if posting actually states them. It does state "Competitive wages". However we already have that in benefits list; duplication may be okay but maybe better to avoid duplication. However we must preserve all info; duplication is not prohibited but could be considered redundant. I'd rather keep Pay section with "Competitive wages." and not duplicate in benefits. But then we lose the other benefits details. We'll keep benefits list without Competitive wages. So benefits list will exclude Competitive wages. Pay section will have that. Thus benefits list: - BOE - Major health, dental insurance benefits and vision savings plan - 401k - basic life - Supplemental benefits such as short-term disability, accident, cancer and life insurance - Paid company holidays - earned time off Now we need to output HTML fragment only, no /, no markdown. Let's craft:

              About the role

              Description XDIN subsidiary of ALTEN Group, includes 500 employees dedicated to the automotive engineering development. ALTEN is a Leader in Engineering & Information Technology system, and operates in over 21 countries (Europe, North America, Asia, Africa and Middle East) with more than 28,000 employees of which 88% are engineers. At XDIN, we are always looking for world-class talent to lead our global teams through commitment and dedication to our OEM and Tier I clients. We believe in quality support from concept through production, and delivering the best customer experience while at the same time attaining a great place to work! XDIN Offers Competitive wages, BOE.Major health, dental insurance benefits and vision savings plan. 401k, and basic life.Supplemental benefits such as short-term disability, accident, cancer and life insurance.Paid company holidays and earned time off. We place a high value on thought leadership. We want every employee to develop all the skills required to become an engineering and technology thought leader; contributing to the knowledge assets of our team and our clients. From day one, every consultant is trained and mentored to elevate their careers.

              But note we included the benefits sentence in the About the role paragraph; we might duplicate. Better to remove benefits sentence from About the role to avoid duplication. The About the role paragraph should be the description before benefits. The original description includes: "Description XDIN subsidiary of ALTEN Group, includes 500 employees dedicated to the automotive engineering development. ALTEN is a Leader in Engineering & Information Technology system, and operates in over 21 countries (Europe, North America, Asia, Africa and Middle East) with more than 28,000 employees of which 88% are engineers. At XDIN, we are always looking for world-class talent to lead our global teams through commitment and dedication to our OEM and Tier I clients. We believe in quality support from concept through production, and delivering the best customer experience while at the same time attaining a great place to work! XDIN Offers Competitive wages, BOE.Major health, dental insurance benefits and vision savings plan. 401k, and basic life.Supplemental benefits such as short-term disability, accident, cancer and life insurance.Paid company holidays and earned time off. We place a high value on thought leadership. We want every employee to develop all the skills required to become an engineering and technology thought leader; contributing to the knowledge assets of our team and our clients. From day one, every consultant is trained and mentored to elevate their careers." We can split: first part up to "great place to work!" then benefits sentence, then thought leadership part. To avoid duplication, we can put benefits sentence in Benefits section, and keep About the role without that sentence. So About the role paragraph: up to "great place to work!" plus thought leadership sentences. Thus: "Description XDIN subsidiary of ALTEN Group, includes 500 employees dedicated to the automotive engineering development. ALTEN is a Leader in Engineering & Information Technology system, and operates in over 21 countries (Europe, North America, Asia, Africa and Middle East) with

Similar jobs

Software Developer

Everest InfotechEdison, NJ· 3 mo ago
Engineeringapply on everestinfotechllc.com

Software Developer

University of MichiganAnn Arbor, MI· 2 mo ago
$85k–$95k/yrapply on careers.umich.edu