Jobs · Engineering · Texas

Manager, Salesforce Engineering

GreatAmerica · Dallas, TX · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". We need to extract substantive content. Let's parse the posting. First paragraphs: description of company, mission, etc. That's "About the role"? Actually about the company. Could be "About the role" or maybe "About the company". The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include "About the role" heading with description of role and company. Then responsibilities: many bullet points under "As Manager, Salesforce Engineering, You Will" with subheadings: Leadership & Strategy, Technical Delivery & Innovation, Architecture & Development, Integration & Data Collaboration, Collaboration & Agile Execution. Those are responsibilities. We'll list them as

    • items. Then "Experience" section: requirements: 5+ years technical leadership and people management, 7–8 years hands-on Salesforce development and administration experience, proven expertise in list of technologies. That's requirements/qualifications. Could be "Requirements" heading. Then "Skills & Abilities": list of soft skills. That's "Skills" heading. Then "Education": Bachelor's degree, certifications required. That's "Qualifications" maybe? Actually Education is part of qualifications. Could put under "Qualifications". But we have separate headings: Requirements, Qualifications, Skills. Might combine Education under Qualifications. Then "Financial Benefits": list of benefits: Competitive Compensation, Monthly Bonuses, 401(k) and Company Match, Annual Profit Sharing, Paid Time Off, Health, Wellbeing, And Family Planning Benefits (list), Education And Career Planning Benefits (list), Perks (list). That's benefits. Pay: Not explicitly stated besides "Competitive Compensation". That's vague; we should not create Pay section unless posting actually states them. It says "Competitive Compensation" but no numbers. That's filler? It's not specific; maybe we should not create Pay section because it's not specific. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, they do state specifics (list). So Benefits section is okay. For Pay, they only say "Competitive Compensation" which is vague; better to omit Pay section. Schedule: Not mentioned; omit. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Qualifications? Actually Education could be under Qualifications. Let's decide: We'll have About the role, Responsibilities, Requirements (including experience and technical expertise), Skills (soft skills), Qualifications (education and certifications), Benefits. But we must avoid duplication. Could combine Requirements and Qualifications? The instruction: prefer a few substantive sections over many thin ones. Maybe we can have About the role, Responsibilities, Requirements (covering experience, technical expertise, education, certifications), Skills, Benefits. That's 5 sections. Let's extract content. About the role: combine company description and role overview. Paragraphs: "GreatAmerica is a highly successful entrepreneurial company providing equipment financing to businesses across the United States. Our exemplary customer service, our principle-centered business philosophy and our team-based operating approach are key to our success and growth. We have also recently become a bank! ... As Manager, Salesforce Engineering, you will lead a high-performing team of developers and admins to deliver secure, scalable, and innovative solutions across the Salesforce ecosystem. You’ll combine deep technical expertise with strategic leadership to drive platform excellence, team growth, and business impact." We'll put that as prose under About the role. Responsibilities: list items from each subheading. We need to capture each bullet. Leadership & Strategy: - Lead, mentor, and grow a team of Salesforce engineers and admins, fostering a culture of innovation, collaboration, and continuous learning. - Conduct regular 1:1s, performance reviews, and career development planning. - Advocate for the team’s priorities within the broader engineering and product organization. - Recruit and retain top Salesforce talent. - Promote a DevOps mindset and continuous delivery culture. - Create inclusive, high-trust environments that empower individuals and teams. Technical Delivery & Innovation: - Own end-to-end delivery of Salesforce initiatives, ensuring quality, timeliness, and stakeholder satisfaction. - Establish and enforce development standards, code quality, and deployment processes. - Stay current with Salesforce platform capabilities, releases, and ecosystem trends. - Drive innovation through evaluation and adoption of new Salesforce features, tools, and integrations. - Ensure compliance with security, data privacy, and regulatory requirements. - Participate in Salesforce Governance COE and Architecture Review Boards to uphold platform integrity and best practices. Architecture & Development: - Design and implement scalable solutions across Sales, Service, Experience, Revenue, and Financial Clouds using Apex, LWC, Aura, and declarative tools. - Develop and support Lightning Web Components, Aura components, Visualforce pages, and dynamic forms. - Implement secure programming practices to avoid platform vulnerabilities. - Lead development efforts using CI/CD tools (e.g., Copado), source control (Git), and test-driven development. - Optimize existing features and refactor code to improve performance and maintainability. - Implement robust logging, monitoring, and alerting for deployed solutions. - Troubleshoot and resolve application and data issues, ensuring platform health. Integration & Data Collaboration: - Design and support inbound/outbound integrations using Salesforce APIs (REST/SOAP) and middleware tools like MuleSoft. - Provide OpenAPI Specifications (OAS) for external teams integrating with Salesforce. - Collaborate with non-Salesforce teams on data modeling, access, and integration concerns. - Extend support for functional and non-functional testing teams to ensure quality delivery. Collaboration & Agile Execution: - Partner closely with Product Owners and cross-functional teams to understand business needs and translate them into technical solutions. - Participate in agile ceremonies, including sprint planning, demos, grooming, and standups. - Contribute to design discussions, code reviews, and process improvements. - Support cross-team dependencies and contribute to Agile Release Train planning (SAFe framework experience is a plus). Now Requirements: combine experience and technical expertise. - 5+ years of technical leadership and people management. - 7–8 years of hands-on Salesforce development and administration experience. - Proven expertise in: - Apex, LWC, Aura, SOQL/SOSL, Flows (screen, record-triggered, auto-launch) - Apex triggers, batch classes, scheduled classes - Salesforce security models (Profiles, Permission Sets, Roles, Sharing Rules) - Data modeling, formulas, validation rules - Secure programming practices and performance optimization - Developer Console, CLI, Debug Logs, Query Optimizer - Salesforce APIs, integration patterns, and event architecture - CI/CD environments using tools like Copado - Git workflows, pull request reviews, merge conflict resolution - Agile/Scrum methodologies; SAFe experience preferred - Middleware tools like MuleSoft and cross-platform integrations We can format as
      • items, maybe nested? Simpler: each bullet as
      • . For the proven expertise list, we could make sub-bullets but not required. We'll just list each as separate
      • maybe too many. Could group as one
      • with a semicolon list. But better to keep readable. We'll produce
          with each major bullet. Skills: list from Skills & Abilities. - Exceptional interpersonal skills to communicate effectively with internal & external resources, clients, and third parties - Strong negotiation and collaboration skills and ability to develop and manage stakeholder expectations - Exceptional communication skills (both verbal and written) - Work both independently and in a team-oriented, collaborative environment - Create inclusive team environments that foster trust and a sense of empowerment - Effectively prioritize and execute tasks in a high-pressure environment and excels at communicating shifts in prioritization - Adapt to shifting business priorities, demands, and timelines through analytical and problem-solving capabilities - Must be able to multi-task and have a combination of organizational and analytical skills - Strong push to always gain a combination of business and technical knowledge of the product in their area - Must be systems-oriented, enjoy working with new tools and be a self-motivated learner - Entrepreneurial attitude, with the ability to thrive in a fast-paced work environment - Demonstrated self-starter who is goal-oriented, a critical thinker, and a creative problem solver - Strong sense of urgency and follow-through in addressing issues and meeting timelines Qualifications (Education & Certifications): - Bachelor’s degree in Information Systems or related field. - Salesforce Certified Admin, Advanced Admin, Platform Developer I & II required. - Additional certifications (e.g., Revenue Cloud Consultant, Integration Architecture Designer) are a plus. Benefits: list from Financial Benefits and other benefits. We need to include all benefits mentioned: Financial Benefits Sharing rewards is an integral part of our culture. We believe in the value of hard work and reward our employees beyond the paycheck. Our total rewards package is based on eligibility and includes: - Competitive Compensation - Monthly Bonuses for Eligible Employees - 401(k) and Company Match - Annual Profit Sharing - Paid Time Off Health, Wellbeing, And Family Planning Benefits: - Paid Vacation - Paid Sick Days - Paid Holidays - Gym Reimbursement - Health Insurance - Dental Insurance - Vision Insurance - Short-Term and Long-Term Disability - Company Paid Life Insurance - Flexible Spending Accounts (FSA) - Health Savings Accounts (HSA) - Employee Assistance Program - Parental Leave Education And Career Planning Benefits: - Tuition Assistance - Networking Opportunities - Leadership Development Opportunities Perks: - Paid Parking - Service Awards - Hybrid work arrangements - Business casual environment - A strong organizational culture focused on our greatest asset: you! We'll put these under Benefits heading as
          • . We must not include filler like "Competitive Compensation" maybe it's okay as it's a specific benefit though vague but it's listed as a benefit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits section is okay because they state them. Even if some are vague like "Competitive Compensation", it's still a benefit statement. We'll keep. Now produce HTML. We need to output only HTML fragment, no /, no markdown. We'll wrap sections in maybe not required. Just output headings and content. Example:

            About the role

            ...

            Responsibilities

            • ...
            • ...
            Similarly for others. Make sure to preserve all substantive information. No extra fluff. Let's craft the About the role paragraph. Combine: GreatAmerica is a highly successful entrepreneurial company providing equipment financing to businesses across the United States. Our exemplary customer service, principle-centered business philosophy, and team-based operating approach are crucial to our success and growth. We have also recently become a bank! GreatAmerica is structured in cross-functional product teams that allow individuals to make informed decisions that benefit the company and our customers. There is no doubt that we are building the greatest company of its kind, offering the finest products and services available anywhere. When you are part of the GreatAmerica team,

Similar jobs