PHP/MySQL developer
- for any list of duties/requirements/benefits. Use
for prose. We must avoid filler like "commensurate with experience". Not present. We need to ensure we don't create Pay/Schedule sections. We'll structure:
About the role
... position summary ...
Responsibilities
- ... each responsibility ...
Requirements
Bachelor’s Degree
Qualifications
- ... top required skills ...
Skills
- ... technical skills ... for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
- .
Requirements: Bachelor’s Degree.
Qualifications: Top Required Skills list: "Five or more years of experience with PHP Microservices development with configuration and troubleshooting." etc. Let's extract exactly:
Top Required Skills
- Five or more years of experience with PHP Microservices development with configuration and troubleshooting.
- Five or more years of experience with MySQL database management.
- Five or more years of experience with PHP configuration and troubleshooting.
- Five or more years of experience with Python scripting for loading and query data.
- Five or more years of experience designing, developing, implementing and troubleshooting RESTful APIs.
- Five or more years of experience supporting enterprise web applications hosted on AWS.
We'll list those.
Preferred skills also listed under "Top Preferred Skills": same as required? Actually they repeat same list then add more. Let's capture the "Top Preferred Skills" block:
Experience supporting REDCap in a public health, healthcare, higher education, or research environment.
Experience with REDCap API integration and External Modules implementation.
Experience with Twilio / SMS survey gateway.
Then "Other Highly Desired Qualifications" repeats the required list again plus many more items:
- Five or more years of experience with PHP Microservices development with configuration and troubleshooting.
- Five or more years of experience with MySQL database management.
- Five or more years of experience with PHP configuration and troubleshooting.
- Five or more years of experience with Python scripting for loading and query data.
- Five or more years of experience designing, developing, implementing and troubleshooting RESTful APIs.
- Five or more years of experience supporting enterprise web applications hosted on AWS.
- Experience using AWS Cloud services (EC2, S3, VPC, security groups).
- Experience with Apache or Nginx web servers.
- Experience with OIDC/SAML integration.
- Experience with SSL/TLS certificate management and HIPAA compliance.
- Experience managing application security, authentication, and user access.
- Experience coordinating software upgrades and vendor support.
- Experience with End-user support, documentation and training.
- Strong analytical, troubleshooting, and problem-solving skills.
- Excellent written and verbal communication skills.
- Experience supporting REDCap in a public health, healthcare, higher education, or research environment.
- Experience with REDCap API integration and External Modules implementation.
- Experience with Active Directory, LDAP, or Single Sign-On (SSO).
- Experience using ServiceNow or another enterprise ticketing system.
- Experience with DevOps or similar tools.
- Experience supporting API integrations with enterprise applications.
- Experience with Python scripting for automation.
- Experience with SSIS/ SQL Server agent.
- Experience with Twilio / SMS survey gateway experience.
- AWS Cloud Practitioner, SysOps Administrator, or Solutions Architect certification.
- Knowledge of HIPAA, security, and data privacy best practices.
We need to preserve all substantive info; we can combine these into Qualifications section, maybe separate required and preferred with headings inside? But we cannot add extra headings beyond h3? We could use
to introduce sub-lists. Simplify: Qualifications section will contain two
- lists: one for Required Skills, one for Preferred/Other Highly Desired Qualifications. We'll preface each with a
- .
Benefits: list from "Benefits" block:
- At IntelliBee Long-Term Stability: Join us on a multi-year opportunities with room to grow.
- Comprehensive Health Coverage: Access quality healthcare benefits to keep you and your family well.
- Future Planning: Enroll in our 401(k) program and invest in your financial security.
- GC Assistance: We support immediate Green Card processing, if required.
We'll put as
- . Now ensure we don't include boilerplate like "Date Posted:" etc. Now produce HTML fragment. Check for any repeated content: we have required skills list also appears in Other Highly Desired Qualifications; we might be duplicating. But we must preserve all substantive info; duplication is okay if it's in source. However we might want to avoid duplication but instruction says preserve ALL substantive information; not necessarily avoid duplication. It's okay to repeat if it's in source. But we could combine to avoid duplication but risk losing some nuance. Safer to include as presented: we can have Required Skills list, then Preferred Skills list (the short three), then Other Highly Desired Qualifications list (which includes the required again plus many more). That would duplicate required skills twice. Might be
describing. Skills section: Technical Skills list: Technical Skills - PHP Microservices Development - MySQL database management - PHP configuration and troubleshooting - RESTful APIs - Amazon Web Services (AWS) - Cloud services (EC2, S3, VPC, security groups) - Apache/Nginx web servers - OIDC/SAML integration - Writing, testing, debugging PHP - Python scripting - HTML, CSS, JS front-end coding - REDCap API integration - REDCap External Modules implementation - REDCap administration (user/project management, reports and surveys) - SSL/TLS certificate management and HIPAA compliance - Identity and Access Management - Application Monitoring - Backup and Disaster Recovery - Vendor Coordination - Technical Documentation - Analytical Problem-solving and Troubleshooting - Adept Learner We'll list as
- .
Benefits: list from "Benefits" block:
- At IntelliBee Long-Term Stability: Join us on a multi-year opportunities with room to grow.
- Comprehensive Health Coverage: Access quality healthcare benefits to keep you and your family well.
- Future Planning: Enroll in our 401(k) program and invest in your financial security.
- GC Assistance: We support immediate Green Card processing, if required.
We'll put as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot add other headings, but better to stick to those. We could put required skills under Qualifications, preferred skills also under Qualifications (maybe separate sub-lists). Or we could have two sections: Qualifications (required) and Skills (preferred + technical). But we need to preserve all info. Let's decide: - About the role: position summary paragraph. - Responsibilities: list of responsibilities. - Requirements: Bachelor’s Degree. - Qualifications: Top Required Skills (list). - Skills: Technical Skills list (maybe also include Preferred Skills? Could add a note that preferred skills are also listed). But we might lose preferred skills. Could include Preferred Skills under Qualifications as well, but then we would have two lists under same heading; we can separate with a
note. Better: Qualifications: Top Required Skills (list). Then another heading? Not allowed? Could use Skills for Preferred Skills + Technical Skills combined. But we need to keep technical skills separate maybe. Alternatively, we could have Qualifications: Top Required Skills, and Skills: Technical Skills, and we could add a note that Preferred Skills are also listed under Qualifications? Might be okay. But we must preserve all substantive info; if we omit Preferred Skills, that's lost. So we need to include them somewhere. We could include Preferred Skills under Qualifications as a second list with a preceding
stating "Preferred skills include:" then list. Thus Qualifications section will contain both required and preferred skills. Skills section will contain Technical Skills list. Benefits section: list of benefits. Now we need to extract the exact text. Position Summary: "The State of Michigan is seeking an experienced PHP/MySQL developer with knowledge and skills in PHP Microservices development, MySQL database management and cloud infrastructure and applications management to provide operational and technical support for an existing REDCap application hosted on Amazon Web Services (AWS). The resource will be responsible for the maintenance, troubleshooting, version upgrades, user support, vendor coordination, and integration of the REDCap application to ensure a secure, reliable, and highly available platform. This position requires close collaboration with business stakeholders, DTMB infrastructure teams, AWS administrators, security teams, and Vanderbilt University REDCap support." We'll put that in
. Responsibilities: list each bullet from "Key Responsibilities" block. Let's extract them: - Support the REDCap application hosted in AWS with user/project management, reports and surveys. - Coordinate and implement REDCap software updates, patches, and version upgrades in collaboration with Vanderbilt University. - Install, configure, and support REDCap External Modules using PHP on Linux/AWS environments including Apache/Nginx. - Develop, maintain, and troubleshoot REDCap API integrations with internal and external applications and automate data flows. - Serve as the primary technical contact for REDCap-related issues. - Implement and maintain OIDC integration, Active Directory/LDAP, and SSL/TLS certificates. - Prepare the scripts to load data to Redcap database using Data import tool or using Redcap APIs. - Coordinate with AWS infrastructure teams regarding servers, storage, networking, SSL/TLS certificates, security groups, backups, and system monitoring. - Provide day-to-day operational support, including troubleshooting application, infrastructure, and user issues, documentation and training. - Monitor application performance and proactively identify and resolve issues. - Support disaster recovery, backup validation, and system recovery activities. - Develop automation scripts for reporting, and data validation (PHP and SQL). - Maintain MySQL databases, perform queries and validation. - Maintain technical documentation, standard operating procedures, and configuration documentation. - Coordinate issue resolution with vendors, developers, database administrators, security teams, and business users. - Participate in change management, release management, and production support activities. - Ensure compliance with State security standards, applicable data privacy requirements, HIPAA compliance, and proper audit logging. - Create and maintain Azure DevOps work items for REDCap enhancements, defects, upgrades, API development, and maintenance activities. Maintain priorities, assignments, status, dependencies, and target completion dates. Monitor dashboards and reports to identify aging or overdue work. Provide status reporting to IT leadership and Public Health program stakeholders. That's many items; we need to keep them as