Clinical Database Developer

One CoreDev IT Inc. (CORE); Philippines; On-site; PHP 900,000 - 1,200,000; Full time

Job summary

One CoreDev IT Inc. (CORE) seeks an experienced eSource Developer to build and maintain electronic source data capture forms in the CRIO platform, from study start-up through maintenance, ensuring accurate data collection and audit-trail integrity.

You will translate protocols into CRIO-based instruments, apply validation logic, and coordinate with clinical operations and data management to ensure study readiness. Preference for CRC background or CDISC familiarity.

Qualifications

• Hands-on experience configuring electronic data capture (EDC) forms and edit checks.
• Understanding of translating clinical protocols into study data collection requirements.
• Strong attention to detail with clear written communication.

Responsibilities

• Build eSource forms within the CRIO platform at study start-up, translating protocol into data capture instruments.
• Amend and maintain existing eSource builds through maintenance phases, including protocol amendments.
• Design forms and structuring questions to ensure clear, accurate data entry aligned to protocol requirements.
• Apply edit-check and validation logic to enforce data quality at entry.
• Coordinate with clinical operations, data management, and QA to confirm build accuracy before go-live.
• Maintain version control and documentation to preserve 21 CFR Part 11 audit-trail integrity.

Job description

About the role

The eSource Developer builds and maintains the electronic source data capture forms that Alliance's site staff use to record clinical trial data, from study start-up through the maintenance phase, including amendments to studies already underway. The role requires direct EDC/platform build experience as confirmed by Alliance's eSource team lead. The CRIO platform uses configuration-level logic closer to HTML than to conventional programming, so the harder capability to teach is clinical grounding, not platform syntax. Candidates with adjacent clinical data management backgrounds are accepted but will require supervised platform ramp-up.

Key responsibilities

• Build electronic source (eSource) forms within the CRIO platform at study start-up, translating the protocol and schedule of events into an accurate collection instrument.
• Amend and maintain existing eSource builds through the maintenance phase of a study, including protocol amendments and site-driven change requests.
• Design forms and structure questions within the platform so that data entry at the site level is clear, accurate, and aligned to protocol requirements.
• Apply edit-check and validation logic to enforce data quality at the point of entry.
• Coordinate with clinical operations, data management, and quality assurance to confirm build accuracy before a study goes live.
• Maintain version control and documentation sufficient to preserve 21 CFR Part 11 audit-trail integrity.
• Escalate ambiguous protocol language for interpretation rather than guess at build logic.

About you

• Direct experience with electronic data capture (EDC) systems, including hands-on configuration of forms, edit checks, and database structure.
• Working understanding of how clinical trial protocols translate into study data collection.
• Comfort with configuration-based, HTML-like build logic within a defined platform (CRIO).
• Familiarity with Good Clinical Practice (GCP) and 21 CFR Part 11 as applied to electronic source systems, or demonstrated ability to learn these standards quickly.
• Strong attention to detail and clear written communication; build errors carry direct audit and data-quality consequences.
• Fluent, professional English sufficient for coordination with U.S.-based clinical operations.
• Preferred: Direct, hands-on experience with the CRIO platform specifically.
• Preferred: Prior experience as a Clinical Research Coordinator (CRC) with direct site-level protocol execution.
• Preferred: Exposure to a named EDC platform (for example Medidata Rave, Veeva, Oracle Clinical, or OpenClinica).
• Preferred: Familiarity with CDISC data standards as they inform downstream data mapping.