US IT Technical Recruiter
ConfigUSA is looking for an experienced US IT Technical Recruiter to handle end-to-end staffing processes. The role focuses on managing recruitment for W2, C2C, and 1099 positions. Candidates must have hands-on experience utilizing Beeline and other VMS portals. This is an onsite role based in Hyderabad.
50k new jobs listed every day. Install TAL to find more jobs like this.
Experience
5+ years
Function
Human Resources
Work mode
Onsite, India
Company
Tier 2
What you will work on
ConfigUSA is looking for an experienced US IT Technical Recruiter to handle end-to-end staffing processes. The role focuses on managing recruitment for W2, C2C, and 1099 positions. Candidates must have hands-on experience utilizing Beeline and other VMS portals. This is an onsite role based in Hyderabad.
TAL's take
Defined recruitment role with specific YOE requirements, though company impact is unclear.
Clear expectations and required tool experience provided for a specialized recruiting function.
Must haves
- 5 years of hands-on experience in end-to-end US staffing
- Experience with Beeline
- Experience with VMS portals
- Experience with W2, C2C, and 1099 hiring models
Tools and skills
About the company
unfamiliar company, default mid-tier
Posts mentioning ConfigUSA
Facing issue in R Shiny app for downloading email attachments.
So I am a data analyst and recently I am working on automating the task of downloading email attachments (po, grn etc pdfs). I am using R Shiny for it, where I have created an app like interface. I am using the API for accessing Gmail. I have enabled the API, correctly configured the OAuth consent screen, defined all the scopes in the code, my authentication is also successfully happening by going on the web but still my code is not able to fetch any mail data. I am getting the forbidden:http (403).
Technical suggestion for application packaging domain users
how to upgrade msi having same product code using upgrade table or transform file.i want the solution that works by configuring mst itself it should upgrade the previous version having same upgrade and product code application should uninstall Instead of using seperate script any solutions to solve within transform
Feedback on browserstack jira integration
Hi, I'm curious about the BrowserStack feature that lets you file bugs directly to JIRA after capturing them while testing specifically in Live and app Live products For those who use BrowserStack live / app live but don't use this direct JIRA integration: What's stopping you from using it? Configuration issues? Missing features? Workflow conflicts? What would make you more likely to adopt this feature in your testing process? Do you use a different method to get your BrowserStack findings into JIRA? If so, what's your current workflow? For those who do use the direct integration: What works well about it? What improvements would make it more valuable for your team? I'm interested in understanding the real-world experience with this specific feature to improve the product. Thanks for sharing your insights!