Writing geometry to PostgreSQL database

Does recalculate extent and / or spatial index make the geometry visible?

It does not, unfortunately.

validate the geometry just before writing . use geometry validator transformer.

Sometimes , some geometries are not rendering, because too many points in one location, self intersecting, phantom elements etc...

I've seen dgn files with extreme Z coordinates which can cause an issue for esri. Try 3D forcing it to 0.

Digging into this a little further -

In this database provided by the client, there was existing data in another feature class that appears in the correct location in ArcPro. Note the coordinates in the screenshot:

Now I read in that same feature class with FME, along with the feature class I've written into with FME. The coordinates being displayed in FME Data Inspector do not match what is in ArcPro:

Zooming out in Data Inspector and hovering over the features I created in FME, the coordinates match as expected (where the existing data is being displayed in ArcPro).

I feel like this is a projection issue, but it's not making much sense to me at this point.

Possibly the data was identified as the wrong coordinate system before you reprojected it? I don't think FME recognises DGN coordinate systems, which could be it too. Use a CoordinateSystemSetter to tell the data what its coordinate system is before reprojecting it. Compare with the existing data like you've done to be sure it comes out in the right place, right coordinate range etc.

So, there was a whole host of issues. There were several geometry validation errors, as well as projection issues. I fixed these with the GeometryValidator, and the EsriReprojector, and all is fairly well now 😁 . Thanks @ctredinnick​ and @f.kemminje​ for the suggestions. They helped a lot.