Software Engineer (New Grad)

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Team And How We Work", "A Few Ways We’re Different", "What You'll Do", "What You'll Need", "Our Tech Stack", "Our Interview Process", "Our Benefits", "Hybrid Vs. Remote Approach". Also maybe "About The Team And How We Work" could be considered "About the role"? But we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The posting does not have explicit Pay or Schedule specifics (just hybrid approach description). It does have Benefits described. It does have Responsibilities (What You'll Do). It does have Requirements/Qualifications/Skills (What You'll Need, Our Tech Stack maybe). It does have Benefits. It does not have explicit Pay or Schedule (though hybrid approach mentions schedule but not specific). According to rules: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits is stated, so we can include Benefits. Pay not stated, so omit. Schedule: they talk about hybrid approach but not explicit schedule like "full-time", "part-time". Might be considered schedule info? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state hybrid approach and remote expectations, which is schedule-related. Could be considered schedule content. However they said "Hybrid Vs. Remote Approach" describing expectation. That is schedule-related. So we could include a Schedule section with that content. But we need to use heading

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. We need to map content to appropriate sections. We have: - About the role: could be the introductory paragraph about Miter mission etc. Or "About The Team And How We Work" maybe fits About the role. We'll put that under About the role. - Responsibilities: "What You'll Do" - Requirements: maybe "What You'll Need" (0-1 years experience, problem solving, growth mindset, work ethic, team-oriented). Also "Our Tech Stack" could be Skills or Requirements. We'll treat Skills as separate maybe. - Qualifications: maybe same as Requirements? Could combine. But we need to avoid thin sections. Perhaps we can have Requirements (includes experience, skills) and Qualifications (maybe education? none). Better to have Requirements and Skills separate. - Skills: "Our Tech Stack" (React + React Native, Node/Express, MongoDB, Render, Check, Stripe (Issuing, Treasury), Typescript). Also maybe "Strong problem-solving skills" etc but those are more requirements. - Benefits: list of benefits. - Schedule: Hybrid Vs. Remote Approach description. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, AI hiring process, Talent Community, Equal Opportunity, etc. Also remove navigation, cookie, legal, duplicated lines. We must preserve all substantive information. So we need to keep the mission description, team culture, ways we're different, responsibilities, requirements, tech stack, interview process, benefits, hybrid approach. We must not invent or summarize away detail. Keep specifics. We need to output only HTML fragment, no markdown fences. We'll structure:

About the role

... mission description ...

Maybe also include "A Few Ways We’re Different" as part of About the role? Could be separate section but we only have allowed headings. Could incorporate into About the role paragraph. But we must preserve all substantive information; we can include multiple paragraphs under About the role. Similarly, Responsibilities:

Responsibilities

• Design, build, and maintain products/systems that power our core platform.
... etc. Requirements:

Requirements

• 0-1 years of professional software development experience.
... etc. Skills:

Skills

• React + React Native
... etc. Benefits:

Benefits

... each benefit. Schedule:

Schedule

Hybrid Vs. Remote Approach ...

Interview Process: Not in allowed headings list but we could maybe put under Requirements? But we should not create extra headings not listed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map all content to those headings. Interview Process could go under Requirements or Skills? Maybe under Requirements as part of "What You'll Need"? But it's separate. Could incorporate into Requirements as a bullet: "Our interview process includes: Recruiter Intro, technical screen, virtual onsite, practical coding exercise, Miter values with Engineering leader." That seems okay. Similarly, "A Few Ways We’re Different" could go under About the role. We must not create Pay section. Now let's extract content. Intro paragraph: "A Better Built World At Miter, we’re on a mission to help construction contractors build with confidence. If we’re successful, we’ll make it easier and faster to build critical physical infrastructure - roads, bridges, utilities, data centers, housing, etc. For decades, construction and field services contractors have had to run their businesses on outdated software: clunky, on-premise systems created in the 1980s and 1990s. That’s where Miter comes in. We’re using AI and embedded payments to rebuild the core HR, finance, and operations systems that underpin our physical economy. Using Miter, contractors like Marathon Electrical, W.J. O’Neil, and Truebeck Construction are building stronger teams, controlling job costs, and accelerating jobsite execution. This idea is resonating. Since we launched in 2021, we’ve grown to thousands of customers and tens of millions in ARR, making us one of the fastest growing vertical software companies ever. To double-down on our momentum, we’ve raised $50M+ from top investors (Bessemer, Coatue, and Battery) who share our belief that we’re just getting started." Then "About The Team And How We Work" paragraph: "Building the OS for the built world is no small feat. We’ll need to ship a LOT of high quality code in the coming years, and to do so, we’re building an engineering culture centered around craft, ownership, and collaboration. >25% of our engineers and product managers are ex-founders, and we hire for slope, not intercept. Being a place where you can just build things requires talent density and some unique ways of doing things." Then "A Few Ways We’re Different" bullet points (starting with "> No rules…rules:" etc). We'll need to preserve each bullet. Let's list them: - No rules…rules: Many engineering teams design processes and rules around the lowest common denominator. Not us! We trust brilliant engineers to deliver magical customer outcomes and introduce processes and rules only when necessary. - Full-full-stack: Our technology stack (TypeScript everywhere!) and processes are designed to encourage engineers to run their projects end-to-end. This usually involves writing technical blueprints, implementing full-stack solutions, and talking to customers directly to get feedback. - Lean and AI-native: AI is turning 10x engineers into 100x engineers. We believe lean, talent-dense, AI-native teams will outship much larger teams with less talent density. - Blueprints and building blocks: One of our core Miter values is “build the blueprint”. Writing things down clarifies our thinking and aligns our teams. This also applies to building fundamental building blocks and abstractions that make developers’ lives easier. - We feel our customers’ pain and celebrate their success: We encourage engineers to build direct relationships with customers, feel their pain, and celebrate their success. We love fast feedback loops. - We’re meritocratic: We value results and hard work. We reward engineers who consistently ship and deliver for customers with increased scope and compensation. We need to keep the "> "? The original had "> No rules…rules:" etc. Probably the > is just markdown blockquote. We'll drop the > and keep the text. Now Responsibilities: "What You'll Do" bullet points: - Design, build, and maintain products/systems that power our core platform. - Collaborate with product managers and other engineers to deliver high-quality experiences. - Actively participate in blueprinting, code reviews, and technical documentation for your team. Now Requirements: "What You'll Need" bullet points: - 0-1 years of professional software development experience. - Strong problem-solving skills. - A growth mindset and curiosity to understand business context and user needs. - Strong work ethic and reliability when owning tasks and deliverables. - A team-oriented attitude with humility and openness to new ideas. Now Skills: "Our Tech Stack" list: - React + React Native - Node/Express - MongoDB - Render - Check - Stripe (Issuing, Treasury) - Typescript Now Benefits: list: - Competitive Compensation: We offer competitive (well above “market”) salary, commission, and equity packages. - Medical Insurance: Comprehensive medical, dental, FSA, vision plans to suit you and your family’s needs. - 401(k) Retirement Plan: Company-matched contributions to help you plan for your future. - Flexible PTO: Take the time you need to recharge and be your best self. - Parental Leave: Generous 16-week paid leave for all parents, including adoptive and foster parents. - Learning & Development: We offer every employee an annual educational allowance to explore external professional development. - Office Extras: Snacks, coffee, lunch, and commuter benefits for in-office Mitosaurs. - Community: Company-wide and team-specific off-sites per year. Now Schedule: "Hybrid Vs. Remote Approach" paragraph: We believe the magic of Miter comes from working side by side. We also believe in work flexibility. For roles that are listed as hybrid, our approach is 3 days a week in the office giving us the chance to connect, brainstorm, and build stronger relationships. If you live within a reasonable commute to either our New York City or San Francisco offices, we ask that you work in our hybrid approach. Otherwise, for roles listed as remote or in other cities where we don't have an office location, there is no requirement to work in our hybrid approach. We do travel a few times a year for onboarding, company-wide and team specific off-sites! Now Interview Process: we need to embed somewhere. Could be under Requirements as a bullet list: "Our Interview Process: Recruiter Intro, technical screen where we pair on a real-life problem, (virtual) onsite!, Practical coding exercise, Miter values with Engineering leader." We'll include that as a bullet under Requirements maybe. Now we must ensure we don't include boilerplate: EEO, AI hiring process, Talent Community, Equal Opportunity, etc. Remove those paragraphs. Now produce HTML. We'll wrap each section in

and then

or

• . Make sure to not include extra whitespace? It's fine. Let's craft. Note: Use proper escaping for apostrophes? Not needed. We'll output:

  About the role

  A Better Built World At Miter, we’re on a mission to help construction contractors build with confidence. If we’re successful, we’ll make it easier and faster to build critical physical infrastructure - roads, bridges, utilities, data centers, housing, etc. For decades, construction and field services contractors have