Software Development Engineer
for section headings.
Use - for any list of duties/requirements/benefits.
Use
for prose.
We need to preserve all substantive information.
Let's extract content.
About the role paragraph: "We're rebuilding our architecture from the ground up, and we're looking for a Software Development Engineer to help shape it. You'll design, build, and ship scalable cloud-native applications with a focus on AWS serverless, event-driven architecture, and TypeScript/Node.js, while drawing on solid experience with traditional application architectures too."
Who You Are and What You'll Do maybe also part of About the role? But we have Responsibilities separate for duties. The "Who You Are" is more about traits; could be part of About the role or maybe we could include in About the role as prose. The instruction: About the role heading for section headings (e.g. About the role...). So we can put the descriptive paragraphs under About the role.
Thus About the role content: combine the paragraphs: "We're rebuilding our architecture from the ground up, and we're looking for a Software Development Engineer to help shape it. You'll design, build, and ship scalable cloud-native applications with a focus on AWS serverless, event-driven architecture, and TypeScript/Node.js, while drawing on solid experience with traditional application architectures too." plus "Who You Are..." and "What You'll Do..." maybe.
But we need to avoid too much duplication with Responsibilities. The "What You'll Do" is similar to duties. Might be better to put that under Responsibilities. However the "What You'll Do" paragraph is a high-level overview; the "Major Duties and Responsibilities" is detailed list. We could put the overview under About the role and the detailed list under Responsibilities.
Thus:
About the role: includes first paragraph and maybe "Who You Are" description.
Let's capture "Who You Are": "You're a hands-on engineer with a curious streak. You've opened up a codebase, asked "why does it work like this?", and then actually gone and found out. You're equally comfortable with serverless and traditional architectures, and you know when each one is the right tool. You enjoy hard problems, ambiguous requirements don't rattle you, and you care about how your code connects to the business it serves. When you dig into an existing system, you can tell the difference between what the business actually needs and what someone bolted on years ago as a workaround."
We'll put that as prose under About the role.
Now Responsibilities: the "Major Duties and Responsibilities" list. It's a series of sentences each starting with a verb. We'll turn each into
- .
List items:
- Help shape our new architecture from the ground up, choosing between serverless, containerized, and traditional approaches, and between monolithic and microservice designs, based on what each problem actually needs
- Design, develop, test, and maintain scalable, cloud-native applications using AWS and modern software development practices
- Build serverless and event-driven systems using AWS services including Lambda, API Gateway, SQS/SNS, EventBridge, and Step Functions, as well as ECS and Docker containers
- Apply distributed-system patterns such as pub/sub, saga, idempotency, retries and dead-letter queues, and CQRS to build reliable and resilient systems
- Develop infrastructure as code using AWS CDK and/or SAM
- Build backend services and applications using TypeScript/JavaScript and Node.js
- Design and work with both relational SQL databases and NoSQL databases, including DynamoDB
- Apply strong software engineering fundamentals, including data structures, algorithms, complexity analysis, software design patterns, SOLID principles, and separation of concerns
- Use sound judgment when applying design patterns, recognizing when a pattern improves maintainability and when it introduces unnecessary complexity
- Participate in Git-based development and pull-request workflows, including code reviews and collaborative problem solving
- Build and maintain CI/CD pipelines and automated testing, including unit, integration, and characterization testing
- Analyze existing applications and workflows to understand their business logic, identify the true business rules, and translate them into modern cloud-native designs
- Design integrations between new services and existing applications and platforms, including data synchronization and migration between database platforms
- Monitor and troubleshoot applications using AWS observability tools such as CloudWatch and X-Ray, along with structured logging and other appropriate practices
- Apply sound IAM and cloud security fundamentals when designing and implementing AWS solutions
- Collaborate with technical and non-technical stakeholders to clarify requirements, explain trade-offs, and make practical decisions
- Stay current with emerging development tools, including AI-assisted coding and AI application development, and apply them thoughtfully with appropriate review and testing
- Contribute to LLM-powered applications, including RAG pipelines, vector search, MCP servers, agent tooling, and evaluation of LLM output quality, as applicable to business needs
- Contribute across the technology stack as needed, including frontend development, infrastructure, data, and direct interaction with users
Now Requirements: Required qualifications.
List:
- 5+ years of professional software development experience and a bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related field; equivalent education and experience may be considered
- Hands-on experience building AWS serverless and event-driven applications, including Lambda, API Gateway, SQS/SNS, EventBridge, Step Functions, ECS, and Docker
- Experience designing and building with both serverless and traditional application architectures, and the judgment to know when each is the right fit
- Strong experience with TypeScript/JavaScript, Node.js, SQL, and NoSQL databases such as DynamoDB
- Strong foundation in data structures, algorithms, complexity, software design patterns, SOLID principles, and separation of concerns
- Experience with AWS CDK/SAM, Git, pull-request workflows, CI/CD, and automated testing
- Understanding of distributed systems, microservices, and resilient architecture, including pub/sub, idempotency, retries, dead-letter queues, saga, and CQRS
- Ability to work effectively with existing systems, including reverse-engineering business logic and using characterization testing to capture current behavior
Now Qualifications: Preferred qualifications.
List:
- Experience with React/Next.js, Python, Java, AWS observability and security, and software development in healthcare or other regulated industries
- Experience integrating new cloud-native services with established applications, including data synchronization and migration between platforms
- Experience using AI coding tools effectively and critically reviewing generated code
- Experience building LLM-powered applications, including RAG, embeddings/vector search, MCP servers, agent tooling, and LLM evaluation
- Familiarity with C#/.NET, Angular, Azure, Jira, and Confluence
Now Benefits: list from "Compensation & Benefits" section.
List:
- Market-based competitive wage
- Bonus potential
- 401(k) with employer contribution
- Medical, dental and vision insurance
- Company-paid life insurance
- Wellness program
- Onsite gym
- Paid time off
- Holiday & Floating holiday
- Casual work environment
- Employee assistance program
- Free DUTCH Tests
- …and more! (we can keep "and more!" as part of last item or separate.)
We should not include vague "Market-based competitive wage" if we are omitting Pay section; but it's in Benefits list. It's okay to keep as benefit item.
Now we need to output HTML fragment.
Structure:
About the role
... paragraphs ...
Maybe we need separate for each paragraph.
for prose. We need to preserve all substantive information. Let's extract content. About the role paragraph: "We're rebuilding our architecture from the ground up, and we're looking for a Software Development Engineer to help shape it. You'll design, build, and ship scalable cloud-native applications with a focus on AWS serverless, event-driven architecture, and TypeScript/Node.js, while drawing on solid experience with traditional application architectures too." Who You Are and What You'll Do maybe also part of About the role? But we have Responsibilities separate for duties. The "Who You Are" is more about traits; could be part of About the role or maybe we could include in About the role as prose. The instruction: About the role heading for section headings (e.g. About the role...). So we can put the descriptive paragraphs under About the role. Thus About the role content: combine the paragraphs: "We're rebuilding our architecture from the ground up, and we're looking for a Software Development Engineer to help shape it. You'll design, build, and ship scalable cloud-native applications with a focus on AWS serverless, event-driven architecture, and TypeScript/Node.js, while drawing on solid experience with traditional application architectures too." plus "Who You Are..." and "What You'll Do..." maybe. But we need to avoid too much duplication with Responsibilities. The "What You'll Do" is similar to duties. Might be better to put that under Responsibilities. However the "What You'll Do" paragraph is a high-level overview; the "Major Duties and Responsibilities" is detailed list. We could put the overview under About the role and the detailed list under Responsibilities. Thus: About the role: includes first paragraph and maybe "Who You Are" description. Let's capture "Who You Are": "You're a hands-on engineer with a curious streak. You've opened up a codebase, asked "why does it work like this?", and then actually gone and found out. You're equally comfortable with serverless and traditional architectures, and you know when each one is the right tool. You enjoy hard problems, ambiguous requirements don't rattle you, and you care about how your code connects to the business it serves. When you dig into an existing system, you can tell the difference between what the business actually needs and what someone bolted on years ago as a workaround." We'll put that as prose under About the role. Now Responsibilities: the "Major Duties and Responsibilities" list. It's a series of sentences each starting with a verb. We'll turn each into
About the role
... paragraphs ...
Maybe we need separatefor each paragraph.