Nemetschek India Career Site API Test Job 1

We're a global software company that helps architects stop drawing walls by hand, engineers stop guessing whether a beam will hold, and construction teams stop finding out about clashes after the concrete is poured. In short: we make the buildings of tomorrow slightly less likely to fall down today.

Our software lives on the desktops of people who wear more black turtlenecks than a design school reunion, and our code quietly powers everything from cozy family homes to skyscrapers that show up on postcards. We take 3D modeling, BIM, rendering, and design collaboration seriously — ourselves, somewhat less so.

We're a family of product teams, each obsessed with a different slice of the building lifecycle, all united by one core belief: if it can be modeled in 3D, it should be, and if it can be automated, someone on our team is already annoyed that it isn't yet.

We're looking for a developer who dreams in classes, interfaces, and the occasional recurring nightmare about null pointer exceptions in a 20-year-old C++ codebase. You'll join a team that builds the invisible scaffolding (pun fully intended) behind millions of architectural decisions worldwide.

What you'll actually do:

• Write code that helps render buildings faster than your GPU fan can spin up in protest.
• Debug geometry kernels until you start seeing vertices and polygons when you close your eyes.
• Collaborate with architects who will ask for "just one small feature" that secretly requires rewriting the entire rendering pipeline.
• Optimize file formats so large that opening them without our software should legally require a permit.
• Attend meetings about interoperability standards, then quietly go build your own anyway.
• Explain to product managers, calmly, for the fifth time, why "just make it real-time" is not a JIRA ticket, it's a PhD thesis.

• A degree in Computer Science, Software Engineering, or convincing evidence you taught yourself pointers out of spite.
• Strong skills in C++, C#, or Python — bonus points if you've ever cursed at a matrix transformation at 2am.
• Experience with 3D geometry, CAD, or graphics programming — or a deep, unresolved obsession with how video games render shadows.
• Familiarity with Git, CI/CD pipelines, and the ancient art of writing a commit message that isn't just "fix stuff."
• A working understanding of data structures, algorithms, and the five stages of grief when your unit tests fail on merge day.
• Bonus: experience with BIM standards, IFC, or file formats so complex they come with their own folklore.
• Most importantly: the patience of an architect explaining to a client why the walls can't just "be a little more curvy" without recalculating the entire structural model.

No hard hats required. Metaphorical ones strongly encouraged.

All your information will be kept confidential according to EEO guidelines.