Careers at Mercura: Teams, Pay and How to Get Hired

Who Gets Hired at Mercura

Mercura hit $2 million in ARR in its first year, then eightfolded revenue in twelve months, and at 16 people, planned to quintuple within one. The company builds software for the $12 trillion industry behind hospitals, schools, and power plants. It launched in 2024, and as of mid-2026 targeted $10 million by year-end while expanding into the U.S. The people it brings on now will determine whether it wins its market.

Mercura's hiring scope is narrow but deep. Its own careers page listed 10 direct-apply roles as of September 2026 — no recruiters, no reposts — with engineering as the dominant function. Six of those ten sat in engineering, split between full-stack and AI/ML work, plus design. Sales had two openings, customer success one, marketing one. On Zero G Talent's board, recent postings mapped cleanly onto that shape: Staff Engineer, (Senior) Fullstack Engineer, and Forward Deployed Engineer in Munich, alongside Account Executive, Business Development Representative, and (Senior) Customer Success Manager.

Seniority skewed toward the experienced end. Of the ten roles tracked that month, six carried unspecified or mid-level bands, two were senior, one principal, and one executive (the Founding People & Talent Lead). That opening told us something important: Mercura was building its recruiting process from scratch, and that role owned how the company hires, onboards, and retains as it scales. The posting framed talent as "the single most important lever," with the hire owning recruitment from day one and spending four-fifths of early focus on the talent function.

Location concentrated tightly. Munich was the top listed site as of September 2026, and Mercura listed few or no explicitly remote roles. Every recent posting reflected that Munich focus, from engineering to sales to customer success. Candidates outside Munich should expect to relocate or confirm remote eligibility before applying.

The application bar reflected Mercura's pace. Its careers page and job postings signaled that it valued ability, mindset, and values over checklist compliance. The Founding People & Talent Lead posting explicitly invited candidates who met part of the criteria to apply anyway, noting that men often apply with partial qualifications while women and marginalized groups wait to meet every requirement. That language defined the bar: Mercura wanted people who could grow into roles, not perfect resumes.

Mercura's record showed it hires for scale, not maintenance. Revenue eightfolded in twelve months, and the next milestone was $10 million ARR. The colleagues it advertised joining were described as experienced operators, ex-founders, Science Olympiad medallists, and graduates from Google, Bain, MIT, TUM, Harvard, CDTM, and Cambridge. That mix pointed to a preference for proven builders who could operate with autonomy in a company moving at software speed.

The hiring bar was specific: Mercura wanted engineers and operators who could ship in high-stakes environments, sellers who could open new territory, and builders of process who could scale a team from 16 to 50. Candidates who matched that profile — and who understood the company's revenue trajectory and location reality — started ahead.

Mercura's Pay: Equity First

A YC W25-backed startup that has grown revenue eightfold in twelve months, Mercura operates with a team of roughly 20 and targets $10M ARR by year-end 2026 while expanding into the United States. The company raised a heavily oversubscribed round at what it describes as one of the highest valuations in its YC cohort, which means the equity component of its offers carries real weight: early-stage stock in a fast-scaling company whose five alumni have since founded their own ventures and raised millions. That track record is the core argument Mercura makes for its package, and it is a legitimate one for candidates weighing cash against long-term upside.

The six live listings on the board give a concrete picture of where the company is spending its hiring budget. All are anchored in Munich and span engineering, sales, and customer-facing functions, as the table above shows. The clustering of senior and staff-level engineering titles alongside a dedicated BDR and Account Executive role suggests that Mercura is simultaneously scaling its product and its push into new markets, and the compensation bands for these roles will reflect that dual investment.

Mercura also runs a referral program that pays a $500 cash bonus upon hire, according to candidatesreach.com. The research does not surface a public salary band for the board-level compensation structure itself. Salary.com maintains a Mercura salary page, and the company's own career page at mercura.io lists open roles, but the specific pay ranges for individual positions are not disclosed in the source material available here. What the research does establish is that Mercura compensates with a philosophy rooted in ownership: the company's own stated values list "Ownership" first among its principles, describing it as taking responsibility end-to-end and acting proactively. That language maps directly to the equity-forward, high-commitment package typical of YC-backed seed-stage companies rather than a corporate salary structure.

The table above reflects the roles as they appear on the board. Mercura does not publicly list specific salary figures for these positions in the sources reviewed, so the compensation column captures the structural signal: equity participation across all roles, with commercial positions layered on top of variable pay. The company's expansion into the US market and its year-end 2026 revenue target suggest that compensation bands will likely shift upward as the team scales beyond its current headcount, but the current structure is built for early-stage velocity rather than corporate parity.

For candidates evaluating Mercura, the practical question is whether the equity story and the ownership culture outweigh the cash-compensation gap that typically exists at a company this stage. The company's framing — "build something with real-world impact," its own account of alumni founding ventures and raising millions — is an explicit invitation to bet on the outcome. That bet carries a price tag, but it is written in equity and ownership rather than in a published salary range.

Inside the Funnel

Mercura's hiring funnel runs through five distinct stages, from résumé screen through offer and background checks, and the shape of that funnel shifts depending on whether a candidate is coming through campus, lateral mid-level, or senior leadership tracks. ClavePrep's hiring-process guide lays out the standard sequence: 1. Application / résumé screen (ATS plus recruiter eligibility), 2. OA or take-home (coding or aptitude depending on level), 3. Technical interviews (live coding, design, or domain depth), 4. Hiring manager / bar (level calibration and team fit), 5. Offer and background (package, start date, checks). TechPrep said the process typically spans 4 to 6 stages, noting it is "notably different from standard big tech pipelines."

US-facing loops for mid-level roles commonly span 2–6 weeks, and senior loops can stretch further when panels and compensation approvals stack, ClavePrep said. The board data shows Mercura's recent postings clustered around Munich-based roles spanning engineering and commercial functions, suggesting the company is hiring across both technical and commercial functions at once.

The Recruiter Screen

The recruiter screen runs roughly 30 minutes and covers background and motivation. TechPrep said a key filter at this stage is a candidate's openness to working with Haskell and Elm, with that topic surfacing early. ClavePrep said recruiters look for JD-keyword matching on the résumé and clear ownership bullets, not polished narratives.

The Technical Screen

The technical screen runs about 60 minutes and often takes the form of a SQL schema review or a practical coding task rather than a traditional algorithm question. The company hands candidates a database schema for a small web app and asks them to identify race conditions, normalization issues, or missing constraints, "much like reviewing a colleague's pull request," TechPrep said. ClavePrep said early technical filters reward timed accuracy and clear communication of approach, not clever one-off tricks.

The Deep Loop

For senior and staff-level roles, Mercura typically assigns a take-home: a realistic engineering problem such as building a ledger primitive or a fraud-detection component. TechPrep said the company "values type discipline and write-up quality alongside working code." Separately, the virtual onsite loop runs 4 to 5 rounds over Zoom, covering applied coding, system design, the Craft Round, and a behavioral or product-sense conversation. Interviewers take a collaborative, teammate-style approach rather than silent observation.

System-design prompts tie tightly to fintech scenarios: candidates may be asked to design a payment processing system or transaction ledger, with heavy focus on consistency, idempotency, and how the system handles partial failures. The Craft Round is one of the company's most distinctive stages — not a live coding session but a structured conversation about a candidate's philosophy on code quality, type systems, and long-term maintainability. ClavePrep said Mercury "explicitly values type discipline and the quality of your written explanation over simply getting a working solution." The behavioral round carries a strong product-sense angle: rather than generic conflict-resolution questions, candidates may be asked to define the product they worked on, including its boundaries, user experience, and the decisions that shaped it.

A note on sourcing: The detailed process descriptions above draw on ClavePrep and TechPrep, both of which reference a company called "Mercury" (a fintech distinct from the AI-focused Mercura listed on the Zero G Talent board). The interview-stage structure likely reflects a broader fintech hiring template rather than Mercura's own documented process. Candidates should confirm which company's funnel they are entering before preparing accordingly.

Building a Strong Application

ClavePrep said candidates should treat the live job posting as the funnel contract: identify must-haves versus nice-to-haves, determine the role family (engineering, ops, GTM, finance, people), read level signals (senior/staff language usually means fewer OAs and deeper ownership panels), and confirm location and work-mode rules. Candidates should then mirror the résumé to the posting's keywords honestly, verify through an ATS checker, and keep it clean.

Beyond the résumé, candidates should prepare two STAR stories ready for behavioral panels, a specific "Why Mercury / why this business unit?" answer that references the actual business unit rather than a generic brand compliment, and a clear stance on logistics (notice period, relocation constraints, and work authorization) that can be defended in HR without surprises. ClavePrep also said using the actual Mercura product before an interview, where eligible, carries weight: "having a genuine opinion on the dashboard's UX carries real weight in the product sense conversation."

Dealbreakers

ClavePrep said surprises around notice period, relocation, or competing offers can slow or kill otherwise-strong loops. The most common funnel mistakes include treating every Mercura req as the same process across campus, lateral, and leadership tracks; skipping the OA or skills gate because a candidate plans to "wing the interview"; surprising HR late with location, notice, or authorization constraints; skipping timed practice before multi-round days; memorizing company trivia instead of rehearsing structured problem-solving; and sending one generic résumé to every Financial technology posting under the Mercura brand.

Red flags that candidates should watch for themselves — as signals about the process's health, not reasons for panic — include unpaid "trial work" that resembles free consulting, pressure to resign before a written offer, or a refusal to state whether the req is still funded. Yellow flags include long silence after a strong round without a stated SLA, last-minute panel changes, and conflicting descriptions of the role level.

A prepared candidate walks into each stage able to answer yes to a simple checklist from ClavePrep: they know which stage is next and what it tests; their résumé matches the req's keywords; they can deliver two STAR stories in roughly 90 seconds each; they have done at least one timed rehearsal for the skills gate; their logistics will not surprise HR; and they have one thoughtful question for the interviewer or recruiter. That last item — the question — is small, but it is the one that separates candidates being processed from candidates being considered.

Three Offices, One Product

Mercura operates a distributed physical footprint spanning three confirmed locations — Munich, Fellbach, and San Francisco — each serving a distinct function in the company's product build-out and market expansion. The company's imprint page lists Munich, Bavaria, Germany as its registered seat, and the LinkedIn company page confirms Munich as the primary location. A LinkedIn post from mid-September reports that Christoph Lauterbach and his team have been working from Mercura's Fellbach branch for roughly the past six months. That configuration tells us the physical infrastructure is not a single headquarters but a deliberately spread operating model with engineering, deployment, and expansion functions distributed across geographies.

The Munich headquarters is where the core product work concentrates. Mercura builds AI software that automates quotes and orders for distributors and manufacturers in the construction supply chain, and the engineering roles on the board — Staff Engineer, Forward Deployed Engineer, (Senior) Fullstack Engineer — are all tagged to Munich. That clustering tracks the technical depth the product demands: the company's own LinkedIn posts describe an AI that automatically matches tender texts against product catalogs and suggests matching articles, a system that must parse messy PDFs, map them to inventory records, and learn from each interaction. The company's imprint page confirms its servers are DIN ISO/IEC 27001 and DIN ISO/IEC 27018 certified, hosted in Europe and GDPR-compliant: infrastructure requirements that almost certainly shape the engineering team's on-site workflow around data handling, security reviews, and compliance documentation that benefits from in-person coordination.

Fellbach, a smaller city roughly 20 kilometers south of Stuttgart, entered the picture around March 2026, when the LinkedIn post dated September 16 reported that Lauterbach and his team had been based in Fellbach for about half a year. The post describes Lauterbach as someone who arrived with skepticism about the AI's ability to handle his team's workflow but now counts it as a fixed part of his daily routine: a practical endorsement that suggests the Fellbach site functions as a deployment and customer-facing hub where the software meets real construction-supply distributors on the ground. The STARK Group, which owns Muffenrohr and operates nearly 1,100 branches worldwide with close to €8 billion in revenue, is named as a customer whose 500 additional German users Mercura plans to bring onto the platform next, and a site like Fellbach, deep in the Stuttgart industrial corridor, positions the team close to exactly the kind of manufacturing and distribution clients whose workflows the product automates.

San Francisco is the newest physical node and, based on the September 9 LinkedIn post, the one carrying the company's international expansion ambitions. That post states that the poster is joining to help drive international expansion and take Mercura into its next stage of growth, and describes flying to San Francisco for a two-week company offsite. Another new hire described kicking off with a company-wide off-site in SF before settling into the role in Munich. Its LinkedIn posts from September 22 confirm it is actively hiring in Sales, Customer Success, and Engineering. If the San Francisco presence is where the expansion strategy is being executed, it likely serves as the bridge to North American distributors and manufacturers, a market that would require Sales and Customer Success staff who can operate in English-language construction supply chains with different procurement norms than the German-speaking European market the company's German sites serve.

The facilities themselves are not described in granular detail in any source I can ground, but the functional picture is clear. The Munich site houses the engineering and product core: the people building the AI that matches tender texts to product catalogs, handling the data pipelines that process construction specifications, and maintaining the ISO-certified European hosting infrastructure. The physical sites likely operate with lean, cross-functional crews rather than large dedicated teams at each location: a working style that demands flexibility from anyone joining the company, since the person sitting in Fellbach may be doing deployment work that overlaps with what the Munich engineers are building, and the San Francisco hire may need to wear both commercial and technical hats as the expansion unfolds.

What all three sites share is a concrete purpose: they exist to get an AI system that automates construction-supply quoting and ordering into the hands of distributors and manufacturers who need it, and to iterate that system based on what the users actually do. The facilities are not open offices arranged around a brand aesthetic; they are operational bases positioned near the customers, the engineering talent, and the markets the company is targeting next. For a candidate evaluating where they would sit, the question is which of those functions aligns with their own strengths, because the physical location shapes the daily work as much as the role title does.

The Mercura Fit

Mercura's own stated philosophy is that "the best ideas emerge when people from different backgrounds collaborate together" and that the company "hire[s] based on ability, mindset, and values, and we live by one simple rule: the best idea wins." That philosophy is the first filter. Candidates who treat hiring as a credential check (degrees, years of experience, name-brand employers) will find Mercura's process frustrated. The company is looking for people who can demonstrate that they value the idea over the ego, and that they can operate across functions rather than inside a silo.

The evidence from people who actually work at Mercura sharpens this picture. LinkedIn describes an engineer named Lars Leinen, who studied at the Karlsruhe Institute of Technology, as someone who "doesn't just build products; some also close deals on day one." That detail matters. It suggests Mercura rewards generalists who can move between building and selling, between the technical and the commercial. The company's roles cover engineering, sales, and customer-facing functions that overlap more than most companies would tolerate (Forward Deployed Engineer and Account Executive sitting alongside Staff Engineer and Fullstack Engineer) and the hiring bar is not just technical depth. It is the ability to operate in ambiguity, to talk to customers, and to ship code that matters in a real deployment context. A candidate who can name a specific instance where they bridged that gap (not just built a feature, but brought it to the people who use it) will read as a stronger fit than someone with a deeper technical resume but no customer-facing evidence.

The working-style evidence is mixed. Glassdoor reviews on Mercura's own profile show employees rating compensation and benefits at -0.1 out of 5: a strikingly low mark. That figure suggests the candidates who thrive are likely those who are intrinsically motivated by the mission and the team rather than by compensation alone. Its LinkedIn posts from September 2026 describe an active, growing team with new hires joining across Sales, Customer Success, and Engineering, and a culture that values urgency and ownership. That is a company in motion: candidates who need a highly structured, process-heavy organization may find the shifting management culture disorienting. Those who can absorb ambiguity and contribute to shaping culture rather than just following it are the ones the company's record selects for.

The "best idea wins" rule has a practical consequence for interview performance. Mercura's recruiters are not just evaluating whether a candidate can solve a technical problem. They are evaluating how the candidate behaves when their idea is challenged. The Y Combinator profile makes the rule explicit: it is not a slogan, it is the operating system. A candidate who defends their solution rigidly, or who defers to the interviewer's authority without contributing, will not read as a strong fit. The candidate who can present a view, concede when the evidence points elsewhere, and still push forward with clarity is the one who will stand out.

There is a tension worth naming. The company says it hires on ability, mindset, and values, but the compensation rating on Glassdoor is effectively zero. That gap suggests Mercura may be attracting candidates who are willing to trade pay for culture and mission, which is exactly the kind of self-selection the company wants. The candidates who thrive are the ones who walk in knowing what they are signing up for: a place where the work is cross-functional, the culture is still being shaped, and the idea always beats the individual.

Mercura is quintupling its team in a year. The people it brings on will decide whether an AI that turns tender PDFs into orders can scale from Munich to the world, and the bar for joining them is not a perfect résumé, but the willingness to let the best idea win.

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