Your mission You own a defined formal deliverable end‑to‑end (days to a few weeks). You work independently in known contexts, drive proof closure, and hand over sign‑off artifacts that customers trust. Own a block/area: clarify requirements, co-define the verification strategy (scope, risks, approach), execute, and close. Produce maintainable SVA and a clean formal environment (constraints/assumptions with good hygiene). Debug efficiently, partner with designers on fixes, and prevent regressions. Keep stakeholders aligned with crisp updates and decision-ready evidence. Your profile Proven experience delivering formal results on non‑trivial RTL (e.g., caches, pipelined processors, DMAs, NoCs). Strong SVA skills and hands-on formal tool experience (e.g.: Jasper, VCF, Questa Formal/Onespin). Reliable end‑to‑end ownership in a defined scope. What success looks like in your first ~90 days You nail our onboarding bootcamp and earn the team’s trust: you apply the LUBIS way of working and consistently ship clean, reviewable outputs. You engage confidently in scoping and planning with the team: you clarify open questions early, surface risks, and help translate scope into a concrete plan. You own a deliverable end‑to‑end in a defined area and ship it without a “rescuer”. Where this leads The natural next step is our Senior Formal Verification Engineer role — leading customer engagements, owning formal architecture decisions, mentoring Associates and Professionals, and shaping how LUBIS approaches new verification problems. We make that path concrete: review cycles, customer-lead rotations, and clear competency milestones. About us LUBIS is a fast-growing German startup redefining how the semiconductor industry works. We tackle one of its hardest challenges — ensuring complex chips work flawlessly before they’re built. Our mission is simple: to transform verification from a craft into a system. By structuring how teams work and automation we make chip design faster, reliable, and bug-free. LUBIS isn’t just improving the process — we’re defining how verification is done.