Senior Database Developer

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 if posting has real specific content. We need to parse the posting. First, there is introductory paragraph about Skyward values etc. That could be "About the role" or maybe "About the company". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include the description of the role and company values? The posting includes a description of the company and then "This position is contingent on contract award** We need a Senior Database Developer." Then a paragraph describing the role. So we can put that under About the role. Then "What You'll Do" is responsibilities. So we need a Responsibilities section with list items. Then "What we'd like you to have:" is qualifications/requirements. Could be Requirements or Qualifications. We'll decide: maybe Requirements for mandatory, Qualifications for preferred? But we can combine. The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. The posting includes: "What we'd like you to have:" list of items: bachelor's degree + 8+ years experience, serious database chops, strong SQL skills, report development, hands-on experience developing data frameworks, general understanding of AWS, experience building or improving a data governance framework, comfort being the face of a contract, track record of staying cool under deadline, knack for turning data broken into fix, US citizenship and ability to obtain Public Trust security clearance. Then "What Would Blow Us Away": prior experience supporting federal statistical, data, or reporting program; extra tools: Python, Java, SQL, Tableau; AWS certification. These could be Skills or Preferred Qualifications. Then "And Now The Important Part. What We Offer You": list of benefits: medical, dental, vision insurance; 15 days paid leave; 7 days sick leave; 2 days bereavement leave; 11 paid Federal holidays; up to 40 hours for jury duty; 401K with 4% employer contribution; up to 4 weeks paid paternity and maternity leave; company provided laptop; $5,000 per year for professional development; $600 per year for technical supplies and equipment; $2,000 referral bonus; life and disability insurance; HSA and FSA; Legal Shield and ID Shield Voluntary Benefits; Opportunity to work in collaborative team... So that's Benefits. Then salary: "$110,000 - $120,000 a year". Also mention flexible working hours and remote opportunities. That could be Pay and Schedule sections. We need to include Pay section only if posting actually states them. Yes salary is stated. So we include Pay. Schedule: posting mentions flexible working hours and remote opportunities. That's schedule info. So we include Schedule. We must not include boilerplate like EEO, legal, etc. There's some about background investigation, security clearance, AI tools. Those are not boilerplate? They are part of posting but maybe considered legal? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The lines about background investigation, security clearance, AI tools might be considered legal? They are about hiring process. Might be considered boilerplate? The instruction says remove legal boilerplate. The security clearance requirement is substantive (US citizenship and ability to obtain Public Trust security clearance) - that is a requirement, not boilerplate. The background investigation contingency is also a condition of offer; could be considered legal? Might be considered boilerplate but it's a condition of employment. However it's not duplicated lines. I'd keep it as part of Requirements maybe. The AI tools paragraph is about hiring process; could be considered boilerplate? It's not EEO but still about process. Might be considered boilerplate? I'd remove it as it's not substantive about the job. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools paragraph is about hiring process, maybe considered application instructions? It's not exactly instructions to apply but about process. Safer to remove. Also the line "Offers of employment with Skyward are contingent upon acceptable results of a background investigation." That's also about hiring process; could be considered boilerplate? Might be considered legal. I'd remove it as it's not about job duties/requirements. However the security clearance requirement is a requirement; we keep that. Thus we will keep: US citizenship and ability to obtain Public Trust security clearance as a requirement. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

About the role

...

Then

Responsibilities

• ... each duty

Then

Requirements

• ... each requirement

Then

Preferred Qualifications

maybe "Skills" or "Qualifications". We have "What Would Blow Us Away" which are nice-to-haves. Could be Skills. We'll use

Skills

for those. Then

Benefits

• ... benefits

Then

Pay

$110,000 - $120,000 a year

Then

Schedule

Flexible working hours with remote work opportunities.

We need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to extract the content precisely. About the role: combine the introductory paragraph about Skyward values and the description of the role. Let's capture: "We are Skyward. That is, a love for people, for improvement, for human advancement through information technology. We are a people-centered business with a desire to serve others. We are diverse and unified; creative and collaborative; a collection of complementary, not competing talents. And though on the surface we remain relaxed, beneath, a torrent of energy links us to our civic tech mission. We stand by our values, and we won’t compromise on any of them. Integrity: We’re conscientious, intentional, and empathetic. Our words and actions align. That’s our character. Please don’t ask us to play another part, we’re poor actors. Compassionate: If we may borrow a quote from Theodore Roosevelt: “No one cares how much you know until they know how much you care.” Because our team is thoughtful and supportive, caring deeply for each other, our clients, and our work, this comes naturally. Inquisitive: We remain students by failing openly and turning lessons into solutions. Unconventional: For us, life isn’t what happens outside of work. Work happens inside of life and our culture erases the line often dividing the two. Authentic: Made possible only because we embody the values listed above. We’re relaxed and fun yet intensely curious and driven. Team members are placed with thought, care, and precision to ensure that Trust, Truth, and Transparency continue to represent our brand. Because of that, we continue Onward, Upward, and Skyward. This position is contingent on contract award** We need a Senior Database Developer. Do you speak fluent SQL, dream in schemas, and somehow also happen to be the calmest, most trusted point of contact anyone's ever worked with? Can you architect a data warehouse before lunch and then hop on a call with a federal client without missing a beat? If you're part database whisperer, part professional right-hand-person - equally happy designing a data pipeline as you are owning a client relationship - then we want you to apply. Come join us if you're motivated to learn from others, to learn from mistakes, to be part of a future-looking and growth-oriented team. Let's go Skyward together." That is a big paragraph. We'll put that in

. Now Responsibilities: list from "What You'll Do". Items: - Be the human Rosetta Stone between raw data and real insight. - Assess our client's current data systems and design a data management framework that actually makes sense. - Build (and guard) a central data repository like it's Fort Knox, but friendlier. - Whip messy data into shape with validation rules and automated cleansing. No rogue duplicates on your watch. - Set up access controls so the right people see the right data, and only the right data. Least privilege, maximum peace of mind. - Build backup and disaster-recovery plans so solid that "we lost the data" becomes a foreign phrase. - Automate the boring stuff - data collection, transformation, and reporting pipelines that hum along without someone babysitting them. - Keep a living, breathing data dictionary and enforce naming standards, so nobody's guessing what a field actually means ever again. - Be THE point of contact for our government client's Contracting Officer and COR. The one name everyone knows to call. - Keep a bird's-eye view of everything happening across the contract, including the work of the analysts on your team. - Answer the call (literally) within 24 hours, every time. Because reliability is basically your love language. We'll put each as

. Now Requirements: from "What we'd like you to have:" list: - A bachelor’s degree and 8+ years of experience. - Serious database chops: architecture, development, and administration, not just "I know how to write a SELECT statement." - Strong SQL skills. You write queries that are clean, fast, and a little bit beautiful: joins, CTEs, window functions, performance tuning, the works. - A solid understanding of report development and automation. You'd rather build a report that runs itself than hit "refresh" every Monday morning. - Hands-on experience developing data frameworks. You look at a pile of disconnected tables and think, "Oh, I can fix that." - A general understanding of AWS. You know your way around the cloud well enough to never get lost in it. - Experience building or improving a data governance framework (data quality, security, access control. The whole nine yards). - Comfort being the face of a contract. You've been the go-to person a client trusts, not just the person quietly fixing things behind the scenes. - A track record of staying cool under a deadline. Federal clients love a fast, calm response. - A knack for turning "the data is broken" into an actual fix, calmly, before anyone panics. - U.S. citizenship and the ability to obtain a Public Trust security clearance (non-negotiable for this one - the government's rules, not ours). We'll put each as

. Now Skills (Preferred Qualifications): from "What Would Blow Us Away": - Prior experience supporting a federal statistical, data, or reporting program. - Extra tools in your belt: Python, Java, SQL, and Tableau. Bonus points if you can build a dashboard people actually want to look at. - An AWS certification. Official proof that your head is in the cloud (in the best way). We'll put each as

. Now Benefits: list from "What We Offer You": - Medical, dental, vision insurance - 15 days of paid leave - 7 days of sick leave - 2 days bereavement leave - 11 paid Federal holidays - Up to 40 hours for jury duty - 401K with 4% employer contribution (and no vesting period) - Up to 4 weeks of paid paternity and maternity leave - Company provided laptop - $5,000 per year for professional development - $600 per year for technical supplies and equipment - $2,000 referral bonus - Life and disability insurance - HSA and FSA - Legal Shield and ID Shield Voluntary Benefits - Opportunity to work in a collaborative, motivated team focused