Junior Full Stack Software Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, etc. Only include sections with real content. We need to parse the posting. Location: Fully Remote (USA) · Timezone-aligned Compensation: 80k–100k + Equity + Quarterly Performance Bonuses Mission: paragraph. The Opportunity: paragraph. The Role: Code at the Speed of Thought: description of work. What We’re Looking For: bullet list of requirements. How We Work: paragraph. The Stack: list. Why Join Lumion Now?: bullet list of metrics. Remote First: paragraph. Compensation and Benefits: bullet list. We need to map to sections: About the role (maybe mission + opportunity?), Responsibilities (the role description), Requirements (what we're looking for), Qualifications (maybe degree requirement?), Skills (stack?), Benefits (compensation and benefits), Pay (salary range), Schedule (remote first overlapping hours). Also maybe "About the company" but not needed. We must not repeat job title as heading. No job ID. We must not include boilerplate like EEO, etc. Not present. We must not include application instructions (the golden banana thing) - that's application instruction, remove. We must not include duplicated lines. We need to preserve all substantive info. Let's extract content. Mission paragraph: "Many businesses still depend on disconnected software, spreadsheets, manual processes, and knowledge trapped inside individual employees’ heads. Lumion brings those systems and processes together so organizations can operate more intelligently and efficiently. We are starting with trade and technical schools. Our platform powers the entire institution, from the first lead through enrollment, tuition payments, compliance reporting, graduation, and career tracking. These schools prepare electricians, welders, nurses, technicians, and other skilled professionals who keep the country moving. By modernizing their operations, Lumion helps them serve more students and strengthen the skilled workforce." Opportunity paragraph: "This is a place to launch your career at the cutting edge of software development. You will learn how coding will be done in the future and become part of the wave changing how software is created. Our stack and development processes are AI First. Claude Code and Codex are part of our normal workflow, with access to the latest frontier models without having to ration tokens or worry about usage limits. You will learn the workflows, judgment, and verification practices required to use these systems effectively and become a 100x developer. Working at a startup also gives you the opportunity to wear different hats and see problems from engineering, product, customer, and business perspectives. You will gain experience that is difficult to find when working inside one narrow area of a larger company. If you want a fast moving environment, the excitement of solving new problems, and the chance to look back proudly on helping build something significant, this is that opportunity." The Role paragraph: "Your work will span backend business logic, data models, APIs, integrations, administrative workflows, customer facing interfaces, and automated tests. You will be a full member of the engineering team from day one and trusted with meaningful production work. Important assignments are not reserved for people with longer résumés. You will be held to the same standards for quality, communication, and follow through as every other engineer at Lumion." What We’re Looking For bullet list: - Professional software engineering experience is not required. - A Bachelor’s degree in Computer Science is required. The degree must be completed before your employment begins. Current students may apply if they will graduate before their start date. - Evidence that you have put your programming skills into practice. This can come from a capstone, internship, personal project, open source contribution, research project, freelance engagement, or another hands on project. We want to understand what you worked on, what you personally contributed, and what you learned. - Confidence in at least one programming language. You can build with it, debug it, and explain the logic behind your decisions. The language does not need to be PHP, and prior Laravel experience is not required. - An understanding of web development fundamentals. You are familiar with concepts such as HTTP, APIs, authentication, databases, browser interfaces, version control, and automated testing. - Logical problem solving. You can break an unfamiliar problem into manageable parts, investigate failures systematically, and work toward the underlying cause. - Product judgment. You consider the person using the software and connect technical decisions to the problem being solved. How We Work paragraph: "Lumion is a high trust team. We share context openly, keep our egos low, raise risks early, and ask questions when something does not make sense." The Stack bullet list: - Application: PHP 8.4+, Laravel 12+, Livewire, Filament, Blade, JavaScript, and Tailwind CSS - Data: MySQL, Redis, pgvector, and Pinecone - Testing: Pest PHP Why Join Lumion Now? bullet list: - Lumion closed a $10.7 million seed round backed by TTV Capital and Tusk Venture Partners. - More than 400 career schools use our platform to support over 150,000 students across 48 states and 29 industries. - Schools using Lumion see 47% more completed applications, a 73.6% application to enrollment rate, 91% on time tuition collection, and 21% higher student retention. - We have the capital and momentum to build something that lasts while remaining early enough for every engineer to influence the product and company. Remote First paragraph: "This is a full time remote position. You must reside in and be authorized to work in the United States. Your normal workday must overlap by at least six hours with our Salt Lake City team." Compensation and Benefits bullet list: - Salary: $80,000 to $100,000 USD - Equity: Meaningful stock options - Bonuses: Quarterly performance based cash bonuses - Time Off: Unlimited paid time off - Retirement: 401(k) - Health: Health, dental, and vision reimbursement up to $537.50 per month - Technology: $200 monthly technology stipend - Wellness: $100 monthly wellness stipend Now we need to decide sections. Possible sections: - About the role (maybe combine Mission + Opportunity? Could be "About the role" describing what the company does and the opportunity). The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings. We need to include sections only when posting has real specific content. We have content for: - About the role: could be mission + opportunity (description of company and role). We'll put mission and opportunity paragraphs under About the role. - Responsibilities: The Role paragraph (work span). Could be responsibilities. - Requirements: What We’re Looking For list (requirements). Could be requirements. - Qualifications: maybe degree requirement? But that's already in requirements. Could separate Qualifications: Bachelor's degree in Computer Science required. But we can also put under Requirements. However we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But instructions list them as possible headings; we can choose to include only those with substantive content. We have both Requirements (list) and Qualifications (degree). Could make Qualifications heading with degree requirement. But the degree is also in the list; we could keep it under Requirements and not have Qualifications. That's fine. - Skills: The Stack list (technologies). Could be Skills. - Benefits: Compensation and Benefits list (benefits). Could be Benefits. - Pay: Salary range (maybe separate). Could be Pay. - Schedule: Remote First paragraph (overlap requirement). Could be Schedule. We need to avoid filler like "commensurate with experience". Not present. We must not include application instructions (golden banana). Remove. We must not include duplicated lines. Now produce HTML fragment. Structure:

About the role

Mission paragraph

Opportunity paragraph

Responsibilities

Role paragraph

Requirements

• Professional software engineering experience is not required.
• A Bachelor’s degree in Computer Science is required. The degree must be completed before your employment begins. Current students may apply if they will graduate before their start date.
• Evidence that you have put your programming skills into practice. This can come from a capstone, internship, personal project, open source contribution, research project, freelance engagement, or another hands on project. We want to understand what you worked on, what you personally contributed, and what you learned.
• Confidence in at least one programming language. You can build with it, debug it, and explain the logic behind your decisions. The language does not need to be PHP, and prior Laravel experience is not required.
• An understanding of web development fundamentals. You are familiar with concepts such as HTTP, APIs, authentication, databases, browser interfaces, version control, and automated testing.
• Logical problem solving. You can break an unfamiliar problem into manageable parts, investigate failures systematically, and work toward the underlying cause.
• Product judgment. You consider the person using the software and connect technical decisions to the problem being solved.

Skills

• Application: PHP 8.4+, Laravel 12+, Livewire, Filament, Blade, JavaScript, and Tailwind CSS
• Data: MySQL, Redis, pgvector, and Pinecone
• Testing: Pest PHP

Benefits

• Time Off: Unlimited paid time off
• Retirement: 401(k)
• Health: Health, dental, and vision reimbursement up to $537.50 per month
• Technology: $200 monthly technology stipend
• Wellness: $100 monthly wellness stipend

Pay

Salary: $80,000 to $100,000 USD

Equity: Meaningful stock options

Bonuses: Quarterly performance based cash bonuses

Schedule

This is a full time remote position. You must reside in and be authorized to work in the United States. Your normal workday must overlap by at least six hours with our Salt Lake City team.

Check if any content duplicated: The mission and opportunity paragraphs are separate; we included both under About the role. Good. We omitted How We Work paragraph and Why Join Lumion Now? metrics. Those are substantive; we should include them somewhere. Could be under About the role as additional paragraphs, or maybe a separate section like "Company Overview". But headings list does not include Company Overview; we could add under About the role. The instructions: use headings for those examples, but we can also include other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should stick to those. So we need to fit all substantive content into those sections. We have How We Work and Why Join Lumion Now? metrics. Where to put? Could be under About the role as additional paragraphs. That seems appropriate: About the role can include company mission, opportunity, how we work, why join. Thus About the role will have multiple paragraphs: mission, opportunity, how we work, why join. Let's extract How We Work paragraph: "Lumion is a high trust team. We share context openly, keep our egos low, raise risks early, and ask questions when something does not make sense." Why Join Lumion Now? bullet list: we have four bullet points. We'll