Description:
Must have: ArcGIS Enterprise, front end experience, Geoevent, and good communication
Deep experience specifically with ArcGIS Enterprise (not just general GIS tools)
Comfortable working in the current environment (10.9.1, moving to 11.3)
Ability to:
Understand existing implementations quickly
Modify and extend them without ramp time
Explicitly stated: they cannot hire someone who needs training or courses
#1 priority skill They need ArcGIS Enterprise, front end experience, GeoEvent, and good communication skills.
2) Balanced Front-end + Back-end (≈50/50 split) The role is not purely technical or purely UI—they want a blend.
Front-end (VERY important) Candidates must be comfortable with:
ArcGIS Experience Builder
Web apps (user-facing tools)
Survey123
Mapping tools (Map Builder, ArcGIS Pro for modeling/publishing)
Business users rely heavily on dashboards and visual tools.
Back-end (important, but supported)
Understanding of:
Data flows / ETL
GeoEvent services
Integrations (internal + external data sources)
Python + .NET:
Working knowledge required , not deep mastery
Internal dev team already supports this area
They want someone who can talk to developers effectively , even if not a hardcore engineer.
3) Ability to jump into existing architecture This is not a greenfield role.
The candidate must:
Review what exists (apps, surveys, geo-events, dashboards)
Understand it quickly
Extend it immediately
Diagnose issues and know where to look inside the system
Modify geofencing rules
Adjust data flows
Understand multi-server architecture
“Hit the ground running” was explicitly emphasized.
4) Experience with GeoEvent + data-heavy environments This is a key differentiator skill :
Handling multiple data inputs (internal + external)
Working with:
GeoEvent server
It’s not just GIS—it’s operational, data-driven GIS .
5) Ability to bridge business + technical teams
Work with non-technical business users
Translate requirements into system changes
Explain what’s happening without deep technical jargon
Business users only interact with dashboards.
They don’t understand backend systems.
6) Seniority level
Enough experience to:
Work independently
Lead pieces of work
7) Bonus / “Unicorn” traits (nice-to-have) They joked about wanting a “unicorn,” which translates to:
Strong in BOTH:
ArcGIS platform (core)
Development (Python/.NET)
Able to act as a “tip of the spear” technically with the team
What will NOT work Candidates will likely be rejected if they are:
Too back-end focused (heavy API / infrastructure, no UI work)
Experienced in non-Esri GIS tools only
#J-18808-Ljbffr