Contractor Support to Digital Workflow Prototyping & Citizen Development

Job Description

Job Description:\n\nContractor Support to Digital Workflow Prototyping & Citizen Development\nDEFTEC delivers mission-critical solutions through skillfully delivered services and innovative products. We are inspired by our clients' critical missions and driven to provide the most effective solutions to execute their missions, operational challenges, and requirements. Our dedicated, experienced, and talented employees work closely with our clients to ensure the delivery of exceptional services and products.\nPosition Overview:\nThe Contractor Support to Digital Workflow Prototyping & Citizen Development supports CAPDEV organizations through hands-on rapid development of digital workflow proofs of concept, prototypes, and operational pilots, using approved non-Microsoft low-code, no-code, and comparable rapid-development platforms to transform manual, spreadsheet-intensive, email-driven, or otherwise fragmented processes into streamlined digital solutions. This role works directly with process owners, operational users, and stakeholders to document existing workflows and translate operational needs into minimum viable prototypes, configuring data capture, business rules, routing, approvals, and integrations with authorized data sources through APIs, databases, or web services, while applying proportionate lifecycle practices such as version control, testing, and documentation appropriate to rapid prototyping. The incumbent conducts user testing and operational pilots, iteratively improving solutions based on stakeholder feedback and operational findings, while identifying security, architecture, and sustainment constraints early to inform transition planning; qualifying candidates bring a technical or related degree (or equivalent experience), recent hands-on delivery of user-adopted digital solutions, proficiency with multiple non-Microsoft low-code/no-code platforms, and demonstrated experience across business process discovery, data integration, technical scripting, and lifecycle discipline. Finally, this individual prepares comprehensive transition packages-including requirements, data structures, business rules, and known limitations-and collaborates with enterprise developers, DevSecOps teams, and platform owners to support scaling successful prototypes into enduring implementations, while presenting findings and recommendations to CAPDEV leaders to inform decisions on continuation, revision, or retirement of piloted solutions.\nJob Responsibilities:\n\n Support CAPDEV organizations through hands-on rapid development of digital workflow proofs of concept, prototypes, and operational pilots using approved non-Microsoft low-code, no-code, configurable-application, workflow, lightweight development, or comparable platforms and tools.\n Work directly with process owners, operational users, analysts, managers, and information stakeholders to understand existing work and information flows, decisions, handoffs, data requirements, pain points, and opportunities for digital transformation.\n Document current and desired workflows at sufficient detail to identify user roles, workflow states, decision points, information exchanges, business rules, data requirements, and minimum functionality needed to test a redesigned process.\n Translate operational needs into minimum viable prototype or pilot requirements that can be rapidly developed, demonstrated, tested, and iterated with users.\n Design, configure, develop, test, and improve digital applications and workflows that replace or materially reduce manual, spreadsheet-intensive, email-driven, form-based, document-centric, or otherwise fragmented CAPDEV processes.\n Configure structured data capture, user roles, workflow states, business rules, validations, routing, approvals, notifications, status tracking, role-based views, and other functionality required to operationally test redesigned workflows.\n Integrate prototype and pilot solutions with approved data sources or services using APls, databases, web services, webhooks, structured file exchange, or other authorized mechanisms appropriate to the technical environment.\n Develop lightweight scripts, components, application logic, or integrations when configurable or low-code functionality alone is insufficient to test the operational requirement.\n Use approved Al-assisted development capabilities, where available and appropriate, to accelerate prototyping, code development, configuration, testing, documentation, or iterative solution improvement while maintaining appropriate human review and technical accountability.\n Conduct user testing and operational pilots with representative CAPDEV users and iteratively improve solutions based on observed use, stakeholder feedback, technical findings, and changes to the operational requirement.\n Establish appropriate baselines and assess prototype or pilot effects on factors such as cycle time, manual processing effort, data completeness, information availability, workflow visibility, traceability, usability, and user adoption.\n Identify security, data-management, information-management, architecture, integration, licensing, hosting, scalability, and sustainment constraints sufficiently early to inform whether and how a prototype should progress toward enduring implementation.\n Design prototypes to use authoritative information sources where practical and avoid unnecessary creation of duplicate, unsupported, or orphaned data stores.\n Apply proportionate development and lifecycle practices appropriate to rapid prototyping, including version or configuration control, documentation of business rules and dependencies, testing, management of development artifacts, and separation of prototype and operational environments where supported.\n Document process requirements, workflow logic, data structures, integrations, user roles, business rules, configuration, code or scripts, assumptions, known limitations, test findings, and operational lessons sufficiently to support reuse, assessment, and transition.\n Prepare transition packages for successful prototypes and pilots, including requirements, process design, user stories or equivalent functional descriptions, data structures, integrations, business rules, test results, known limitations, technical dependencies, and recommendations for enduring implementation.\n Collaborate with enterprise developers, DevSecOps teams, platform owners, system integrators, data teams, cybersecurity personnel, and other scaling organizations to support transition from CAPDEV prototype or pilot to enduring implementation.\n Maintain visibility of active prototypes and pilots, including purpose, users, status, dependencies, risks, technical debt, evidence of operational value, and recommended disposition such as continue testing, revising, transition for scaling, sustain locally, or retire.\n Present prototype and pilot findings, user feedback, technical constraints, trade-offs, implementation risks, and scaling recommendations to CAPDEV leaders and stakeholders.\n Perform additional tasks as required by the COTR that are directly related to this labor category and do not constitute a materially different labor requirement.\n\nRequired Qualifications:\n\n Active NATO Secret Security Clearance\n Education or Relevant Professional Experience: A University/Bachelor's degree in Computer Science, Information Systems, Software Engineering, Engineering, Human-Centered Design, Business Process Management, Business Information Technology, or a closely related field; or a minimum of five years of directly relevant professional experience in lieu of the degree.\n \n Directly relevant professional experience shall include work in at least two of the following areas: low-code/no-code or configurable-application development; workflow automation; software or web application development; business-process digitization; rapid prototyping or minimum-viable-product development.\n Either the degree or experience-in-lieu route fully satisfies this qualification.\n \n Recent End-to-End Hands-On Digital Solution Delivery: Demonstrated recent experience personally developing digital applications, workflows, prototypes, or pilots from identification of a user or business-process requirement through configuration or development, testing, user feedback, and operational use or pilot activity.\n \n The candidate shall demonstrate at least twelve calendar months within the last twenty-four months during which hands-on digital application, workflow, or prototype development constituted a substantial and recurring portion of the candidate's assigned duties, and at least one personally developed digital solution used by an identified user group as part of an active business process or operational pilot within the last eighteen months.\n The candidate shall identify the month and year of qualifying experience, approximate proportion of assigned duties devoted to hands-on development, business process addressed, personal technical contribution, technologies or platforms used, and user group.\n Experience limited to directing, supervising, managing, advising, governing, architecting, technical leadership, product ownership, program management, coordinating, or overseeing development performed by others does not satisfy this requirement. Multiple components developed for the same user group to address the same business-process requirement shall be considered one example. Qualifying experience may overlap in time with experience used to satisfy other Essential Qualifications where the work demonstrates the required competencies.\n \n Non-Microsoft Low-Code, No-Code, or Configurable Application Development: Minimum of two years within the last five years, including hands-on development within the last twenty-four months, personally designing, configuring, building, testing, and deploying applications or workflows using non-Microsoft low-code, no-code, configurable-application, workflow, or comparable rapid-development platforms.\n \n The candidate shall demonstrate at least two personally developed applications or workflow solutions, including at least one used by an identified user group as part of an active business process or operational pilot within the last twenty-four months and a second qualifying example within the last three years.\n Across the candidate's qualifying examples, the candidate shall demonstrate hands-on development using at least two distinct non-Microsoft rapid-development platforms, frameworks, or application-development technologies. The candidate is not required to demonstrate equal depth or duration of experience in each.\n At least one qualifying solution shall demonstrate three or more of the following characteristics, with at least one characteristic drawn from items 3, 5, or 7:\n \n\n multiple workflow states, screens, forms, or user roles;\n conditional or role-based behaviour;\n structured data model or relationships between data entities;\n custom validation, business rules, or workflow logic;\n integration with more than one data source, service, or application;\n automated routing, approvals, notifications, or task coordination; or\n reusable components, scripts, extensions, or comparable application logic, with the candidate identifying the component, script, or extension and describing what it performed.\n \n For each example, the candidate shall identify the platform or technology used, business process addressed, personal technical contribution, qualifying characteristics, user group, and resulting operational or pilot use, and shall briefly describe how the claimed characteristics were personally implemented.\n Applications or workflows configured or developed primarily by others, basic forms or templates, or demonstration-only builds do not satisfy this requirement.\n Qualifying experience may overlap in time with experience used to satisfy other Essential Qualifications where the work demonstrates the required competencies.\n \n\n Rapid Prototyping and Minimum Viable Solution Delivery: Demonstrated hands-on experience within the last five years, including at least one example within the last twenty-four months, rapidly translating an identified operational or business-process requirement into a testable digital proof of concept, prototype, minimum viable solution, or pilot.\n \n The candidate shall identify at least two examples in which they personally contributed to requirements discovery and personally developed the resulting prototype or pilot.\n At least one qualifying example shall have progressed from initial requirement or process discovery to a testable solution available to representative users within ninety calendar days or less.\n Across the two qualifying examples, at least one shall demonstrate at least two of the qualifying solution characteristics identified under Essential Qualification 3, including at least one characteristic from items 3, 5, or 7 of that qualification. The example demonstrating the required solution characteristics may be the same example that satisfies the ninety-day requirement or a different qualifying example.\n For each example, the candidate shall identify the initial requirement, timeframe from discovery to testable solution, personal contribution, platform or technologies used, users involved in testing, qualifying solution characteristics where applicable, and resulting disposition or next step.\n Experience involving only development against fully predetermined specifications without rapid iteration with users does not satisfy this requirement.\n Qualifying experience may overlap in time with experience used to satisfy other Essential Qualifications where the work demonstrates the required competencies.\n \n Business Process Discovery and Workflow Redesign: Minimum of two years within the last five years, including at least one qualifying example within the last three years, working directly with operational users, process owners, managers, or information stakeholders to understand existing business processes and design digitally enabled future workflows.\n \n The candidate shall demonstrate at least two examples in which they personally analyzed an existing manual, spreadsheet-based, email-driven, document-centric, or otherwise fragmented process and identified user roles, process steps, handoffs, decisions, information requirements, pain points, and opportunities for redesign prior to development.\n For each example, the candidate shall identify the user or process-owner group, existing process or problem, findings from process discovery, proposed workflow changes, and resulting prototype, pilot, or digital solution.\n Experience limited to receiving predetermined requirements without direct engagement with users or process owners does not satisfy this requirement.\n Qualifying experience may overlap in time with experience used to satisfy other Essential Qualifications where the work demonstrates the required competen