Mobile Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. The posting includes: Description (some intro), Job Title, Location, About the customer, Requirements (list), Job responsibilities (list), What we offer (list of benefits), Also pay range mentioned in DescriptionNote: starting pay range $120k-$130k. So we have Pay section. Schedule? Not explicitly mentioned; maybe hybrid location but schedule not given. So we omit Schedule. Benefits: we have "Excellent Benefits:" list. Also "Work-Life Balance", "Professional Development", "Exciting Projects", "Collaborative Environment". Those could be under Benefits or maybe separate sections. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have About the role: could be the introductory paragraph about the role and customer. That's present: "Our customer is an American manufacturer...". Also maybe "Job Title: Senior Mobile Software Engineer Location: Santa Clara, CA (Hybrid)" but we should not repeat job title as heading. We can include location in a short paragraph. Responsibilities: list of duties. Requirements: list of requirements. Qualifications: maybe education requirement (Bachelor's degree). Could be separate. Skills: maybe technical skills list (Android, BLE, iOS, Agile, etc). Could be separate. Benefits: list from "What we offer" and "Excellent Benefits". Pay: the pay range. Schedule: not present, omit. We must not include boilerplate like EEO etc. There's none. We must preserve all substantive info; not invent. We need to output only HTML fragment, no markdown fences. Let's extract content. Intro: "Note: GlobalLogic estimates the starting pay range for this role to be performed hybrid in Santa Clara, CA is $120,000 – $130,000 and reflects base salary only. This pay range is provided as a good faith estimate and the amount offered may be higher or lower. GlobalLogic takes many factors into consideration in making an offer, including candidate qualifications, work experience, operational needs, travel and onsite requirements, internal peer equity, prevailing wage, responsibilities, and other market and business considerations. Job Title: Senior Mobile Software Engineer Location: Santa Clara, CA (Hybrid) Our customer is an American manufacturer and globally recognized leader in Healthcare and Medical Devices. In close cooperation with the international team you will have the ability to participate in product feature definition, development, testing, and post-release support for innovative medical products." We should not repeat job title as heading, but we can include location and maybe job title in a paragraph? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and maybe job title in a short paragraph under About the role? Probably we can include location and brief description. Thus About the role section:

About the role

... (including location and description). We'll include the note about pay? Actually pay will be separate Pay section. So we can keep pay note out of About the role. Thus About the role paragraph: "Our customer is an American manufacturer and globally recognized leader in Healthcare and Medical Devices. In close cooperation with the international team you will have the ability to participate in product feature definition, development, testing, and post-release support for innovative medical products. The role is hybrid based in Santa Clara, CA." We could also include the note about pay range? Better to put in Pay section. Now Responsibilities: list items from "Job responsibilities:" bullet list. Let's extract each responsibility line: - Design and develop Android mobile applications that connect to medical devices via BLE, ensuring secure and reliable data transmission. - Collaborate with iOS developers, QA, clinical, and hardware teams to create consistent and compliant cross-platform experiences. - Implement BLE workflows including device discovery, secure pairing, bonding, characteristic interactions, and firmware updates. - Rapidly ramp up and contribute to iOS development (Swift/Objective-C) where required. - Write clean, testable, and well-documented code following medical device software standards (e.g., IEC 62304). - Participate in architecture, risk assessment, and design reviews, especially in the context of regulated medical software. - Support validation, verification, and regulatory submission processes by generating compliant documentation and test evidence. - Diagnose and resolve issues related to BLE communication, device interoperability, and user-reported bugs. - Documents software development and/or test development by writing documents, reports, memos, change requests. Methods used are determined by approved procedures and standards. - Follow the full design life cycle process including driving efforts in requirements specification, design activities, planning, code reviews and creating corresponding artifacts. - Analyzes, evaluates, verifies requirements, software and systems using software engineering standards and best practices - Provide complete expert engineering solutions that are well thought out that is architecturally and technically sound We'll put each as

. Now Requirements: list from "Requirements:" after "We are seeking a Principal Mobile Software Engineer – Mobile..." Actually the requirements list starts after that sentence. Let's extract: - 8+ years of experience in mobile application development, with at least 5+ years in Android (Kotlin/Java). - Hands-on experience with BLE protocols for mobile-device interaction, ideally in healthcare or medical applications. - Deep understanding of BLE operations: scanning, connecting, bonding, characteristic read/write, notifications, background tasks. - Experience working in or willingness to learn iOS development (Swift/Objective-C, CoreBluetooth). - Familiarity with medical device software development lifecycle (IEC 62304), software documentation, and quality systems. - Experience with Agile/Scrum methodologies and version control systems (Git). - Strong analytical, debugging, and communication skills. - Strong oral and written communication skills (duplicate? maybe keep once) - Ability to work independently and come up with solutions that are well thought out and technically sound - Demonstrated experience in software development lifecycle (Agile), object-oriented design methodology - Demonstrated technical leadership skills - Creative / innovative thinker - Good organizational and multi-tasking skills - Bachelor’s degree in computer science, electrical engineering, or a related field Note there are duplicates: Strong analytical, debugging, and communication skills and Strong oral and written communication skills. We'll keep both as separate items? Might be redundant but we preserve. Now Qualifications: maybe education requirement (Bachelor's degree) could be under Qualifications. But we already have Bachelor's degree in Requirements. Could move to Qualifications. However we need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the Bachelor's degree somewhere. We could put it under Qualifications section. Then we should not duplicate it in Requirements. But the Requirements list includes it; we could keep it there and not have Qualifications. But we need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one Requirements section? But they ask to use headings for those specific names if content exists. We could have Requirements section containing all requirement items, and Qualifications section maybe empty -> we must not emit empty heading. So we should not include Qualifications if no distinct content beyond what's already in Requirements. However the Bachelor's degree is a qualification; but it's already in Requirements list. So we can keep it in Requirements and omit Qualifications. Skills: we could extract technical skills: Android (Kotlin/Java), BLE, iOS (Swift/Objective-C, CoreBluetooth), Agile/Scrum, Git, etc. But many are already in Requirements. Could create Skills section for technical competencies like "Android development, BLE, iOS, Agile, Git, etc." But that would duplicate. Better to not create Skills if it would be thin/duplicate. However the instruction: Prefer a few substantive sections over many thin ones. So maybe we keep only About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. Benefits: from "What we offer" and "Excellent Benefits". Let's extract: Exciting Projects: Come take your place at the forefront of digital transformation! With clients across all industries and sectors, we offer an opportunity to work on market-defining products using the latest technologies. Collaborative Environment: You can expand your skills by collaborating with a diverse team of highly talented people in an open, laidback environment — or even abroad in one of our global centers or client facilities! Work-Life Balance: GlobalLogic prioritizes work-life balance, which is why we offer flexible work schedules and opportunities to work from home. Professional Development: We provide continuing education classes, professional certification and training (technical, soft skills, language, and communication skills) to help you realize your professional goals. Being part of a global organization, there are additional learning opportunities through international knowledge exchanges. Excellent Benefits: We provide our employees with competitive salaries, health and life insurance, short-term and long-term disability insurance, a matched contribution 401K plan, flexible spending accounts, and PTO and holidays. We could combine these into a Benefits section with list items. Pay: from DescriptionNote: starting pay range $120,000 – $130,000 base salary only. Also note about factors. We'll include that as prose. Now we need to output HTML fragment with headings

and

• for lists,

  for prose. Let's craft. About the role:

  About the role

  Our customer is an American manufacturer and globally recognized leader in Healthcare and Medical Devices. In close cooperation with the international team you will have the ability to participate in product feature definition, development, testing, and post-release support for innovative medical products. The role is hybrid based in Santa Clara, CA.

  Responsibilities:

  Responsibilities

  • Design and develop Android mobile applications that connect to medical devices via BLE, ensuring secure and reliable data transmission.
  • Collaborate with iOS developers, QA, clinical, and hardware teams to create consistent and compliant cross-platform experiences.
  • Implement BLE workflows including device discovery, secure pairing, bonding, characteristic interactions, and firmware updates.
  • Rapidly ramp up and contribute to iOS development (Swift/Objective-C) where required.
  • Write clean, testable, and well-documented code following medical device software standards (e.g., IEC 62304).
  • Participate in architecture, risk assessment, and design reviews, especially in the context of regulated medical software.
  • Support validation, verification, and regulatory submission processes by generating compliant documentation and test evidence.
  • Diagnose and resolve issues related to BLE communication, device interoperability, and user-reported bugs.
  • Document software development and/or test development by writing documents, reports, memos, change requests. Methods used are determined by approved procedures and standards.
  • Follow the full design life cycle process including driving efforts in requirements specification, design activities, planning, code reviews and creating corresponding artifacts.
  • Analyze, evaluate, verify requirements, software and systems using software engineering standards and best practices.
  • Provide complete expert engineering solutions that are well thought out, architecturally and technically sound.
  Requirements:

  Requirements

  • 8+ years of experience in mobile application development, with at least 5+ years in Android (Kotlin/Java).
  • Hands-on experience with BLE protocols for mobile-device interaction, ideally in healthcare or medical applications.
  • Deep understanding of BLE operations: scanning, connecting, bonding, characteristic read/write, notifications, background tasks.
  • Experience working in or willingness