Skip to main content
← frontier

Y Combinator's Comena Has 7 Openings in Munich, Pays Up to $168,000

By Elena Petrova•

The Roles Comena Is Actually Filling

Zero G Talent’s live board separates Comena’s openings into three internships and four non-intern roles. Comena builds AI agents for industrial distributors and manufacturers, with its product page centered on industrial order processing. The roster divides between software delivery, customer integration and GTM/sales. Conflicting job-board labels over role count, seniority and location mean candidates cannot read the title alone: they must first reconcile the roster, then identify the evidence each individual posting asks them to provide.

Comena’s careers page divides the openings roughly in half between engineering and go-to-market, or GTM. Zero G says the company added two openings in the past week. The mix appears in the live roster:

Opening Function Level Location
Software Engineering Intern Engineering Intern Munich, Germany
Fullstack Engineer Full-stack engineering Non-intern Munich, Germany
Forward Deployed Engineer Engineering and customer deployment Non-intern Munich, Germany
GTM Associate Intern GTM and sales Intern Munich, Germany
Founding GTM Associate GTM and sales Non-intern Munich, Germany
Founder's Associate GTM Non-intern Munich, Germany
Founder's Associate Intern GTM Intern Munich, Germany

The current titles sit inside the broad engineering/GTM split, but the named roles specify the work more closely. Forward Deployed places customer implementation inside engineering, while the associate titles are grouped on the GTM side. Earlier aggregator labels complicate any title-only reading, but they do not set the current titles; they create a classification mismatch around level and employment type.

The Forward Deployed Engineer posting makes that scope explicit:

“As a Forward Deployed Engineer, you will be one of our very first hires.”

The role works closely with the founders Jiehua Wu and Almo Sutedjo, as well as with customers. Y Combinator’s Comena profile lists Wu and Sutedjo as founders, gives 2025 as the founding year and places the company in the S25 batch. Comena’s posting says it is keeping the team deliberately small. A Landed snapshot put headcount at 14. Comena’s own Ashby board also shows a Forward Deployed Engineering Lead alongside the Forward Deployed Engineer, so the title set does not resolve seniority on its own.

The Forward Deployed Engineer configures, tests and deploys AI agents; connects customer catalogs and ERPs; learns custom workflows; and adjusts backend logic and interface code. The role also guides and trains customers so they can adopt the system. Comena requires fluent English and German and the ability to work with nontechnical stakeholders. The work joins systems integration to customer adoption.

Comena lists Python and Django for the backend, TypeScript for the frontend, Postgres and current large language models. Engineers carry product work from idea to production across interfaces, business logic and cloud services. Landed says the order-processing platform extracts data from PDFs, emails and handwritten notes. The product page says Comena automates order and quote entry from inbox to ERP and that its agent processes orders and finds the right products. A Simplify Jobs description adds that it matches products from unstructured text and, after optional human review, sends finalized orders to a client’s ERP.

Together, the seven openings combine software delivery, customer implementation and GTM around the same order-processing problem. That mix makes role count, level and location fields worth checking against individual records.

Conflicting Counts, Seniority, and Remote Status

Aggregator totals describe different feeds, not a settled roster. The snapshots cover different feeds, and their labels do not agree on internships or full-time work.

Source and snapshot Reported count What the record shows
Landed, Oct. 21, 2026 11 Snapshot of Comena’s careers page
Alion, Oct. 21, 2026 5 All listings are less than a month old
AI Jobs Desk 6 Includes listings dated 93–166 days earlier

Zero G’s verified live board remains the reference point for the seven-role roster, but Comena’s own careers page lists eight positions and marks all but one on-site. Landed’s total sits above both the seven-role live board and the eight-position Ashby page, while Alion’s and AI Jobs Desk’s totals fall below them. The records do not explain the difference, so the totals do not reconcile the feeds.

At the other end, the Anti Job Board said it tracked no live vacancies:

“We aren't tracking any live Comena vacancies today. We re-check daily and this page updates as soon as a role appears.”

The tracker said Comena uses Ashby, while Alion said the application form opens through Work at a Startup. The evidence does not explain the discrepancy, but the tracker’s wording limits its claim to what it sees. It does not show that Comena stopped hiring.

Comena’s Work at a Startup page identifies the same two founders, while its Ashby board and the aggregator pages cover different slices of the roster. These pages let candidates compare the employer’s wording with an aggregator’s label instead of relying on the label alone.

Seniority labels vary more than the titles do. Landed labeled its entire sample intern-level, but only the current titles containing Intern fit that description; the others carry no intern label. Comena’s Work at a Startup listings require at least a year of experience on three openings. Alion’s sample carries junior, intern, full-time and internship labels, while AI Jobs Desk mixes a staff/lead full-time sales category with an entry/junior on-site internship. The live board is not an all-intern roster, and treating it as one would hide the four non-intern roles.

The location evidence is more consistent than the totals. Alion classifies all five of its tracked records as in-office roles in Munich. Landed marks its records nonremote, and the older AI Jobs Desk records for forward deployment and sales also require on-site work. Although Alion lists Comena’s headquarters in Ottobrunn, the vacancy records across the sources point to Munich rather than unrestricted remote work across Germany. The Anti Job Board’s Unspecified label sits on a page that reports no live roles, so it cannot describe the current openings. Comena serves customers in the US and Germany, but that customer footprint does not make the positions remote or split across those markets.

Pay figures vary because the sources cover different slices:

Source and sample Pay shown
AI Jobs Desk $45,000–$168,000; $84,000 median
Alion, every tracked vacancy $67,000 lower quartile; $100,000 median; $168,000 upper quartile
Comena’s Work at a Startup, Founder’s Associate $60,000–$90,000

Individual board records mix monthly and annual pay in euros and dollars, while the sources do not explain their weighting or currency conversion. The board’s Founder’s Associate record gives no range, but Comena’s Work at a Startup listing supplies one.

Use the source-linked role pages, not one aggregator’s total, to build the practical roster. Open the exact posting, check the employment type and location, then confirm whether the pay is monthly or annual and which currency it uses. Treating every opening as an internship is a classification mismatch; an empty tracker is one feed’s result. The individual record is the vacancy. Once the vacancy is fixed, the next question is what the individual posting asks a candidate to prove.

What Actually Gets You Past Comena’s Screen

The Fullstack Engineer posting lists a 30-minute founder call, a compensated take-home challenge and then an offer. The available role descriptions point to a common bar: Can the candidate handle a messy customer operation and ship software that supports it? That combination calls for hybrid judgment, not enthusiasm for artificial intelligence.

The Fullstack Engineer posting sets out the expected work. The Y Combinator job post asks candidates to carry a feature from the interface through backend business logic to cloud deployment. It also places customer onboarding and implementation inside engineering, treating customer-specific behavior as part of the build rather than a handoff after shipping. Together, those duties make production delivery and customer-specific implementation the clearest documented baseline.

The stack test for industrial AI agent order-processing roles

Experience building with a large language model can support an application, but it does not show that someone can connect a model to production software used in sales and procurement. A credible candidate should explain where the interface ends, where the service begins, how the database holds working data and how the system handles an unusual customer workflow without corrupting the order record.

For this workflow, extraction and business-rule decisions are different layers. A candidate should be able to say which layer recognizes an order, which resolves exceptions, and how a reviewed result reaches the ERP without treating a raw model response as a record. A portfolio should make those boundaries visible rather than stop at a chatbot interface.

The client-facing test is equally concrete. The posting values people who can work with clients, while Landed’s summary says Comena’s openings most often ask for cold calling, TypeScript and Postgres. That summary does not disclose what the founder call weighs, but the first-party description spells out client-facing work. A candidate who can translate a customer constraint into a system requirement—and explain the tradeoff back—has stronger evidence than one who lists tools.

What the founder call and take-home reveal

The Forward Deployed Engineer posting’s founder biographies provide useful context for the hybrid profile. The posting says Wu was the youngest software engineer at Google Zurich and the first sales hire at Lio, while Sutedjo was the first engineer at Leaping AI and shipped code at Microsoft and Amazon Web Services. The posting supplies these biographies; it does not disclose a hiring rubric. They put one founder’s background in sales and the other’s in engineering, which is consistent with the mixed demands in the role descriptions.

For the Fullstack Engineer founder call, prepare a short account of the work you want to do and the evidence that you can do it. A concrete example of taking an ambiguous customer workflow from discovery to a shipped implementation gives the interviewer more than a list of model names. Be ready to ask how Comena’s customers vary their ERP setups and what the take-home is meant to test. Those questions show that implementation is a two-way process, rather than a one-sided product presentation for a uniform customer.

The company states its work bar this way:

“Ships full-stack apps quickly without compromising on code quality”

The posting also asks for high agency, startup comfort and effort beyond a traditional nine-to-five schedule. These are conditions, not perks, and candidates should assess them honestly. The relevant evidence is a record of owning decisions, handling customer-specific requirements and shipping working software under pressure. A claim that you move fast means little unless you can show what you decided, what you built and what shipped.

Treat the compensated take-home as paid work and confirm the expected deliverable. The available material does not disclose the exact brief, so the stack and product description are preparation signals, not proof of a hidden test. Make any coding submission easy to evaluate: include setup instructions and tests, state your assumptions and explain the tradeoffs.

If the task touches an order workflow, show what you need to learn about the customer’s ERP and where its custom rules enter the system. State what you would verify before sending an extracted order into production.

Before the Fullstack Engineer founder call, prepare a single proof: trace an order from a source document to an ERP record, mark the customer-specific decisions and verification steps, add a short account of the interface, service and database boundaries, and show one example of shipping under real constraints. Those pieces give the interviewer a coherent view of how you work. If you cannot connect those points, the role fit is not yet proven. With that proof in hand, the candidate can place their experience against Comena’s job boundaries.

How Industrial Automation Job Seekers Should Respond

Once the proof is clear, the application should show where the candidate’s own operating experience belongs. The GTM titles sit on the sales and customer-contact side of the roster, while the engineering openings include explicit customer onboarding, implementation and production duties. Candidates should not treat an associate title as interchangeable with a forward-deployed role, or present internship work as if it carried full production ownership.

Reconciling the metadata still leaves the hardest part unanswered: how the interview weighs the work. Comena’s postings do show where customer decisions meet production software. A candidate from factory controls or physical robotics should check the fit before moving: Comena addresses software-mediated order processing, not machine control.

Match the seniority of the Comena opening first, then prove that you can move an industrial order from messy input to an ERP-ready outcome.

Sales and GTM candidates: show operational judgment

Operational judgment appears in the gap between what a customer sends and what another system can safely act on. A candidate can show this judgment by explaining how they would interpret intent, identify missing information and decide when an exception needs human attention.

Candidates with wholesale distribution, building-materials or construction-supply experience should locate their place in that process. They should identify whether they qualified demand, interpreted purchase orders, corrected product data, chased missing information or resolved delivery exceptions, then name the systems used, the handoffs they owned and the result. If they can substantiate a volume, error-rate or processing-time improvement, include it. If not, an honest account of the decision and outcome is stronger than a generic order-entry responsibility.

The founding sales titles also need a level check. A candidate should confirm whether customer implementation and order operations fall within the mandate rather than assume the company’s definition of GTM. Ask what success looks like in the first six months. That question can reveal more than a generic sales-funnel conversation.

Candidates should also avoid arguing that software should replace sales representatives. The case for distributor order automation is to remove repetitive administrative work while leaving customer relationships, ambiguous cases and high-risk exceptions to people. A GTM candidate who knows when to automate, when to ask a question and when to escalate will fit that model.

Backend and deployment candidates: prove the messy-to-reliable path

A backend candidate should reduce the pitch to a concrete claim: they have built or operated a system that turns incomplete, inconsistent input into an action another system can trust. The relevant evidence lies in parsing, validation, normalization, handoffs to a system of record and low-confidence exception handling.

Show the failure cases, not only the successful path. A deployment-focused candidate should add evidence of working beside sales, operations or distribution teams and turning a messy business rule into testable system behavior. An intern can use a smaller project if its scope, tests and engineering choices are clear. A full-stack candidate should show ownership beyond a detached backend component.

The roster table above omits the stack even though the postings name it. Clarify which technologies are must-haves, how model outputs are evaluated, what data and enterprise systems must connect, and whether the role includes production support. The answers show whether the fit centers on full-stack delivery, data engineering, machine-learning operations or customer deployment. Until then, prioritize evidence of comparable work over tool names.

Verify the terms before tailoring

Before tailoring an application, confirm the listed city, whether the job expects office attendance and what work authorization or relocation support, if any, applies. Check the seniority attached to each title, including what the employer means by founding and which decisions an associate owns.

Make the application specific. Tailor it to one Comena opening and one relevant workflow. A GTM candidate can present a process map or a measured operational improvement. An engineering candidate can offer a short architecture and failure-handling example. Put unresolved questions about the stack, location and scope to the interviewer before the interview. That exchange should show whether the role matches the evidence you can defend.

The documented order workflow comes down to one operational sequence: messy customer input, optional human review and an ERP-ready record. Put that sequence on the page.


Working in frontier tech? Zero G Talent tracks the openings: see every open Comena role, browse frontier tech jobs, the companies hiring, and the people building the field.

Ready to Start Your Space Career?

Browse frontier jobs and find your next opportunity.

View frontier Jobs