Application Lead
United Flow Technologies (UFT) · Irving, TX · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate (EEO etc). Preserve all substantive info.
We need to parse the posting.
Content:
First paragraph: United Flow Technologies description. That's about the company, maybe "About the role"? Actually "About the role" could be description of role. The first paragraph is about the company, not role. But we can treat as "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role (summary of role), Responsibilities (What you'll do), Requirements (What you bring?), Qualifications (maybe education), Skills (technical skills), Benefits (maybe none), Pay (none), Schedule (none). We need to include only sections with real specific content.
Let's extract:
Role summary: "The Application Lead will own the design, development, integration, deployment, and ongoing support of UFT’s enterprise application portfolio. This role will partner with business leaders, the Head of IT, acquired entities, and third-party providers to translate functional and technical requirements into scalable solutions across Quickbase, ERP, financial reporting, and related platforms. The Application Lead will establish application and integration standards, automate business processes, manage the Quickbase vendor relationship, and convert application data and stakeholder feedback into actionable insights. The role requires hands-on technical leadership, strong customer advocacy, sound documentation practices, and the ability to adapt quickly as UFT’s technology needs evolve."
That's good for About the role.
Responsibilities: "What you'll do:" list items.
List:
- Lead the full application lifecycle for Quickbase and other enterprise solutions, including requirements, design, demonstrations, development, testing, documentation, training, deployment, support, and continuous improvement
- Design, build, and maintain secure REST APIs, SQL-based ETL processes, and integrations across HR, finance, operations, sales, marketing, customer service, Talent and People, legal, and other enterprise systems
- Develop production-grade AI automations, custom skills, plugins, and MCP integrations, supported by prompt-engineering standards, governance, data security, and access controls
- Serve as the single point of contact for application needs, manage key vendor relationships, advise stakeholders on best practices, and escalate material risks or issues to the PMO and Head of IT
- Maintain application dashboards, service metrics, process documentation, and regular reporting while ensuring compliance with data privacy, security, and audit requirements
- Monitor and resolve escalated application support tickets within established service-level targets and identify recurring issues for permanent remediation
That's responsibilities.
Requirements: maybe "What you bring:" includes experience etc. Could be split into Requirements (experience) and Qualifications (education) and Skills (technical). Let's parse:
"What you bring:" bullet list (though not bullet but sentences):
- 8+ years of experience delivering technical solutions in software development, application services, engineering, or support, including 4+ years designing and building Quickbase, relational database, SaaS integration, and enterprise application solutions
- Hands-on experience developing REST APIs, JavaScript solutions, SQL-based ETL processes, and integrations with ERP and financial platforms such as Sage, NetSuite, QuickBooks, and Vena
- Experience designing AI automation solutions using Claude Code, Claude Cowork, Codex, Gemini, or similar platforms, including agentic workflows, document-processing pipelines, intelligent assistants, custom skills, plugins, and MCP integrations
- Demonstrated ability to optimize and automate business processes, communicate with technical and non-technical stakeholders, produce clear user and technical documentation, and build relationships from individual contributors through the C-suite
- Bachelor’s degree in Computer Science, Engineering, MIS, or a related field preferred; experience in a private equity-owned portfolio company, regulated industry, or critical infrastructure environment is also preferred
- Authorized to work in the United States and able to travel as business needs require
- Experience with Quickbase and enterprise business applications, along with REST APIs, JavaScript, .NET, and Windows/cloud-based environments
- Familiarity with ERP and financial platforms such as QuickBooks, Sage, NetSuite, Foundation, aACE, Epicor, or Vena, with AI experience using tools such as Claude, Gemini, or Codex preferred
We can categorize:
Requirements: maybe the experience years etc. Qualifications: education. Skills: technical skills (REST APIs, JavaScript, .NET, etc). But we need to avoid duplication. Let's decide:
Section "Requirements": list of experience requirements (8+ years, 4+ years Quickbase, etc). Could also include authorization to work, travel.
Section "Qualifications": Bachelor's degree preferred, etc.
Section "Skills": hands-on experience developing REST APIs, JavaScript solutions, SQL-based ETL, integrations with ERP, experience designing AI automation, ability to optimize processes, communication, documentation, relationship building, experience with Quickbase, .NET, Windows/cloud, familiarity with ERP platforms, AI experience with Claude etc.
But there is overlap. We need to preserve all substantive info, not invent. We can combine into fewer sections to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements & Qualifications combined? But they said use headings for those categories. We could have About the role, Responsibilities, Requirements (including experience, qualifications, skills). But they also want Skills separate if content. However we can combine qualifications and skills into Requirements if we think it's still substantive. But better to follow the headings list: we can include About the role, Responsibilities, Requirements, Qualifications, Skills. If any section lacks specific content, we omit it.
We have content for About the role, Responsibilities, Requirements (experience years etc), Qualifications (degree preferred etc), Skills (technical skills). Benefits, Pay, Schedule: none mentioned, so omit.
Now we need to ensure we don't include filler like "preferred" etc. That's okay.
We must not repeat job title. Not include boilerplate like EEO.
Now produce HTML fragment:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role (summary of role), Responsibilities (What you'll do), Requirements (What you bring?), Qualifications (maybe education), Skills (technical skills), Benefits (maybe none), Pay (none), Schedule (none). We need to include only sections with real specific content.
Let's extract:
Role summary: "The Application Lead will own the design, development, integration, deployment, and ongoing support of UFT’s enterprise application portfolio. This role will partner with business leaders, the Head of IT, acquired entities, and third-party providers to translate functional and technical requirements into scalable solutions across Quickbase, ERP, financial reporting, and related platforms. The Application Lead will establish application and integration standards, automate business processes, manage the Quickbase vendor relationship, and convert application data and stakeholder feedback into actionable insights. The role requires hands-on technical leadership, strong customer advocacy, sound documentation practices, and the ability to adapt quickly as UFT’s technology needs evolve."
That's good for About the role.
Responsibilities: "What you'll do:" list items.
List:
- Lead the full application lifecycle for Quickbase and other enterprise solutions, including requirements, design, demonstrations, development, testing, documentation, training, deployment, support, and continuous improvement
- Design, build, and maintain secure REST APIs, SQL-based ETL processes, and integrations across HR, finance, operations, sales, marketing, customer service, Talent and People, legal, and other enterprise systems
- Develop production-grade AI automations, custom skills, plugins, and MCP integrations, supported by prompt-engineering standards, governance, data security, and access controls
- Serve as the single point of contact for application needs, manage key vendor relationships, advise stakeholders on best practices, and escalate material risks or issues to the PMO and Head of IT
- Maintain application dashboards, service metrics, process documentation, and regular reporting while ensuring compliance with data privacy, security, and audit requirements
- Monitor and resolve escalated application support tickets within established service-level targets and identify recurring issues for permanent remediation
That's responsibilities.
Requirements: maybe "What you bring:" includes experience etc. Could be split into Requirements (experience) and Qualifications (education) and Skills (technical). Let's parse:
"What you bring:" bullet list (though not bullet but sentences):
- 8+ years of experience delivering technical solutions in software development, application services, engineering, or support, including 4+ years designing and building Quickbase, relational database, SaaS integration, and enterprise application solutions
- Hands-on experience developing REST APIs, JavaScript solutions, SQL-based ETL processes, and integrations with ERP and financial platforms such as Sage, NetSuite, QuickBooks, and Vena
- Experience designing AI automation solutions using Claude Code, Claude Cowork, Codex, Gemini, or similar platforms, including agentic workflows, document-processing pipelines, intelligent assistants, custom skills, plugins, and MCP integrations
- Demonstrated ability to optimize and automate business processes, communicate with technical and non-technical stakeholders, produce clear user and technical documentation, and build relationships from individual contributors through the C-suite
- Bachelor’s degree in Computer Science, Engineering, MIS, or a related field preferred; experience in a private equity-owned portfolio company, regulated industry, or critical infrastructure environment is also preferred
- Authorized to work in the United States and able to travel as business needs require
- Experience with Quickbase and enterprise business applications, along with REST APIs, JavaScript, .NET, and Windows/cloud-based environments
- Familiarity with ERP and financial platforms such as QuickBooks, Sage, NetSuite, Foundation, aACE, Epicor, or Vena, with AI experience using tools such as Claude, Gemini, or Codex preferred
We can categorize:
Requirements: maybe the experience years etc. Qualifications: education. Skills: technical skills (REST APIs, JavaScript, .NET, etc). But we need to avoid duplication. Let's decide:
Section "Requirements": list of experience requirements (8+ years, 4+ years Quickbase, etc). Could also include authorization to work, travel.
Section "Qualifications": Bachelor's degree preferred, etc.
Section "Skills": hands-on experience developing REST APIs, JavaScript solutions, SQL-based ETL, integrations with ERP, experience designing AI automation, ability to optimize processes, communication, documentation, relationship building, experience with Quickbase, .NET, Windows/cloud, familiarity with ERP platforms, AI experience with Claude etc.
But there is overlap. We need to preserve all substantive info, not invent. We can combine into fewer sections to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements & Qualifications combined? But they said use headings for those categories. We could have About the role, Responsibilities, Requirements (including experience, qualifications, skills). But they also want Skills separate if content. However we can combine qualifications and skills into Requirements if we think it's still substantive. But better to follow the headings list: we can include About the role, Responsibilities, Requirements, Qualifications, Skills. If any section lacks specific content, we omit it.
We have content for About the role, Responsibilities, Requirements (experience years etc), Qualifications (degree preferred etc), Skills (technical skills). Benefits, Pay, Schedule: none mentioned, so omit.
Now we need to ensure we don't include filler like "preferred" etc. That's okay.
We must not repeat job title. Not include boilerplate like EEO.
Now produce HTML fragment:
About the role
... (the summary)
Responsibilities
- ... ...
Requirements
- 8+ years of experience delivering technical solutions in software development, application services, engineering, or support, including 4+ years designing and building Quickbase, relational database, SaaS integration, and enterprise application solutions
- Hands-on experience developing REST APIs, JavaScript solutions, SQL-based ETL processes, and integrations with ERP and financial platforms such as Sage, NetSuite, QuickBooks, and Vena
- Experience designing AI automation solutions using Claude Code, Claude Cowork, Codex, Gemini, or similar platforms, including agentic workflows, document-processing pipelines, intelligent assistants, custom skills, plugins, and MCP integrations
- Demonstrated ability to optimize and automate business processes, communicate with technical and non-technical stakeholders, produce clear user and technical documentation, and build relationships from individual contributors through the C-suite
- Authorized to work in the United States and able to travel as business needs require
Qualifications
- Bachelor’s degree in Computer Science, Engineering, MIS, or a related field preferred; experience in a private equity-owned portfolio company, regulated industry, or critical infrastructure environment is also preferred
Skills
- Experience with Quickbase and enterprise business applications, along with REST APIs, JavaScript, .NET, and Windows/cloud-based environments
- Familiarity with ERP and financial platforms such as QuickBooks, Sage, NetSuite, Foundation, aACE, Epicor, or Vena, with AI experience using tools such as Claude, Gemini, or Codex preferred