Oracle Data migration - Public Safety
Snowrelic Inc · United States · 3 wk ago
RemoteRemoteInformation TechnologyFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. The posting includes: job title line, then description: "Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration Resources Start - asap Open for C2C, 1099, W2, FTE Visa - USC only Duration 6-12 months with possible extension Location - work is remote Other US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems. Role Requirements ..."
We need to parse content into sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have details: "Start - asap", "Open for C2C, 1099, W2, FTE", "Visa - USC only", "Duration 6-12 months with possible extension", "Location - work is remote", "US Citizenship required - CJIS sensitive position ...". Those could go under About the role or maybe Benefits? Not benefits. Could be under About the role (metadata). Also "Role Requirements" heading present; we can treat that as Requirements section.
We need to extract list items: The bullet list after "Role Requirements" is a series of sentences each starting with a capital letter and ending with period. They are not bullet points but we can treat each as a list item under Requirements.
We also have earlier description: "Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration". That's about the role.
Thus sections:
- About the role: paragraph summarizing role: Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration. Also include start ASAP, contract types, duration, location remote, US citizenship required, CJIS background.
- Responsibilities: maybe not explicitly listed; but the list after Role Requirements includes responsibilities like design, configure, test, deploy integrations, coordinate, create artifacts, support go-lives, utilize AI tools, identify patterns. Those could be responsibilities. However the heading "Role Requirements" suggests those are requirements. But we can split: maybe Requirements = experience, qualifications; Responsibilities = duties. The list includes both. We need to decide.
Given instruction: Use sections only when posting has real, specific content for it. We have content for Requirements (experience, skills). We have content for Responsibilities (design, configure, test, deploy integrations, coordinate, create artifacts, support go-lives, utilize AI, identify patterns). We have content for Skills (Java, JavaScript, Python, REST/SOAP APIs, GraphQL, file-based interfaces, databases, JSON/XML/CSV, iPaaS OIC). Also maybe Qualifications (10+ years development experience, etc). But we can combine.
We need to avoid thin sections. Perhaps we can have:
- About the role (summary)
- Responsibilities (list of duties)
- Requirements (list of experience/qualifications)
- Skills (list of technical skills)
We have no explicit Benefits, Pay, Schedule content, so omit those.
Now we must preserve all substantive information; do not invent or summarize away detail. Must not omit any detail. So we need to include all details from the posting.
Let's extract details:
From first line: "Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration"
Interpretation: 8+ years? Actually "8+ Public Safety data conversions/migrations". Might be "8+ Public Safety data conversions/migrations". We'll keep as is.
Then "Resources Start - asap Open for C2C, 1099, W2, FTE Visa - USC only Duration 6-12 months with possible extension Location - work is remote Other US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems."
Then "Role Requirements" followed by list:
1. 10+ years of development experience architecting enterprise and application solutions, preferably in public safety software.
2. Working development knowledge of Java, JavaScript, or Python, including object-oriented programming and using code or scripts to support integrations, automation, and data transformation.
3. Experience configuring and troubleshooting REST and SOAP APIs, GraphQL, file-based interfaces, databases, and common data formats such as JSON, XML, and CSV.
4. Review and build from integration discovery documents; documented requirements, data mappings, interfaces, dependencies, assumptions, risks, and acceptance criteria.
5. Design, configure, test, and deploy integrations using an iPaaS platform Oracle Integration Cloud (OIC) and related APIs, files, databases, and messaging capabilities.
6. Translate between customer business needs and technical implementation details; clearly communicate options, trade-offs, timelines, and issue status.
7. Coordinate with Oracle consultants, developers, support team, and integration partners to troubleshoot interface failures, data-quality issues, authentication problems, and connectivity issues.
8. Create and maintain customer-facing implementation artifacts, including solution designs, configuration guides, test plans, runbooks, data mappings, and handoff documentation.
9. Support customers go-lives and early-life stabilization, helping to triage issues and ensure successful adoption of implemented integrations.
10. Utilize AI-enabled tools responsibly to accelerate requirements analysis, documentation, troubleshooting, and knowledge sharing while protecting customer data and following Oracle policies.
11. Identify repeatable implementation patterns and contribute to standards, templates, and reusable integration assets that improve delivery quality and speed.
We need to preserve all that.
Now we need to decide which items go to which section.
We could treat items 1-3 as Requirements/Qualifications/Skills. Items 4-11 as Responsibilities.
But we also have skills like Java, JavaScript, Python, REST/SOAP APIs, GraphQL, file-based interfaces, databases, JSON/XML/CSV, OIC. Those appear in items 2 and 3 and 5.
We could create a Skills section listing those specific technologies.
But we must not invent or summarize away detail; we can list them as bullet points.
We need to ensure we don't lose any detail. If we split, we must still include all details somewhere.
Let's propose sections:
- About the role: paragraph containing the initial description plus start, contract types, duration, location, citizenship, CJIS requirements.
- Responsibilities: list items 4-11 (maybe also item 5? Actually item 5 is design, configure, test, deploy integrations using OIC - that's a responsibility). We'll include items 4-11.
- Requirements: items 1-3 (experience, development knowledge, configuring APIs). Also maybe include "10+ years of development experience architecting enterprise and application solutions, preferably in public safety software." etc.
- Skills: list specific technologies: Java, JavaScript, Python, object-oriented programming, REST APIs, SOAP APIs, GraphQL, file-based interfaces, databases, JSON, XML, CSV, Oracle Integration Cloud (OIC), APIs, files, databases, messaging capabilities. But some of these are already in requirements; we might duplicate. Better to avoid duplication. Perhaps we combine Requirements and Skills into one section called Requirements & Skills. But instruction says prefer few substantive sections over many thin ones. So we could have just two sections: About the role and Responsibilities (which includes requirements). But we need to preserve all details; we can put requirements inside Responsibilities as list items; that's okay.
But we must use headings for sections only when there is real content. We can have About the role and Responsibilities. In Responsibilities we can include both duties and requirements as list items. That would preserve all info.
But we need to ensure we don't miss any detail like "8+ Public Safety data conversions/migrations". That is in About the role.
Let's craft About the role paragraph:
"Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration. Start ASAP. Open for C2C, 1099, W2, FTE. Visa - USC only. Duration 6-12 months with possible extension. Location - work is remote. US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems."
Now Responsibilities/Requirements list: we need to include all items from Role Requirements plus maybe also the earlier bullet about "8+ Public Safety data conversions/migrations"? Already in About.
We'll output
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. The posting includes: job title line, then description: "Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration Resources Start - asap Open for C2C, 1099, W2, FTE Visa - USC only Duration 6-12 months with possible extension Location - work is remote Other US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems. Role Requirements ..."
We need to parse content into sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have details: "Start - asap", "Open for C2C, 1099, W2, FTE", "Visa - USC only", "Duration 6-12 months with possible extension", "Location - work is remote", "US Citizenship required - CJIS sensitive position ...". Those could go under About the role or maybe Benefits? Not benefits. Could be under About the role (metadata). Also "Role Requirements" heading present; we can treat that as Requirements section.
We need to extract list items: The bullet list after "Role Requirements" is a series of sentences each starting with a capital letter and ending with period. They are not bullet points but we can treat each as a list item under Requirements.
We also have earlier description: "Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration". That's about the role.
Thus sections:
- About the role: paragraph summarizing role: Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration. Also include start ASAP, contract types, duration, location remote, US citizenship required, CJIS background.
- Responsibilities: maybe not explicitly listed; but the list after Role Requirements includes responsibilities like design, configure, test, deploy integrations, coordinate, create artifacts, support go-lives, utilize AI tools, identify patterns. Those could be responsibilities. However the heading "Role Requirements" suggests those are requirements. But we can split: maybe Requirements = experience, qualifications; Responsibilities = duties. The list includes both. We need to decide.
Given instruction: Use sections only when posting has real, specific content for it. We have content for Requirements (experience, skills). We have content for Responsibilities (design, configure, test, deploy integrations, coordinate, create artifacts, support go-lives, utilize AI, identify patterns). We have content for Skills (Java, JavaScript, Python, REST/SOAP APIs, GraphQL, file-based interfaces, databases, JSON/XML/CSV, iPaaS OIC). Also maybe Qualifications (10+ years development experience, etc). But we can combine.
We need to avoid thin sections. Perhaps we can have:
- About the role (summary)
- Responsibilities (list of duties)
- Requirements (list of experience/qualifications)
- Skills (list of technical skills)
We have no explicit Benefits, Pay, Schedule content, so omit those.
Now we must preserve all substantive information; do not invent or summarize away detail. Must not omit any detail. So we need to include all details from the posting.
Let's extract details:
From first line: "Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration"
Interpretation: 8+ years? Actually "8+ Public Safety data conversions/migrations". Might be "8+ Public Safety data conversions/migrations". We'll keep as is.
Then "Resources Start - asap Open for C2C, 1099, W2, FTE Visa - USC only Duration 6-12 months with possible extension Location - work is remote Other US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems."
Then "Role Requirements" followed by list:
1. 10+ years of development experience architecting enterprise and application solutions, preferably in public safety software.
2. Working development knowledge of Java, JavaScript, or Python, including object-oriented programming and using code or scripts to support integrations, automation, and data transformation.
3. Experience configuring and troubleshooting REST and SOAP APIs, GraphQL, file-based interfaces, databases, and common data formats such as JSON, XML, and CSV.
4. Review and build from integration discovery documents; documented requirements, data mappings, interfaces, dependencies, assumptions, risks, and acceptance criteria.
5. Design, configure, test, and deploy integrations using an iPaaS platform Oracle Integration Cloud (OIC) and related APIs, files, databases, and messaging capabilities.
6. Translate between customer business needs and technical implementation details; clearly communicate options, trade-offs, timelines, and issue status.
7. Coordinate with Oracle consultants, developers, support team, and integration partners to troubleshoot interface failures, data-quality issues, authentication problems, and connectivity issues.
8. Create and maintain customer-facing implementation artifacts, including solution designs, configuration guides, test plans, runbooks, data mappings, and handoff documentation.
9. Support customers go-lives and early-life stabilization, helping to triage issues and ensure successful adoption of implemented integrations.
10. Utilize AI-enabled tools responsibly to accelerate requirements analysis, documentation, troubleshooting, and knowledge sharing while protecting customer data and following Oracle policies.
11. Identify repeatable implementation patterns and contribute to standards, templates, and reusable integration assets that improve delivery quality and speed.
We need to preserve all that.
Now we need to decide which items go to which section.
We could treat items 1-3 as Requirements/Qualifications/Skills. Items 4-11 as Responsibilities.
But we also have skills like Java, JavaScript, Python, REST/SOAP APIs, GraphQL, file-based interfaces, databases, JSON/XML/CSV, OIC. Those appear in items 2 and 3 and 5.
We could create a Skills section listing those specific technologies.
But we must not invent or summarize away detail; we can list them as bullet points.
We need to ensure we don't lose any detail. If we split, we must still include all details somewhere.
Let's propose sections:
- About the role: paragraph containing the initial description plus start, contract types, duration, location, citizenship, CJIS requirements.
- Responsibilities: list items 4-11 (maybe also item 5? Actually item 5 is design, configure, test, deploy integrations using OIC - that's a responsibility). We'll include items 4-11.
- Requirements: items 1-3 (experience, development knowledge, configuring APIs). Also maybe include "10+ years of development experience architecting enterprise and application solutions, preferably in public safety software." etc.
- Skills: list specific technologies: Java, JavaScript, Python, object-oriented programming, REST APIs, SOAP APIs, GraphQL, file-based interfaces, databases, JSON, XML, CSV, Oracle Integration Cloud (OIC), APIs, files, databases, messaging capabilities. But some of these are already in requirements; we might duplicate. Better to avoid duplication. Perhaps we combine Requirements and Skills into one section called Requirements & Skills. But instruction says prefer few substantive sections over many thin ones. So we could have just two sections: About the role and Responsibilities (which includes requirements). But we need to preserve all details; we can put requirements inside Responsibilities as list items; that's okay.
But we must use headings for sections only when there is real content. We can have About the role and Responsibilities. In Responsibilities we can include both duties and requirements as list items. That would preserve all info.
But we need to ensure we don't miss any detail like "8+ Public Safety data conversions/migrations". That is in About the role.
Let's craft About the role paragraph:
"Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration. Start ASAP. Open for C2C, 1099, W2, FTE. Visa - USC only. Duration 6-12 months with possible extension. Location - work is remote. US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems."
Now Responsibilities/Requirements list: we need to include all items from Role Requirements plus maybe also the earlier bullet about "8+ Public Safety data conversions/migrations"? Already in About.
We'll output - for each item.
We must not repeat job title as heading.
We must not include boilerplate.
Thus final HTML:
About the role
Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration. Start ASAP. Open for C2C, 1099, W2, FTE. Visa - USC only. Duration 6-12 months with possible extension. Location - work is remote. US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems.
Responsibilities
- 10+ years of development experience architecting enterprise and application solutions, preferably in public safety software.
- Working development knowledge of Java, JavaScript, or Python, including object-oriented programming and using code or scripts to support integrations, automation, and data transformation.
- Experience configuring and troubleshooting REST and SOAP APIs, GraphQL, file-based interfaces, databases, and common data formats such as JSON, XML, and CSV.
- Review and build from integration discovery documents; documented requirements, data mappings, interfaces, dependencies, assumptions, risks, and acceptance criteria.
- Design, configure, test, and deploy integrations using an iPaaS platform Oracle Integration Cloud (OIC) and related APIs, files, databases, and messaging capabilities.
- Translate between customer business needs and technical implementation details; clearly communicate options, trade-offs, timelines, and issue status.
- Coordinate with Oracle consultants, developers, support team, and integration partners to troubleshoot interface failures, data-quality issues, authentication problems, and connectivity issues.
- Create and maintain customer-facing implementation artifacts, including solution designs, configuration guides, test plans, runbooks, data mappings, and handoff documentation.
- Support customers go-lives and early-life stabilization, helping to triage issues and ensure successful adoption of implemented integrations.
- Utilize AI-enabled tools responsibly to accelerate requirements analysis, documentation, troubleshooting, and knowledge sharing while protecting customer data and following Oracle policies.
- Identify repeatable implementation patterns and contribute to standards, templates, and reusable integration assets that improve delivery quality and speed.
That's all.
Check for any missing detail: The phrase "Resources Start - asap" we captured as "Start ASAP." Good.
"Open for C2C, 1099, W2, FTE Visa
About the role
Oracle Data migration - Public Safety 8+ Public Safety data conversions/migrations, system integrations, reports and other system configuration. Start ASAP. Open for C2C, 1099, W2, FTE. Visa - USC only. Duration 6-12 months with possible extension. Location - work is remote. US Citizenship required - This is a Criminal Justice Information Systems (CJIS) sensitive position and will require a fingerprint-based background investigation, conducted by customer criminal justice agencies. Contractors for this position will be required to obtain and maintain CJIS access approval by Federal, state, and/or local agencies for Criminal Justice information, related law enforcement databases, and communications systems.
Responsibilities
- 10+ years of development experience architecting enterprise and application solutions, preferably in public safety software.
- Working development knowledge of Java, JavaScript, or Python, including object-oriented programming and using code or scripts to support integrations, automation, and data transformation.
- Experience configuring and troubleshooting REST and SOAP APIs, GraphQL, file-based interfaces, databases, and common data formats such as JSON, XML, and CSV.
- Review and build from integration discovery documents; documented requirements, data mappings, interfaces, dependencies, assumptions, risks, and acceptance criteria.
- Design, configure, test, and deploy integrations using an iPaaS platform Oracle Integration Cloud (OIC) and related APIs, files, databases, and messaging capabilities.
- Translate between customer business needs and technical implementation details; clearly communicate options, trade-offs, timelines, and issue status.
- Coordinate with Oracle consultants, developers, support team, and integration partners to troubleshoot interface failures, data-quality issues, authentication problems, and connectivity issues.
- Create and maintain customer-facing implementation artifacts, including solution designs, configuration guides, test plans, runbooks, data mappings, and handoff documentation.
- Support customers go-lives and early-life stabilization, helping to triage issues and ensure successful adoption of implemented integrations.
- Utilize AI-enabled tools responsibly to accelerate requirements analysis, documentation, troubleshooting, and knowledge sharing while protecting customer data and following Oracle policies.
- Identify repeatable implementation patterns and contribute to standards, templates, and reusable integration assets that improve delivery quality and speed.