Finance Manager (m/w/d)

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. We must not repeat job title as heading. Remove boilerplate, navigation, etc. Must preserve all substantive info. We need to parse the posting. Job title: "2026 Job Openings Finance Manager (m/w/d) 2026 Full-time Location: Vienna from October". Not needed as heading. We have sections: "Your Responsibilities" then list of responsibilities. Then "Your Profile" then list of profile. Then "What We Offer" then list of offers. Then "For this position the collective agreement minimum salary..." then "Role You can expect a varied role..." then application instructions (we drop). Also mention "Role" maybe part of description. We need to map to headings: About the role (maybe a brief description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be a short prose summarizing role? The posting includes "Your Responsibilities" and "Your Profile". There's no explicit "About the role" but we could create a short paragraph from the initial description: "Finance Manager (m/w/d) Full-time Location: Vienna from October". However we must not repeat job title as heading, but we can include a paragraph describing role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including it in prose. So we can include a short

about the role: maybe "Finance Manager position based in Vienna, starting October, full-time." That's substantive. - Responsibilities: we have list under "Your Responsibilities". Use

Responsibilities

then

• each. - Requirements: Could be from "Your Profile" includes experience, degree, knowledge, etc. That's qualifications/requirements. We need separate sections for Requirements, Qualifications, Skills if content distinct. The posting lumps them together. We could split: Requirements (professional experience, degree), Qualifications (knowledge of controlling, accounting, etc.), Skills (analytical skills, ERP knowledge, language, etc.). But we must not create sections with filler. We need to see if we have enough distinct content for each. Let's extract: Your Profile bullet points (actually sentences): - Several years of professional experience in Financial Controlling, Finance, Accounting, or FP&A - Completed degree in Finance, Accounting, Controlling, Business Administration, or a comparable qualification - Strong knowledge of Controlling, Accounting, Financial Reporting, corporate planning, and contribution margin accounting using the declining contribution margin method - Experience with budgeting, forecasting, cash-flow planning, and KPI reporting - Excellent analytical skills and a strong understanding of business models and financial interrelationships - In-depth knowledge of ERP and financial accounting software; specific experience with Odoo is an advantage; proficient in Microsoft Office - Structured, independent, and solution-oriented working style, with a willingness to build and continuously improve processes - Ability to present complex financial topics clearly and understandably to management and other teams - Very good German and English skills - Entrepreneurial mindset and a hands-on mentality We could map: Requirements: professional experience, degree. Qualifications: strong knowledge of controlling, accounting, financial reporting, corporate planning, contribution margin accounting; experience with budgeting, forecasting, cash-flow planning, KPI reporting. Skills: analytical skills, understanding business models; ERP knowledge, Odoo advantage, MS Office; structured independent work style; ability to present; language skills; entrepreneurial mindset. But we need to avoid duplication. Could also combine Qualifications and Skills into one section if not enough distinct. However instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one "Requirements" section, and Skills into another "Skills". Or we could have Requirements (experience + degree), Qualifications (knowledge/experience), Skills (soft skills/languages). That seems reasonable. Benefits: from "What We Offer": list includes: - A key role in an innovative and future-oriented technology company - Excellent development opportunities in a rapidly growing environment - A supportive company culture with short decision-making processes - Flexible working arrangements, including remote work and flexible working hours - Above-average compensation and attractive additional benefits Pay: specific salary info: "For this position the collective agreement minimum salary is €76.216 gross per year (for full-time basis -including all special payments 14 salaries/ Year). A higher salary is offered depending on qualifications and experience." Schedule: maybe from "Flexible working arrangements, including remote work and flexible working hours" could be schedule. But we already used flexible working arrangements in Benefits. Could treat schedule as separate if we have explicit schedule info. The posting mentions "Full-time" and "Flexible working hours". Could create Schedule section with "Full-time position with flexible working hours and remote work options." However we need to avoid filler. We have info: "Full-time" and "Flexible working arrangements, including remote work and flexible working hours". That's schedule info. So we can create Schedule section. But we must not duplicate content. If we put flexible working arrangements in Benefits, we might duplicate. Better to put schedule info in Schedule section, and benefits list other items (key role, development opportunities, culture, attractive compensation). However "Above-average compensation and attractive additional benefits" is compensation/benefit; we could put that in Benefits. Pay section already covers salary. So Benefits could be: key role, development opportunities, supportive culture. That seems fine. Thus sections: - About the role (p) - Responsibilities (h3 + ul) - Requirements (h3 + ul) (experience + degree) - Qualifications (h3 + ul) (knowledge, budgeting, forecasting, cash-flow, KPI) - Skills (h3 + ul) (analytical, ERP/Odoo/MS Office, structured work, presentation, languages, entrepreneurial mindset) - Benefits (h3 + ul) (key role, development opportunities, supportive culture) - Pay (h3 + p) (salary details) - Schedule (h3 + p) (full-time, flexible hours, remote work) We must ensure we don't create sections with filler like "not specified". All have content. Now we need to output only HTML fragment, no /. Use

  for headings. Use

  • for lists. Use

    for prose. We must not include job ID/requisition numbers. Not present. We must remove boilerplate like application instructions: "We look forward to receiving your detailed application with photo and letter of motivation by e-mail to: office@backbone.io". Remove that. Also remove "Role You can expect a varied role, attractive conditions, a professional environment, and the security of a successful company." That's somewhat generic; maybe we could incorporate into About the role? It's a bit filler but still substantive? It says "You can expect a varied role, attractive conditions, a professional environment, and the security of a successful company." That's somewhat generic but still info. Could include in About the role paragraph. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that sentence. It's not boilerplate; it's part of the posting. So we should include it. Thus About the role paragraph could combine: "Finance Manager (m/w/d) Full-time position located in Vienna, starting October. You can expect a varied role, attractive conditions, a professional environment, and the security of a successful company." We must not repeat job title as heading, but we can include it in paragraph. Now let's craft lists. Responsibilities list (from "Your Responsibilities"): - Responsibility for Finance, Controlling, and Management Reporting - Preparation and further development of budgets, forecasts, and financial plans - Analysis of financial performance and development of recommendations for action - Implementation and management of product and project cost accounting - Management of the interface between financial accounting (FiBu) and the ERP system - Responsibility for liquidity planning and cash management - Close collaboration with senior management and relevant departments - Support with strategic and operational financial decisions - Management and continuous development of Finance processes and structures - Further development of KPIs, reports, and Finance tools - Interface with Accounting, tax advisors, auditors, and external partners Make each as

  • . Requirements list (experience + degree): - Several years of professional experience in Financial Controlling, Finance, Accounting, or FP&A - Completed degree in Finance, Accounting, Controlling, Business Administration, or a comparable qualification Qualifications list (knowledge, budgeting, forecasting, cash-flow, KPI): - Strong knowledge of Controlling, Accounting, Financial Reporting, corporate planning, and contribution margin accounting using the declining contribution margin method - Experience with budgeting, forecasting, cash-flow planning, and KPI reporting Skills list (analytical, ERP/Odoo/MS Office, structured work, presentation, languages, entrepreneurial mindset): - Excellent analytical skills and a strong understanding of business models and financial interrelationships - In-depth knowledge of ERP and financial accounting software; specific experience with Odoo is an advantage; proficient in Microsoft Office - Structured, independent, and solution-oriented working style, with a willingness to build and continuously improve processes - Ability to present complex financial topics clearly and understandably to management and other teams - Very good German and English skills - Entrepreneurial mindset and a hands-on mentality Benefits list (key role, development opportunities, supportive culture): - A key role in an innovative and future-oriented technology company - Excellent development opportunities in a rapidly growing environment - A supportive company culture with short decision-making processes Pay paragraph: include salary details. Schedule paragraph: full-time, flexible working hours, remote work. We must not include "Above-average compensation and attractive additional benefits" because we already have Pay and Benefits; but that sentence is about compensation/benefits. Could we incorporate into Benefits? It says "Above-average compensation and attractive additional benefits". That's somewhat redundant with Pay and Benefits. But we must preserve all substantive information; we cannot drop it. So we need to include it somewhere. Perhaps we can add to Benefits list as an item: "Above-average compensation and attractive additional benefits". However we already have Pay section detailing salary; but we can still include this as a benefit item. It's not duplicate exactly; it's a statement about compensation and benefits. We'll include it in Benefits list. Thus Benefits list items: - A key role in an innovative and future-oriented technology company - Excellent development opportunities in a rapidly growing environment - A supportive company culture with short decision-making processes - Above-average compensation and attractive additional benefits Now Schedule: we have "Full-time" and "Flexible working arrangements, including remote work and flexible working hours". Also the job posting says "Full-time" at top. So schedule paragraph: "Full-time position with flexible working hours and remote work options." Now About the role paragraph: include the job title? Not as heading but we can include. Let's write: "Finance Manager (m/w/d) – Full-time position based in Vienna, starting October. You can expect a varied role, attractive conditions, a professional environment, and the security of a successful company." Check we haven't missed any substantive info: The line "For this position the collective agreement minimum salary is €76.216 gross per year (for full-time basis -including all special payments 14 salaries/ Year). A higher salary is offered depending on qualifications and experience." We captured in Pay. We also have "Role You can expect a varied role, attractive conditions, a professional environment, and the security of a successful company." Already included. We have "Your Responsibilities" list captured. We have "Your Profile" captured split. We have "What We Offer" captured. We have no other info. Now ensure we didn't include any boilerplate like cookie/navigation/legal/EEO etc. Not present. Now output HTML fragment. We need to wrap