Senior Software Engineer
GreatAmerica · Dallas, TX · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description of company, role responsibilities, requirements (education, experience), skills (technologies), benefits (financial, health, etc). No explicit Pay or Schedule details. So we should not include Pay or Schedule sections. Also maybe "Qualifications" could be combined with Requirements? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
- About the role: we have introductory paragraph describing company and role purpose. Could be "About the role". We'll put that as
About the role
thenwith description. - Responsibilities: list of duties (design, develop, test, implement, maintain services and APIs, troubleshoot, debug, document, etc). We'll put
Responsibilities
then- items.
- Requirements: education and experience bullet list? The posting includes "To Be Successful In The Role You Will Need Education Bachelors Degree or equivalent experience." then list of experience years. Could be Requirements.
- Qualifications: maybe separate but we can combine? The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they are distinct headings. We could put Requirements for education/experience, and Qualifications for technical skills? However Skills heading is for technical skills. Let's map:
Requirements: Education Bachelors or equivalent experience; 8+ years software engineer; 8+ years OOP; 8+ years SQL; 5+ years Agile; 5+ years Swagger/OAS; 5+ years C#; 5+ years Postman; 3+ years Event-Driven Architecture; 3+ years AsyncAPI; 3+ years Salesforce; experience with microservices; Azure, MuleSoft preferred; ability to read design artifacts.
Qualifications: maybe not needed separate; but we could treat the list of experience as Requirements, and Skills as technical languages/tools. However the list includes many technical skills already. Could treat Requirements as education + years experience, Skills as specific technologies (C#, SQL, Swagger, Postman, Azure, MuleSoft, Salesforce, Event-Driven, AsyncAPI, microservices). Benefits: list of financial, health, wellbeing, education, perks.
Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information, not invent or summarize away detail. Must not omit any detail. So we need to include all bullet points from responsibilities, requirements, skills, benefits.
Let's extract.
Company intro: "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! We Are Looking to Add a Key Member to Our Enterprise Technology Group! This position is responsible for designing, developing, and implementing services and APIs for a wide variety of business needs. A successful candidate will have full-stack software engineering experience and demonstrate passion to solve business problems with integrations and software solutions, work in a collaborative agile team environment, and strive for excellence. The candidate shows initiative and exceptional communication skills, with a desire and mindset for growth and self-improvement. The candidate is also able to effectively mentor and coach other developers."
That's about the role.
Responsibilities bullet list (from "As a Senior Software Engineer, You Will"):
- Design, develop, test, implement, and maintain services and APIs
- Troubleshoot, debug, and implement fixes in the existing applications, services, and APIs
- Document and build application code based on best practices and engineering principles defined by our software engineering community and Integration Platform team
- Understand and engage in the broader context of the business “why” and needs behind the code
- Contribute ideas on best practices and process improvements to the software engineering team in GreatAmerica
- Actively participate in design/architectural discussions, reviewing user stories, providing technical solutions and related acceptance criteria and dependencies, sprint demos, and daily standups of corresponding product teams
- Participate in agile product teams to build quality products for consistency, robustness, and scalability
- Deploy, and manage services and APIs in different environments using CI/CD
- Create and maintain automated tests at the integration and unit levels
- Perform peer code reviews
- Present new services and APIs developed to the team and stakeholders
- Answer qualified support calls from users
- Work closely with architects to define processes and technologies to be implemented by all developers
- Determine coding best practices and process improvements
- Enforce coding standards and best practices to ensure only quality code is promoted to higher environments.
- Train, coach, and mentor other Software Engineers and interns
That's a lot.
Requirements (Education + experience):
- Bachelors Degree or equivalent experience.
- 8+ years’ experience as a software engineer with recent focus on developing services and APIs
- 8+ years’ experience with object-oriented principals, solution design, automated testing, validation, and error handling
- 8+ years’ experience with SQL-based databases and SQL programming skills
- 5+ years’ experience working in Agile development environment
- 5+ years’ experience with Swagger or OAS and developing APIs based on the specification
- 5+ years’ experience with C# or similar object-oriented programming language
- 5+ years’ experience with Postman and other Integration testing tools
- 3+ years’ experience with Event-Driven Architecture and creation of event publishers and subscribers
- 3+ years’ experience with AsyncAPI specifications and developing APIs based on the specification
- 3+ years of working in and with Salesforce platform and ecosystem
- Experience with implementing and consuming microservices
- Experience with Azure, MuleSoft, or similar API gateway technologies preferred
- Ability to read, use and produce system design artifacts such as flowcharts and wireframes
Skills: Could be overlapping with requirements; but we can treat the technical skills as Skills heading: C#, SQL, Swagger/OAS, Postman, Event-Driven Architecture, AsyncAPI, Salesforce, microservices, Azure, MuleSoft, ability to read design artifacts, OOP, automated testing, validation, error handling, Agile, CI/CD, unit/integration testing, peer code review, mentoring.
But to avoid duplication, maybe we just have Requirements covering education+experience, and Skills covering technical proficiencies (languages, tools, methodologies). However the list includes many overlapping items. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Skills into one section called "Requirements & Skills"? But headings are prescribed; we could still include both but ensure they have content. It's okay to have both if they have distinct content. However many items overlap; but we can split: Requirements: education + years experience (generic). Skills: specific technologies/tools/methodologies.
Let's define:
Requirements:
- Bachelors Degree or equivalent experience.
- 8+ years’ experience as a software engineer with recent focus on developing services and APIs
- 8+ years’ experience with object-oriented principals, solution design, automated testing, validation, and error handling
- 8+ years’ experience with SQL-based databases and SQL programming skills
- 5+ years’ experience working in Agile development environment
- 5+ years’ experience with Swagger or OAS and developing APIs based on the specification
- 5+ years’ experience with C# or similar object-oriented programming language
- 5+ years’ experience with Postman and other Integration testing tools
- 3+ years’ experience with Event-Driven Architecture and creation of event publishers and subscribers
- 3+ years’ experience with AsyncAPI specifications and developing APIs based on the specification
- 3+ years of working in and with Salesforce platform and ecosystem
- Experience with implementing and consuming microservices
- Experience with Azure, MuleSoft, or similar API gateway technologies preferred
- Ability to read, use and produce system design artifacts such as flowcharts and wireframes
Skills: maybe we can list: Full-stack software engineering, passion for solving business problems with integrations, collaborative agile team, initiative, exceptional communication, desire for growth, mentoring/coaching. But those are more soft skills. Could be under Skills. However the instruction says use Skills heading for list of skills. We could put soft skills there. But we already have many technical skills in Requirements. Might be okay to have Skills for soft skills and maybe some remaining technical not covered? However we already covered technical. Let's put Skills for soft skills: initiative, exceptional communication, desire and mindset for growth and self-improvement, ability to mentor and coach, passion to solve business problems with integrations and software solutions, collaborative agile team environment, strive for excellence.
But we also have "full-stack software engineering experience". That's a skill.
Thus Skills section bullet list:
- Full-stack software engineering experience
- Passion to solve business problems with integrations and software solutions
- Ability to work in a collaborative agile team environment
- Initiative and exceptional communication skills
- Desire and mindset for growth and self-improvement
- Ability to effectively mentor and coach other developers
- Strive for excellence
Benefits: list from "Financial Benefits Sharing rewards..." and subsequent bullet-like lists.
Let's extract benefits:
Financial Benefits:
- 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 should preserve all.
Now format HTML.
We'll output:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
for prose. Could be multiple
but okay. We'll put:
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! We are looking to add a key member to our Enterprise Technology Group. This position is responsible for designing, developing, and implementing services and APIs for a wide variety of business needs. A successful candidate will have full-stack software engineering experience and demonstrate passion to solve business problems with integrations and software solutions, work in a collaborative agile team environment, and strive for excellence. The candidate shows initiative and exceptional communication skills, with a desire and mindset for growth and self-improvement. The candidate is also able to effectively mentor and coach other developers.
Now Responsibilities list: each bullet as - . We'll copy each responsibility exactly as in posting