Principal Engineer
Free to start · No card · 5 credits the moment you sign up
Job description
Roles & Responsibilities
- Play as key role with principal engineer team to: design solution architecture and build PrimeData customer data analytic platform in collaboration.
- Design, optimize and execute an efficient development process (tasks allocation strategies, code review policies, etc.)
- Ensure maintainability, reliability, and expendability of all components across multiple teams.
- Investigate and prototype features with new technologies and frameworks.
- Contribute to team-wide fundamentals/infrastructure investments.
Job requirements:
- 8+ years in total experiences.
- Had hands-on experiences being an architect, designing and building large scale production systems, especially data-intensive systems.
- Had experiences using and tuning large-scale distributed databases (SQL or NoSQL, e.g. Postgres, Cassandra, Clickhouse, Redis, Elasticsearch).
- Had strong capability of technology and solution evaluation.
- Solid grasp on good software engineering practices such as code reviews, deep focus on quality and documentation.
- Experience with delivering data-oriented solutions in the recent jobs (Data Platform, DL/DW, BI, ETL, etc), cloud technologies such as GCP, AWS and/or cloud native (K8s).
- Solid knowledge of cyber security and data privacy.
- Great team spirit and solution-oriented attitude.
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for Dikshatek. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.