- Company Name
- Roundtable
- Job Title
- Développeur·se Senior Full-stack - Toulouse (H/F)
- Job Description
-
<think>
Alright, I need to normalize this job description into a concise mini-job profile. The user wants it in English, translated if needed. Let me start by reading through the original job posting carefully.
First, the job title is "Développeur·se Senior Full-stack - Toulouse (H/F)". Translating that gives "Senior Full-Stack Developer". I should omit location, so just "Senior Full-Stack Developer" as the title.
Next, the role summary. The company is looking for someone to join their tech team, emphasizing collaboration across product and business teams. They're building a premium platform for co-investing in private equity. I need to summarize that into one sentence. Maybe: "Lead development of a premium private equity co-investment platform, collaborating across tech, product, and business teams to drive strategic and technical decisions."
Expectations section lists their responsibilities. It mentions collaborating at the tech and business level, contributing to strategic decisions, developing and deploying features, code reviews. Need to condense these into a few bullet points. Let's see. The main points here are strategic collaboration, sustainable decisions, full-stack development, and knowledge sharing.
Key Responsibilities include specific challenges like capital table management, multi-country compliance, multi-asset platform, financial operations, real-time dashboards, automation, security. These are the technical challenges. I should convert these into key responsibilities, listing them concisely.
Required skills: 5+ years TypeScript full-stack, PostgreSQL and ORMs (Prisma nice to have), financial calculations and decimal precision, GraphQL (Apollo/Yoga). Also soft skills like reliability, handling demanding topics, sustainable choices, explaining tech to non-technical people. Important to list the required skills and separate from the bonuses.
Education and certifications: The job mentions no specific requirements beyond experience, so maybe just "N/A".
I need to check the word count. The user wants it under 500 words and ATS-friendly. Also, exclude company details, location, benefits. Make sure all the technical jargon is correctly included but in a more concise form. For example, the stack includes TypeScript, PostgreSQL, etc., but in key responsibilities, they mention specific tools. However, the user wants to exclude fluff, so maybe focus on the main technical requirements.
Wait, in the original description, the key responsibilities have six main challenges. Let me map those into responsibilities. Each challenge is a separate bullet point. Like:
- Design capital table systems for thousands of investors with cent-level accuracy
- Implement multi-country compliance workflows and regulatory rules
- Expand platform to support diverse asset classes and investment structures
- Develop robust financial transaction workflows
- Build real-time portfolio valuation dashboards
- Automate legal document generation from dynamic templates
- Secure sensitive financial data with authentication, authorization, and encryption
Required skills include technical experience and mindset. The user wants Required Skills to be factual. So list the technical skills first, then maybe mindset as part of the role summary.
Let me structure each section as per the user's request:
Job Title: Senior Full-Stack Developer
Role Summary: [One sentence as above]
Expectations: Strategic collaboration, sustainable contributions, full-stack development, knowledge sharing.
Key Responsibilities: The key challenges as separate bullets.
Required Skills: 5+ years full-stack TypeScript, PostgreSQL/ORMs, financial precision, GraphQL.
Required Education & Certifications: N/A.
Check for ATS keywords like TypeScript, PostgreSQL, GraphQL, etc. Avoid using any markdown. Make sure it's in English and concise. Also, ensure the technical aspects like Domain-Driven Design, observability tools are mentioned in the key responsibilities or skills if necessary. Wait, the user wants to exclude fluff. The stack details are included in the original job description, but the user asked to exclude fluff. However, the key responsibilities should reflect the necessary technical challenges. The stack is part of the responsibilities, like using TypeScript, GraphQL, etc.
Wait, in the original job description, the stack is detailed, but the user wants to exclude fluff. However, the required skills should include the key technologies needed. So, for example, TypeScript experience is required, PostgreSQL, GraphQL. The rest of the stack (like Biome, Turborepo) are part of the infrastructure but not necessarily required skills unless specified. The job requires experience with those, but maybe not required for the role. The user says to exclude fluff, so maybe mention the core stack components that are essential. The original job says "Compétences techniques** 5+ ans d’expérience sur des applications full-stack en TypeScript" so that's in required skills. "À l’aise avec PostgreSQL..." so also in required skills. GraphQL is a bonus maybe? Let me check.
Original job says "Expérience avec GraphQL appréciée" which is "Experience with GraphQL is appreciated." So maybe list it under required skills as a plus. But the user says to exclude fluff. Wait, the user wants the Required Skills to be factual. So if it's a requirement, include it. The original job says "5+ ans d’expérience sur des applications full-stack en TypeScript" so that's required. "À l’aise avec PostgreSQL..." is required. "Expérience avec GraphQL appréciée" is a bonus. So in Required Skills, include the first two, and in the key responsibilities or another section, maybe mention GraphQL as a plus? Wait, the user's example shows "Required Skills" and "Bonus" as separate, but the user instructions say to exclude fluff. Maybe just list the required skills and under key responsibilities, include the technical challenges.
But the user wants the Required Skills section only. So perhaps include GraphQL under Required Skills as "Experience with GraphQL (Apollo, Yoga, or equivalent)" since it's appreciated. The job says it's appreciated, not required. Hmm. The user wants to be factual. Since it's listed as appreciated, maybe not include it in required skills. Need to check the original job description again.
Original says for required skills: 5+ TypeScript, PostgreSQL/ORMs, financial calculations, GraphQL is appreciated. So perhaps include the first three as required and indicate GraphQL as a plus in another section. But the user didn't mention a "Bonus" section. The user's example output includes "Required Skills, Required Education & Certifications", so perhaps the bonus is included in the Key Responsibilities or omitted.
Alternatively, maybe list it as part of the required skills even if it's appreciated, but the user said to exclude fluff. So maybe only list the required ones. Let me check the original job's "Ce poste est fait pour vous si..." section. The technical competencies listed are:
- 5+ years full-stack TypeScript
- Comfort with PostgreSQL and ORMs
- Good understanding of financial calculations and decimal precision
- Experience with GraphQL (appreciated)
- Bonus: fintech experience, regulatory compliance, cap table management.
So the required are the first three, GraphQL is appreciated, and the rest are bonuses.
So in the Required Skills, include the first three. In the Key Responsibilities, perhaps mention the bonus as part of the responsibilities if needed. Wait, the user wants to exclude fluff. The bonus items are in the "Ce poste est fait pour vous" section. The user says to exclude fluff, so maybe not include those. Let me re-read the user's instructions:
"Exclude company details, location, benefits, or fluff."
So any non-essential information (fluff) should be omitted. The bonus items are not required, so they might be considered fluff. However, the user says to include key responsibilities, which may include the technical challenges. The bonus items are part of the key responsibilities or expectations.
The original job description lists under "Vos futurs défis métier" the key responsibilities. So those are the main points to include. Then in the "Compétences techniques" the required skills are listed, with some as required and others as appreciated.
The user's example output includes Required Skills with the main required ones and Required Education & Certifications as N/A. So for this job, Required Skills would be:
- 5+ years of full-stack web development with TypeScript
- Experience with PostgreSQL and ORMs (e.g., Prisma)
- Strong understanding of financial calculations and decimal precision
- Experience with GraphQL (Apollo, Yoga, or equivalent) preferred
But since the user wants to exclude fluff, maybe leave out the preferred ones. So Required Skills would be the first three points, and omit the GraphQl one as it's appreciated. However, in the original job description, the GraphQL experience is appreciated, but it's part of the key responsibilities (like implementing multi-country compliance workflows with GraphQL). So maybe include GraphQL as part of the key responsibilities.
But the user wants the Required Skills section. Let me check again. The user says: "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expactations [probably expectations], Key Responsibilities, Required Skills, Required Education & Certifications. Keep it factual, concise, ATS-friendly, and globally neutral."
So the Required Skills should be the skills required to perform the job, as per the job description. The user says to exclude fluff, but the job description's "Compétences techniques**" lists:
- 5+ years full-stack TypeScript
- PostgreSQL and ORMs (Prisma)
- Financial calculations and decimal precision
- GraphQL (appreciated)
- Bonus: fintech, compliance, cap table management
So the required are the first three. The fourth is appreciated, the rest are bonuses. So in Required Skills, include the first three. The fourth, GraphQL, since it's "appreciée", maybe not include in required. But if it's part of the key responsibilities (like using GraphQL Yoga and Apollo for API), then maybe list GraphQL in