Senior Salesforce Administrator and Business Analyst
About the role
,Responsibilities
,Requirements
,Qualifications
,Skills
,Pay
,Schedule
. Possibly also "About the role" is a heading already present. We'll include content from posting. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information. Use- for lists. Use
for prose. We need to extract sections: About the role: The posting has "About The Role" paragraph describing responsibilities split into admin and BA. Also "What the role involves" with subpoints. We'll combine. Responsibilities: Could be the bullet list under "What the role involves" (two categories: Salesforce administration and delivery; Business analysis). We'll make a list. Requirements: maybe the "Who might be a good fit" list of qualities. Qualifications: maybe the bullet list under "A Successful Candidate Will Possess Most Of These Qualities" (these are qualities). But we already used that for Requirements? Might need differentiate. Could treat "Requirements" as the list of qualities, and "Qualifications" as certifications etc. However the posting includes "Significant hands-on experience with Salesforce: You have 5+ years..." etc. Also "Salesforce certified: Salesforce Certified Administrator, plus at least one of Advanced Administrator or Business Analyst." Also "Desirable, But Not Required" etc. We'll split: Requirements = mandatory qualifications (5+ years experience, certifications). Qualifications = desirable? But instructions: Use sections only when posting has real specific content. We'll include both. Skills: maybe list of skills like "Natural fluency with business processes", "Stakeholder-minded", etc. Could be overlapping. We'll decide: Skills = the list of qualities (Natural fluency..., Stakeholder-minded..., Familiar across connected systems..., Collaborative..., Significant hands-on experience..., Salesforce certified..., High ownership..., Experienced in a code-first org..., Experience with AI-enabled workflows). That seems like skills/qualities. Requirements could be the mandatory ones: 5+ years experience, certifications. Qualifications could be the desirable ones: Additional certifications, breadth of exposure, mission-driven experience, basic Apex/LWC, integration experience. We'll need to ensure we don't duplicate content. Let's extract text. From posting: About The Role: "This role involves two primary responsibilities: 1) developing a deep understanding of what CG’s stakeholders need, and 2) building it in Salesforce. On the “Administrator” side, you’d own a meaningful share of our incoming ticket triage rotation and make hands-on declarative updates in Salesforce, working closely with our team. On the “Business Analyst” side, you’d own intake, discovery, and requirements work so that projects have build-ready requirements and get shipped faster. Requests increasingly span Salesforce, other tools like Airtable and Slack, Claude-powered workflows, and manual processes, and you’d help gather requirements for workflows that involve many tools, with a strong understanding of how changes in one may affect connecting workflows. While we currently expect our ideal candidate to spend 60% of their time on administration and 40% on business analysis, it is possible that the exact balance could shift depending on team needs and the candidate’s particular strengths. You would join a growing Salesforce team — spanning Eastern, Central, and Brasília time — that meets daily and works closely together. This is an individual contributor role with no direct reports. Our system keeps getting more complex as CG grows, which means more to administer, more processes to document, and more opportunities to make how we work better!" What the role involves: - Salesforce administration and delivery: list of items. - Business analysis: list of items. Who might be a good fit: "We are looking for an experienced Salesforce professional who pairs the technical skills of a seasoned administrator with a real appetite for understanding, documenting, and improving processes through business analysis. A Successful Candidate Will Possess Most Of These Qualities Natural fluency with business processes and how to improve them: You enjoy leading discussions about requirements, translating between people with very different levels of technical familiarity, and documenting clear requirements. Stakeholder-minded: You work collaboratively with users and stakeholders of varying levels of technical fluency across teams like Operations and Programs. You describe past work in terms of the friction you removed for users, not only the cases you closed. Familiar across connected systems: You’re at ease gathering requirements for work that spans Salesforce and associated tools. You can help a stakeholder think through whether a request is best met in Salesforce, via Claude, in Airtable, or through a process change and speak to the rough tradeoffs, even if you’re not the one building it. Collaborative: We are a small team that shares work and leans on each other’s strengths, so you are as comfortable deferring to a colleague as making the call yourself. Significant hands-on experience with Salesforce: You have 5+ years of hands-to-keyboard configuration and declarative build — for example, custom objects and fields, validation rules, email alerts, screen flows, page layouts and Lightning pages, permission sets, sharing settings, custom metadata types, custom settings, and complex cross-object formula fields and roll-up summaries — and are experienced deploying changes from sandbox to production. Salesforce certified: Salesforce Certified Administrator, plus at least one of Advanced Administrator or Business Analyst. High ownership in a fast-paced environment: You thrive when there is a lot in motion. You drive ambitious, under-scoped work to completion and make tradeoff recommendations rather than waiting for perfectly scoped requirements. Priorities shift, and you can rebalance. While this is an in-house role, our team manages many priorities at once and is continuously building something new. Experienced in a code-first org: While you would not be expected to write Apex, a lot of our automation lives in code rather than in Flow. We’d expect you can read enough of it to understand why a record behaves the way it does and to scope requests knowing the answer may be code rather than declarative configuration. Experience with, or strong openness to, AI-enabled workflows: You are excited to contribute to our recently implemented Salesforce MCP and iterate quickly on it and surrounding workflows. Desirable, But Not Required Additional certifications: Having both Advanced Administrator and Business Analyst certifications rather than just one. Breadth of exposure: You’ve seen how different teams, stakeholders, or organizations solve similar problems, whether that comes from consulting across multiple orgs or from working extensively in-house at a complex organization with many internal stakeholders and varied processes. Ideally, you’ve had experience in the mission-driven, philanthropic, and/or nonprofit space. Basic Apex or LWC development experience: Knowing basic Apex or LWC development, or holding a Platform Developer I certification. The more of our code-first build you can engage with or contribute to directly, the better. Integration experience: Third-party integration experience, especially with systems in our stack (Airtable, Zapier, FormAssembly, Fillout, Ironclad, and our BigQuery-based data infrastructure)." We Expect All Our Staff To ... (mission etc.) Not needed for sections. Role details & benefits Position type: This is a full-time position. Salary $155,825 / Yearly Four-day Week No (maybe "Four-day Week" indicates schedule). So Pay: $155,825 yearly. Schedule: Four-day week. Now craft HTML. We'll have:
About the role
... (the About The Role paragraph)
Responsibilities
- Salesforce administration and delivery: configure and build on platform, delivering enhancements and new features declaratively — e.g. custom objects and fields, validation rules, screen flows, page layouts, permission sets, and complex cross-object formula fields and roll-up summaries; own a meaningful share of incoming ticket triage rotation alongside project work, responding to and resolving inbound tickets (cases) with high autonomy and ownership; deploy changes from sandbox to production, working within DevOps practices and suggesting improvements; support users through User Acceptance Testing, and help stand up additional testing and signoff processes where needed; maintain accurate and helpful documentation of system functionality, including user-facing and team-facing documentation; proactively propose enhancements and bug fixes to existing systems and processes.
- Business analysis: own case and project intake, lead discovery sessions, write requirements and level-of-effort estimates, and drive backlog refinement so that there’s always sprint-ready work in the queue; work with stakeholders of varying technical familiarity and translate their requests into requirements any member of the team could pick up and deliver, understanding the business problem in depth; gather requirements for work that spans multiple systems, understanding the workflows that connect Salesforce with other tools and how changes in one can affect others; surface what sits behind a request: technical impact, data integrity considerations, level of effort, and the scalability, maintainability, and user-experience tradeoffs involved; facilitate productive conversations when a request diverges from what’s best overall, including knowing when something may not belong in Salesforce at all; lead the next stage of how we gather and refine requirements, building on the intake process we already have so that requirements are clear up front and late-breaking changes rarely delay delivery of a case or project; document business processes, flagging opportunities for improvement as you go; improve flows or forms that make grantmaking operations more efficient; gather and refine requirements for new fields and automation behind expanding partnerships work; run discovery for cross-system integration and form opinions on data placement and sync direction; standardize and automate project intake, requirements gathering, refinement, and approval; scope a stakeholder’s Salesforce request and fulfill it using the best possible set of tools, whether that’s building in Salesforce or exploring other options like a Claude-powered workflow, Airtable view, or process change.
Requirements
- Significant hands‑on experience with Salesforce: 5+ years of hands‑to‑keyboard configuration and declarative build (custom objects and fields, validation rules, email alerts, screen flows, page layouts and Lightning pages, permission sets, sharing settings, custom metadata types, custom settings, complex cross‑object formula fields and roll‑up summaries) and experience deploying changes from sandbox to production.
- Salesforce certified: Salesforce Certified Administrator, plus at least one of Advanced Administrator or Business Analyst.
Qualifications
- High ownership in a fast‑paced environment: thrive when there is a lot in motion, drive ambitious, under‑scoped work to completion, make tradeoff recommendations, rebalance priorities.
- Experienced in a code‑first org: able to read enough Apex to understand record behavior and scope requests knowing the answer may be code rather than declarative configuration.
- Experience with, or strong openness to, AI‑enabled workflows: excited to contribute to the recently implemented Salesforce MCP and iterate quickly on it and surrounding workflows.
Skills
- Natural fluency with business processes and how to improve them: enjoy leading discussions about requirements, translating between people with different technical familiarity, documenting clear requirements.
- Stakeholder‑minded: work collaboratively with users and stakeholders of varying technical fluency across teams like Operations and Programs; describe past work in terms of friction removed for users.
- Familiar across connected