Senior iOS Developer

Experis · Plano, TX · 3 wk ago

On-siteEngineering$65–$67/hrContract

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only when posting has real specific content. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove "Job Title: Application Programmer III" as heading (the page already shows it). Also do not put Job ID/requisition numbers as headings. We need to preserve all substantive information. Let's parse the posting: - Opening: "Our client, a leading organization in the technology sector, is seeking an Application Programmer III to join their team. As an Application Programmer III, you will be part of the Software Development Department supporting the Mobile Applications Team. The ideal candidate will have strong problem-solving skills, excellent communication abilities, and a proactive mindset, which will align successfully in the organization." That's about the role. Could be "About the role" section. - "Job Title: Application Programmer III Location:Plano, TX Pay Range: $65-$67/hr" We need to include Pay section if posting states it. So we have Pay Range: $65-$67/hr. Also location maybe not needed as heading; we can embed in a short
maybe. - "What's the Job?" bullet list: Participate in the full application lifecycle, including development, testing, and deployment of iOS applications. Develop automation scripts and test solutions for iOS platforms using Copilot and other automation tools. Collaborate with product teams to design new features, prototypes, and estimate project timelines. Ensure application quality, performance, and adherence to best practices. Maintain and update documentation for all features and functionalities in development. That's responsibilities. - "What's Needed?" bullet list: Bachelor's degree in computer science, software engineering, or related field. 5+ years of experience in iOS development using Swift, UIKit, and automation frameworks like Appium. Proficiency in Objective-C, Swift UI, and extensive knowledge of XCode. Experience with code versioning tools such as Git and Bitbucket. Strong understanding of Web Services, Rest APIs, and mobile security features like Biometrics and push notifications. That's requirements/qualifications/skills. We need to decide sections: Requirements, Qualifications, Skills. The posting lumps them; we can split maybe into Requirements (education + experience) and Skills (technical). But we need to avoid thin sections. Could combine into one "Requirements" section with both education/experience and skills. Or we could have "Requirements" and "Skills". The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one "Requirements" section that includes education, experience, and technical skills. - "What's in it for me?" bullet list: Opportunity to work on innovative iOS applications in a dynamic environment. Engage with cutting-edge automation tools and frameworks. Collaborate with talented professionals and contribute to impactful projects. Gain valuable experience in a fast-paced, technology-driven organization. Access to comprehensive health and wellness plans after the waiting period. Upon Completion Of Waiting Period, Consultants Are Eligible For Medical and Prescription Drug Plans Dental Plan Vision Plan Health Savings Account Health Flexible Spending Account Dependent Care Flexible Spending Account Supplemental Life Insurance Short Term and Long Term Disability Insurance Business Travel Insurance 401(k), Plus Match Weekly Pay That's benefits. Also note "Weekly Pay" maybe part of pay? But we already have pay range. Could include "Weekly Pay" as part of pay? But we already have pay range; we could note that pay is weekly? The posting says "Weekly Pay" under benefits. Might be considered part of Pay section? But we already have Pay Range. We could include a Pay section with the range and note that it's weekly. However instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay Range, so we can have Pay section. It also mentions Weekly Pay under benefits; but we can incorporate that into Pay section or Benefits. Probably better to keep Pay section with the range and note it's weekly. Benefits section can list the health etc. - Then there is a paragraph about applying etc. That's application instructions; we must remove. - Then there is a paragraph about ManpowerGroup etc. That's boilerplate about the company; we should remove as it's not substantive job info? It's about the staffing agency; likely considered boilerplate/navigation/legal? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ManpowerGroup description is not exactly those categories but could be considered boilerplate about the staffing firm. It's not part of the job description; it's likely considered "about the company" but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Is that substantive? It's about the parent company; might be considered not essential to the role. However it's not explicitly listed as boilerplate to remove, but it's not about the job. The safe approach: keep it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's a description of Experis/ManpowerGroup. Could be considered "about the company" but not part of the job. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we remove it, we are summarizing away detail (the description). But is that detail substantive to the job? It's about the staffing agency; maybe not needed for the candidate but still part of posting. The instruction doesn't explicitly say to remove company description. It only mentions specific boilerplate types. So we should keep it? However the section about ManpowerGroup is quite long and could be considered boilerplate but not listed. I'd lean to keep it as a paragraph maybe under a generic "About the company" but we don't have a heading for that. We could just include it as a
after the sections, without a heading. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. We could just output paragraphs without headings for that company description. But we need to ensure we don't include any filler like "commensurate with experience". Not present. We also need to avoid repeating the job title as a heading. So we won't put

Application Programmer III

. We need to output only HTML fragment. Let's structure:

About the role

Our client, a leading organization in the technology sector, is seeking an Application Programmer III to join their team. As an Application Programmer III, you will be part of the Software Development Department supporting the Mobile Applications Team. The ideal candidate will have strong problem-solving skills, excellent communication abilities, and a proactive mindset, which will align successfully in the organization.

Responsibilities

Participate in the full application lifecycle, including development, testing, and deployment of iOS applications.
Develop automation scripts and test solutions for iOS platforms using Copilot and other automation tools.
Collaborate with product teams to design new features, prototypes, and estimate project timelines.
Ensure application quality, performance, and adherence to best practices.
Maintain and update documentation for all features and functionalities in development.

Requirements

Bachelor's degree in computer science, software engineering, or related field.
5+ years of experience in iOS development using Swift, UIKit, and automation frameworks like Appium.
Proficiency in Objective-C, Swift UI, and extensive knowledge of XCode.
Experience with code versioning tools such as Git and Bitbucket.
Strong understanding of Web Services, Rest APIs, and mobile security features like Biometrics and push notifications.

Benefits

Opportunity to work on innovative iOS applications in a dynamic environment.
Engage with cutting-edge automation tools and frameworks.
Collaborate with talented professionals and contribute to impactful projects.
Gain valuable experience in a fast-paced, technology-driven organization.
Access to comprehensive health and wellness plans after the waiting period.
Upon completion of waiting period, consultants are eligible for:

Medical and Prescription Drug Plans
Dental Plan
Vision Plan
Health Savings Account
Health Flexible Spending Account
Dependent Care Flexible Spending Account
Supplemental Life Insurance
Short Term and Long Term Disability Insurance
Business Travel Insurance
401(k), Plus Match

Weekly Pay

But note we already have Pay section; we might not need Weekly Pay in benefits. Could move Weekly Pay to Pay section. Let's create Pay section:

Pay

Pay Range: $65-$67/hr (Weekly Pay)

But we need to avoid filler like "not specified". We have actual range. We also have location: "Location:Plano, TX". Could include in About the role paragraph or a separate short p. Could add after About the role:

Location: Plano, TX

. That's fine. Now we need to decide whether to include Qualifications and Skills sections separately. We combined into Requirements. That's okay. We should not create Schedule section because not mentioned. Now we need to remove the application instructions and the ManpowerGroup description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The ManpowerGroup description is substantive? It's about the staffing agency; but it's not about the job. However it's part of the posting. If we remove it, we are summarizing away detail (the description). But the instruction also says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company description. So we should keep it. Thus after the sections, we can add a

containing the ManpowerGroup description. But we need to ensure we don't include any duplicated lines. The description includes repeated phrases maybe; but we keep as is. Let's copy the ManpowerGroup description exactly: "About ManpowerGroup, Parent Company of: Manpower, Experis and Talent Solutions. Experis® is a global leader in technology services and part of the ManpowerGroup® (NYSE: MAN) family of brands. We connect skilled technology professionals with meaningful opportunities where they can grow their careers, expand their expertise and make a real impact. Guided by the belief that it takes Human Ingenuity to unlock the true potential of technology, Experis helps people gain experience with leading organizations, build sought-after skills and take the next step toward a brighter future. Backed by ManpowerGroup's 75+ years of workforce expertise and global reach across more than 70 countries and territories, Experis brings the scale, insight and opportunity to help people and businesses thrive. ManpowerGroup is consistently recognized for its commitment to inclusion, ethics and responsible business, including being named one of the World's Most Ethical Companies. Learn more at Experis.com." We need to ensure we don't include any HTML tags inside that paragraph besides

. It's fine. Now check for any other boilerplate: "If this is a role that interests you and you'd like to learn more, click apply now