Developer

Position : ESRI developerLocation : plano, Texas( 3 days a week)Contract : 6-18 MonthsInterview : VideoMust have: ArcGIS Enterprise, front end experience, Geoevent, and good communication1) Strong, hands-on Esri / ArcGIS expertise (NON‑negotiable)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 quicklyModify and extend them without ramp timeExplicitly stated: they cannot hire someone who needs training or courses 1👉 This is the #1 priority skill2) 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 BuilderDashboardsWeb apps (user-facing tools)Survey123Mapping tools (Map Builder, ArcGIS Pro for modeling/publishing)Reason:Business users rely heavily on dashboards and visual toolsCandidate must quickly modify UI elements, filters, widgets, etc. 1Back-end (important, but supported)Understanding of:Data flows / ETLGeoEvent servicesIntegrations (internal + external data sources)Python + .NET:Working knowledge required, not deep masteryInternal dev team already supports this area 1👉 Key insight:They want someone who can talk to developers effectively, even if not a hardcore engineer.3) Ability to jump into existing architectureThis is not a greenfield role.The candidate must:Review what exists (apps, surveys, geo-events, dashboards)Understand it quicklyExtend it immediatelyDiagnose issues and know where to look inside the systemExample responsibilities mentioned:Modify geofencing rulesUpdate dashboard filters/logicAdjust data flowsUnderstand multi-server architecture👉 “Hit the ground running” was explicitly emphasized 14) Experience with GeoEvent + data-heavy environmentsThis is a key differentiator skill:Handling multiple data inputs (internal + external)Working with:GeoEvent serverReal-time data streamsUnderstanding how data feeds into dashboards👉 This is not just GIS—it’s operational, data-driven GIS5) Ability to bridge business + technical teamsCandidate must:Work with non-technical business usersTranslate requirements into system changesExplain what’s happening without deep technical jargonReason:Business users only interact with dashboardsThey don’t understand backend systems 16) Seniority levelEnough experience to:Work independentlyLead pieces of work7) 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 1⚠️ What will NOT workCandidates will likely be rejected if they are:Too back-end focused (heavy API / infrastructure, no UI work)Experienced in non-Esri GIS tools onlyMissing dashboard / Experience Builder exposure