Software Development Engineer I – III (Salesforce)
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out things like "We are an Equal Opportunity employer..." etc. Also "Learn More About Our Benefits." maybe keep? It's a link but we can keep as prose? Probably remove as it's navigation. Also "We are happy to offer work from home options..." maybe keep as part of Benefits? It's about remote work requirement; could be part of Benefits or Schedule? It's about work-from-home options; maybe include in Benefits? But it's not a benefit per se; it's a work arrangement. Could be part of Schedule? The schedule already mentions hybrid 3 days/week in office; remote work option details could be extra. Might be considered part of Benefits? Not sure. The instruction: include a section ONLY when posting has real, specific content for it. So we can include a section "Work Arrangement" maybe? But only allowed headings are listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings. So we can put remote work details under Schedule or Benefits? Probably Schedule (since it's about work location/hybrid). We'll include schedule details: hybrid role (3 days/week in office) at list of offices, preference for current employees and candidates within commutable distance or willing to relocate. Also mention work-from-home options with internet requirements and MFA device requirement.
Pay section: include salary ranges for each level and location.
Benefits section: list benefits: medical/dental/vision, mental health, annual employer contribution to HSA, generous PTO varying by role/tenure plus 10 company-paid holidays, market-leading retirement plan with company match, up to 12 weeks paid parental leave, award-winning wellness programs, Employee Assistance Fund, commute and parking benefits.
Also maybe include "Learn More About Our Benefits." but that's just a link; we can omit.
Responsibilities: could be "What You Will Do At Cambia (Not Limited To)" which is a list of duties. So we can make a Responsibilities section with that list.
Requirements: maybe combine Qualifications and Skills? But we have Qualifications (education/experience) and Skills And Attributes (skills). Could split: Qualifications section for education/experience; Skills section for skills and attributes. We'll follow allowed headings: Qualifications, Skills.
About the role: maybe we have a brief intro: "Build a career with purpose. Join our Cause to create a person-focused and economically sustainable health care system." plus "Who We Are Looking For" paragraph. Could be About the role.
We also have "About Cambia" and "Why Join the Cambia Team?" Could be part of About the role or maybe separate sections but we only have allowed headings; we could incorporate into About the role as prose.
We must not create sections with filler. So we need to ensure each heading has substantive content.
Let's outline:
About the role
Build a career with purpose. Join our Cause to create a person-focused and economically sustainable health care system. Who We Are Looking For Every day, Cambia’s dedicated team of Software Development Engineers are living our mission to make health care easier and lives better. As a member of the Software Development Engineering team, our Software Development Engineers participate in a cross-team environment for the delivery and maintenance of application systems. They are responsible for programming, debugging, building, deploying, testing, and documentation of applications in development and production environments, as well as database design and system testing and documentation. This position provides technical, interpersonal, and administrative skills in performing day-to-day work - all in service of making our members' health journeys easier. Do you thrive as a part of a collaborative, caring team? Then this role may be the perfect fit.
But note that some of that is also in Responsibilities; we might duplicate. Better to keep About the role short: maybe just the purpose statement and who we are looking for summary. However we must preserve all substantive information; we cannot omit details. So we need to include all info somewhere. We can put the detailed responsibilities in Responsibilities section. So About the role can contain the purpose and maybe the "Who We Are Looking For" paragraph (the first paragraph after "Who We Are Looking For").
Let's extract: After "Who We Are Looking For" there is: "Every day, Cambia’s dedicated team of Software Development Engineers are living our mission to make health care easier and lives better. As a member of the Software Development Engineering team, our Software Development Engineers participate in a cross-team environment for the delivery and maintenance of application systems. They are responsible for programming, debugging, building, deploying, testing, and documentation of applications in development and production environments, as well as database design and system testing and documentation. This position provides technical, interpersonal, and administrative skills in performing day-to-day work - all in service of making our members' health journeys easier. Do you thrive as a part of a collaborative, caring team? Then this role may be the perfect fit."
That's a good About the role.
Now Responsibilities: "What You Will Do At Cambia (Not Limited To)" list. We'll make - each bullet.
Responsibilities list:
- Develop Lightning Web Components, Aura components, Apex classes, Triggers and Visualforce pages based on business requirements.
- Integrate Salesforce with internal and external systems using real-time or batch APIs and third-party applications.
- Build and support solutions in Salesforce Sales Cloud, Service Cloud, and Experience Cloud.
- Troubleshoot and resolve issues found during testing or reported in production.
- Work with senior developers and follow coding standards and development best practices.
- Provide technical guidance to Salesforce administrators on validation rules, formula fields, data exports and basic coding questions.
- Participate in Agile ceremonies including sprint planning, standups and retrospectives
- Expected to contribute to process improvement.
- Develops efficient and effective program and system solutions in solving complex business problems.
- Meets established deadlines while maintaining a high level of quality.
- Negotiates changes to delivery dates.
We need to ensure each bullet is a
- .
Now Qualifications: education and experience for levels I, II, III. We'll present as prose maybe bullet list? Could be
- for each level? The instruction: Use
- for any list of duties/requirements/benefits. So qualifications is a list of requirements; we can list each level as bullet.
Qualifications:
- Software Development Engineer I: Bachelor's degree in Computer Science, Mathematics, Business Administration, Engineering, or a related field and relevant experience in a multi-platform environment, including, but not limited to application development or database development.
- Software Development Engineer II: Bachelor's degree in Computer Science, Mathematics, Business Administration, Engineering, or a related field and at least 3 years relevant experience in a multi-platform environment.
- Software Development Engineer III: Bachelor's degree in Computer Science, Mathematics, Business Administration, Engineering, or a related field and at least 5 years relevant experience in a multi-platform environment.
Now Skills: list of skills and attributes. We'll bullet each.
Skills list (from "Skills And Attributes"):
- Communicates clearly in a timely manner in both verbal and written communication.
- Comfortable working in a remote and/or distributed team environment, and proficient in asynchronous communication tools such as Microsoft Teams or Slack.
- Able to work well with business customers, as well as engineering and technical partners.
- Able to take direction, in analyzing and solving program and system issues.
- Familiar with core technologies and methodologies used by the team.
- Able to analyze, diagnose, and resolve simple programming problems and system coordination issues.
- Able to work with minimum direction.
- Able to plan and manage their own work.
- Communicate effectively with peers.
- Familiar with Test Driven Development (TDD) and Behavior Driven Development (BDD) including unit and behavior test creation.
- Follows corporate and departmental coding standards and guidelines.
- Able to learn continuous integration and continuous deployment (CI/CD) practices.
- Able to learn containerization technologies and orchestration tools.
- Able to learn RESTful and/or GraphQL API (Application Programming Interface) design and best practices.
- Applies software security best practices.
- Familiarity with defensive programming, OWASP top 10 to mitigate injection vulnerabilities, cross-site scripting (XSS), server-side request forgery (SSRF).
- Familiar with authentication principles, security hygiene and data stewardship.
- Depending on business area, demonstrated experience of building Data pipelines: Data Exchange, Cleansing, Validation, Standardization, Search and Ranking based on Data Science.
- Ability to collaborate openly with all partners/audiences while solving technical problems.
- Ability to lead groups of business customers and external technology partners.
- Ability to establish clarity from uncertainty and break down complex, open-ended problems.
- Excellent communication skills and the ability to collaborate effectively with technical and non-technical stakeholders.
- Anticipates problems and defines creative alternatives proactively.
- Deep experience with multiple technologies.
- Preferred Skills: Knowledge of Apex classes, triggers, custom objects, SOQL, Lightning Flows, Lightning Components (Aura and LWC) and Visualforce pages
- Working knowledge of the Salesforce security model, including profiles, permission sets, org-wide defaults (OWD), role hierarchies and sharing rules; able to configure and troubleshoot data visibility issues with guidance or independently depending on complexity
- Familiarity with Git or other version control systems and exposure to DevOps tools such as Copado.
- Knowledge of REST APIs and integration concepts.
- Experience working in Agile/Scrum environments
We could separate preferred skills but it's okay to include all.
Now Pay: include salary ranges for each level and location.
We need to preserve all substantive info. So we will list:
Pay:
- Software Development Engineer I:
- Oregon, Washington, Utah, and Idaho: Expected hiring range $79K - $99K, full salary range $79K - $129K, bonus target 10%.
- North Dakota: Expected hiring range $72K - $96K, full salary range $72K - $119K.
- Software Development Engineer II:
- Oregon, Washington, Utah, and Idaho: Expected hiring range $87K - $109K, full salary range $87K - $142K, bonus target 15%.
- North Dakota: Expected hiring range $81K - $106K, full salary range $81K - $133K.
- Software Development Engineer III:
- Oregon, Washington, Utah, and Idaho: Expected hiring range $104,000 - $131,000, full salary range $104,000 - $208,000, bonus target 15%.
- North Dakota: Expected hiring range $90,000 - $119,000, full salary range $90,000 - $149,000.
We need to keep the exact numbers; note formatting includes commas. We'll keep as is.
Now Schedule: hybrid role (3 days/week in office) at
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out things like "We are an Equal Opportunity employer..." etc. Also "Learn More About Our Benefits." maybe keep? It's a link but we can keep as prose? Probably remove as it's navigation. Also "We are happy to offer work from home options..." maybe keep as part of Benefits? It's about remote work requirement; could be part of Benefits or Schedule? It's about work-from-home options; maybe include in Benefits? But it's not a benefit per se; it's a work arrangement. Could be part of Schedule? The schedule already mentions hybrid 3 days/week in office; remote work option details could be extra. Might be considered part of Benefits? Not sure. The instruction: include a section ONLY when posting has real, specific content for it. So we can include a section "Work Arrangement" maybe? But only allowed headings are listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings. So we can put remote work details under Schedule or Benefits? Probably Schedule (since it's about work location/hybrid). We'll include schedule details: hybrid role (3 days/week in office) at list of offices, preference for current employees and candidates within commutable distance or willing to relocate. Also mention work-from-home options with internet requirements and MFA device requirement. Pay section: include salary ranges for each level and location. Benefits section: list benefits: medical/dental/vision, mental health, annual employer contribution to HSA, generous PTO varying by role/tenure plus 10 company-paid holidays, market-leading retirement plan with company match, up to 12 weeks paid parental leave, award-winning wellness programs, Employee Assistance Fund, commute and parking benefits. Also maybe include "Learn More About Our Benefits." but that's just a link; we can omit. Responsibilities: could be "What You Will Do At Cambia (Not Limited To)" which is a list of duties. So we can make a Responsibilities section with that list. Requirements: maybe combine Qualifications and Skills? But we have Qualifications (education/experience) and Skills And Attributes (skills). Could split: Qualifications section for education/experience; Skills section for skills and attributes. We'll follow allowed headings: Qualifications, Skills. About the role: maybe we have a brief intro: "Build a career with purpose. Join our Cause to create a person-focused and economically sustainable health care system." plus "Who We Are Looking For" paragraph. Could be About the role. We also have "About Cambia" and "Why Join the Cambia Team?" Could be part of About the role or maybe separate sections but we only have allowed headings; we could incorporate into About the role as prose. We must not create sections with filler. So we need to ensure each heading has substantive content. Let's outline:
About the role
Build a career with purpose. Join our Cause to create a person-focused and economically sustainable health care system. Who We Are Looking For Every day, Cambia’s dedicated team of Software Development Engineers are living our mission to make health care easier and lives better. As a member of the Software Development Engineering team, our Software Development Engineers participate in a cross-team environment for the delivery and maintenance of application systems. They are responsible for programming, debugging, building, deploying, testing, and documentation of applications in development and production environments, as well as database design and system testing and documentation. This position provides technical, interpersonal, and administrative skills in performing day-to-day work - all in service of making our members' health journeys easier. Do you thrive as a part of a collaborative, caring team? Then this role may be the perfect fit.
But note that some of that is also in Responsibilities; we might duplicate. Better to keep About the role short: maybe just the purpose statement and who we are looking for summary. However we must preserve all substantive information; we cannot omit details. So we need to include all info somewhere. We can put the detailed responsibilities in Responsibilities section. So About the role can contain the purpose and maybe the "Who We Are Looking For" paragraph (the first paragraph after "Who We Are Looking For"). Let's extract: After "Who We Are Looking For" there is: "Every day, Cambia’s dedicated team of Software Development Engineers are living our mission to make health care easier and lives better. As a member of the Software Development Engineering team, our Software Development Engineers participate in a cross-team environment for the delivery and maintenance of application systems. They are responsible for programming, debugging, building, deploying, testing, and documentation of applications in development and production environments, as well as database design and system testing and documentation. This position provides technical, interpersonal, and administrative skills in performing day-to-day work - all in service of making our members' health journeys easier. Do you thrive as a part of a collaborative, caring team? Then this role may be the perfect fit." That's a good About the role. Now Responsibilities: "What You Will Do At Cambia (Not Limited To)" list. We'll make- each bullet. Responsibilities list: - Develop Lightning Web Components, Aura components, Apex classes, Triggers and Visualforce pages based on business requirements. - Integrate Salesforce with internal and external systems using real-time or batch APIs and third-party applications. - Build and support solutions in Salesforce Sales Cloud, Service Cloud, and Experience Cloud. - Troubleshoot and resolve issues found during testing or reported in production. - Work with senior developers and follow coding standards and development best practices. - Provide technical guidance to Salesforce administrators on validation rules, formula fields, data exports and basic coding questions. - Participate in Agile ceremonies including sprint planning, standups and retrospectives - Expected to contribute to process improvement. - Develops efficient and effective program and system solutions in solving complex business problems. - Meets established deadlines while maintaining a high level of quality. - Negotiates changes to delivery dates. We need to ensure each bullet is a
- .
Now Qualifications: education and experience for levels I, II, III. We'll present as prose maybe bullet list? Could be
- for each level? The instruction: Use
- for any list of duties/requirements/benefits. So qualifications is a list of requirements; we can list each level as bullet. Qualifications: - Software Development Engineer I: Bachelor's degree in Computer Science, Mathematics, Business Administration, Engineering, or a related field and relevant experience in a multi-platform environment, including, but not limited to application development or database development. - Software Development Engineer II: Bachelor's degree in Computer Science, Mathematics, Business Administration, Engineering, or a related field and at least 3 years relevant experience in a multi-platform environment. - Software Development Engineer III: Bachelor's degree in Computer Science, Mathematics, Business Administration, Engineering, or a related field and at least 5 years relevant experience in a multi-platform environment. Now Skills: list of skills and attributes. We'll bullet each. Skills list (from "Skills And Attributes"): - Communicates clearly in a timely manner in both verbal and written communication. - Comfortable working in a remote and/or distributed team environment, and proficient in asynchronous communication tools such as Microsoft Teams or Slack. - Able to work well with business customers, as well as engineering and technical partners. - Able to take direction, in analyzing and solving program and system issues. - Familiar with core technologies and methodologies used by the team. - Able to analyze, diagnose, and resolve simple programming problems and system coordination issues. - Able to work with minimum direction. - Able to plan and manage their own work. - Communicate effectively with peers. - Familiar with Test Driven Development (TDD) and Behavior Driven Development (BDD) including unit and behavior test creation. - Follows corporate and departmental coding standards and guidelines. - Able to learn continuous integration and continuous deployment (CI/CD) practices. - Able to learn containerization technologies and orchestration tools. - Able to learn RESTful and/or GraphQL API (Application Programming Interface) design and best practices. - Applies software security best practices. - Familiarity with defensive programming, OWASP top 10 to mitigate injection vulnerabilities, cross-site scripting (XSS), server-side request forgery (SSRF). - Familiar with authentication principles, security hygiene and data stewardship. - Depending on business area, demonstrated experience of building Data pipelines: Data Exchange, Cleansing, Validation, Standardization, Search and Ranking based on Data Science. - Ability to collaborate openly with all partners/audiences while solving technical problems. - Ability to lead groups of business customers and external technology partners. - Ability to establish clarity from uncertainty and break down complex, open-ended problems. - Excellent communication skills and the ability to collaborate effectively with technical and non-technical stakeholders. - Anticipates problems and defines creative alternatives proactively. - Deep experience with multiple technologies. - Preferred Skills: Knowledge of Apex classes, triggers, custom objects, SOQL, Lightning Flows, Lightning Components (Aura and LWC) and Visualforce pages - Working knowledge of the Salesforce security model, including profiles, permission sets, org-wide defaults (OWD), role hierarchies and sharing rules; able to configure and troubleshoot data visibility issues with guidance or independently depending on complexity - Familiarity with Git or other version control systems and exposure to DevOps tools such as Copado. - Knowledge of REST APIs and integration concepts. - Experience working in Agile/Scrum environments We could separate preferred skills but it's okay to include all. Now Pay: include salary ranges for each level and location. We need to preserve all substantive info. So we will list: Pay: - Software Development Engineer I: - Oregon, Washington, Utah, and Idaho: Expected hiring range $79K - $99K, full salary range $79K - $129K, bonus target 10%. - North Dakota: Expected hiring range $72K - $96K, full salary range $72K - $119K. - Software Development Engineer II: - Oregon, Washington, Utah, and Idaho: Expected hiring range $87K - $109K, full salary range $87K - $142K, bonus target 15%. - North Dakota: Expected hiring range $81K - $106K, full salary range $81K - $133K. - Software Development Engineer III: - Oregon, Washington, Utah, and Idaho: Expected hiring range $104,000 - $131,000, full salary range $104,000 - $208,000, bonus target 15%. - North Dakota: Expected hiring range $90,000 - $119,000, full salary range $90,000 - $149,000. We need to keep the exact numbers; note formatting includes commas. We'll keep as is. Now Schedule: hybrid role (3 days/week in office) at
- for each level? The instruction: Use