Fidessa, FIX connectivity, JIRA, Splunk, SQL, Linux/Unix shell , Control-M. Fintech Industry, Application Support Analyst
Could you introduce yourself and tell us about you? Your current / recent jobs and employers? Previous companies and jobs? He has been in the Fintech industry for 8 years. He completed his degree inComputer Science from University of XXXX. He started in a technical support role at a financial software company, then moved to an electronic trading solutions provider as a production support analyst, then to the equities technology team of a global investment bank, and is now a Application Support Analyst at a regional brokerage and trading technology firm. In his current role he is the escalation point for production incidents that affect order entry, order routing and trade execution, and he works day to day with traders, sales-traders, dealing desks, operations, developers, network and infrastructure teams, vendor support and compliance. On a daily basis, he starts before the market open with system health checks and readiness confirmation, then spends the trading session monitoring alerts and handling desk queries, and the rest of the day on incident follow-up, change coordination, testing with clients and venues, and documentation. In the evenings or on weekends he joins releases and upgrades when they are scheduled. He spends a good part of the week on onboarding work for new clients and new market connections, and on service review meetings with business users and vendors. What skill(s) / experience would you self-describe as strongest or specialist in? Strongest skill would be live production support for equity trading platforms, especially Fidessa. He has supported it through version upgrades, configuration changes, user and entitlement set-up, routing rule changes, market data issues and end-of-day processing. When something goes wrong during the session, he follows a fixed approach: check the health of the application and gateways, trace the order through its lifecycle, find the failing component, work with the right team on a fix or workaround, and keep the desk updated until service is restored. Another strength is FIX connectivity. He reads raw FIX logs to understand why an order was rejected, delayed or left unacknowledged, and he can tell whether the problem is on the client side, inside the broker’s platform or at the exchange or venue side. He has handled logon failures, sequence number gaps, resend requests, heartbeat timeouts and cancel/replace problems, and he has run certification and regression testing for new client links and for venue-side changes. He is also disciplined about process. He uses JIRA to manage incidents, problems and changes, prepares post-incident reviews with root cause and preventive actions, and writes runbooks and knowledge articles so that repeat issues are solved faster by the wider team. He has helped reduce repeat incidents by setting up ticket categories, escalation workflows and dashboards. He is also, hands-on with Splunk, SQL, Linux/Unix shell and Control-M.
