Forward Deployed Engineer
Maisa · Madrid, NY · 3 wk ago
Engineering$25/hrFull-time
We need to output HTML fragment with sections for headings where content exists. The posting includes sections: About The Company, About The Role (with subparts: What You’ll Do..., What You’ll Bring..., Why join Maisa!). Also there is some boilerplate about EEO and data consent which should be removed. Also there is "About The Company" content includes description. We need to use for section headings. Do not repeat job title. No Job ID. Use
for section headings. Do not repeat job title. No Job ID. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate, duplicated lines, etc. Also we should not create sections like Pay, Schedule, Benefits unless present. There's no explicit pay, schedule, benefits listed. There's mention of weekly transportation, weekly team lunches, etc. Those could be considered benefits? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting mentions weekly transportation and weekly team lunches as part of company culture. That could be considered benefits but not explicitly labeled as Benefits. However we could include them under About The Company description; we shouldn't create a separate Benefits section unless the posting explicitly states benefits. It does mention weekly transportation and lunches as part of culture; but not a dedicated Benefits heading. So we should not create a Benefits section.
We need to decide headings: About The Company, About The Role (maybe we can split into subheadings: What You’ll Do, What You’ll Bring, Why join Maisa). The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says prefer a few substantive sections over many thin ones. So we could have About The Company, About The Role (with subsections maybe as as well? But we could embed subheadings as too. However we need to avoid too many thin sections. Could have About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. That's four sections. Could also combine What You’ll Do and What You’ll Bring under About The Role? But we need to preserve content. Could have About The Role as a heading and then inside have subheadings? But we cannot nest headings inside? We could use for About The Role and then use for subheadings? Not allowed? The instruction only mentions using for section headings; doesn't forbid other headings but we should follow pattern. Safer to use for each major section: About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. Also maybe include a section for "About The Role" as an overview? But the overview is small: "We’re seeking Forward Deployed Engineers..." Could be included under What You’ll Do? Actually the "About The Role…" paragraph is a summary; we could treat that as part of What You’ll Do or as a separate section. But we have to avoid thin sections. Could merge that summary into What You’ll Do as introductory paragraph.
Thus final HTML:
About The Company
... content ...
What You’ll Do
... combined from About The Role overview + Integrations & Supporting Services + Customer Infrastructure Deployments / DevOps sections ...
What You’ll Bring
... content from What You’ll Bring... plus skill sets ...
Why Join Maisa
... content from Why join Maisa! ...
We need to remove boilerplate: EEO statement, data consent line. Also remove duplicated lines? Not seeing duplicates.
We need to preserve all substantive information: include details about remote/hybrid, hubs, transportation, lunches, culture shaping, mission, platform description, etc.
Let's extract About The Company content:
"About The Company The Best of Both Worlds At Maisa, we believe great work happens when people have the freedom to choose the setup that works best for them. Prefer the flexibility of remote work? You’re welcome to work remotely. Most of our roles are currently focused on Spain, although depending on the position and profile, we may be open to hiring from other locations. Looking for some social energy? Our hybrid setup gives you the option to connect and work alongside teammates at our hubs in Valencia, Barcelona, Madrid and Murcia. And as we grow, our spaces will grow with us: when we build a team of more than 10 people in a location, our ambition is to create a hub there too. We also want the time we spend together in person to be worth it. Today, that includes weekly transportation from the city center to our Valencia headquarters and weekly team lunches in Valencia and Barcelona, with more experiences to come as our teams and hubs evolve. The Culture is OURS to Create We’re still shaping how we work together—and that’s part of what makes joining Maisa now specifically exciting. Everyone who joins has the opportunity to influence how we collaborate, connect, and build our culture. Rather than inheriting a finished playbook, you’ll have a voice in creating it. Remote when you want flexibility. Together when you want connection. And a culture you can help shape from day one. Welcome to Maisa – Making AI Accountable! Maisa is building the next generation of Agentic Process Automation, helping enterprises automate complex, decision-heavy processes that traditional automation can’t handle and GenAI alone can’t be trusted with. Our platform combines AI-driven reasoning with deterministic execution, enabling reliable, auditable, and enterprise-ready AI systems."
We need to keep that.
Now What You’ll Do: includes the "About The Role…" paragraph and the two subsections.
Let's capture:
About The Role… We’re seeking Forward Deployed Engineers to work at the intersection of engineering, product, and customers, deploying and adapting Maisa Studio, our flagship Agentic Process Automation platform, to solve real-world enterprise problems.
Then subheadings:
Customer-Facing Engineering Work directly with enterprise customers to understand their processes and goals. Design and implement solutions using Maisa Studio to automate complex workflows, acting as a trusted technical partner during onboarding and deployment while translating requirements into technical implementations and product feedback.
Collaboration & Product Feedback Partner with product and engineering teams to influence roadmap development. Surface customer needs, edge cases, and scalability concerns while defining best practices, reference architectures, and reusable components that accelerate delivery.
Reliability, Security & Quality Ensure deployments meet enterprise standards for reliability, performance, and security. Support customers in regulated environments by aligning with compliance requirements and collaborating with QA, SRE, and AppSec teams for stable rollouts.
What You’ll Do… You will work closely with enterprise customers and internal teams to deliver robust, secure, and maintainable deployments in complex, often regulated environments, across 2 key technical domains: Integrations & Supporting Services (Build what makes the use case work) Configure, extend, and integrate Maisa Studio into customer environments, designing end-to-end solutions that include APIs, connectors, webhooks, serverless functions, microservices, and event-driven flows. Translate functional requirements from Automators and Technical Account Managers into concrete technical implementations using Go, Python, or JavaScript, clarifying ambiguities and proposing pragmatic paths forward. Ensure robustness through strong engineering practices including testing, logging, monitoring, and documentation. Troubleshoot complex issues across distributed systems and support handover to internal teams or customers when applicable.
Customer Infrastructure Deployments / DevOps (On-prem & Customer Cloud) Design and support deployments of Maisa Studio in customer environments, including on-premise and customer-managed cloud infrastructures. Work closely with customer DevOps, SRE, and Security teams to achieve production readiness, configuring platform requirements including authentication (OIDC, SAML), IAM, networking (VPNs, DNS, ingress/egress), and operational controls (deployment pipelines, monitoring, backups, high availability). Diagnose and resolve deployment-level incidents, ensure the platform operates within customer security and compliance requirements, and produce clear operational documentation including runbooks, deployment patterns, and troubleshooting guides.
We need to preserve all that.
Now What You’ll Bring…:
"You have strong experience as a Software Engineer, Solutions Engineer, DevOps/SRE Engineer, or Forward Deployed Engineer in customer-facing or delivery-oriented roles. You're comfortable operating in ambiguous environments, moving quickly from problem to solution while maintaining reliability, with strong troubleshooting skills across code, integrations, and infrastructure. You bring a customer-first mindset and can explain technical concepts clearly to drive alignment. We are seeking candidates with one of two skill sets, or a mix of both: Integrations & Supporting Services (Build what makes the use case work) Strong experience as a backend or full-stack developer shipping production systems.Hands-on experience with APIs, microservices, and event-driven architectures/queues.Familiarity with serverless and integration patterns commonly used in enterprise environments.Strong debugging skills and comfort operating across code, infrastructure touchpoints, and workflow logic. Customer Infrastructure Deployments / DevOps (On-prem & Customer Cloud) Strong experience in DevOps / SRE, supporting production workloads.Hands-on knowledge of Kubernetes, cloud providers and/or on-prem infrastructure, and networking fundamentals.Practical experience with security and identity standards: OIDC, SAML, VPNs, certificates, and IAM concepts.Ability to quickly understand customer infrastructure and adapt to their tools and processes.Clear, structured communication with technical stakeholders in customer organizations."
Now Why join Maisa!:
"You will be joining one of Europe’s most exciting early-stage AI start-ups, where you’ll have the opportunity to work with cutting-edge Agentic Process Automation that’s reshaping how enterprises approach AI deployment. You will get to directly influence how major multinational organizations transform critical business processes, working on genuinely differentiated technology that solves real enterprise AI challenges. Following our recent $25m Seed Round, backed by leading Venture Capital firms including Creandum, Forgepoint, NFX, and Village Global, we’re scaling quickly and realising significant enterprise traction. This is your opportunity to help solve real AI enterprise challenges, working alongside deep technical and industry experts, where you will be challenged daily and expedite your learning and development."
We should remove the EEO line and data consent line.
Now format.
We need to use - for any list of duties/requirements/benefits. In the content there are some lists like "Integrations & Supporting Services (Build what makes the use case work)" etc. Those are headings within paragraphs, not list items. However there are enumerated items like "Strong experience as a backend or full-stack developer shipping production systems." etc. Those are sentences, not list. The instruction: Use
- for any list of duties/requirements/benefits. If there are no explicit bullet lists, we may not need to add lists. However there are some sections that could be turned into lists but we must not invent. So we keep as paragraphs.
But there are some bullet-like sentences separated by periods. We'll keep as prose.
Now ensure we don't include any empty sections.
Let's craft HTML.
We'll need to escape any HTML special characters? Not needed.
Let's produce:
About The Company
At Maisa, we believe great work happens when people have the freedom to choose the setup that works best for them. Prefer the flexibility of remote work? You’re welcome to work remotely. Most of our roles are currently focused on Spain, although depending on the position and profile, we may be open to hiring from other locations. Looking for some social energy? Our hybrid setup gives you the option to connect and work alongside teammates at our hubs in Valencia, Barcelona, Madrid and Murcia. And as we grow, our spaces will grow with us: when we build a team of more than 10 people in a location, our ambition is to create a hub there too. We also want the time we spend together in person to be worth it. Today, that includes weekly transportation from the city center to our Valencia headquarters and weekly team lunches in Valencia and Barcelona, with more experiences to come as our teams and hubs evolve. The Culture is OURS to Create We’re still shaping
for prose. We need to preserve all substantive information, remove boilerplate, duplicated lines, etc. Also we should not create sections like Pay, Schedule, Benefits unless present. There's no explicit pay, schedule, benefits listed. There's mention of weekly transportation, weekly team lunches, etc. Those could be considered benefits? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting mentions weekly transportation and weekly team lunches as part of company culture. That could be considered benefits but not explicitly labeled as Benefits. However we could include them under About The Company description; we shouldn't create a separate Benefits section unless the posting explicitly states benefits. It does mention weekly transportation and lunches as part of culture; but not a dedicated Benefits heading. So we should not create a Benefits section. We need to decide headings: About The Company, About The Role (maybe we can split into subheadings: What You’ll Do, What You’ll Bring, Why join Maisa). The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says prefer a few substantive sections over many thin ones. So we could have About The Company, About The Role (with subsections maybe as as well? But we could embed subheadings as too. However we need to avoid too many thin sections. Could have About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. That's four sections. Could also combine What You’ll Do and What You’ll Bring under About The Role? But we need to preserve content. Could have About The Role as a heading and then inside have subheadings? But we cannot nest headings inside? We could use for About The Role and then use for subheadings? Not allowed? The instruction only mentions using for section headings; doesn't forbid other headings but we should follow pattern. Safer to use for each major section: About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. Also maybe include a section for "About The Role" as an overview? But the overview is small: "We’re seeking Forward Deployed Engineers..." Could be included under What You’ll Do? Actually the "About The Role…" paragraph is a summary; we could treat that as part of What You’ll Do or as a separate section. But we have to avoid thin sections. Could merge that summary into What You’ll Do as introductory paragraph.
Thus final HTML:
About The Company
too. However we need to avoid too many thin sections. Could have About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. That's four sections. Could also combine What You’ll Do and What You’ll Bring under About The Role? But we need to preserve content. Could have About The Role as a heading and then inside have subheadings? But we cannot nest headings inside? We could use for About The Role and then use for subheadings? Not allowed? The instruction only mentions using for section headings; doesn't forbid other headings but we should follow pattern. Safer to use for each major section: About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. Also maybe include a section for "About The Role" as an overview? But the overview is small: "We’re seeking Forward Deployed Engineers..." Could be included under What You’ll Do? Actually the "About The Role…" paragraph is a summary; we could treat that as part of What You’ll Do or as a separate section. But we have to avoid thin sections. Could merge that summary into What You’ll Do as introductory paragraph.
Thus final HTML:
About The Company
for subheadings? Not allowed? The instruction only mentions using for section headings; doesn't forbid other headings but we should follow pattern. Safer to use for each major section: About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. Also maybe include a section for "About The Role" as an overview? But the overview is small: "We’re seeking Forward Deployed Engineers..." Could be included under What You’ll Do? Actually the "About The Role…" paragraph is a summary; we could treat that as part of What You’ll Do or as a separate section. But we have to avoid thin sections. Could merge that summary into What You’ll Do as introductory paragraph.
Thus final HTML:
About The Company
for each major section: About The Company, What You’ll Do, What You’ll Bring, Why Join Maisa. Also maybe include a section for "About The Role" as an overview? But the overview is small: "We’re seeking Forward Deployed Engineers..." Could be included under What You’ll Do? Actually the "About The Role…" paragraph is a summary; we could treat that as part of What You’ll Do or as a separate section. But we have to avoid thin sections. Could merge that summary into What You’ll Do as introductory paragraph.
Thus final HTML:
About The Company
... content ...
What You’ll Do
... combined from About The Role overview + Integrations & Supporting Services + Customer Infrastructure Deployments / DevOps sections ...
What You’ll Bring
... content from What You’ll Bring... plus skill sets ...
Why Join Maisa
... content from Why join Maisa! ...
We need to remove boilerplate: EEO statement, data consent line. Also remove duplicated lines? Not seeing duplicates. We need to preserve all substantive information: include details about remote/hybrid, hubs, transportation, lunches, culture shaping, mission, platform description, etc. Let's extract About The Company content: "About The Company The Best of Both Worlds At Maisa, we believe great work happens when people have the freedom to choose the setup that works best for them. Prefer the flexibility of remote work? You’re welcome to work remotely. Most of our roles are currently focused on Spain, although depending on the position and profile, we may be open to hiring from other locations. Looking for some social energy? Our hybrid setup gives you the option to connect and work alongside teammates at our hubs in Valencia, Barcelona, Madrid and Murcia. And as we grow, our spaces will grow with us: when we build a team of more than 10 people in a location, our ambition is to create a hub there too. We also want the time we spend together in person to be worth it. Today, that includes weekly transportation from the city center to our Valencia headquarters and weekly team lunches in Valencia and Barcelona, with more experiences to come as our teams and hubs evolve. The Culture is OURS to Create We’re still shaping how we work together—and that’s part of what makes joining Maisa now specifically exciting. Everyone who joins has the opportunity to influence how we collaborate, connect, and build our culture. Rather than inheriting a finished playbook, you’ll have a voice in creating it. Remote when you want flexibility. Together when you want connection. And a culture you can help shape from day one. Welcome to Maisa – Making AI Accountable! Maisa is building the next generation of Agentic Process Automation, helping enterprises automate complex, decision-heavy processes that traditional automation can’t handle and GenAI alone can’t be trusted with. Our platform combines AI-driven reasoning with deterministic execution, enabling reliable, auditable, and enterprise-ready AI systems." We need to keep that. Now What You’ll Do: includes the "About The Role…" paragraph and the two subsections. Let's capture: About The Role… We’re seeking Forward Deployed Engineers to work at the intersection of engineering, product, and customers, deploying and adapting Maisa Studio, our flagship Agentic Process Automation platform, to solve real-world enterprise problems. Then subheadings: Customer-Facing Engineering Work directly with enterprise customers to understand their processes and goals. Design and implement solutions using Maisa Studio to automate complex workflows, acting as a trusted technical partner during onboarding and deployment while translating requirements into technical implementations and product feedback. Collaboration & Product Feedback Partner with product and engineering teams to influence roadmap development. Surface customer needs, edge cases, and scalability concerns while defining best practices, reference architectures, and reusable components that accelerate delivery. Reliability, Security & Quality Ensure deployments meet enterprise standards for reliability, performance, and security. Support customers in regulated environments by aligning with compliance requirements and collaborating with QA, SRE, and AppSec teams for stable rollouts. What You’ll Do… You will work closely with enterprise customers and internal teams to deliver robust, secure, and maintainable deployments in complex, often regulated environments, across 2 key technical domains: Integrations & Supporting Services (Build what makes the use case work) Configure, extend, and integrate Maisa Studio into customer environments, designing end-to-end solutions that include APIs, connectors, webhooks, serverless functions, microservices, and event-driven flows. Translate functional requirements from Automators and Technical Account Managers into concrete technical implementations using Go, Python, or JavaScript, clarifying ambiguities and proposing pragmatic paths forward. Ensure robustness through strong engineering practices including testing, logging, monitoring, and documentation. Troubleshoot complex issues across distributed systems and support handover to internal teams or customers when applicable. Customer Infrastructure Deployments / DevOps (On-prem & Customer Cloud) Design and support deployments of Maisa Studio in customer environments, including on-premise and customer-managed cloud infrastructures. Work closely with customer DevOps, SRE, and Security teams to achieve production readiness, configuring platform requirements including authentication (OIDC, SAML), IAM, networking (VPNs, DNS, ingress/egress), and operational controls (deployment pipelines, monitoring, backups, high availability). Diagnose and resolve deployment-level incidents, ensure the platform operates within customer security and compliance requirements, and produce clear operational documentation including runbooks, deployment patterns, and troubleshooting guides. We need to preserve all that. Now What You’ll Bring…: "You have strong experience as a Software Engineer, Solutions Engineer, DevOps/SRE Engineer, or Forward Deployed Engineer in customer-facing or delivery-oriented roles. You're comfortable operating in ambiguous environments, moving quickly from problem to solution while maintaining reliability, with strong troubleshooting skills across code, integrations, and infrastructure. You bring a customer-first mindset and can explain technical concepts clearly to drive alignment. We are seeking candidates with one of two skill sets, or a mix of both: Integrations & Supporting Services (Build what makes the use case work) Strong experience as a backend or full-stack developer shipping production systems.Hands-on experience with APIs, microservices, and event-driven architectures/queues.Familiarity with serverless and integration patterns commonly used in enterprise environments.Strong debugging skills and comfort operating across code, infrastructure touchpoints, and workflow logic. Customer Infrastructure Deployments / DevOps (On-prem & Customer Cloud) Strong experience in DevOps / SRE, supporting production workloads.Hands-on knowledge of Kubernetes, cloud providers and/or on-prem infrastructure, and networking fundamentals.Practical experience with security and identity standards: OIDC, SAML, VPNs, certificates, and IAM concepts.Ability to quickly understand customer infrastructure and adapt to their tools and processes.Clear, structured communication with technical stakeholders in customer organizations." Now Why join Maisa!: "You will be joining one of Europe’s most exciting early-stage AI start-ups, where you’ll have the opportunity to work with cutting-edge Agentic Process Automation that’s reshaping how enterprises approach AI deployment. You will get to directly influence how major multinational organizations transform critical business processes, working on genuinely differentiated technology that solves real enterprise AI challenges. Following our recent $25m Seed Round, backed by leading Venture Capital firms including Creandum, Forgepoint, NFX, and Village Global, we’re scaling quickly and realising significant enterprise traction. This is your opportunity to help solve real AI enterprise challenges, working alongside deep technical and industry experts, where you will be challenged daily and expedite your learning and development." We should remove the EEO line and data consent line. Now format. We need to use- for any list of duties/requirements/benefits. In the content there are some lists like "Integrations & Supporting Services (Build what makes the use case work)" etc. Those are headings within paragraphs, not list items. However there are enumerated items like "Strong experience as a backend or full-stack developer shipping production systems." etc. Those are sentences, not list. The instruction: Use
- for any list of duties/requirements/benefits. If there are no explicit bullet lists, we may not need to add lists. However there are some sections that could be turned into lists but we must not invent. So we keep as paragraphs.
But there are some bullet-like sentences separated by periods. We'll keep as prose.
Now ensure we don't include any empty sections.
Let's craft HTML.
We'll need to escape any HTML special characters? Not needed.
Let's produce:
About The Company
At Maisa, we believe great work happens when people have the freedom to choose the setup that works best for them. Prefer the flexibility of remote work? You’re welcome to work remotely. Most of our roles are currently focused on Spain, although depending on the position and profile, we may be open to hiring from other locations. Looking for some social energy? Our hybrid setup gives you the option to connect and work alongside teammates at our hubs in Valencia, Barcelona, Madrid and Murcia. And as we grow, our spaces will grow with us: when we build a team of more than 10 people in a location, our ambition is to create a hub there too. We also want the time we spend together in person to be worth it. Today, that includes weekly transportation from the city center to our Valencia headquarters and weekly team lunches in Valencia and Barcelona, with more experiences to come as our teams and hubs evolve. The Culture is OURS to Create We’re still shaping
- for any list of duties/requirements/benefits. If there are no explicit bullet lists, we may not need to add lists. However there are some sections that could be turned into lists but we must not invent. So we keep as paragraphs.
But there are some bullet-like sentences separated by periods. We'll keep as prose.
Now ensure we don't include any empty sections.
Let's craft HTML.
We'll need to escape any HTML special characters? Not needed.
Let's produce: