Aspiring Environment/Procedural Technical Artist — portfolio gap-check for AA/Indie roles

Hi all :waving_hand: — I’m building my career toward Procedural / Environment Technical Art. I’ve been learning Houdini by building my own procedural systems, but I’m not sure whether I’m developing the right skills for becoming employable in production.

I’d really appreciate some direct feedback on the gaps in my current skill set and what you would prioritize next.

Background:
I studied architecture and am transitioning into technical art. I’m particularly drawn to procedural environment / world-building because of the overlap with spatial design, terrain, and site logic.

Current stack:
Houdini + VEX, Unreal Engine / PCG, and Python for automation.

What I’ve built so far:

  • Rock Generator HDA — a procedural system that creates varied rock formations while maintaining artist control.

  • Surface Scatter HDA — a controllable mesh-based scattering system with masks, spacing, density, and variation controls.

  • Curve-Based Road HDA — a procedural road generator that also modifies voxel-based terrain and outputs masks for downstream scattering.

  • Procedural Environment Integration — an integrated system combining terrain generation + erosion, curve-based roads with terrain deformation, rock scattering, mask-driven distribution, and Houdini → Unreal integration.

  • Procedural Forest System — dependency-based vegetation distribution where trees influence bushes, and bushes influence grass, driven by height, slope, humidity, and custom masks.

GitHub: Mina-MDM (Mina D.) · GitHub

Art Station: https://www.artstation.com/mina_mdm

Where I think I might be light:

  • Optimization / LOD / performance considerations at scale in-engine

  • Production-oriented pipeline and collaboration experience

  • Turning procedural systems into tools that fit real production constraints

:red_question_mark: Specific questions:

  1. Does the terrain → road → scatter integration project read as production-relevant, or does it still come across more like a learning / tutorial exercise?

  2. For AA / indie environment-TA hiring specifically, what is the biggest gap you see in what I’ve shown so far — optimization and engine constraints, tool design, art direction, presentation, scale, or something else?

  3. Would you recommend making my next project a polished, playable environment built using these existing systems, or would it be more valuable to build a new standalone procedural system (for example, erosion authoring, biome blending, etc.)?

  4. Is there anything in my current direction that you’d recommend changing before I go much further?

Appreciate any direct feedback. I’m especially interested in hearing from people who have hired or worked with / as environment / procedural TAs in production.:cherry_blossom:

Happy to share HDA breakdowns or node graphs if useful.

1 Like

Hi Mina,

I’m Daniel, a Lead/Senior Procedural Artist and Technical Artist. I took a look at your portfolio, and you’re definitely moving in the right direction as a procedural environment artist.

One thing I’d recommend, if you have the time and freedom to explore, is to work on complete projects rather than random isolated tools. For example, take a strong environment created by an experienced technical environment artist and ask ChatGPT to break it down into the systems, tools, and development order required to build it. This helps you learn how to think in terms of complete procedural systems rather than focusing only on individual assets like rock generators.

A key skill to develop is the ability to analyze an environment and understand how all the systems work together. Building a procedural environment is about creating and connecting systems, not just generating assets.

Another important area is optimization. You’ll be working heavily with instancing, so understanding performance and scalability is essential. A great exercise would be to build a complete environment pipeline for Unity or Unreal, including:

Terrain generation

Layers/splatmaps

Scattering and vegetation systems

Instance management

Optimization and performance testing

Going through a full production workflow like this will help you grow both visually and technically. Repeat the process with different environments, and you’ll continue improving very quickly.

I also noticed one thing regarding your terrain work. Try to avoid perfectly vertical 90-degree terrain walls. In most production environments, those areas are usually represented with rock meshes, cliffs, or other instanced assets rather than the terrain itself.

Here’s an example from one of my projects: https://www.artstation.com/artwork/ayNay2

Also, don’t worry too much if your portfolio isn’t perfect at this time. Mine certainly isn’t, but it has still helped me secure great opportunities throughout my career. Focus on building a strong skills that clearly demonstrates both your artistic and technical skills.

One final piece of advice: if you’re creating tools, try to build something more ambitious and unique. The tools that attract the most attention are often the ones that solve problems in a way nobody has done before.

If you’d ever like feedback on your work, feel free to contact me. My email is on my portfolio.

Best of luck with your journey, and keep going. You’re on the right path.

My e-book is free download here: Introduction to Houdini Zero to Hero - Beginner Editor