> Markdown version of [/jobs/ext/2661165-software-engineer-i](https://www.wearedevelopers.com/jobs/ext/2661165-software-engineer-i). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer I - **Company:** Acrisure LLC - **Location:** Austin, TX, United States - **Experience:** Starter - **Salary:** $100,000.0 - $150,000.0 - **Contract:** Permanent contract - **Skills:** Clean Code Principles, JavaScript (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Automation of Tests, Software Bug Management, Software Quality, Code Review, Software Debugging, DevOps, Python (Programming Language), Software Engineering, Systems Integration, TypeScript - **Published:** August 31, 2026 - **Apply:** https://www.dice.com/job-detail/6c3029d9-4d54-4516-b3d1-160890cd70f2 ## About the Role * Technical Ability: Implements assigned tasks, bug fixes, tests, and documentation; writes modular, maintainable code with guidance; demonstrates growing fluency in Python or JavaScript/TypeScript and modern engineering practices. * Communication: Communicates progress, blockers, and risks clearly; keeps stories and tasks up to date; asks clarifying questions when requirements or technical direction are unclear. * Critical Thinking: Applies a structured approach to problem solving, adjusts when new information becomes available, and looks for simple, practical solutions before escalating. * Organizational Contribution: Participates actively in team rituals, code reviews, and engineering discussions; shares observations and feedback in a constructive way. * Business Impact: Delivers assigned work on time and with quality; begins to understand how engineering work supports underwriting, policy administration, and business operations., * 1+ year of software engineering experience. * Strong foundational skills in Python or JavaScript/TypeScript. * Familiarity with APIs, integrations, automated testing, debugging, and modern development workflows. * Comfortable using AI-assisted development tools, with Claude Code strongly preferred. * Eagerness to learn the insurance domain and apply business context to technical work. * Strong communication skills, curiosity, accountability, and willingness to ask for help when needed. Candidates should be comfortable with an on-site presence to support collaboration, team leadership, and cross-functional partnership. ## Description The Software Engineer I builds and maintains APIs, workflows, integrations, and tooling that support underwriting and policy administration. Embedded in an engineering team under an Engineering Team Lead, this role is focused on delivering assigned work with quality, learning the insurance domain, and developing the technical judgment needed to contribute more independently over time. The Software Engineer I is expected to implement well-defined tasks, ask questions early, communicate progress clearly, and participate in testing, debugging, and operational support with guidance from more experienced engineers. Reporting and Scope * Reports to: Engineering Team Lead * Works with: Engineers on the team, Delivery Lead, underwriting/business stakeholders, internal systems teams, and external vendors as needed * Career framework alignment: Entry-level role on the Software Engineer ladder; this description is specific to SDE1 How the Role Fits the Operating Model The Software Engineer I is on the supply side of the prioritization triangle, helping turn requirements from the Team Lead and Delivery Lead into working software on the policy administration platform. This role learns the insurance domain - including quoting, binding, endorsements, rating, forms, and the policy lifecycle - and applies that context to complete assigned development work., * Build and maintain: Build and maintain APIs, workflows, integrations, and tooling supporting underwriting and policy administration systems. * Implement defined work: Complete assigned stories, tasks, bug fixes, tests, and documentation based on clear requirements and acceptance criteria. * Write quality code: Write modular, maintainable code with guidance and proactively ask for help when needed. * Support operational workflows: Work with engineering leads and business stakeholders to support operational workflow implementation. * Contribute to integrations: Assist with integrations between internal systems, external vendors, and policy administration platforms under guidance from senior engineers. * Participate in production support: Support debugging, testing, automation, and operational support for production systems, escalating issues appropriately. * Improve tooling: Help improve internal engineering tooling and developer workflows by identifying small opportunities for efficiency and quality. * Use AI-assisted engineering: Use AI-assisted engineering workflows, including Claude Code or similar tools, to support development speed, code quality, testing, and documentation. * Learn the domain: Build understanding of insurance domain concepts including quoting, binding, endorsements, rating, forms, and the policy lifecycle. * Demonstrate ownership: Take ownership of assigned work, follow through on commitments, incorporate feedback, and demonstrate curiosity when working through unfamiliar problems. ## Related Videos - [From DevOps to Scaled DevOps: How We’re Rebuilding Continuous Delivery as a Platform](https://www.wearedevelopers.com/videos/100018-from-devops-to-scaled-devops-how-we-re-rebuilding-continuous-delivery-as-a-platform) - [Do TypeScript without TypeScript](https://www.wearedevelopers.com/videos/327-do-typescript-without-typescript) - [Are Code Reviews Worth It? Insights from 16 Years of Review Data](https://www.wearedevelopers.com/videos/1135-are-code-reviews-worth-it-insights-from-16-years-of-review-data) - [Are We All Prompt Engineers? How AI Changed What It Means to Build Software](https://www.wearedevelopers.com/videos/1980-are-we-all-prompt-engineers-how-ai-changed-what-it-means-to-build-software) - [DevOps Maturity Check – a way to balance autonomy and alignment](https://www.wearedevelopers.com/videos/58-devops-maturity-check-a-way-to-balance-autonomy-and-alignment) - [The AI-Native Engineering Org: What’s Real, What’s Hype, What’s Next](https://www.wearedevelopers.com/videos/100004-the-ai-native-engineering-org-what-s-real-what-s-hype-what-s-next) ## Related Articles - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [The 12 Best Jobs for Software Engineers](https://www.wearedevelopers.com/magazine/401-the-12-best-jobs-for-software-engineers) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [Transforming Software Development: The Role of AI and Developer Tools](https://www.wearedevelopers.com/magazine/527-transforming-software-development-the-role-of-ai-and-developer-tools)