Principal Consultant (Budget)
Euna Solutions · Atlanta, GA · 1 mo ago
HybridFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. No filler like "commensurate with experience". We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. No Job ID/requisition numbers as headings.
We need to parse the posting.
Let's extract sections:
- About the role: The opening paragraph: "The Opportunity At Euna Solutions, we're looking for a Software Implementation Consultant with expertise in Public Sector Budgeting to join our team and help public sector organizations get the most from their Euna solutions. You'll be the bridge between current operations and future possibilities – conducting discovery sessions around the customer’s current state, identifying pain points, designing the system solution to meet the customer’s needs all while balancing scope, finding alternatives, directing the technical team to define the integration and data model, and working with the Product and Development teams to resolve complex integration challenges. This role requires some domain subject matter expertise and well as technical acumen so that you can discuss the technical aspects of the build with the customer and other members of the implementation team. We are looking for someone who has led complex customer implementations, has exceptional business acumen and has managed customer relationships before."
That's about the role.
- Responsibilities: The "What You'll Do" section with bullet points: Lead Enterprise Implementations (own end-to-end delivery...), Serve as primary point of contact..., Facilitate Discovery and Design..., Oversee Configuration and Integration..., Manage the Customer Relationship... Each bullet includes subpoints. We need to represent as
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. No filler like "commensurate with experience". We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. No Job ID/requisition numbers as headings.
We need to parse the posting.
Let's extract sections:
- About the role: The opening paragraph: "The Opportunity At Euna Solutions, we're looking for a Software Implementation Consultant with expertise in Public Sector Budgeting to join our team and help public sector organizations get the most from their Euna solutions. You'll be the bridge between current operations and future possibilities – conducting discovery sessions around the customer’s current state, identifying pain points, designing the system solution to meet the customer’s needs all while balancing scope, finding alternatives, directing the technical team to define the integration and data model, and working with the Product and Development teams to resolve complex integration challenges. This role requires some domain subject matter expertise and well as technical acumen so that you can discuss the technical aspects of the build with the customer and other members of the implementation team. We are looking for someone who has led complex customer implementations, has exceptional business acumen and has managed customer relationships before."
That's about the role.
- Responsibilities: The "What You'll Do" section with bullet points: Lead Enterprise Implementations (own end-to-end delivery...), Serve as primary point of contact..., Facilitate Discovery and Design..., Oversee Configuration and Integration..., Manage the Customer Relationship... Each bullet includes subpoints. We need to represent as - items. Probably each bullet as a list item; subpoints can be within same li using sentences.
- Requirements: The "What You Bring" section: 5+ years’ experience with budget software implementation or working in a budget office (strongly preferred) or other with configuration and delivery responsibility for similar complex ERP software, e.g. SAP, Workday, Salesforce in a customer-facing role. Direct experience running discovery workshops and documenting future state requirements and decisions in a structure manner with a demonstrated ability to design future-state workflows that satisfy customer objectives while accounting for realistic system and process constraints. Strong change management instincts... Excellent project management skills... Strong facilitation and documentations skills... These are requirements.
- Qualifications: The "Nice-to-Have Qualifications": Familiarity with SQL, views, and stored procedures; Ability to use AI to create repeatable processes and improve customer outcomes.
- Skills: Not explicitly separate; maybe we can combine some skills like "Strong facilitation and documentation skills", "Excellent project management skills", etc. But we already have those in Requirements. Could create a Skills section for things like "Strong change management instincts", "Excellent project management skills", "Strong facilitation and documentation skills". However we must not create sections with filler. The posting includes those as part of "What You Bring". Could treat them as Skills. But we need to decide.
Better: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Benefits: The posting includes "Life at Euna Solutions" with bullet points: hybrid work schedule (3 days/week in Atlanta office), Eunafier Days (extra day twice a year), Community involvement, Philanthropy Time (up to eight hours a year), Real connection at scale, Room to grow (development budget, mentorship, opportunity). Also location: hybrid with 3 days/week in Atlanta office (Tuesday, Wednesday & Thursday). Also AI Mindset section about encouraging AI usage. That could be considered Benefits or maybe part of culture. We'll treat as Benefits.
Pay: No salary info given. So we should NOT create Pay section because no specific content.
Schedule: The posting mentions hybrid schedule: 3 days/week in Atlanta office (Tuesday, Wednesday & Thursday). Also "standard hours on those days". That's schedule info. So we can create a Schedule section with that detail.
We must not include boilerplate like EEO, accessibility statement, etc. Also remove duplicated lines, navigation, legal, etc. Also remove "Please know Euna Solutions is committed to providing a comfortable and accessible interview process..." etc. Also remove "To learn more, visit www.eunasolutions.com." etc. Also remove "Euna's privacy policy is available here." etc. Also remove "Please visit our website: https://eunasolutions.com/careers/ and check out our LinkedIn Pages". Also remove "We believe in embracing new perspectives..." etc. Also remove "Upon request, appropriate accessible formats..." etc. Also remove "For any inquiries or requests regarding accessibility at Euna Solutions, please email recruiting@eunasolutions.com or call our office at 1.877.707.7755." etc. Also remove "We believe the future of work is human + AI." Actually that is part of AI Mindset, which we might keep as part of Benefits or maybe as a separate section? The instruction says include a section only when posting has real specific content. AI Mindset is specific content about encouraging AI usage. Could be part of Benefits or maybe a separate section like "AI Mindset". But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate AI Mindset into Benefits or maybe Skills? Probably Benefits.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- Lead Enterprise Implementations: Own the end-to-end delivery of enterprise-level implementations, managing scope, timeline, risk, and stakeholder communication from kickoff through go-live. Serve as the primary point of contact for customers throughout the implementation lifecycle, building trust and setting realistic expectations at every stage.
- Facilitate Discovery and Design: Plan and facilitate working sessions with customer stakeholders to document current-state workflows, pain points, and business requirements. Design and document future-state workflows that meet the customer's underlying objectives, balancing what the customer asks for with what will work well in the system. Identify where workflow changes will be needed and proactively manage the change management conversation with customers so that adoption goes smoothly.
- Oversee Configuration and Integration: Oversee data migration activities, including mapping, cleansing, validation, and load ensuring the technical team has a full understanding of the desired outcome. Understand the requirements and logic behind the stored procedures that drive the workflows to be able to explain the desired outcome to the technical team. A basic understanding of SQL, views, and stored procedures is very helpful here. Bring product gaps to the Product and Development teams to discuss the requirements and technical feasibility of the requested change through the CCB. Ensure the project team complete tasks and meets their deliverables with quality before turning over to the customer. Facilitate timely customer verification to ensure seamless signoff.
- Manage the Customer Relationship: Bring experienced insight to managing scope by understanding what the customer needs, what is possible in the solution, and managing expectations to keep the project on budget. Facilitate discussions around issues and risks and develop plans to ensure issues are resolved and risk actively managed. Support testing, training, and go-live readiness activities and support the customer post-go-live to ensure system stability and serving as an escalation point for the support team.
Requirements
- 5+ years’ experience with budget software implementation or working in a budget office (strongly preferred) or other with configuration and delivery responsibility for similar complex ERP software, e.g. SAP, Workday, Salesforce in a customer-facing role.
- Direct experience running discovery workshops and documenting future state requirements and decisions in a structured manner with a demonstrated ability to design future-state workflows that satisfy customer objectives while accounting for realistic system and process constraints.
- Strong change management instincts: the ability to guide customers through process and workflow changes without losing their confidence or trust.
- Excellent project management skills, with the ability to manage multiple concurrent implementations, timelines, and stakeholders.
- Strong facilitation and documentation skills, with experience presenting to and advising customer executives and project teams.
Qualifications
- Familiarity with SQL, views, and stored procedures.
- Ability to use AI to create repeatable processes and improve customer outcomes.
Skills
Strong change management instincts, excellent project management, strong facilitation and documentation abilities, business acumen, technical acumen, ability to discuss technical aspects with customers and implementation team.
But we already listed many of those in Requirements; maybe Skills could be redundant. However we need to avoid filler. Could we omit Skills section? The instruction: Prefer a few substantive sections over many thin ones. If we already have Requirements covering skills, we could omit Skills. But we need to include sections only when posting has real specific content. Skills content is present but maybe covered elsewhere. However we could still include Skills if we have distinct content not already in Requirements. The posting mentions "domain subject matter expertise and technical acumen", "exceptional business acumen", "led complex customer implementations", "managed customer relationships". Those are more like qualifications/experience. Might be okay to omit Skills.
But we need to ensure we preserve all substantive information. If we omit Skills, we might lose some nuance like "business acumen", "technical acumen". However those are captured in Requirements? Not exactly. The Requirements section includes experience, change management, project management, facilitation/documentation. Business acumen and technical acumen are mentioned in the About the role paragraph: "This role requires some domain subject matter expertise as well as technical acumen so that you can discuss the technical aspects of the build with the customer and other members of the implementation team. We are looking for someone who has led complex customer implementations, has exceptional business acumen and has managed customer relationships before." That's in About the role. So we already captured that.
Thus we could omit Skills section.
Now Benefits: We need to capture Life at Euna Solutions bullet points.
Let's extract:
- Hybrid — three days a week in our Oakville or Atlanta offices, with standard hours on those days. What the remaining days look like depends on your role and your manager. We talk about it early in the process so there are no surprises on either side.
- Eunafier Days: Twice a year, you get an extra day tacked onto a long weekend. Simple reason: people who take breaks do better work. Use it however you need.
- Community is part of who we are: Our Engagement Committee finds meaningful ways to give back through time, donations, and shared expertise. We're invested in the places where our people actually live and work.
- Philanthropy Time: We give every employee up to eight hours a year to spend on causes that matter to them. We want you to show up for your community — and we make time for it.
- Real connection at scale: You won't know all 600+ people — and that's okay. What matters is building real relationships with the people you work with every day. Our culture team creates consistent opportunities for that, so work doesn't feel isolating.
- Room to grow: Whether you're going deep on AI, building expertise in government tech, or stepping into a bigger role, we invest in your development — through budget, mentorship, and real opportunity to move when you're ready.
Also AI Mindset: "We believe the future of work is human + AI. At Euna Solutions, we encourage our team members to leverage AI tools to enhance creativity, efficiency, and decision-making. We’re looking for people who are curious about emerging technologies, eager to experiment, and committed to using AI responsibly to augment—not replace—their expertise. If you enjoy exploring new ways to solve problems, learning continuously, and applying AI to make your work smarter and more impactful, you’ll thrive here."
Also Location: "This position will be
About the role
...
Responsibilities
- Lead Enterprise Implementations: Own the end-to-end delivery of enterprise-level implementations, managing scope, timeline, risk, and stakeholder communication from kickoff through go-live. Serve as the primary point of contact for customers throughout the implementation lifecycle, building trust and setting realistic expectations at every stage.
- Facilitate Discovery and Design: Plan and facilitate working sessions with customer stakeholders to document current-state workflows, pain points, and business requirements. Design and document future-state workflows that meet the customer's underlying objectives, balancing what the customer asks for with what will work well in the system. Identify where workflow changes will be needed and proactively manage the change management conversation with customers so that adoption goes smoothly.
- Oversee Configuration and Integration: Oversee data migration activities, including mapping, cleansing, validation, and load ensuring the technical team has a full understanding of the desired outcome. Understand the requirements and logic behind the stored procedures that drive the workflows to be able to explain the desired outcome to the technical team. A basic understanding of SQL, views, and stored procedures is very helpful here. Bring product gaps to the Product and Development teams to discuss the requirements and technical feasibility of the requested change through the CCB. Ensure the project team complete tasks and meets their deliverables with quality before turning over to the customer. Facilitate timely customer verification to ensure seamless signoff.
- Manage the Customer Relationship: Bring experienced insight to managing scope by understanding what the customer needs, what is possible in the solution, and managing expectations to keep the project on budget. Facilitate discussions around issues and risks and develop plans to ensure issues are resolved and risk actively managed. Support testing, training, and go-live readiness activities and support the customer post-go-live to ensure system stability and serving as an escalation point for the support team.
Requirements
- 5+ years’ experience with budget software implementation or working in a budget office (strongly preferred) or other with configuration and delivery responsibility for similar complex ERP software, e.g. SAP, Workday, Salesforce in a customer-facing role.
- Direct experience running discovery workshops and documenting future state requirements and decisions in a structured manner with a demonstrated ability to design future-state workflows that satisfy customer objectives while accounting for realistic system and process constraints.
- Strong change management instincts: the ability to guide customers through process and workflow changes without losing their confidence or trust.
- Excellent project management skills, with the ability to manage multiple concurrent implementations, timelines, and stakeholders.
- Strong facilitation and documentation skills, with experience presenting to and advising customer executives and project teams.
Qualifications
- Familiarity with SQL, views, and stored procedures.
- Ability to use AI to create repeatable processes and improve customer outcomes.
Skills
Strong change management instincts, excellent project management, strong facilitation and documentation abilities, business acumen, technical acumen, ability to discuss technical aspects with customers and implementation team.
But we already listed many of those in Requirements; maybe Skills could be redundant. However we need to avoid filler. Could we omit Skills section? The instruction: Prefer a few substantive sections over many thin ones. If we already have Requirements covering skills, we could omit Skills. But we need to include sections only when posting has real specific content. Skills content is present but maybe covered elsewhere. However we could still include Skills if we have distinct content not already in Requirements. The posting mentions "domain subject matter expertise and technical acumen", "exceptional business acumen", "led complex customer implementations", "managed customer relationships". Those are more like qualifications/experience. Might be okay to omit Skills. But we need to ensure we preserve all substantive information. If we omit Skills, we might lose some nuance like "business acumen", "technical acumen". However those are captured in Requirements? Not exactly. The Requirements section includes experience, change management, project management, facilitation/documentation. Business acumen and technical acumen are mentioned in the About the role paragraph: "This role requires some domain subject matter expertise as well as technical acumen so that you can discuss the technical aspects of the build with the customer and other members of the implementation team. We are looking for someone who has led complex customer implementations, has exceptional business acumen and has managed customer relationships before." That's in About the role. So we already captured that. Thus we could omit Skills section. Now Benefits: We need to capture Life at Euna Solutions bullet points. Let's extract: - Hybrid — three days a week in our Oakville or Atlanta offices, with standard hours on those days. What the remaining days look like depends on your role and your manager. We talk about it early in the process so there are no surprises on either side. - Eunafier Days: Twice a year, you get an extra day tacked onto a long weekend. Simple reason: people who take breaks do better work. Use it however you need. - Community is part of who we are: Our Engagement Committee finds meaningful ways to give back through time, donations, and shared expertise. We're invested in the places where our people actually live and work. - Philanthropy Time: We give every employee up to eight hours a year to spend on causes that matter to them. We want you to show up for your community — and we make time for it. - Real connection at scale: You won't know all 600+ people — and that's okay. What matters is building real relationships with the people you work with every day. Our culture team creates consistent opportunities for that, so work doesn't feel isolating. - Room to grow: Whether you're going deep on AI, building expertise in government tech, or stepping into a bigger role, we invest in your development — through budget, mentorship, and real opportunity to move when you're ready. Also AI Mindset: "We believe the future of work is human + AI. At Euna Solutions, we encourage our team members to leverage AI tools to enhance creativity, efficiency, and decision-making. We’re looking for people who are curious about emerging technologies, eager to experiment, and committed to using AI responsibly to augment—not replace—their expertise. If you enjoy exploring new ways to solve problems, learning continuously, and applying AI to make your work smarter and more impactful, you’ll thrive here." Also Location: "This position will be