Senior Software Engineer - .NET
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines.
We need to parse the posting.
Let's extract sections:
- About Us: Not needed as heading? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Thus we should include "About the role" heading with content from "About The Role". Also "What will you be doing?" is responsibilities. "What are we looking for?" includes required technologies and additional skills. Could be split into Requirements and Skills? The instruction: Use headings for those categories if content exists. We need to decide. We have "Qualifications" section later. Also "What do we offer?" is benefits. Also schedule/hybrid info is in "About The Role" and also in benefits? The posting says: "This position is hybrid (3 days per week in office - Tuesday through Thursday) and is located in Austin, TX." Also later under benefits: "🏠 We are a hybrid company. All team members at Auctane in Austin come into the office Tuesdays, Wednesdays and Thursdays." So schedule/hybrid info appears. We can include a Schedule section with that detail. Pay: Not mentioned. So we should NOT include Pay section. Benefits: We have many benefits listed. So include Benefits. Skills: Could be "Additional Skills" and "Nice to Have". We'll combine into Skills section. Requirements: Could be "Required Technologies" and maybe "Qualifications". But Qualifications is separate heading. We'll have Requirements for required tech, and Qualifications for qualifications (experience, degree, etc). Skills for additional skills and nice to have. Let's extract content precisely. About The Role paragraph: "We're seeking an experienced Senior Software Engineer - .NET to join our engineering team. In this role, you'll architect and build scalable backend systems that power our applications, working across our modern tech stack to deliver robust, high-performance solutions. This position is focused on the ShipStation API brand. This position is hybrid (3 days per week in office - Tuesday through Thursday) and is located in Austin, TX." We'll put that under About the role. Responsibilities: "What will you be doing?" bullet list: - You'll design and implement backend services and APIs that serve millions of requests, working closely with frontend teams to create seamless user experiences. - Your work will involve building new features, optimizing existing systems, and making key architectural decisions that shape our platform's future. - You'll mentor other engineers, participate in code reviews, and help establish best practices across the team. - System Architecture & Design: Architect, build, and maintain scalable, robust backend services and microservices using C# and .NET. - API Development: Create and consume secure REST APIs for seamless communication between backend services and front-end/mobile applications. - Database Management: Design, query, and optimize relational databases (both SQL and NoSQL). - Code Quality & Best Practices: Conduct rigorous code reviews, enforce engineering standards, and write clean, maintainable, production-ready code. - Mentorship: Provide technical guidance, support, and mentorship to mid-level and junior developers. - DevOps & Cloud: Collaborate with the infrastructure team to configure CI/CD pipelines, deploy applications to the cloud (AWS), and maintain different environments. - Testing: Develop and maintain unit tests and integration tests to ensure application reliability. We can keep as
- items.
Requirements: "What are we looking for?" includes Required Technologies and Additional Skills. But we separate.
Required Technologies:
- .NET - Strong proficiency in .NET, including ASP.NET Core, Entity Framework Core, and building RESTful APIs.
- Experience with C# design patterns and async programming
- AWS - Hands-on experience deploying and managing services on AWS, including EC2, Lambda, RDS, S3, CloudFront, SQS and API Gateway.
- Familiarity with infrastructure as code (Terraform, CloudFormation or CDK)
- React - Some experience with front-end JavaScript component libraries such as React.
We'll put these under Requirements.
Skills: Additional Skills and Nice to Have.
Additional Skills:
- Background in DevOps practice
- Strong understanding of database design (both SQL and NoSQL)
- Experience with containerization (Docker) and orchestration
- Knowledge of authentication/authorization patterns (OAuth, JWT)
- Understanding of microservices architecture and distributed systems
- Proficiency with Git and CI/CD pipelines
- Experience with monitoring, logging, and performance optimization
Nice to Have:
- TypeScript
- Experience with event-driven architectures and message queues
- Knowledge of caching strategies (Redis, CDN)
- Background in DevOps practices (duplicate? but okay)
We'll combine.
Qualifications section:
- 4+ years of backend development experience
- Bachelor’s Degree in Computer Science
- Proven track record of building and scaling production applications
- Strong problem-solving abilities and attention to detail
- Experience mentoring junior developers
- Demonstrated ability to use AI tools responsibly to enhance productivity
Also note about AI-assisted development: "We embrace AI-assisted development and expect our engineers to leverage these tools effectively. You should be comfortable using AI coding assistants (like GitHub Copilot, Claude, or similar tools) to accelerate development while maintaining code quality and security standards. Experience integrating AI capabilities into applications (OpenAI API, Claude API, or AWS Bedrock) is a plus. We value engineers who can critically evaluate AI-generated code, understand when to use these tools, and when human expertise is essential."
That could be part of Qualifications or maybe Skills. But we have Qualifications already; we could add a bullet about AI tools. However the Qualifications bullet list already includes "Demonstrated ability to use AI tools responsibly to enhance productivity". The paragraph about AI could be added as extra prose under Qualifications.
We'll include that as a
under Qualifications. Benefits: The "What do we offer?" list includes many items. We'll extract each as
- .
List:
- 🏠 We are a hybrid company. All team members at Auctane in Austin come into the office Tuesdays, Wednesdays and Thursdays.
- 🛬Take the reins of your time off with our Flex Time Off policy – because work-life balance should always be in your hands!
- 🌅 We offer 12 paid holidays for all of our US employees!
- 💰401k employer matching program – because your future deserves a friendly boost!
- ⭐️We conduct annual merit reviews to recognize and reward your hard work and achievements.
- 🏟️ Company events, we work hard, play hard! We do our best every day, even at our regular team-building events.
- 🏢 Attractive office space in the heart of central Austin, Texas (free drinks, snacks…).
- 🍽Indulge in weekly catered lunches at our office – a delicious perk to fuel your work.
- 🏐 Health and Wellness: The well-being of our team is super important to us. Choose from different options that include medical, dental, and vision plans.
- 🏋🏾♀️Fitness center in the office with Tonal Mirrors, Pelotons, free weights, etc.
- 🧠Employee Assistance Program. We offer up to 8 free mental health sessions.
- 💪🏽We offer gym discounts to help you stay fit and healthy!
- 📚We offer education reimbursement to all employees, ensuring that you can pursue your educational goals while excelling in your career with us. Invest in your future and let us support your growth every step of the way.
- 🔗 Employee Referral Program! We reward employees helping us find top talent!
- 💜 An inclusive, casual and upbeat work environment. The personality and opinions of each of our team members are important and valid; we aim to offer all employees a safe environment where they can be themselves and thrive.
We'll keep these as benefit items.
Schedule: We have hybrid schedule info. Could be separate Schedule section: "This position is hybrid (3 days per week in office - Tuesday through Thursday) and is located in Austin, TX." Also benefits mention hybrid. We'll put schedule details.
We should not repeat same info in both Benefits and Schedule? It's okay but we can keep schedule separate with just the hybrid and location.
We must not include boilerplate like Equal Opportunity Employer, etc. Also remove "Additional Position Duties:" list (the ergonomic stuff) as it's not a section heading we have; but it's substantive? It's about physical demands. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Should we keep that? It's not under a heading we have; but we could include it under Responsibilities? Not really. It's additional position duties. Could be part of Responsibilities? Might be considered responsibilities but it's about physical requirements. The instruction says use headings for sections only if posting has real specific content. It does have content: list of physical demands. Could we create a section like "Additional Position Duties"? Not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. Physical demands could go under Responsibilities? Not exactly. Could go under Requirements? Not really. Could go under Qualifications? Not. Could go under Skills? Not. Could go under Benefits? Not. Could go under Schedule? Not. Could go under About the role? Not.
But we could incorporate them into Responsibilities as a bullet? The instruction says preserve ALL substantive information. If we cannot fit into allowed headings, maybe we need to create a section despite not in list? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. And they say "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we must decide if physical demands content is substantive enough to warrant a section. Since there is no appropriate heading, maybe we drop it? But that would lose substantive info. However maybe it's considered boilerplate? It's not typical boilerplate but it's a list of physical demands. Could be considered part of Responsibilities? Might be okay to include under Responsibilities as a bullet: "Additional Position Duties: ..." but that's a heading inside a list? Might be okay. We could add a
- under Responsibilities: "Additional Position Duties: Sit for prolonged periods of time; Utilize wrist and hands for a prolonged period of time; Walk short distances; Stand for short periods; Speaking and conversing with others; Lift up to 25lbs without assistance up to chest height."
That preserves info.
Now we need to ensure we don't include duplicated lines. Check duplicates: The hybrid schedule appears both in About the role and Benefits. We'll keep both but maybe it's okay. Could deduplicate by only mentioning in Benefits? But About the role also includes location. We'll keep both but maybe it's okay.
Now produce HTML.
Structure:
About the role
... (the paragraph)
Responsibilities
- ... each bullet ...
Requirements
- ... each