Technical Solutions Engineer II
Konami Gaming, Inc. · Las Vegas, NV · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Must include only sections with real content. No job title heading. No Job ID etc. Remove boilerplate: EEO, accommodation, etc. Also remove application instructions (none). Keep substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The first paragraph: "Konami Gaming is looking for a Technical Solutions Engineer II to join our team! A Technical Solutions Engineer II is responsible for items that go beyond Customer Service support that require more technical skills. The position requires expertise in the Java programming language. The position must also show strong skills and knowledge of the SQL database language and know how to apply that towards the SYNKROS database. The Technical Solutions Engineer II must not only be able to work with external customers but must be able to work with internal customers also from Sales, Compliance, Project Management, R&D and SQA. They must work with R&D, customer service, and senior managers to maintain and troubleshoot existing customer code base keeping to current system and industry requirements. This position also requires flexibility to always act autonomously while adhering to overall department and company policies and procedures."
That's about the role.
- Responsibilities: The "What you'll be doing:" section includes bullet-like sentences. We'll need to format as
- . The content:
* Level II Customer Service Support: Effectively resolve all associated issues in a timely manner, keeping with regulatory SLAs when applicable.
* Maintain professionalism with customers and vendors to meet their demands.
* Troubleshoots and diagnoses escalated customer issues and resolve in efficient and timely manner in the areas of the SYNKROS application, interfaces, or database.
* Contacts customers and/or vendors, as necessary, to aid in SYNKROS related issues.
* Reports any discrepancies, changes or recommendations, and/or problems for resolution to senior management.
* Receive escalations from level I & level II support.
* Be available after-hours for critical/dire situations needing assistance from any internal customer.
* SYNKROS Maintenance: Effectively and efficiently identify bugs across SYNKROS and report these to R&D along with recommended fixes.
* Ensure fixes meet customer expectations and report timeline of fix to Customer Service.
* Efficiently perform SYNKROS upgrades meeting timelines and a 100% success rate that the correct approve code is pushed.
* Maintain contact and communication with R&D to keep visibility on all new functionality from each development cycle.
* Reports and recommends bug-related fixes to R&D and follows the process to track the fix back to customer service.
* Performs SYNKROS version upgrades.
* Special Projects: Successful project completion.
* Work with all associated groups to maintain and develop new tools to be used within Customer Service to aid in quick and efficient resolutions.
* Performs other related duties as assigned.
We can group maybe but just list each as li.
- Qualifications: The "What we'll want you to have:" list includes many items. We'll need to output as ul li.
List items:
* Intermediate and above-level understanding and usage of Microsoft Office products.
* Intermediate knowledge and understanding of the following technologies will be highly regarded and some may be required depending on the position requirements:
- Java programming expertise (OO, JVM, reflection, I/O, data structures).
- Socket programming.
- Thread programming.
- TCP/IP stack knowledge.
- Advance SQL query procedure building.
- JDBC, Oracle, or other RDBMS, SQLPlus.
- Advance knowledge of XML and HTML 5.
- Linux basics.
- Performance and monitoring knowledge.
- Design pattern experience.
- API design.
- ORM experience.
- SOA knowledge.
- Understanding of automation and deployment.
- Ability to obtain licensing, gaming card, or other certifications required by gaming regulations or jurisdictions.
- Ability to read and interpret documents such as safety rules, operating and maintenance instructions, and procedure manuals.
- Ability to write routine reports and correspondence.
- Ability to speak effectively before groups of customers or employees of organization.
- Ability to work with mathematical concepts such as probability and statistical inference, and fundamentals of plane and solid geometry and trigonometry.
- Ability to apply concepts such as fractions, percentages, ratios, and proportions to practical situations.
- Ability to define problems, collect data, establish facts, and draw valid conclusions.
- Ability to interpret an extensive variety of technical instructions in mathematical or diagram form and deal with several abstract and concrete variables.
- Strong oral and written communication skills.
- A high degree of analytical thinking and problem-solving.
- Excellent organizational skills and an extremely high level of accuracy and attention to detail.
We could keep the bullet list as separate li items; but the nested list for technologies may be flattened.
- Skills: Might be overlapping with qualifications; but we can treat the technical skills as a separate Skills section if we want. However the instruction: Prefer a few substantive sections over many thin ones. We could combine Qualifications and Skills into one? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have About the role (yes). Responsibilities (yes). Qualifications (yes). Skills maybe we can extract from qualifications but we could also put technical skills under Skills. However we already have Qualifications containing many items; we could split: Qualifications: education/experience? But not given. Could treat Qualifications as the list of abilities (soft skills) and Skills as the technical list. Let's see.
The posting includes: "Intermediate and above-level understanding and usage of Microsoft Office products." then "Intermediate knowledge and understanding of the following technologies will be highly regarded and some may be required depending on the position requirements:" then list of technical skills. Then later: "Ability to obtain licensing..." etc. Then many ability statements.
Thus we could have:
- Qualifications: list of ability statements (soft skills, licensing, etc.)
- Skills: list of technical skills (Java, SQL, etc.)
But we need to avoid duplication. Let's extract.
Technical skills list:
* Java programming expertise (OO, JVM, reflection, I/O, data structures).
* Socket programming.
* Thread programming.
* TCP/IP stack knowledge.
* Advance SQL query procedure building.
* JDBC, Oracle, or other RDBMS, SQLPlus.
* Advance knowledge of XML and HTML 5.
* Linux basics.
* Performance and monitoring knowledge.
* Design pattern experience.
* API design.
* ORM experience.
* SOA knowledge.
* Understanding of automation and deployment.
Also "Intermediate and above-level understanding and usage of Microsoft Office products." could be a skill.
Now Qualifications (soft skills):
* Ability to obtain licensing, gaming card, or other certifications required by gaming regulations or jurisdictions.
* Ability to read and interpret documents such as safety rules, operating and maintenance instructions, and procedure manuals.
* Ability to write routine reports and correspondence.
* Ability to speak effectively before groups of customers or employees of organization.
* Ability to work with mathematical concepts such as probability and statistical inference, and fundamentals of plane and solid geometry and trigonometry.
* Ability to apply concepts such as fractions, percentages, ratios, and proportions to practical situations.
* Ability to define problems, collect data, establish facts, and draw valid conclusions.
* Ability to interpret an extensive variety of technical instructions in mathematical or diagram form and deal with several abstract and concrete variables.
* Strong oral and written communication skills.
* A high degree of analytical thinking and problem-solving.
* Excellent organizational skills and an extremely high level of accuracy and attention to detail.
Also maybe "Intermediate knowledge and understanding of the following technologies will be highly regarded and some may be required depending on the position requirements:" is a preamble; we could keep as part of Skills section intro.
Now Benefits: The posting includes: "Konami Offers Competitive Wages Great 401(k) plan with company match Comprehensive health benefits package Generous Company paid Holidays and Paid Time Off (PTO) Tuition reimbursement program". That's benefits.
Pay: Not explicitly stated besides "Competitive Wages". That's vague but could be considered Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Competitive Wages" which is a pay indication, albeit not specific. Should we include Pay? It says "Competitive Wages". That is a statement about pay. So we could include Pay section with that sentence. However the instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive Wages" is not exactly filler; it's a real statement albeit vague. I'd include Pay.
Schedule: The posting includes "Work Environment: Full-time / 40+ hours per week. Must be flexible to work overtime, including nights, weekends, and holidays as required." That's schedule info. So we can include Schedule section.
Now we need to avoid boilerplate: Remove EEO, accommodation request, etc. Also remove "About Konami Gaming, Inc."? That's company description; could be part of About the role? Might be considered extra but it's substantive about company. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About Konami Gaming, Inc. paragraph. Where to place? Could be part of About the role or maybe a separate section like "About the company". But we only have allowed headings list; we could put it under About the role as additional paragraph.
Thus About the role section will have two paragraphs: first about role responsibilities, second about company description.
Now we need to output HTML fragment only, no /. Use
for headings. Use
- for lists. Use
for prose. We must not repeat job title as heading. So no h3 for "Technical Solutions Engineer II". Good. We must not put Job ID/requisition numbers as headings; none present. Now construct:
About the role
Konami Gaming is looking for a Technical Solutions Engineer II to join our team! A Technical Solutions Engineer II is responsible for items that go beyond Customer Service support that require more technical skills. The position requires expertise in the Java programming language. The position must also show strong skills and knowledge of the SQL database language and know how to apply that towards the SYNKROS database. The Technical Solutions Engineer II must not only be able to work with external customers but must be able to work with internal customers also from Sales, Compliance, Project Management, R&D and SQA. They must work with R&D, customer service, and senior managers to maintain and troubleshoot existing customer code base keeping to current system and industry requirements. This position also requires flexibility to always act autonomously while adhering to overall department and company policies and procedures.
About Konami Gaming, Inc.: For Players. For Operators. For Each Other. Konami Gaming, Inc. entered the US gaming market in the 2000s and we have spent the last two decades moving the industry forward with breakthrough games, head turning cabinets, and a casino management system that brings it all together. Over that time, we have garnered our share of awards and established a corporate culture of success and innovation. A world leader in systems and game development, Konami can offer you the best of both worlds - stability within a dynamic, creative environment. We are excited to announce that Konami Gaming Inc. is growing and expanding into new product lines, including premium and standard games, and new market segments. As we enter a new growth period for the Company, we are expanding our reach to attract top talent in game studio operations, technology and product development.
Responsibilities
- Level II Customer Service Support: Effectively resolve all associated issues in a timely manner, keeping with regulatory SL
- for lists. Use