Application Developer (hybrid)

Location: remote; may have occasional on-site meetings in Reno; you would be responsible for costs if you are not local.

Pay: $100/hr (1099 contract only; we cannot do c2c)

Duration: mid-July 2026 through November 2026

Project Description:

Project 1: Shared Car Fleet Reservation System

Objective & Scope
Design and implement a secure, mobile-friendly reservation platform with GPS trip tracking, photo-based pickup/return, Azure AD authentication, audit logging, cost-allocation reporting, and admin tools for fleet, depots, and availability.

Deliverables

• Requirements, architecture, ERD, API specs, UX wireframes.
• React Native mobile app (background GPS), web app for reservations/admin, ASP.NET Core APIs, Azure SQL schema, reporting dashboards, CSV export.
• Infrastructure (Azure Gov), CI/CD, monitoring, documentation, and 30‑day stabilization.

Key Non-Functional Requirements
FedRAMP-aligned security, WCAG 2.1 AA accessibility, performance targets (API p95 <300 ms), auditability of GPS sessions and budget code changes.

Timeline
3-4 months from discovery through launch.

Assumptions
Azure Gov readiness, approved mapping provider, privacy/consent policy for tracking.

Project 2: EAM Version 2.0 Enhancements

Objective & Scope
Enhance the Employee Account Management (EAM) module with sortable/filterable grid (default by Commit Date), richer Submitted Actions reporting, transfer algorithm updates to preserve Teams lines/numbers, phone type capture, automated “Telecom Template” delivery, credential‑recipient redirection, GIN reports, admin master data for Position Titles/Duty Locations, and grid display of full Duty Location address. Include a flag for “Mirror Account Required” when only default AD groups are present.

Deliverables

• UI/UX updates for grid sort/filter and modification highlights.
• Backend logic changes for transfers, reports, and validation rules.
• Mail‑merge generation and automated notifications.
• Admin tools for master data (titles/locations).

Constraints/Notes
Stakeholder comments indicate urgency for username/email uniqueness, requests for workflow documentation, and considerations about AD authoritative sources and an Employee Card lift. These inform prioritization and dependencies.

Estimated LOE
Ranges from Very Low (<1 hr) to Very High (4–6 days) per objective, guiding sprint planning.

Project 3: OCHA Version 3 – Intake & Referrals Automation

Objective & Scope
Extend OCHA with Power Automate forms (passcode gate, purpose‑based branching), file upload notifications/renaming, SharePoint integration, public website form, and services/APIs to parse spreadsheets (Excel/CSV/delimited) and selected Word templates; add Referrals page with “Convert to Intake” and an Existing Record Inbox supporting status updates (Screening/Approval/Denial).

Deliverables

• Power Automate flows, custom forms, SharePoint permissions.
• Parsing/update APIs; doc‑template submethods.
• UI pages for Referrals and Inbox; email notifications.

Dependencies/Questions
Confirm file‑upload capabilities in forms, clarify business stages where providers submit files to drive database updates and Inbox status transitions.

Pay: $100.00 per hour

Education:

• Bachelor's (Preferred)

Experience:

• Application development: 7 years (Required)

Language:

• English (Required)

Location:

• Reno, NV 89521 (Preferred)

Work Location: Hybrid remote in Reno, NV 89521