ARK Solutions, Inc.
API Developer
⭐ - Featured Role | Apply direct with Data Freelance Hub
This role is for an API Developer on a contract basis, remote from Dover, DE, with a pay rate of "unknown". Requires 7+ years of experience in Microsoft SQL and RESTful API development, including OpenAPI documentation and Agile methodologies.
🌎 - Country
United States
💱 - Currency
$ USD
-
💰 - Day rate
Unknown
-
🗓️ - Date
January 24, 2026
🕒 - Duration
Unknown
-
🏝️ - Location
Remote
-
📄 - Contract
Unknown
-
🔒 - Security
Unknown
-
📍 - Location detailed
United States
-
🧠 - Skills detailed
#Data Dictionary #SQL (Structured Query Language) #"ETL (Extract #Transform #Load)" #Logging #GraphQL #REST (Representational State Transfer) #Agile #Data Pipeline #Strategy #API (Application Programming Interface) #Monitoring #Documentation #Scrum #Microsoft SQL #Datasets #Scala #GIT #Metadata #Data Management #Security
Role description
Title: API Developer
Location: - Dover, DE 19904 (Remote)
Hire Type: Contract
Project Summary:
The Redding Equity Dashboard will provide a secure, public facing view of key equity indicators across schools, with consistent definitions, suppression rules, and filtering to support transparent reporting and data driven decision making. The API Developer will build and maintain the data services that power the dashboard, ensuring reliable, scalable access to curated datasets and enabling timely updates and future expansion.
Purpose and objectives:
Design and implement secure, documented APIs that deliver aggregated dashboard datasets to the Web Developer.
Implement consistent business rules described in the data considerations, including enrollment scope, exclusion rules, and suppression for counts
Data domains to support:
APIs must support all data domains within department's public reporting database.
Handling known data gaps and inconsistencies:
Provide a data availability endpoint so the UI can communicate limitations by Local Education Agency (LEA) and metric, aligned to the documented missing data lists.
Partner with department staff to ensure all data elements needed are available
API design requirements:
REST or GraphQL, with preference determined by department standards, with OpenAPI documentation required for all endpoints.
Versioning strategy, including backward compatible changes for the Web Developer.
Standard query parameters
Domain, metric, year, as of date.
Geography: city, county, state, district, school
LEA type: traditional public, charter, vo tech, as categorized.
Standard response structure
Metadata: dataset name, as of date, refresh cadence, suppression policy, and calculation notes.
Data payload: categories, counts, percents, suppressed indicators, denominator values where applicable.
Caching headers and server-side caching for common queries.
Security and governance:
Public read only access pattern with protection against abuse:
API gateway and rate limiting.
Logging and monitoring.
No PII exposure. Only aggregated values with suppression.
Align to Department and Data Management Office (DMO) security standards for hosting and operations.
Data pipeline and refresh:
Define extract and transform processes with DMO, including data validations needed for:
Verified address for City of Wilmington.
LEA code mappings for attendance and tardy codes.
Refresh cadence:
Support snapshot-based refresh were stated in the document that data will not be continuously updated.
Provide clear run logs and publish last refresh timestamps.
Automated tests for calculations and suppression rules.
Deliverables:
API implementation deployed to the agreed environment.
OpenAPI specification and developer portal documentation.
Data dictionary and metric definition catalog aligned to UI needs.
Data availability and gap reporting endpoints aligned to the documented considerations.
Operational runbook for refresh, monitoring, incident response, and onboarding new metrics.
Acceptance criteria:
API responses match documented business rules and suppression.
Performance supports dashboard use with reasonable response times under load.
Security controls implemented and validated.
Documentation enables the Web Developer to implement the UI without additional reverse engineering.
DMO review and sign off on governance, definitions, and operational readiness.
Required Skills:
At minimum 7 years' experience, Microsoft SQL, RESTful
API development: JASON payloads, OpenAPI and Git documentation
Experience with Agile/Scrum Methodologies
Title: API Developer
Location: - Dover, DE 19904 (Remote)
Hire Type: Contract
Project Summary:
The Redding Equity Dashboard will provide a secure, public facing view of key equity indicators across schools, with consistent definitions, suppression rules, and filtering to support transparent reporting and data driven decision making. The API Developer will build and maintain the data services that power the dashboard, ensuring reliable, scalable access to curated datasets and enabling timely updates and future expansion.
Purpose and objectives:
Design and implement secure, documented APIs that deliver aggregated dashboard datasets to the Web Developer.
Implement consistent business rules described in the data considerations, including enrollment scope, exclusion rules, and suppression for counts
Data domains to support:
APIs must support all data domains within department's public reporting database.
Handling known data gaps and inconsistencies:
Provide a data availability endpoint so the UI can communicate limitations by Local Education Agency (LEA) and metric, aligned to the documented missing data lists.
Partner with department staff to ensure all data elements needed are available
API design requirements:
REST or GraphQL, with preference determined by department standards, with OpenAPI documentation required for all endpoints.
Versioning strategy, including backward compatible changes for the Web Developer.
Standard query parameters
Domain, metric, year, as of date.
Geography: city, county, state, district, school
LEA type: traditional public, charter, vo tech, as categorized.
Standard response structure
Metadata: dataset name, as of date, refresh cadence, suppression policy, and calculation notes.
Data payload: categories, counts, percents, suppressed indicators, denominator values where applicable.
Caching headers and server-side caching for common queries.
Security and governance:
Public read only access pattern with protection against abuse:
API gateway and rate limiting.
Logging and monitoring.
No PII exposure. Only aggregated values with suppression.
Align to Department and Data Management Office (DMO) security standards for hosting and operations.
Data pipeline and refresh:
Define extract and transform processes with DMO, including data validations needed for:
Verified address for City of Wilmington.
LEA code mappings for attendance and tardy codes.
Refresh cadence:
Support snapshot-based refresh were stated in the document that data will not be continuously updated.
Provide clear run logs and publish last refresh timestamps.
Automated tests for calculations and suppression rules.
Deliverables:
API implementation deployed to the agreed environment.
OpenAPI specification and developer portal documentation.
Data dictionary and metric definition catalog aligned to UI needs.
Data availability and gap reporting endpoints aligned to the documented considerations.
Operational runbook for refresh, monitoring, incident response, and onboarding new metrics.
Acceptance criteria:
API responses match documented business rules and suppression.
Performance supports dashboard use with reasonable response times under load.
Security controls implemented and validated.
Documentation enables the Web Developer to implement the UI without additional reverse engineering.
DMO review and sign off on governance, definitions, and operational readiness.
Required Skills:
At minimum 7 years' experience, Microsoft SQL, RESTful
API development: JASON payloads, OpenAPI and Git documentation
Experience with Agile/Scrum Methodologies
