- Company Name
- Via
- Job Title
- Full Stack Software Engineer, Remix by Via
- Job Description
-
<think>
Okay, let's see. The user wants me to normalize a job description into a concise mini-job profile for job matching. They specified excluding certain details like company info, location, benefits, and fluff. The output needs to include only the job title, role summary, expectations, key responsibilities, required skills, and education/certs. Also, it should be factual, concise, and ATS-friendly.
First, I need to parse the original job description. The job title is "Full Stack Software Engineer, Remix by Via" but the user wants to convert that into a standard title, so probably just "Full Stack Software Engineer". Then the role summary. The original job description starts with Via's mission, which is important to include in the role summary because it's about public transportation systems. They want the engineer to build software cities use for public transit, focusing on access, equity, sustainability.
Next, expectations. The original says they work on improving planning products, partner with designers and product managers, own features end-to-end, use specific tech stack but care more about fundamentals and user-centered approach. Key responsibilities would be the bullet points under "About the Role": improving planning products, working with customers to understand needs, using various technologies for projects, contributing to engineering practices and architecture, building processes and tools.
Required skills: 4+ years professional software engineering, full-stack user-centric dev. Mission-driven. User-centric (talk to customers). Collaborative, humble, empathetic, feedback-driven. Experience with React and geospatial tech are pluses, but not required. Education: probably a bachelor's in computer science or related? Since they mention required education and certifications, but the original doesn't specify, maybe leave that blank unless inferred.
Wait, the original job description under "About You" doesn't mention education or certifications, so maybe just exclude that part. Skills are the main focus here. The user wants required education and certifications as separate fields. If it's not mentioned, maybe leave it as "Bachelor's degree in computer science or related field" but the original doesn't say that. Hmm, but the user said to exclude fluff. The original doesn't state education, so maybe it's not required to include. Or maybe assume the standard for such a role. But since the user says to be factual and exclude fluff, maybe just leave it out unless specified. Let me check the job description again. The original "About You" doesn't mention education or certs, so perhaps that section shouldn't be included. But the user wants to see that in the output. Wait, the user's instruction says to include "Required Education & Certifications". So maybe infer that a bachelor's degree is required, as it's common for software engineering roles. But the original didn't state it, so perhaps better to omit it unless specified. Alternatively, maybe the user wants to include it if it's in the job description. Since it's not there, perhaps leave it blank or note that it's not specified. However, the user wants it to be factual. So if the job description doesn't mention education or certs, then we shouldn't add it. Therefore, maybe omit that section or put something like "Not specified". But the user's example might have it. Let me check the example. In the problem statement, the user provided an example output which includes education, but in the given job description, it's not there. Wait, the user's example is the one they're giving us to solve. The example given in the problem is the job description to be converted. So the original job posting doesn't mention education or certifications, so we should not include that. But the user's instruction says to include "Required Education & Certifications". Hmm, perhaps in that case, if the original job doesn't mention it, we just leave it blank. But the user's output requires that field. So maybe, in the absence of the job description mentioning education or certifications, just write "Not specified" or leave it as a blank. However, the user's instruction says to exclude fluff. Maybe better to leave it as is, not include it if not present. But the user might want that section to be present regardless. Since the user says to include all those sections, perhaps if education or certifications aren't mentioned in the job description, we can note that. Alternatively, perhaps assume that a bachelor's degree is a standard requirement for such a role and include that. But since the job description doesn't mention it, that could be considered adding fluff. So better to not include it and leave it as "Not specified" or omit that section. However, looking at the example from the user (the sample input and output), perhaps I should check. The original job description here does not mention education or certifications. So in the output, perhaps "Required Education & Certifications" would be omitted. But the user wants to output all the sections: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So if the original doesn't mention education or certifications, then that section would be absent. However, the user might expect to include a standard assumption. Alternatively, perhaps the user wants that section to be present, so in the absence of info, we can write "Not required" or similar. Alternatively, maybe the original job has a minimum requirement not stated. But since the user is to extract only what is there, maybe just exclude that line. However, the user's instruction says to provide all the sections. So in this case, perhaps just leave it as a blank bullet point or not include it. But the user's example output might have it. Since the user hasn't given an example output, I have to make a judgment. Perhaps in the absence of explicit information, the "Required Education & Certifications" section can be omitted. However, the user's instruction says to include it, so perhaps even if not specified, we have to include that section. If there is no information, perhaps write "Not specified" under that section. Let me proceed with that.
Now, compiling the information.
Job Title: Full Stack Software Engineer
Role Summary: Develop software for public transportation systems focused on access, equity, and sustainability. Collaborate with cross-functional teams to build user-centric digital tools for modern transit planning.
Expectations: Own features end-to-end; work on improving planning products for data-driven decisions; deliver end-to-end user experiences; contribute to engineering best practices and maintain high productivity/code quality.
Key Responsibilities:
- Enhance planning products to support transit planners' decisions using data.
- Collaborate with customers to identify and address user needs.
- Utilize various technologies across the stack to deliver user experiences.
- Participate in engineering best practices and architectural discussions.
- Develop and maintain processes and tools to ensure productivity and code quality.
Required Skills:
- 4+ years of professional software engineering experience, preferably full-stack.
- Strong full-stack fundamentals, user-centered approach.
- Mission-driven with passion for values and purpose.
- User-centric, engaging with customers to solve core needs.
- Collaborative traits: humble, empathetic, feedback-driven.
- Experience with React (plus) and geospatial/mapping technologies (plus).
Required Education & Certifications: Not specified in the job description.
Wait, but the user wants it in English, concise, and within 500 words. Also, need to make sure it's ATS-friendly, meaning using proper keywords like React, Typescript, etc., which the original tech stack mentions. However, the job description says they use Typescript, React, Rails, Python, Postgres with PostGIS, but they value strong fundamentals over specific tools. So maybe in the required skills, mention strong full-stack fundamentals. But the job description does mention that experience with React is a plus. However, the user wants required skills. Since React is a plus but not required, perhaps mention it as a plus under "Key Responsibilities" or "Required Skills". However, in the "Required Skills" section, we should only list what's required, not the pluses. So the plus items might go under "nice to have" but the user's instructions don't mention that. Wait, the user says "Required Skills", so only required skills. So the React and geospatial experience are pluses, not required. Therefore, perhaps not include them in the required skills. However, the original job says "Experience in developing complex React applications is a plus, but not required". But in the "About You" section, the required skills are 4 years and full-stack. So the required skills are the 4 years in software engineering, preferably full-stack. So the Required Skills would be:
- 4+ years full-stack software engineering experience (preferably user-centric)
Then under Required Skills, list the main ones needed. Also include the soft skills like mission-driven, user-centric, collaborative traits.
Also, need to make sure to use bullet points or just commas? The example from the user probably uses bullet points. Since the user says "output only: [sections]" so in the format they want, perhaps bullet points separated by commas. However, looking at the example they might have bullet points. Let me check the example again. The user hasn't provided an example output, but given the instruction, I need to structure each section as bullet points. Wait, no. The user says "concise summary for job matching. Max 500 words. Exclude... Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications. Keep it factual, concise, ATS-friendly, and globally neutral. Do not add any introduction, explanation, or extra text."
So each section's content should be a brief statement, not necessarily bullet points. For example, "Role Summary" would be a sentence or two. "Expectations" might be a list of bullet points, but the user didn't specify. However, the example